2025-03-17 8:59 AM
Hi everyone,
I'm experiencing an issue uploading a simple onboard LED blinking program to my STM32H755ZIQ board. Every time I try to start a debug session, I get the following error:
STMicroelectronics ST-LINK GDB server. Version 7.9.0
Copyright (c) 2024, STMicroelectronics. All rights reserved.
Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
InitWhile : Enabled
Info : default port : 7184
Info : Remote address: 127.0.0.1
Info : stlinkserver already running, exit
Target no device found
Error in initializing ST-LINK device.
Reason: No device found on target.
What I've Tried:
Hardware Checks:
Software and Firmware:
IDE Configuration:
Despite these steps, the ST-LINK GDB server still fails to detect the device, and the board doesn't even enter debug mode.
Has anyone encountered a similar issue with the STM32H755ZIQ, or does anyone have additional suggestions to get past the "No device found" error? Any help would be greatly appreciated!
Thanks in advance for your time and support.
2025-03-17 9:25 AM
In the debug configuration, are you connecting to AP0?
Can you connect with STM32CubeProgrammer?
2025-03-17 9:37 AM
Yes, I am doing that
2025-05-09 8:23 AM
I recently purchased 2 NUCLEO-H755ZI-Q and both of them will not boot. ST has problems. In UM2408 Rev 6 it says the default power configuration is DIRECT SMPS but a quick scan of the board shows SB92, SB75, SB79, SB76 and R35 are INSTALLED. This is in direct contrast to what UM2408 describes in section 7.4.8 as the defaults for DIRECT_SMPS. The board did not come configured for DIRECT_SMPS.
After observing this I tried configuring my software for PWR_LDO and it still will not boot.
after each attempt I must hold BOOT0 high with a wire during power up then erase the FLASH using ST Programmer. The MCU always comes back after this process but something is royally screwed with the board's power configuration coming new from ST.
I also have been using the H747-DISCO with no problems so I do have experience with the Duel Core MCUs.
ST needs to investigate this and get it straightened out.
2025-05-09 8:45 AM
Hello all,
Please check this discussion out.
2025-05-09 9:13 AM
No Go! When I change the ioc file and regen code I do not get USE_PWR_LDO_SUPPLY defined under properties. I ONLY get USE_PWR_DIRECT_SMPS_SUPPLY. and still NO GO.
This does not change the fact that the board's power configuration is NOT the default described in UM2408.
In UM2408 Rev 6 it says the default power configuration is DIRECT SMPS but a quick scan of the board shows SB92, SB75, SB79, SB76 and R35 are INSTALLED. This is in direct contrast to what UM2408 describes in section 7.4.8 as the defaults for DIRECT_SMPS. The board did not come configured for DIRECT_SMPS.
ST needs to investigate this and get it straightened out.
2025-05-09 9:58 AM
PWR_DIRECT_SMPS_SUPPLY is the correct default option.
I can create a default CubeMX project for this board, which has PWR_DIRECT_SMPS_SUPPLY selected, and can program/debug normally.
> In UM2408 Rev 6 it says the default power configuration is DIRECT SMPS but a quick scan of the board shows SB92, SB75, SB79, SB76 and R35 are INSTALLED. This is in direct contrast to what UM2408 describes in section 7.4.8 as the defaults for DIRECT_SMPS. The board did not come configured for DIRECT_SMPS.
I'm not seeing a contradiction here. "X" means installed. "-" means not installed.
"Internal SMPS only" and "Direct SMPS" are the same. The core is powered directly from the SMPS.
2025-05-09 10:01 AM
As stated by @TDK, the default configuration of that board is SMPS. No need for any modification.
2025-05-09 10:47 AM
That was certainly my experience (uses SMPS), but I got the board quite a while ago. But it might be helpful to get a picture of this board's configuration, and the full part# / revision and any QA marks. Where was the board sourced?
For the H7's generally I've soldered a right-angle jumper post on the VDD/BT0 pin pair because locking the cores it easy enough to do.
Watch for PA13/PA14 being disabled or reconfigured.
2025-05-09 10:48 AM
I have come to that conclusion. X means installed. It took quite a few iterations of attempt to program, no device detected. BOOT0 high, erase FLASH and reprogram ... then it suddenly started working. Why I had to go through that is a complete unknown but I did go through this to a lesser degree with an H747-DISCO also.