5 years, 10 months ago.

Well, the information is correct. I found the post useful, but, nowadays, lots of users are complaining about an Error Code 0x9d". Click the link https://errorcode0x.com/fix-epson-printer-error-code-0x9d/ and know the steps for How To Recover the Epson Printer Error Code 0x9d issue.

5 years ago.

Thanks for the solution provided. Even I am also facing the same consequences regarding the ST Nucleo F103RB. I have a small query regarding the Epson WF 3640 ADF. I am getting an error code of 0x97 in my printer. I have configured my printer settings and contacted the helpdesk. I have gone through their given instructions https://printerssupport.co/epson-wf-3640-adf-not-working/,but it's not working out. Guide us if we have missed out on anything.

9 years, 11 months ago.

Is the board still listed as an unknown device under Windows Device Manager ?

If yes, then the device driver did not install or is not the correct device driver for this board.

Perhaps related to the same issue we faced earlier this morning using another Nucleo board on Windows 8 64 bit. From where did you download the driver package ? We found the following to be correct for supporting our 64 bit version of Windows 8 (also will be correct to use for Windows 7 use):

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

STSW-LINK009 ST-LINK/V2-1 USB driver on Windows XP (including WinUSB coinstallers)

Please review and test. If the above driver does not install then proceed to review the Device Manager -> select this unknown device -> post back the details for:

Details tab -> Hardware IDs (pulldown) = VID_ and PID_ for your attached board.

Update...

1) Is the cable applied to the Nucleo board a quality cable ?

2) Can you seat the cable onto another USB port ? Do you have access to another computer to test the same board ?

3) If using a USB hub, bypass and go direct to your PC.

The reading of USB IDs is a very fundamental part of the USB enumeration process. Device Manager should be able to read and list the IDs from the attached USB device. From the internet, the issue may be local to the Windows OS and perhaps can be resolved through a Microsoft service pack. However, before going this far, consider to test on a different box to see if the cable and board are confirmed operational and able to be detected by another box.

Please review this thread about Windows 7 & USB with UNKNOWN Device

http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/unknown-usb-device/4b780c00-9ef2-49dd-9e6a-eb2a1ed8f27e

Will check around the building to see if we have the same Nucleo board in the lab. If we do, will write back with our results.

On this note, the Nucleo is shipped with MBED mode (NUCLEO) and as an option can be used with the ST-Link mode. See the dual jumpers near the USB connectors.

If both jumpers are closed = MBED mode (NUCLEO).

If both jumpers are open, ST-Link mode.

Which mode is being tested now ? Consider to configure the opposite to test. Unplug -> change jumpers and reseat into the PC USB port on each attempt.

The idea is to confirm if the firmware is ok or corrupted. If the issue is still the same with either jumper configuration then review the idea of testing on another box so you can focus on the operating system / installation of the service packs.

8 years, 10 months ago.

Note that I had the same symptoms, tried on various PCs (Windows 7, Windows 10) and in the end it turns out it was down to the quality of the USB cable I was using. I tried two cables, no luck, only started working with a 3rd, better cable.