I try to connect STM32H750-DK with STM32CudeProgrammer but it shows as the picture. What should I do?

[wsuwa.1]

..

[RomainR.]

Hello wsuwa.1 (Community Member)

Could you confirm that you connect the STM32H750-DK using a data USB cable type and not a charger type?

If yes, the micro usb side of the cable must be connected to CN14 which is the USB STLink used by STM32CubeProgrammer in SWD/JTAG mode.

Then check the following jumper configuration on board:

JP1 is present and JP8 is present on 5V_USB_STLK.

Let me know.

Best regards,

Romain,

[wsuwa.1]

Yes,I do everything like you said.

[RomainR.]

Can you share the full STM32CubeProgrammer Log ?

Are you able to connect with the same computer and same STM32CubeProgrammer on an other STM32 board ?

[wsuwa.1]

I don't have another board.

[RomainR.]

Hello wsuwa.1 (Community Member)

I looked at your logs, the STM32H7 is not detected.

Your STM32H750-DK board been modified from a hardware or software point of view?

Did you change the Option Bytes, such RDP in Level 2 chip protection ?

What version of the STM32CubeProgrammer are you using?

What are the ST-Link configuration (right menu in CubeProgrammer) Port=SWD ? Frequency? ...

Best regards,

Romain,

[Tesla DeLorean]

Could also be LDO vs SMPS setting

Would suggest finding a circuit node or jumper related to the BOOT0 pin, and pulling/strapping that HIGH, then power cycling the board completely several timer (remove all power/connections). Until you can connect with the STM32 Target, and then erase the problematic user code.

Then check your source carefully, especially SystemClock_Config() and whatever it is doing with LDO, SMPS and VOS settings specifically.

Reconfiguring the SWD pins, or disabling the debug interface will cause headaches. Low power modes that turn OFF pins and internal circuitry are also counter-productive when it comes to connectivity.

[Adem]

I can't find where the BOOT0 pin is exactly on my STM32H750B-DK board

 

[wsuwa.1]

STM32CubeProgrammer version 2.13.0

[wsuwa.1]

..

[Tesla DeLorean]

Ok, and?

​

[RomainR.]

Hello wsuwa.1 (Community Member)

I don't reproduce this problem on my side with the latest version v2.13.0 and the same DK board.

Please follow the very good recommendations of Tesla DeLorean to erase the firmware by connecting BOOT0 IO to 3.3V (shorting solder bridge R144 on pcb).

Best regards,

Romain,

[wsuwa.1]

What is BOOT0 IO?

[RomainR.]

On all STM32 the BOOT0 pin is a GPIO which has the function to select different boot memory areas.

Depending of voltage level apply, you can force the MCU to boot in user flash (Default when BOOT0=GND) or in Bootloader mode in system memory (BOOT0=3.3V).

As explained, if your able to set BOOT0 (by closing unmounted R144 on pcb) you will have chance to connect and erase the flash of the board.

I suggest you to read the document below in chapter 2.6 Boot configuration.

https://www.st.com/resource/en/reference_manual/rm0433-stm32h742-stm32h743753-and-stm32h750-value-line-advanced-armbased-32bit-mcus-stmicroelectronics.pdf

Best regards,

Romain,