When I change only a tiny bit in a sourcecode, and compile and start the debug process again, sometimes (few times
per day) the debugger does not upload the changed program and starts the old firmware
in the chip.
This can cost a lot of time when I don’t recognize it right away, and believe that the code in the debug-window is the code that is actually executed.
If I recognize it, I have to erase the chip with some other means, to force J-Link to really upload the new program.
I use a STM32F100 .. with Segger Version 4.96
Is there a way to force J-Link to always up-load the whole binary before debugging?
per day) the debugger does not upload the changed program and starts the old firmware
in the chip.
This can cost a lot of time when I don’t recognize it right away, and believe that the code in the debug-window is the code that is actually executed.
If I recognize it, I have to erase the chip with some other means, to force J-Link to really upload the new program.
I use a STM32F100 .. with Segger Version 4.96
Is there a way to force J-Link to always up-load the whole binary before debugging?
The post was edited 2 times, last by rensem ().