cancel
Showing results for 
Search instead for 
Did you mean: 

Nucleo-H7A3 Error: No STM32 target found!

Evan .1
Associate II

I'm trying to get a nucleo-H7A4 getting to run my code.

Only I got this message now:

     -------------------------------------------------------------------

                      STM32CubeProgrammer v2.4.0                 

     -------------------------------------------------------------------

ST-LINK SN : 003A001A3038510234333935

ST-LINK FW : V3J6M2

Voltage    : 3.31V

Error: No STM32 target found!

2nd connect tentative with a lower frequency (8MHz)

ST-LINK SN : 003A001A3038510234333935

ST-LINK FW : V3J6M2

Voltage    : 3.30V

Error: No STM32 target found!

Encountered Error when opening C:\ST\STM32CubeIDE_1.0.2\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_1.3.0.202002181050\tools\bin\STM32_Programmer_CLI.exe

Error in STM32CubeProgrammer

Debugger connection lost.

Shutting down...

Is the device now bricked? Any how is this possible with only programming flash?

1 ACCEPTED SOLUTION

Accepted Solutions
PMath.4
Senior III

I've had precisely this problem.

Solution is to connect BOOT0 high. Then power on. Connect a second USB cable to CN13. Run STM32CubeProgrammer and connect over USB - not ST-LINK. You should get a connection. Then erase all memory on the H7A3. Power off. Remove BOOT0 connection. Power-on and you should find ST-LINK works again.

Why? - Who knows - a bug in ST-LINK V3?

View solution in original post

4 REPLIES 4
Uwe Bonnes
Principal II

Try connect under reset.

I did, the device doesn't start programming when the reset button is pressed.

When I release the reset button I got the same error message.

PMath.4
Senior III

I've had precisely this problem.

Solution is to connect BOOT0 high. Then power on. Connect a second USB cable to CN13. Run STM32CubeProgrammer and connect over USB - not ST-LINK. You should get a connection. Then erase all memory on the H7A3. Power off. Remove BOOT0 connection. Power-on and you should find ST-LINK works again.

Why? - Who knows - a bug in ST-LINK V3?

Thanks!. That solved it.