Atollic

1. Check your requirements

If you are using the ST-Link V1-probe you need:

- Admin rights in Windows.
- One available disk drive letter (check if it appears on ST-Link connection)

2. If you have connected the USB before installing the driver

If your hardware is a ST-Link V2 or evaluation board embedding it, and you have plugged in the USB before installing the ST-LINK_V2_USBdriver, you should do an "update driver" from the control panel, because in that case the device is referenced as "unknown" by the system (yellow exclamation mark on XP).

3. Check your installation

If you are using Windows XP, the ST-LINK_V2_USBdriver needs to be installed to get the winusb.dll file installed into system32. To check and correct the installation, please follow this guide:

1. Look into C:\windows\system32 for the file winUSB.dll. For a 64.bit-system the directory is c:\windows\sysWow6.

2. Make sure that C:\Windows\inf\stlink_winusb.inf is present

If one of the files isn’t there, the installation has failed.
In that case - click and run the existing C:\Program Files\Atollic\TrueSTUDIO STM32 Pro 2.1.0\Servers\ST-LINK_gdbserver\ST-Link_V2_USBdriver.exe
Make sure the missing file is in place now.

4. addressing the STLink-probe

If you are using the ST-Link V1 probe you need to Check how STLinkUSBDriver.dll 4.2.2.0 is addressing the ST-Link probe.

STLinkUSBDriver.dll 4.2.2.0 uses direct access to disk interface, which may conflict with some other applications such as Daemon Tools and Alcohol 120%. Some people using Alcohol 120% has reported that it does not work with the ST-link probe at all.

People using Daemon Tools have to make sure that no virtual disk has the same disk drive letter as ST-Link probe. This is done by re-assigning a different drive letter to one of them. Assuming one is using Windows 7, this would be done by navigating to:

Control Panel > System and Security > Administrative Tools > Computer Management > Storage > Disk Management. Find the virtual device that is interfering with the ST-Link probe and right-click on it. Choose Change Drive Letter and Paths, and then change the drive letter to one that is available.

5. Check your cabling

Some customer also have had a problem with a bad USB cable that not always worked due to a bad connection. Try to replace the USB cable.