- This topic has 6 replies, 2 voices, and was last updated 8 years ago by
.
-
Posts
-
Hello,
I aware that my problem is out of scope of your book but You can certainly help me. Currently I meet a problem when I plug a nucleo board ( I own one NUCLEO-L476RG, two NUCLEO-L073RZ and one STM32F429-DISCOVERY) the ST-LINK is no detected by STM32 ST-LINK utility or by ST-LINK/V2, ST-LINK/V2-1 firmware upgrade. This behavoir is particulary strange because in my device manager the STLink
Virtual COM Port is well recognize under Ports entry and instead STLink dongle under USB devices I have STLINK debug under USB devices. When I plug it I can also read NODE-L073RZ or NODE-L476RG in my windows tree or under my icons notification.For your information when I plug my discovery board the ST-link is well detected under STM32-LINK.
So I reinstalled ST-LINK, ST-LINK/V2, ST-LINK/V2-1 USB driver signed for Windows7, Windows8, Windows10 (STSW-LINK009) and I also reinstalled STSW-LINK004 (rev 4.0), but I have the same problem.ON the side of hardware I ‘m sure that two jumper are installed on CN2 and that my USB wire works because I can Flash my disco-board.
To finish last week I loaded an example from github’s for my NUCLEO-L073RZ (I tried CHAP4_Ex1)
and I can load it. I’m sure that I did it with ST-LINK utilisy as OPENOCD doesn’t work with L0 series.Have you an idea where is located my problem ?
Thank you for you answer!
This is an issue related to device drivers. It seems that it’s really common in Windows, because several people encounter this problem.
Another reader of my book fixed it with this procedure:
– Deinstall all ST link drivers, both related to VCP and ST-LINK dongle
– Deinstall ST-LINK Utility if already installed
– Reboot Windows
– Download the latest ST-LINK Utility (4.x) and install it.
– Launch ST-LINK Utility and connect your Nucleo to the PC.The ST-LINK Utility should fix the issue. Otherwise, try what described in my book at page 150.
Thank you for the answer, however nothing solve my problem. I think that my problem is located in device manager more precisely with my usb driver. I found on the net this topic about the same problem:
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 USBVID_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, USBVID_0483&PID_3748 %DeviceName% =USB_Install, USBVID_0483&PID_374A&MI_00 %DeviceName% =USB_Install, USBVID_0483&PID_374B&MI_00 %DeviceNameRW% =USB_InstallRW, USBVID_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, USBVID_0483&PID_374B&REV_0100
‘NB could use %DeviceName% =USB_Install, USBVID_0483&PID_374B to be more generic’
End of Mod M.Simpson
[Standard.NTamd64] %DeviceName% =USB_Install, USBVID_0483&PID_3748 %DeviceName% =USB_Install, USBVID_0483&PID_374A&MI_00 %DeviceName% =USB_Install, USBVID_0483&PID_374B&MI_00 %DeviceNameRW% =USB_InstallRW, USBVID_0483&PID_374A&MI_01See Note i) above (this was added here for alternate systems)
%DeviceName% =USB_Install, USBVID_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
Effectively I meet the same issue about ‘Hardware Ids’ however I can’t reinstall the right driver I followed his instructions but I haven’t understood ==> “I was able to Perform ‘UPDATE DRIVER’ which could now be found and the nucleo board now works.”
I don’t know if the driver must be installed before the modification because when I add the ‘hardware Ids’ in the .inf I have a pb during installation of “dpinst_amd64.exe” and when I want update my driver in device manager I have a huge list of the same driver, I try it all but it’s always wrong no ST-link detected…
I am really disappointed…
Nb: I use windows 10 and the linker works with openOCD under eclipse env but not in standalone with ST-link utility for exemple.
Nb: I didn’t ask on the site where I found the topic because this is an old topic…
Thank you for your help.
Regarding your first post in this thread, what’s not totally clear for me how did you upload the firmware on the Nucleo if the ST-LINK Utility doesn’t recognize it? Can you post a capture of the ST-LINK Utility when you try to connect to the Nucleo boards?
Sure, I’m sry it’s out of scope of your book, really thank you for your help and sorry too for my broken english…
ST-link utility (I try it with a NUCLEO-L073RZ):
Check of my Device manager when I plug my NUCLEO-L073RZ:
My device seems well recognized nevertheless the ST-link is not detected…
Nb: As I using Windows 10 I have ST-link debug instead ST-link dongle someone said me.
My hardware Id’s (of this driver) according to my previous post:
One that is highlighted is not present in my stlink_dbg_winusb.inf it’s for this reason that I tried this procedure.
Thanks.
Have you tried the zadig tool described at page 150? Can you post me the capture of that tool once the Nucleo is plugged in?
I suspect that there is something wrong with the libusb, because i see in your capture that the libwdi is used.
Of course I used zadig, but the problem persisted.
Finally I fixed it, in fact I browsed in pilot update and it purpose me lot of different pilote (see below picture)
I choosed STMicroelectronics ST-link dongle instead STM32 STLink (libwdi) and then It worked.
Each pilote have an associated oemXX.inf, for example for ST-link dongle it’s oem10.inf (right way) and for STM32 STLink it’s oem59.inf (wrong way).
I don’t know why I have so many drivers installed for the same periphérique?
Furthermore I saw that to delete the bad oemXX.inf you must open a windows terminal and type one specific command to delete them previously you have to identify which oemXX.inf are bad.
I hope that this problem could help others.
Thanks.
- You must be logged in to reply to this topic.