Nucleo-H745: Debbuger stopped working after programming USB

[seppeltronics_v]

Hello,

after programming the code via the OnBoard ST-Link and connecting/disconencting USB on the Device side in order to find out if the works, I can no longer access the microcontroller.

I have no idea what the rootcause is, 3.3V is fine. Could it be that the MCU is stuck in a lowpower mode(I did not configure any).

Thanks a lot.

Best Regards, Seppel

 

[Tesla DeLorean]

Likely the same issue with all H7 dual core 'V'-step parts, incorrect LDO/SMPS or VOS settings. See reporting on H747I-DISCO and H7508-DK's

Strap BOOT0 HIGH, fully cycle power several times until you can connect with STM32 Cube Programmer, and erase your errant code.

[seppeltronics_v]

Hello Clive,

could you plese tell me what "BOOT0" is and some Details? I'm just sarting with the H745,... .

Once I've got access, is there a way to avoid it? Never had these problems before when I fiddled with it.

V-Step, thats the marking on the first line of the Controller?

Thanks a lot.

Best Regards, Seppel

[Tesla DeLorean]

https://community.st.com/s/question/0D50X0000Bh5aWoSQI/stm32h747-discovery-kit-not-debugprogrammer

https://community.st.com/s/question/0D53W00000LeaeiSAB/location-of-stm32h747idisco-boot0-pin

https://community.st.com/s/question/0D50X0000BqBA6TSQW/error-to-connect-to-target-stm32h747idisco

https://community.st.com/s/question/0D53W00000LeYL1SAN/get-stm32h735gdk-out-of-deadlock

Sensitive to the power supply and voltage scaling settings

static void SystemClock_Config(void)

{

 RCC_ClkInitTypeDef RCC_ClkInitStruct;

 RCC_OscInitTypeDef RCC_OscInitStruct;

 HAL_StatusTypeDef ret = HAL_OK;

 /*!< Supply configuration update enable */

 HAL_PWREx_ConfigSupply(PWR_DIRECT_SMPS_SUPPLY);

 /* The voltage scaling allows optimizing the power consumption when the device is

   clocked below the maximum system frequency, to update the voltage scaling value

   regarding system frequency refer to product datasheet. */

 __HAL_PWR_VOLTAGESCALING_CONFIG(PWR_REGULATOR_VOLTAGE_SCALE1);

 while(!__HAL_PWR_GET_FLAG(PWR_FLAG_VOSRDY)) {}

#BRICKED #NUCLEO-H745ZI

[Tesla DeLorean]

BOOT0 is a pin controlling boot behaviour into ROM or your code into FLASH.

Should be marked on one of the pin headers, and findable via the User Manual / Schematic, usually close to a VDD pin for easy connection

[seppeltronics_v]

Ok, I found it:

1. Disconnected the USB ( Debugger)
2. Jumperwire from 3.3V to BT0
3. Connected the USB (Debugger)
4. Started the Debugging in the STMCubeIDE
5. Party :grinning_face: !!!

There is a seperate section in the Manual, I added it so others that read this post can find it instantly:

 

[seppeltronics_v]

However, how can that be avoided? What do I have to do to not have this issue again?

What are the correct LDO/SMPS or VOS settings for the Nucleo-H745?

Thanks a lot.

Best Regards, Seppel

[Tesla DeLorean]

Board provides for multiple powering methods, SW and HW need to be consistent.

Looking at this blindly, I'd guess you selected the LDO, not the SMPS setting

 HAL_PWREx_ConfigSupply(PWR_LDO_SUPPLY); // USED THIS, FROM H743

 HAL_PWREx_ConfigSupply(PWR_DIRECT_SMPS_SUPPLY); // WANTED THIS

[seppeltronics_v]

Wow, I can't even find these settings. the settings should be in the config-Tool?

All I found was this:

[Tesla DeLorean]

I'm not a CubeMX/IDE/WTF adherent, I work code the old fashion way..