9 years, 11 months ago.

Hi,

Had same problem with XP. I've downloaded USB driver from ST and it is working fine now.

http://www.st.com/web/en/catalog/tools/FM116/SC959/SS1532/LN1847/PF260320

Upgraded Nucleo firmware as well. You'll get warning that driver is not installed, just cliclk "instal automatically" and all is well.

James.

10 years, 6 months ago.

Same problem here, but under Windows XP, both native and as a virtual machine. Tried installing as Admin, from command line etc. but no luck. The firmware updates tells me something about winusb.dll missing, (which it is, according to this guide: http://www.atollic.com/index.php/kb/3-debugging/28-kb_st_link_connection_error)

If I try to reinstall the driver through device manager, it says "parameter incorrect". This is unbelievable. When I saw the board on Farnell I was like: ooeh nice. When I tried it out, no firmware would run whatsoever (mbed). So I take it I have to upgrade firmware, but this is nearly impossible. Being a Mac guy, I'm used to not getting native utilities, but this crap has cost me hours already. It's been some time since I threw away hardware, but this might be the exception.

Anyone from ST care to join the discussion?

10 years, 6 months ago.

hei i have experience about this, i only download stm32 utility and the program will guide you with driver stlink too.. lets download stm32 utility , and don't forget update it

8 years, 2 months ago.

Hi,

I have STM32F746 board and try to communicate with PC through a USB Virtual Serial Port. but I can't install STLINK v2 usb driver(stsw-link009) under Windows XP/32bit. Both status of the error is Install failed(Unsigned).

Thank you

Takuro

10 years, 8 months ago.

Did you install both the new firmware on the board as well as the stlink USB drivers on the PC.

9 years, 10 months ago.

Hi. Just received our new Nucleo-F070RB boards (Mouser) and attempted to confirm / upgrade the latest ST-Link firmware on Windows 8 (64 bit). However, before you can do this, the proper device drivers must be installed with the reported IDs (thanks Martin !). Using Windows 8 so landed on the wrong ST webpage for the (older) drivers (ie. the INF file does not support the PID_374B but rather the older PID_3748 - note the 8). Brick wall...

After an hour of this fun during which found this web posting (thanks all !!) - the above method will not be able to support 64 bit operating systems. That is, any modification to a signed INF file will invalidate the supporting CAT signature file (ie. the Microsoft signature will break and will not allow for the 64 bit OS to install the now tainted driver package).

The (confirmed) working solution is to install the latest ST-LinkSW009 package from here:

http://www.st.com/web/catalog/tools/FM147/SC1887/PF260219?s_searchtype=partnumber

This download package indeed has the support of PID_374B. Now the 2 functions related to this Nucleo boards have installed correctly.

Hope this someone some time :)

Thanks MBED for a great product !

Mon2

Updated - now with the correct Windows 8 drivers installed, we can run the

Nucleo Firmware utility (which started this exercise).

The utility runs fine but it appears that the Nucleo-F070RB boards are shipped with a more current firmware so best to leave it alone :)

The boards are shipped with firmware version V2.J23.M9

while the latest posted MBED firmware is version V2.J23.M6

10 years ago.

Hi All,

You have to do some 'fancy footwork' ok this is what I did to resolve the issue.

In the Device Manager with the problem device listed i.e. yellow stamped. Right click and select properties Select the Details 'leaf' Note the Device description is probably correct, however.... Select from the drop down 'Property' Box - 'Hardware Ids' Make a careful note of the first listed string (Mine was USB\VID_0483&PID_374B&REV_0100)

Now using explorer find your Downloaded Driver From STM It will where you unzipped the driver install files such as ..\stsw-link008 There you should find TWO *.inf files. One of which will be 'stlink_dbg_winusb.inf' Contained in that file are a list of Manufacturer Hardware ID stamps to tell the Device Installer to Match the Hardware to the driver it wishes to install. (Mine as above was not listed!)

So I added the following Text as indicated by comments:-

/* #####START of Section ##### */

========== Manufacturer/Models sections ===========

[Manufacturer] %ManufacturerName% = Standard,NTx86,NTamd64

[Standard.NTx86] %DeviceName% =USB_Install, USB\VID_0483&PID_3748 %DeviceName% =USB_Install, USB\VID_0483&PID_374A&MI_00 %DeviceName% =USB_Install, USB\VID_0483&PID_374B&MI_00 %DeviceNameRW% =USB_InstallRW, USB\VID_0483&PID_374A&MI_01

Added the following line to match my Hardware ID for the STM32 Nucleo Board

That failed to install on plugging into the USB i)

%DeviceName% =USB_Install, USB\VID_0483&PID_374B&REV_0100

'NB could use %DeviceName% =USB_Install, USB\VID_0483&PID_374B to be more generic'

End of Mod M.Simpson

[Standard.NTamd64] %DeviceName% =USB_Install, USB\VID_0483&PID_3748 %DeviceName% =USB_Install, USB\VID_0483&PID_374A&MI_00 %DeviceName% =USB_Install, USB\VID_0483&PID_374B&MI_00 %DeviceNameRW% =USB_InstallRW, USB\VID_0483&PID_374A&MI_01

See Note i) above (this was added here for alternate systems)

%DeviceName% =USB_Install, USB\VID_0483&PID_374B&REV_0100

End of Mod M.Simpson

/* #### End of Section ####### */

After Saving this file (and of course re-booting into unsigned installation mode) I was able to Perform 'UPDATE DRIVER' which could now be found and the nucleo board now works.

Hope this Helps others

Best wishes

Martin

NB Corrected some spelling typos and added generic HardwareID Note

8 years, 7 months ago.

Attended an ST-Micro workshop recently and picked up the STM32F746 board. ST-Link/V2 came up properly on the laptop... but would NOT on the work computer. Went round-and-round for DAYS until spotting Martin's fix for the INF file.

"B" vs "8". It HAS to be a typo. A time-expensive typo but a typo nonetheless.

Install fails via the automatic installer; that one-line fix breaks driver signing. Installing it via Device Manager and overriding the complaint of an unsigned driver does the trick.

Martin, THANK YOU!