cancel
Showing results for 
Search instead for 
Did you mean: 

How to configure the built-in ST-Link debugger on STM32MP157D-DK1 Discovery Kit?

Saeed1
Associate

I am having difficulties using built-in ST-Link debugger on STM32MP157D-DK1 Discovery Kit. I am using the latest version of the STM32CubeIDE, Version: 1.10.1. Upon connecting the debugger it asked for FW upgrade on the ST-Link which I accepted and it completed the FW upgrade successfully.

GDB Connection: Autostart local GDB server

Debugger Load Mode: thru JTAG/SWD Link

I have configure the debug probe to be OpenOCD

Connection setup: SWD

Dropped the clock to 4, and 1.8 none worked.

Here is the log for the debugger:

Open On-Chip Debugger 0.11.0+dev-00449-g53fa0f7 (2022-06-09-09:42)

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Info : STLINK V2J40M27 (API v2) VID:PID 0483:3752

Info : Target voltage: 3.245293

Info : clock speed 125 kHz

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x6ba02477

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x6ba02477

Info : STM32MP157DACx.cm4: Cortex-M4 r0p1 processor detected

Info : STM32MP157DACx.cm4: target has 6 breakpoints, 4 watchpoints

Info : STM32MP157DACx.cm4: external reset detected

Info : STM32MP157DACx.cpu0: hardware has 6 breakpoints, 4 watchpoints

Info : STM32MP157DACx.cpu1: hardware has 6 breakpoints, 4 watchpoints

Info : gdb port disabled

Info : gdb port disabled

Info : gdb port disabled

Info : starting gdb server for STM32MP157DACx.cpu0 on 3334

Info : Listening on port 3334 for gdb connections

Info : starting gdb server for STM32MP157DACx.cm4 on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

Info : Halt timed out, wake up GDB.

Error: timed out while waiting for target halted

Error executing event gdb-attach on target STM32MP157DACx.cm4:

Info : New GDB Connection: 1, Target STM32MP157DACx.cm4, state: reset

Warn : GDB connection 1 on target STM32MP157DACx.cm4 not halted

Warn : negative reply, retrying

Warn : negative reply, retrying

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x6ba02477

Info : Deferring arp_examine of STM32MP157DACx.cm4

Info : Use arp_examine command to examine it manually!

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x6ba02477

Info : STM32MP157DACx.cm4: Cortex-M4 r0p1 processor detected

Info : STM32MP157DACx.cm4: target has 6 breakpoints, 4 watchpoints

Info : Halt timed out, wake up GDB.

Error: timed out while waiting for target halted

Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (1828 ms). Workaround: increase "set remotetimeout" in GDB

Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (1831 ms). Workaround: increase "set remotetimeout" in GDB

Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (1835 ms). Workaround: increase "set remotetimeout" in GDB

Warn : target STM32MP157DACx.cm4 is not halted (add breakpoint)

Error: can't add breakpoint: target running

1 REPLY 1
PatrickF
ST Employee

Hi @Saeed​ ,

I encourage you to check the following wiki pages

PC_prerequisites

https://wiki.st.com/stm32mpu/wiki/Getting_started

https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-DK2/Develop_on_Arm%C2%AE_Cortex%C2%AE-M4

https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-DK2/Develop_on_Arm%C2%AE_Cortex%C2%AE-M4/Modify,_rebuild_and_reload_a_firmware

Regards,

In order to give better visibility on the answered topics, please click on 'Select as Best' on the reply which solved your issue or answered your question. See also 'Best Answers'

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.