2022-08-05 06:03 PM
Failed to execute MI command:
target remote localhost:61234
Error message from debugger back end:
localhost:61234: Connection timed out.
2022-08-05 07:09 PM
Check connectivity and erase with STM32 Cube Programmer directly.
2022-08-05 07:28 PM
Debugger can t connect for multiple reasons. Low power clock stop mode being one of them. Use bootloadder boot pin to check this point. Emulating eeprom in flash with a bugged code that massively erase could wear and tear the memory is another.
2022-08-05 08:32 PM
Thank you. I checked, connectivity is okay. Board is getting flashed with STM32 Cube programmer ( invoked if select Autostart local GDB server) but not directly using from ST-LINK. Does this help in bringing more clarity to my issue?
2022-08-05 08:35 PM
Thank you but the code is of few lines, basic GPIO toggle and I did not have any wires connected to nucleo board apart from usb cable. Board is surely not in low power mode.
2022-08-06 03:07 AM
On your image is selected remote GDB , this result your system try connect to network debuger.
I use this for Cube on one PC and device with stlink 10km remote on next PC,
You maybe missunderstand image , for normal local debug you need upper choice Autostart.
2022-08-06 05:12 AM
Not really.
Isn't the server on the local (this) machine?
Anything that's causing the remote server not to start, or be blocked? Say AV software change recently.
Try and think what changed between the time that it worked, and when it stopped working.
2022-08-06 11:50 AM
Thank you. You awakened my sleeping brain.
2022-08-06 11:50 AM
Well, my silly brain....:(.
I think somewhere along, I inadvertently changed my default setting to "Connect to remote GDB server" and was thinking it as the default setting. But thanks to all of you, my brain came out of sleep and all good now.
My bad for posting a very silly mistake of mine as an issue.
thanks everyone!