cancel
Showing results for 
Search instead for 
Did you mean: 

STM32H747I-DISCO failed to connect after disabling CM7 in option bytes

SBACO
Associate III

After the validation of my CM4 application in the dual core I wanted to find a way to launch it automatically on power ON, which was not the case. The CM7 was running a touchgfx application, which was stopped during my debug session on CM4. Trying to figure out how to have the 2 applications running or at least the CM4 app, I disable in the option bytes the CM7 using STM32CubeProgrammer 2.6.0 and embedded STLinkv3. The option byte write fail during the operation, and after that impossible to reconnect the STM32. I try to force BOOT0 to '1' by short cutting R192 but not better.

Here is the output of the cube programmer:

 16:32:40:297 : STLinkUSBDriver.dll loaded

 16:32:40:301 : STLinkUSBDriver.dll loaded

 16:32:40:301 : ST-LINK SN : 003D001E3137511439383538

 16:32:40:302 : ST-LINK FW : V3J7M2

 16:32:40:302 : Board      : STM32H747I-DISCO

 16:32:40:302 : Voltage    : 3.24V

 16:32:40:704 : No STM32 target found!

 16:32:40:706 : STLinkUSBDriver.dll loaded

 16:32:40:706 : ST-LINK SN : 003D001E3137511439383538

 16:32:40:707 : ST-LINK FW : V3J7M2

 16:32:40:707 : Board      : STM32H747I-DISCO

 16:32:40:707 : Voltage    : 3.24V

 16:32:41:111 : Error: No STM32 target found!

Hope you have an idea to save the board...

regards

1 REPLY 1
Bouraoui Chemli
ST Employee

Hello @SBACO​ 

You can refer to application note AN5286 "STM32H7x5/x7 dual-core microcontroller debugging"

I suggest to check the access port, check the ST-LINK setup is connected under reset ...

Bouraoui