Solved
ST-LINK/V2-1 with V2J35M26 looses communication with MCU on Nucleo-H743ZI
ST-LINK/V2-1 with Nucleo-H743ZI loose connection when target program is run. The target program loads fine with STLINK-gdbserver coupled with gdb, but few seconds into execution, it starts to complain that it can not get status and quits after several attempts.
STMicroelectronics ST-LINK GDB server. Version 5.2.3
Copyright (c) 2019, STMicroelectronics. All rights reserved.
Starting server with the following options:
Persistent Mode : Enabled
LogFile Name : debug.log
Logging Level : 31
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
Hardware watchpoint supported by the target
SWD frequency = 4000 kHz
ST-LINK Firmware version : V2J35S26
Device ID: 0x450
PC: 0x8040eac
ST-LINK device status: HALT_MODE
ST-LINK detects target voltage = 3.24 V
ST-LINK device status: HALT_MODE
ST-LINK device initialization OK
Waiting for debugger connection...
Waiting for connection on port 61234...
Accepted connection on port 61234...
Debugger connected
TraceCaptureStart and SWV event set to APP_TRUE
ST-LINK device status: RESET_MODE
ST-LINK device status: RUN_MODE
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: Failed to get status, Target not responding, retrying...
Target is not responding, retrying...
ST-LINK device status: TMO (Max Retries)
Error! Failed to read target status Then, when this happens, the ST-LINK/V2-1 falls into some unknown state that STLINK-gdb complains it can not connect to the device until the ST-LINK/V2-1 is power cycled.
STMicroelectronics ST-LINK GDB server. Version 5.2.3
Copyright (c) 2019, STMicroelectronics. All rights reserved.
Starting server with the following options:
Persistent Mode : Enabled
LogFile Name : debug.log
Logging Level : 31
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
Target no device found
Error in initializing ST-LINK device.
Reason: No device found on target.This issue started after upgrading to V2J35M26, so I suspect that there's a problem with this version of the firmware.
Some additional information:
- The issue develops on two different Nucleo-H743ZI board.
- The issue DOES NOT develop on a Nucleo-H743ZI2 (with STLINK-V3).
- The target program runs fine on all three boards if ST-LINK/V2-1 is not controlling MCUs.
Hope someone comes up with some information about the issue (or provide a way to downgrade to older versions that I can try).