2018-02-25 02:43 AM
For the past months I've been working with my STM32F722ZE Nucleo board without any issues. But a few days ago debugging suddenly broke. I can still create a session, but when the debugger hits a breakpoint (I assume), I only get this error message (at the end of the log):
Info : STM32F722ZETx.cpu: hardware has 8 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection on tcp/3333Info : Stlink adapter speed set to 1800 kHzadapter speed: 1800 kHzSTM32F722ZETx.cpu: target state: haltedtarget halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x080059d4 msp: 0x20040000Info : Stlink adapter speed set to 4000 kHzadapter speed: 4000 kHzInfo : flash size probed value 512Info : flash size probed value 512Info : Stlink adapter speed set to 1800 kHzadapter speed: 1800 kHzSTM32F722ZETx.cpu: target state: haltedtarget halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x080059d4 msp: 0x20040000Info : Stlink adapter speed set to 1800 kHzadapter speed: 1800 kHzSTM32F722ZETx.cpu: target state: haltedtarget halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x080059d4 msp: 0x20040000Info : Stlink adapter speed set to 4000 kHzadapter speed: 4000 kHzSTM32F722ZETx.cpu: target state: haltedtarget halted due to breakpoint, current mode: Thread xPSR: 0x61000000 pc: 0x20000084 msp: 0x20040000Info : Stlink adapter speed set to 1800 kHzadapter speed: 1800 kHzSTM32F722ZETx.cpu: target state: haltedtarget halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x080059d4 msp: 0x20040000Error: jtag status contains invalid mode value - communication failureWarn : target STM32F722ZETx.cpu is not haltedPolling target STM32F722ZETx.cpu failed, trying to reexamineExamination failed, GDB will be halted. Polling again in 100msInfo : Previous state query failed, trying to reconnect...Error: jtag status contains invalid mode value - communication failurePolling target STM32F722ZETx.cpu failed, trying to reexamineExamination failed, GDB will be halted. Polling again in 6300msshutdown command invoked (<--- stopped debug)Info : dropped 'gdb' connection
While this is happening, the Nucleo connection LED shows both green and orange at the same time (not blinking).
My setup for SYS is 'trace async with SW', and those three pins are unconnected/unused but configured.
What is causing this? Google did not provide an answer.
#debug #error2018-02-26 08:45 AM
Small update: Breakpoints on code that is regularly called my main.c work just fine. The above problems only occur on interrupt handlers (unless there is some hidden timing issue)!
My debug configuration should also be fine: connect under reset, SWD, 4 MHz (tried lower as well), enable debug for low power.