I have been using System Workbench for STM32 for a while now without problems. Until recently when I updated Eclipse Neon. Since then the debugger didn’t work properly any more. So I created a fresh install of Eclipse Oxygen 4.7.0 and System Workbench for STM32. I can compile, flash the chip and start the debugger. Right after starting it stops at the first breakpoint and single-steps without a problem. However, when I set a second breakpoint, it will stop there and single-step does not work any more. I can resume, but the chip hangs. When I terminate the debug session, an error message is displayed:
Failed to execute MI command:
-stack -list -frames 0 0
Error message from debugger back end:
Invalid thread id: 1
Any help please?
(Win10, Eclipse Oxygen, bluepill board with F103C8, ST-LINK dongle, OpenOCD 1.16.0, OpenSTM32 IDE 2.2.0)
Edit: I noticed and fixed one issue on my side: the ST-LINK server wasn’t installed because I used the import method from within Eclipse. I installed the full package and the red warning message disappeared from the debug configuration panel. However, the problem still exists.