I have a Win7/64 development machine configured (by someone else I can't contact) to develop/debug an embedded project using an ST-LINK/V2 dongle. The PC detects and installs the dongle Ok but no application can access the dongle, giving 'No ST-Link device detected' type errors.
What makes this so frustrating is I have another Win7/64 machine that works flawlessly using identical driver, software and dongle and I haven't been able to transfer the dev environment between machines.
I've found (using USBlyzer) that WinUSB returns IRP Status STATUS_ACCESS_DENIED to each dongle access request. I'm hoping someone has seen something like this before.
P.S. "STMicroelectronics STLink dongle driver" is dated 28/07/2010.
The difference is not with the development software but the USB driver installed in the OS for the class of the ST-LINK/V2 dongle. The original installation installs a custom driver to support the dongle. Note that there is a different USB driver for Windows 8 and for Windows 7. STM has a site for the appropriate custom Windows drivers as well as firmware updates for the processor in the dongle, itself.
Related
I am developing a Win10 C# application dependent on a third party library, which enables me to control a USB3 device.
By trial and error, I found that I needed to run FTD3XXDriver_WHQLCertified_v1.3.0.4_Installer.exe, which in the end populated the SysWOW64 with FTD3XX.dll and System32\Drivers with FTDIBUS3.sys and the ancillary files and folder.
I would like to run my application from a USB thumb drive on different PC's in my organization without installing any of the drivers. Is there a way to do that?
Bad news: To the best of my knowledge you cannot address an FTDI device if the driver is not installed.
But windows normally install the driver automatically via the windows updater. At least, this is the case for the USB 2 devices of FTDI i.e. 232 family. I do not have a FT60X here to test if the windows updater has a driver ready for this as well.
If the driver is installed via the updater you have to bundle the FTD3XX.DLL with your application as it is not part of the "windows standard" driver. At least this was the case for the FTD2XX.DLL.
Long story short: connect your device to a computer without preinstalled driver. Check if the driver is installed via the windows updater. If this is the case, you mostlikely just need to bundle the FTD3XX.DLL with you application.
I'm trying to install some unsigned legacy drivers to my computer from command line. I have used dpinst.exe and installhinfsection functions which work fine, however everything I've tried is software first, meaning it installs the driver onto your computer and then doesn't actually show up in the device manager until you plug the device into your computer.
I'm wanting to install the driver and have it show up in the device manager without having to plug in any devices.
I can do this with adding legacy hardware from the device manager, but I want this to be an automated process so all from command line and not having to do it manually through device manager.
thanks in advance
EDIT
The drivers were written by me (UserModeDriverFramework), they are emulating real devices.
Hi I have been trying to connect a few boards to my computer. These boards depend on RNDIS driver to get into concole. So if I connect a board for the first time my Win7 Laptop properly detects it as a RNDIS ethernet adapter or device. But when I plug in the boards second time it just comes up as a unknown device in USB section of device manager. From searching the web I assume that something is RNDIS to fail. So I try to install the driver manually using http://www.sharpduino.com/en/articles/article/19 where it suggest to manually install a driver under Network Adapters > Microsoft Corporation > RNDIS. But here is the problem the entire Microsoft corporation folder in the driver setup is missing. I am getting no help on the web on why this is so.
And this problem is not just on one board but on others as well. Boards used so far Intel Edison, Arietta G25.
I'm manufacturing a device that connects to my computer using Bluetooth and then a desktop Java app uses the Bluetooth connection to send serial data to the device which is then displayed.
When I try to connect my device to windows 7 it successfully finds and pairs with it creating a Bluetooth link on a COM port. This link can then be used by a serial prompt (used for testing) or my Java application. It works initially however soon after windows drops the connection and the only way to reconnect is to delete the device within devices and printers and then reconnect.
This seems to be a known problem with windows bluetooth so I decieded to use a third party Bluetooth application. I downloaded and tried Toshiba's Bluetooth Stack and it was able to add a Bluetooth device and keep a stable connection which works great however this only works for Toshiba computers without getting a cracked version.
This device is commercial and can't be sold with cracked versions of software. Has anybody experienced the same problems or not in other operating systems and has any solutions of advice as that would be a tremendous help.
This is not a good idea/method to use the COM ports generated by Windows, it's not working fine and not reliable in any scenario ; you should use Bluetooth Sockets instead.
Using Toshiba or Widcomm or BleuSoleil won't help: under Win7, all dongles are now trying to use the Microsoft Stack, not their own implementation.
I've been asked to help with some problems that a company are having with an Windows installer they have that includes some custom driver installation for some hardware they make.
I've got access to the source code to build the software and installer (which is an WIX/MSI one), but don't have access to the hardware, so can't actually test it properly.
Is it possible (either with a toolkit, or without) to trick windows into thinking that a specific device USB device has been attached to the computer in order to trigger Windows into trying to install the drivers? . I've got access to all the Vendoer Id, DeviceID, etc information.
Thanks
Tom
That should be possible. Take a look at WDK USBSamp and NDIS Virtual miniport (or virtual serial driver) samples. The first one is a USB driver sample and second one demonstrates how to build virtual driver. You should be able to combine the two to create a virtual USB driver.