![]() %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 # */Īfter Saving this file (and of course re-booting into unsigned installation mode) I was able to %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 %ManufacturerName% = Standard,NTx86,NTamd64 * #START of Section # */ = Manufacturer/Models sections = ![]() So I added the following Text as indicated by comments:. ![]() One of which will be 'stlink_dbg_winusb.inf'Ĭontained 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. It will where you unzipped the driver install files such as. Now using explorer find your Downloaded Driver From STM Make a careful note of the first listed string (Mine was USB\VID_0483&PID_374B&REV_0100) Select from the drop down 'Property' Box - 'Hardware Ids' Note the Device description is probably correct, however. In the Device Manager with the problem device listed i.e. You have to do some 'fancy footwork' ok this is what I did to resolve the issue. While the latest posted MBED firmware is version V2.J23.M 6 The boards are shipped with firmware version V2.J23.M 9 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 :) Nucleo Firmware utility (which started this exercise). Updated - now with the correct Windows 8 drivers installed, we can run the Now the 2 functions related to this Nucleo boards have installed correctly. This download package indeed has the support of PID_374B. The (confirmed) working solution is to install the latest ST-LinkSW009 package from here: the Microsoft signature will break and will not allow for the 64 bit OS to install the now tainted driver package). That is, any modification to a signed INF file will invalidate the supporting CAT signature file (ie. Brick wall.Īfter 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. the INF file does not support the PID_374B but rather the older PID_3748 - note the 8). Using Windows 8 so landed on the wrong ST webpage for the (older) drivers (ie. However, before you can do this, the proper device drivers must be installed with the reported IDs (thanks Martin !). Just received our new Nucleo-F070RB boards (Mouser) and attempted to confirm / upgrade the latest ST-Link firmware on Windows 8 (64 bit). ![]() I am certain that the links specified on the card are configured correctly.Hi. LD1 on the probe does, however, flash 3 or 4 times when it is plugged into the USB port. I have searched the internet and this forum and I am completely out of ideas to try next.Īccording to the Getting Started card in the box an LED should flash, and when a button is pressed it changes. Its as if the development board is not compatible with the driver or the driver has a problem. I have tried the same on a Windows XP and Windows 7 PC and all report similar errors. In Device Manager, under the Universal Serial Bus controllers section I have an entry which shows as 'Unknown USB Device (Device Descriptor Request Failed), which is presumably the STLINK/V2 probe in the development board. The installation appears to succeed, however, when I plug in the development board via USB Windows complains with 'USB device not recognised'. I am using a Windows 10 64-bit laptop with USB 3 ports and have installed the STLINK utility, en_stsw-link004.zip, which includes the relevent USB drivers. I have recently purchased a number of NUCLEO-L476 boards but cannot get the USB drivers to install correctly whch are required for both ther STLINK utility and also for System Workbench for STM32.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |