AnsweredAssumed Answered

STM32F4 - connect ST-Link without RESET

Question asked by kelly.andrew.001 on Oct 14, 2016
Latest reply on Oct 17, 2016 by Clive One

I have an issue with a custom board using an STM32F427 that only shows up when I run outside the debugger.  I've done some searching without any luck - is there a way to get TrueSTUDIO (or any other debug environment) to connect to a running board without issuing a RESET?

I'm running TrueSTUDIO v6 connecting to the target using the ST-Link v2 in SWD mode.

I've tried pre-starting the GDB_server in "presistant mode" and connecting to the "remote" GDB server from TrueSTUDIO ..  but, when starting gdb_server, I get see:

C:\Program Files (x86)\Atollic\TrueSTUDIO for ARM 6.0.0\Servers\ST-LINK_gdbserver>ST-LINK_gdbserver.bat

Atollic TrueSTUDIO gdbserver for ST-Link.  Version 2.4.3 Pro
Copyright 2010-2016, Atollic AB.

Starting server with the following options:
        Persistant Mode            : Enabled
        LogFile Name               : debug.log
        Logging Level              : 31
        Listen Port Number         : 61234
        Status Refresh Delay       : 15s
        Verbose Mode               : Enabled
        SWD Debug                  : Enabled

Connecting to the ST-Link Debugger...Enter STM32_AppReset() function
NVIC_DFSR_REG   = 0x00000009
NVIC_CFGFSR_REG = 0x00000000
XPSR = 0x01000000
ST_LINK Major version =2 Jtag version =25
ST_LINK VID=1155 PID=14152
ST_LINK device status: HALT_MODE
ST_LINK detects target voltage =3.21 Volt
Hardware watchpoint supported by the target
FuncEntry
STM32 device: id =20016419
STM32 device: Flash size =2048
FuncExit
FuncEntry
FuncExit
 OK
Start Logging
Waiting for debugger connection...Waiting for TrueSTUDIO client to connect on port 61234 ...

I'm guessing that the "Enter STM32_AppReset() function" is probably what's doing it.

Outcomes