cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Connect to STM32H747 After Flashing Code in CubeIDE

KAnahar
Associate III

Hello,

I am using my custom PCB with the STM32H747IIT6 microcontroller. I have set up a JTAG/SWD connection. Initially, when I power up the board and connect via ST-Link, I can access the microcontroller through STM32CubeProgrammer without any issues.

However, after generating a new code in CubeIDE and flashing it onto the MCU, I can no longer connect to the device. I have tried selecting all available connection modes in CubeProgrammer, but none of them work.

"Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication."

While downloading to the code, terminal giving below messages:

"Opening and parsing file: ST-LINK_GDB_server_a16936.srec

Memory Programming ...

File : ST-LINK_GDB_server_a16936.srec

Size : 131.00 KB

Address : 0x08000000

 

Erasing memory corresponding to segment 0:

Erasing internal memory sectors [0 1]

Download in Progress:

File download complete

Time elapsed during download operation: 00:00:02.893

 

Verifying ...

Download verified successfully

 

Target is not responding, retrying...

Target is not responding, retrying...

Shutting down...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying...

Target is not responding, retrying..."

 

The only way to regain access is by setting the BOOT0 pin HIGH, performing a Full Chip Erase, and then pulling BOOT0 back to LOW. After this process, I can connect again, but as soon as I flash new firmware, the same issue occurs.

I have attached images of my configuration settings and schematics.
How can I resolve this issue? I have tried both Serial Wire and JTAG modes, but the problem persists.

Thank you!

1 REPLY 1
TDK
Guru

Does your firmware modify flash or go into low power states or reassign the SWD pins? Put a 1s delay before doing any of those things.

If you feel a post has answered your question, please click "Accept as Solution".