STM32 Blue Pill ID Error workaround

More information about this issue: www.eevblog.com/forum/beginne...

[@lucianosalvatore2214]

TO EVERYONE: THIS METHOD IS NOT LONGER VALID FOR DEBUGGING. The openOCD that comes w/ the IDE have a doble-check to avoid fake or null IDs

[@Mossy06]

I there a new method?

[@keen2461]

This is no longer working as mentioned on prior comment. Has anybody found a workaround?

[@aak1473]

After followed the step told in video, the problem still occur, an error "Failed to execute MI command:
target extended-remote localhost:3333" appear. May I know how to solve it?

[@mampfi]

It seems like openocd is not running properly. Do you have the same settings as 1:28 in the video? Have you tried rebooting? If it still doesn't work try to ask at community.st.com/

[@Frisky0563]

Hi I’m using STM32CubeIDE 1.10.0 and I’m having issues still after modifying the stm32F1.Cfg file.

[@mampfi]

Thanks for watching, what do you get in your console as output?

[@kmlyzr]

could not verify st device please verify that the latest version of gdb-server . How can ı solve this problem. ı saw a video which solved by using hex code but is there any solving different from this?

[@sharana.p5921]

Thank for the video. is this for Chinese chips?

[@mampfi]

Thank you, yes it is

[@fatihcay3387]

Thanks

[@mampfi]

I'm glad I could help

[@enis1678]

this is not work. ıcant debug pls help

[@mampfi]

Hi enis, do you get some console output?