2025-01-01 09:00 PM
Hello ST Community,
I’m encountering significant difficulties connecting to and debugging my STM32 microcontroller and would greatly appreciate your guidance.
After erasing the full chip flash memory and uploading my code, the microcontroller initially worked as expected. However, after the first successful flash, I’ve been unable to reflash or debug the microcontroller. Here are the error messages I’m encountering across different tools:
Error Messages:
1.ST-Link Utility:
Can not connect to target!
If you're trying to connect to an STM32W1xx device, please select Normal or HotPlug mode from Target->Settings menu.
If you're trying to connect to a low-frequency application, please select a lower SWD Frequency mode from Target->Settings menu.
2.STM32CubeProgrammer:
UR connection mode is defined with the HWrst reset mode
ST-LINK SN : 003F00164741500420383733
ST-LINK FW : V3J13M4
Board : STM32H747I-DISCO
Voltage : 3.28V
Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication.
3.STM32CubeIDE:
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
Target no device found
Error in initializing ST-LINK device.
Reason: No device found on target.
Steps I’ve Taken:
Development board: STM32H747I-DISCO
Questions:
I’m still a beginner and would deeply appreciate any insights or advice the community can offer.
Thank you for your time and support!
2025-01-02 12:32 AM
Hello,
this happens when your firmware misconfigures core power-supply selection. If you haven't made any modifications to your DISCO HW kit, it must be configured as 'SMPS power supply'. If you selected something else, the board will lock up.
And the only way out is through BOOT0 pin. It is described somwehere in the manual of the H747-DISCO. This will let you erase the flash from CubeProgrammer and then you can normally program it again. Just make sure your FW sets the Core Power supply correctly, then it will work.
2025-01-02 12:42 AM - edited 2025-01-02 12:43 AM
Hello @ch-premchand and welcome to the community,
If you set the power supply to LDO for this board, this is expected. The board is configured in SMPS by hardware. To recover from this situation please review this article.