2021-06-16 02:00 PM
I have had STM32CubeIDE v1.3.0 working with my hardware. I just upgraded to Cube to v1.6.1. Now when I try to debug, I get "No ST-LINK detected! " message box This has happened before (my upgrade to 1.4.1 failed so I rolled back to 1.3.0).
ST-LINK v4.5.0 has no issue programming the board. (USBDriver.dll=v5.1.2.0).
I'm running W10, 64 bits.
Help!
2021-06-16 04:15 PM
What do you see in the Windows device manager when the ST-LINK is connected?
2021-06-16 05:14 PM
OP indicated ST-LINK Utilities V4.5.0 works, so assume physical connectivity and drivers are functional
2021-06-17 07:39 AM
2021-06-18 06:10 AM
Any further thoughts on this? What is perplexing to me is that I can program my device through the ST-Link utility, but I'd really like to be able to debug through Cube.
Thanks for your help!
2021-06-18 06:17 AM
Wow. Just after sending the preceding message, I tried again.
What may be significant is that W10 helpfully rebooted my machine to install some updates. When I launched Cube this time, Windows Defender popped asking to access a port in the firewall. I said yes. Now it works.
So...it seems I am now up and running. Thank you.