2024-11-25 6:46 PM - edited 2024-11-25 9:38 PM
STM32CubeIDE
Version: 1.15.1
Build: 21094_20240412_1041 (UTC)
OS: Windows 10, v.10.0, x86_64 / win32
Java vendor: Eclipse Adoptium
Java runtime version: 17.0.8.1+1
Java version: 17.0.8.1
STLINK V3J15M6B5S1
At localhost, I can use "ST-LINK(OpenOCD)" to debug STM32H723ZG
The config file:
# This is an NUCLEO-H723ZG board with a single STM32H723ZGTx chip
#
# Generated by STM32CubeIDE
# Take care that such file, as generated, may be overridden without any early notice. Please have a look to debug launch configuration setup(s)
source [find interface/stlink-dap.cfg]
set WORKAREASIZE 0x8000
transport select "dapdirect_swd"
set CHIPNAME STM32H723ZGTx
set BOARDNAME NUCLEO-H723ZG
# Enable debug when in low power modes
set ENABLE_LOW_POWER 1
# Stop Watchdog counters when halt
set STOP_WATCHDOG 1
# STlink Debug clock frequency
set CLOCK_FREQ 8000
# Reset configuration
# use hardware reset, connect under reset
# connect_assert_srst needed if low power mode application running (WFI...)
reset_config srst_only srst_nogate connect_assert_srst
set CONNECT_UNDER_RESET 1
set CORE_RESET 0
# ACCESS PORT NUMBER
set AP_NUM 0
# GDB PORT
set GDB_PORT 3333
# BCTM CPU variables
source [find target/stm32h7x.cfg]
I have a Raspi4B with STlinkV3 connected and make OpenOCD run. Raspi4B connect in same subnet by WiFi.
From the log, STlinkV3 connect to target successfully as it got "Cortex-M7 r1p2 processor detected". But when I run debug in STM32CudeIDE, I got error:
The logs from OpenOCD:
sudo openocd -f stlink.cfg
Open On-Chip Debugger 0.12.0+dev-01805-g133dd9d66 (2024-11-26-13:10)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
WARNING: interface/stlink-dap.cfg is deprecated, please switch to interface/stlink.cfg
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V3J15M6B5S1 (API v3) VID:PID 0483:3753
Info : Target voltage: 0.001595
Error: target voltage may be too low for reliable debugging
Info : Unable to match requested speed 1800 kHz, using 1000 kHz
Info : Unable to match requested speed 1800 kHz, using 1000 kHz
Info : clock speed 1000 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x6ba02477
Info : [STM32H723ZGTx.ap2] Examination succeed
Info : [STM32H723ZGTx.cpu0] Cortex-M7 r1p2 processor detected
Warn : [STM32H723ZGTx.cpu0] Erratum 3092511: Cortex-M7 can halt in an incorrect address when breakpoint and exception occurs simultaneously
Info : [STM32H723ZGTx.cpu0] The erratum 3092511 workaround will resume after an incorrect halt
Info : [STM32H723ZGTx.cpu0] target has 8 breakpoints, 4 watchpoints
Info : [STM32H723ZGTx.cpu0] Examination succeed
Info : [STM32H723ZGTx.ap2] gdb port disabled
Info : [STM32H723ZGTx.cpu0] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections
Info : [STM32H723ZGTx.cpu0] external reset detected
Info : accepting 'gdb' connection on tcp/3333
Error: timed out while waiting for target halted
Error: [STM32H723ZGTx.cpu0] Execution of event gdb-attach failed:
Error: Failed to read memory at 0x5c001000
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected
Info : Halt timed out, wake up GDB.
The config file "stlink.cfg" is mostly same. Only one line added:
bindto 0.0.0.0
to make OpenOCD can accept incoming from all network interfaces.
Stucked at this error and can not go on. Does anyone have the remote debug run?
We’re moving the ST Community to a new platform to give you a better and more reliable community experience.