I'm working on the STM32H747-DISCO Board, and studently the onboard ST-Link-V3 stopped recognizing the STM32H747 MCU.No matter what i do, it wont find the target,when I connect a simple STM32F411-DISCO everything works as expected.Rebooting the Power won't help.Updating the ST-Link FW won't Help.no matter what debug configuration I do it won't recognize the target MCU.Not only that the CubeIDE and CubeMX are very buggy, now the MCU is dead ???this MCU costs a lot and it's dead ?very disappointing !!!!I request that ST representative will help me sort this matter.

Associate II

Solved

STM32H747-DISCO Board - ST-Link V3 - Target Not Found

Forum|Forum|2 years ago
October 11, 2023
4 replies
3924 views

I'm working on the STM32H747-DISCO Board, and studently the onboard ST-Link-V3 stopped recognizing the STM32H747 MCU.

No matter what i do, it wont find the target,

when I connect a simple STM32F411-DISCO everything works as expected.
Rebooting the Power won't help.
Updating the ST-Link FW won't Help.
no matter what debug configuration I do it won't recognize the target MCU.

Not only that the CubeIDE and CubeMX are very buggy, now the MCU is dead ???
this MCU costs a lot and it's dead ?

very disappointing !!!!
I request that ST representative will help me sort this matter.

This topic has been closed for replies.

Best answer by jiangfan

You may refer to: UM2411 Discovery kit with STM32H747XI MCU, in case of "A deadlock occurs if the board SMPS/LDO firmware PWR configuration does not match the hardware configuration".

chapter 5.2.3 SMPS/LDO power supply of the document:

Caution: A deadlock occurs if the board SMPS/LDO firmware PWR configuration does not match the
hardware configuration: after the reset, the ST-LINK cannot connect the target anymore.

1. Power off the board.
2. Connect pin BOOT0 to VDD using a wire (or short R192).
This changes the BOOT0 pin to 1 instead of 0, thus changing the device boot address to boot address 1 and making the bootloader start in System memory. This avoids starting firmware in the user flash memory with a wrong SMPS/LDO configuration versus the hardware board configuration.
...

jiangfan

ST Employee

There is one case the MCU (such as STM32H7) seems dead: it is due to mismatch firmware vs. hardware configuration, for example, hardware configuration is SMPS power (or LDO power) for MCU, but firmware enables only LDO power (or SMPS power) for MCU. For such case, recovery is possible, by changing the boot setting of STM32H7 to boot-from-sram, and connect to PC software such as CubeProgrammer, then erase full chip.

jiangfan

ST Employee

by default, after RESET, both SMPS power and LDO power are enabled for STM32H747.

M

MichaelZemahAuthor

Associate II

Do I need to change a boot resistor of the MCU ? Or change the value given to Boot0 or Boot1 pins ?

What should I do exactly ?

Ive tried connecting to the MCU wice CubeProgrammer before and erase, but couldn't..

What am I missing ?

jiangfanBest answer

ST Employee

You may refer to: UM2411 Discovery kit with STM32H747XI MCU, in case of "A deadlock occurs if the board SMPS/LDO firmware PWR configuration does not match the hardware configuration".

chapter 5.2.3 SMPS/LDO power supply of the document:

Caution: A deadlock occurs if the board SMPS/LDO firmware PWR configuration does not match the
hardware configuration: after the reset, the ST-LINK cannot connect the target anymore.

1. Power off the board.
2. Connect pin BOOT0 to VDD using a wire (or short R192).
This changes the BOOT0 pin to 1 instead of 0, thus changing the device boot address to boot address 1 and making the bootloader start in System memory. This avoids starting firmware in the user flash memory with a wrong SMPS/LDO configuration versus the hardware board configuration.
...