Common OpenOCD issues on the Windows platform

[MGeo]

On: Win 7 Pro 64

When I follow instructions per “Common OpenOCD issues on the Windows platform” (Page 143 of my current copy) to update driver with Zadig utility, it subsequently breaks my ST-Link Utility ability to find and connect to device. When I click Target->Connect in ST-Link Utility the device cannot be found.

To fix, I had to manually reassign the driver via Device Manager back to stlink_dbg_winusb.inf as delivered in ST’s stsw-link009 driver install package. Simply reinstalling with stsw-link009 dpinst_amd64.exe did not work restoring functionality, I had to manually re-install.

NOTE: My original install worked fine with ST-Link Utility working per book and CMD console window. No libusb errors. Book recommends ComEmu so I installed. Using ComEmu then gave libusb errors. Command line OpenOCD still worked in Win CMD window. When I upgraded driver using Zadig per book to get ConEmu working, ConEmu then worked but ST-Link Utility no longer could connect to ST-Link on Nucleo board. I suggest test to confirm findings, and remove Zadig driver update recommendation if it breaks ST-Link Utility.

Also my brief experience with ConEmu indicates benefits over Win CMD were not sufficient to warrant all the subsequent issues raised, I would recommend deleting the footnote recommendation. All book examples so for work fine in Win CMD.
George

• This topic was modified 9 years ago by MGeo.
• This topic was modified 9 years ago by MGeo.
• This topic was modified 9 years ago by MGeo.

[Carmine Noviello]

Hi MGeo,
Thank you for your feedback.

I’ll do some tests, but as far as I know, ConEmu is just a terminal console and it shouldn’t interfere with the underlying OS.

However, it’s true that the Zadig utility can do a mess with the drivers. I’ve to better explain that part.

Carmine

[Author]

Posts