STM32H745 become unresponsive after firmware package updated.

[pranavmv012]

Dear ST Community,

I am currently working on a simple blinky project on a custom STM32H745BIT6-based board. Initially, I developed the project using STM32CubeIDE version 1.16.1 with the H7 firmware package version 1.11.2. The configuration includes an external 25 MHz crystal, and the power supply is set to PWR_DIRECT_SMPS_SUPPLY with voltage scale 1. This setup was working fine without any issues.

However, after updating STM32CubeIDE to version 1.17.0, which also updated the firmware package to version 1.12.1, I encountered an issue. The program works fine on the first power-up, but after a power cycle, the MCU becomes unresponsive. Additionally, I am unable to connect to the MCU via STM32CubeProgrammer.

I came across a forum post: https://community.st.com/t5/stm32-mcus/unable-to-connect-to-stm32h7-devices/ta-p/49296

where a similar issue was discussed. Following the suggestion in the post, I pressed the reset pin while powering on, which allowed me to access the MCU and perform a mass erase. While this approach worked temporarily, it raises concerns about the long-term stability of the firmware and the difficulty of maintaining code over time, especially since this could be a product intended for market use in the next 10 years.

Although I can revert to CubeIDE v1.16.1 and firmware package v1.11.2 to avoid this issue, I would prefer to use the latest versions of CubeIDE and the firmware package.

For reference, I have verified the power supply configuration for PWR_DIRECT_SMPS_SUPPLY, and I have attached a schematic screenshot of my hardware.

I would greatly appreciate any suggestions or workarounds for this issue. Thank you in advance for your assistance.

[KDJEM.1]

Hello @pranavmv012;

--> but after a power cycle, the MCU becomes unresponsive. Additionally, I’m unable to connect to the MCU via STM32CubeProgrammer.

Which error did you get? 

If you are using STM32CubeMX or STM32CubeIDE to generate the code, I think you have the same issue as this thread: Solved: Re: Default settings for NUCLEO-H755 not working a... - STMicroelectronics Community

Did you run a code with LDO configuration by error HAL_PWREx_ConfigSupply(PWR_LDO_SUPPLY);?

Note that your STM32H7’s SMPS or LDO firmware power configuration must match with the board’s hardware configuration. If not, you’ll face a deadlock situation such that after the reset the STLINK can no longer be used to connect to the target.

Could you please

• Refer and follow the steps shared in this FAQ: How can I recover my STM32H7 board after facing a power configuration deadlock?
• Try to upgrade the firmware using STM32CubeProgrammer and erase full chip flash memory.