AnsweredAssumed Answered

Atollic GDB Looses connection when program runs without breakpoints

Question asked by Scott Keitzer on Mar 8, 2018
Latest reply on Apr 27, 2018 by Eric Palmer

Hi,

Using Truestudio 9.0.0 with Nucleo STM32F302R8.

Used CubeMX to generate code.

Using ST-Link to load/ debug. Can download/ examine memory/ etc..

Use embedded COM port for debugging messages..

 

All works fine until I click 'Resume' followed by "suspend"..

 

Then atollic_gdb_server crashes..

 

Seems once embedded program is running, gdb can't suspend it?

 

Atollic TrueSTUDIO gdbserver for ST-Link. Version 4.2.0 (WIN32 2018-01-16 10:57:14 15656)

Copyright (c) 2018, STMicroelectronics. All rights reserved.

 

  

Starting server with the following options:

Persistant Mode : Disabled

LogFile Name : D:/SW_Projects/STM32_workspace/ProjectUart/Projectuart//\Debug\st-link_gdbserver_log.txt

Logging Level : 31

Listen Port Number : 61234

Status Refresh Delay : 15s

Verbose Mode : Enabled

SWD Debug : Enabled

 

Atollic TrueSTUDIO gdbserver for ST-Link. Version 4.2.0 (WIN32 2018-01-16 10:57:14 15656)

Hardware watchpoint supported by the target

STM32 device: Flash size =65535

Enter STM32_AppReset() function

NVIC_DFSR_REG = 0x00000009

NVIC_CFGFSR_REG = 0x00000000

XPSR = 0x01000000

ST_LINK Major version =2 Jtag version =28

ST_LINK VID=1155 PID=14155

ST_LINK device status: HALT_MODE

ST_LINK detects target voltage =3.26 Volt

ST-Link device initialization OK

Waiting for connection on port 61235...

Waiting for debugger connection...

Waiting for connection on port 61234...

Accepted connection on port 61234...

Debugger connected

ST_LINK device status: HALT_MODE

Reading 0x4 bytes of memory from addr 0x8001d90

Reading 0x2 bytes of memory from addr 0x8001d8c

Reading 0x2 bytes of memory from addr 0x8001d8e

Reading 0x4 bytes of memory from addr 0x8001dc4

Reading 0x20 bytes of memory from addr 0xe00fffd0

Reading 0x2 bytes of memory from addr 0x800196c

 

.

.

.

 

ST_LINK Halt Reason break point hit

 

Reading 0x4 bytes of memory from addr 0x800196c

Reading 0x4 bytes of memory from addr 0x20000118

TraceCaptureStart and SWV event set to APP_TRUE

TraceCaptureStart and SWV event set to APP_FALSE

NVIC_DFSR_REG = 0x00000001

ST_LINK Halt Reason halt requested by NVIC, including step

 

Reading 0x4 bytes of memory from addr 0x800196e

Reading 0x4 bytes of memory from addr 0x20000118

TraceCaptureStart and SWV event set to APP_TRUE

TraceCaptureStart and SWV event set to APP_FALSE

NVIC_DFSR_REG = 0x00000001

ST_LINK Halt Reason halt requested by NVIC, including step

 

Reading 0x4 bytes of memory from addr 0x80002a8

Reading 0x4 bytes of memory from addr 0x8001972

Reading 0x2 bytes of memory from addr 0x8001972

TraceCaptureStart and SWV event set to APP_TRUE

TraceCaptureStart and SWV event set to APP_FALSE

NVIC_DFSR_REG = 0x00000003

ST_LINK Halt Reason break point hit

 

Reading 0x4 bytes of memory from addr 0x8001972

Reading 0x4 bytes of memory from addr 0x20000118

TraceCaptureStart and SWV event set to APP_TRUE

ST_LINK device status: RUN_MODE

Encountered a Socket Error, Exiting..

Debugger connection lost.

Shutting down...

 

Any thoughts?#

Outcomes