I have the latest version of CrossWorks for ARM and use it with a Segger JLINK with a LPC4357 and an LPC1768 development board. Right after loading the code to the board, I can start the application running and while it's running, if I click in the margin of a line of code, a breakpoint gets set and execution stops when it hits that breakpoint.
If I leave the application running for a day or two (it's an embedded application that will be running 24/7 when I finish the project), if I click in the margin to set a breakpoint, the breakpoint appears to be set (the red dot appears). The breakpoint is never taken, however, and the processor never stops even though I know it executes the code containing the breakpoint.
This behavior is consistent: if I leave the application running, it will always get into a state where breakpoints no longer seem to be recognized.
When it gets into this state, the pause button will stop the code.
Is this a known issue and is there a fix?
Please sign in to leave a comment.