Sysprogs forums › Forums › VisualGDB › Can’t connect to STM32H7B0
- This topic has 0 replies, 1 voice, and was last updated 5 hours, 46 minutes ago by
intector.
-
AuthorPosts
-
July 26, 2025 at 22:19 #36825
intector
ParticipantHello,
I have a board with a STM32H7B0 and can’t connect to it with VisualGDB. I’m using the STLink-V3MINIE for programming/debugging and have no problems with other STM32 boards and VisualGDB. I tried the STM32Cube Programmer on the STM32H7B0 board and it works fine without any issues. The VisualGDB “Test” connection button gives me this log output:
<div>C:\Users\KaiJensen\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c “gdb_port 52378” -c “telnet_port 52376” -f interface/stlink.cfg -f target/stm32h7x.cfg -c init -c “reset init” -c “echo VisualGDB_OpenOCD_Ready”</div>
<div>Open On-Chip Debugger 0.12.0 (2025-07-10) [https://github.com/sysprogs/openocd]</div>
<div>Licensed under GNU GPL v2</div>
<div>libusb1 d52e355daa09f17ce64819122cb067b8a2ee0d4b</div>
<div>For bug reports, read</div>
<div>http://openocd.org/doc/doxygen/bugs.html</div>
<div>DEPRECATED! use ‘gdb port’, not ‘gdb_port'</div>
<div>DEPRECATED! use ‘telnet port’, not ‘telnet_port'</div>
<div>Warn : DEPRECATED: auto-selecting transport “swd (dapdirect)”. Use ‘transport select swd’ to suppress this message.</div>
<div>Info : STLINK V3J15M7 (API v3) VID:PID 0483:374E</div>
<div>Info : Target voltage: 3.274332</div>
<div>Info : Unable to match requested speed 1800 kHz, using 1000 kHz</div>
<div>Info : Unable to match requested speed 1800 kHz, using 1000 kHz</div>
<div>Info : clock speed 1000 kHz</div>
<div>Info : stlink_dap_op_connect(connect)</div>
<div>Info : SWD DPIDR 0x6ba02477</div>
<div>Info : [stm32h7x.ap2] Examination succeed</div>
<div>Info : [stm32h7x.cpu0] Cortex-M7 r1p1 processor detected</div>
<div>Warn : [stm32h7x.cpu0] Erratum 3092511: Cortex-M7 can halt in an incorrect address when breakpoint and exception occurs simultaneously</div>
<div>Info : [stm32h7x.cpu0] The erratum 3092511 workaround will resume after an incorrect halt</div>
<div>Info : [stm32h7x.cpu0] target has 8 breakpoints, 4 watchpoints</div>
<div>Info : [stm32h7x.cpu0] Examination succeed</div>
<div>Info : [stm32h7x.ap2] gdb port disabled</div>
<div>Info : [stm32h7x.cpu0] starting gdb server on 52378</div>
<div>Info : Listening on port 52378 for gdb connections</div>
<div>[stm32h7x.cpu0] halted due to debug-request, current mode: Thread</div>
<div>xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc</div>
<div>Info : Unable to match requested speed 4000 kHz, using 3300 kHz</div>
<div>Info : Unable to match requested speed 4000 kHz, using 3300 kHz</div>
<div>VisualGDB_OpenOCD_Ready</div>
<div>Info : Listening on port 6666 for tcl connections</div>
<div>Info : Listening on port 52376 for telnet connections</div>
<div>Info : accepting ‘gdb’ connection on tcp/52378</div>
<div>Info : Device: STM32H7Ax/7Bx</div>
<div>Info : flash size probed value 128k</div>
<div>Info : STM32H7 flash has a single bank</div>
<div>Info : Bank (0) size is 128 kb, base address is 0x08000000</div>
<div>Info : New GDB Connection: 1, Target stm32h7x.cpu0, state: halted</div>
<div>Error: Error on socket ‘GDB’: WSAGetLastError==10054, message: An existing connection was forcibly closed by the remote host.</div>
<div></div>
<div>.</div>
<div>Info : dropped ‘gdb’ connection (error -400)</div>
<div>shutdown command invoked</div>
<div></div>
<div>The exception details show this:</div>
<div></div>
<div>VisualGDB version: 6.0.108.5338
—————— System.Exception ——————
System.Exception: Almost all reported device registers have a value of 0. This typically indicates JTAG/SWD wiring problems. Please double-check your board layout and debug connection.
at VisualGDB.Common_GUI.WPF.DebugMethodTestWindow.TestThreadBody()
trace=[VisualGDB.Common_GUI.WPF.DebugMethodTestWindow.TestThreadBody:0]</div>
<div>What am I doing wrong?</div>
<div></div>
-
AuthorPosts
- You must be logged in to reply to this topic.