2020-03-31 08:18 AM
I have been using STM32L010K8T6 with a J link debugger. It has been working good for past month or so. But now whenever I use a breakpoint the system does not stop at that particular break point or sometimes does not reach the break point at all. I thought the issue might be with the Jlink debugger so I got a Nucleo-L010RB board and programmed it with a simple code to blink the LED. Even in this, the system either stops where theres no break point or does not stop at all.So my guess is there is some issue with STM32cubeIDE. What could be the issue?
2020-03-31 08:20 AM
Sometimes this type of behavior can happen when you've set too many breakpoints. There is an error when starting but it's easy to miss. Clear *all* your breakpoints and try again.
2020-03-31 09:25 AM
I have tried that , cleared all the breakpoints and have just one breakpoint. I am still facing the same issue.
2020-03-31 12:14 PM
I found this link which is similar to what I am facing but the solutions suggested on it dont work.
2020-03-31 01:05 PM
Perhaps use some better tools?
Keil has a free license for STM32 CM0(+) devices
A common problem is that CM0 code has significantly more instructions per C line of code, and optimization might distribute the code amongst that for other lines. Disable optimization, or use the disassembly view.
If you stop the debugger has it gone past the breakpoint, or just not got there?
Perhaps instrument your code in a way you can better understand flow and dynamics? Output via a serial port.
2020-03-31 01:55 PM