2025-09-30 4:27 AM
Hello together,
like many others here, I have the problem that after a short time, the debugger closes with the error message “Failed to get status,..”.
The board is the nucleo-F767ZI.
It has already been mentioned in the forum that it could be due to the USB cable. But the
same cable works with an nucleo-H755ZI-Q fine.
It was also written that it could be due to the settings or by the code self.
Therefore i did a test and sets a breakpoint direct after start:
When standing at the breakpoint, the debugger still terminates after a few seconds.
Stm32Device, pollAndNotify running...
Warning: Ignoring a '-' sent by client....
GDB session, device event: 4
GDB session, device event: 4
GDB session, device event: 2
GDB session, device event: 2
NVIC_DFSR_REG = 0x0000000B
Stm32Device, getHaltReason, code: 4
GDB session, device event: 1
GDB session, device event: 1
ST-LINK device status: Failed to get status, Target not responding, retrying... 3
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying... 19
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying... 19
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying... 19
When I stop with the red button and try to start again, i got:
Then i could load again.
As long as the debugger is stopped on line 64 “ bl SystemInit,” no code is running and the settings have not yet been made.
What could be the cause then?
Thank you and best regards,
HiST