FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

STM32H735-DK: Attach to ST-LINK USB debugger port fails, but STM32 programmer works.

DMois.1
Associate III

‎2020-12-17 08:54 PM

I have a STM32H735-DK and I'm trying to load the LedToggling sample app with the STM32CubeIDE 1.5.1. Debug fails with this message.

Starting server with the following options:
        Persistent Mode            : Disabled
        LogFile Name               : C:\Users\davidmoisan\STM32CubeIDE\workspace_1.5.0\LedToggling\STM32CubeIDE\BootROM_ExternalRAM_InternalSRAM_Debug\st-link_gdbserver_log.txt
        Logging Level              : 31
        Listen Port Number         : 61234
        Status Refresh Delay       : 15s
        Verbose Mode               : Enabled
        SWD Debug                  : Enabled
        InitWhile                  : Enabled
 
Target connection mode: Under reset
Reading ROM table for AP 0 @0xe00fefd0
Hardware watchpoint supported by the target 
COM frequency = 24000 kHz
ST-LINK Firmware version : V3J7M2
Device ID: 0x483
PC: 0x801680c
ST-LINK device status: HALT_MODE
ST-LINK detects target voltage = 3.29 V
ST-LINK device status: HALT_MODE
ST-LINK device initialization OK
Waiting for debugger connection...
Waiting for connection on port 61234...
Accepted connection on port 61234...
Debugger connected
Debugger connection lost.
Shutting down...
 

In the GUI, CubeIDE reports "Load failed. Load failed."

I have attached the GDB server log, as well.

I can connect to the device with the STM32CubeProgrammer. What is the minimum configuration that allow this to work?

Preview file
12 KB
0 Kudos
11 REPLIES 11
mattias norlander
ST Employee
In response to reversiverse

‎2021-05-31 05:49 AM

Hi,

Yes, this is a known limitation. OpenOCD does not easily support external memories.

So either rely on SEGGER, or ST-LINK GDB-server for this.

But digging into this a bit I noticed that not even STM32CubeProgrammer stand-alone tool can program the external flash. And as a reminder ST-LINK GDB-server fully relies on STM32CubeProgrammer for flash operations...

So to conclude on the status right now, it seems as if the external loader file:

(C:\ST\STM32CubeIDE_1.7.0.21w21\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.0.0.202105061353\tools\bin\ExternalLoader\MX25LM51245G_STM32H735G-DK.stldr-file)

bundled with CubeProg 2.6.0 contains some bug.

I created ticket#107904 as an internal reference to analyze and fix the issue.

Thanks for reporting!

0 Kudos
Top