Dear ST Technical Support Team,
I am writing to request technical assistance regarding a recurring hardware failure with the STM32H743IIT6 MCU on my custom-designed PCB.
Problem Description:
After initial assembly, the MCU is correctly recognized by STM32CubeProgrammer and STM32CubeIDE via the ST-LINK (Serial Wire mode). I can successfully flash the firmware and debug the device for a limited number of cycles (typically 2 to 5 times). However, the MCU eventually enters a state where:
It is no longer recognized by any programming tool ("No STM32 target found").
The chip begins to draw excessive current (overheating rapidly).
The hardware suffers permanent damage (internal short-circuit).
Firmware Configuration:
Debug Hardware: Serial Wire (SWD).
Timebase Source: SysTick.
Clock Configuration: Configured via STM32CubeIDE (no errors reported in the clock tree).
Operating Voltage: 3.3V stable.
Technical Concerns:
I have verified the schematic, but the repeated physical failure suggests an internal latch-up or power management issue. Specifically, I suspect the transition from the internal LDO to the required VCORE voltage levels might be causing instability during the boot process.
Attached Documents:
Detailed schematic of the MCU section (Power pins, VCAP capacitors, and Reset circuit).
Clock configuration screenshot from CubeMX.
Questions for Support:
Could an incorrect Power Management Unit (PWR) software configuration (e.g., LDO vs. Direct SMPS) in the HAL initialization cause instantaneous physical damage to the H743 series?
Are there specific requirements for the VCAP capacitors (2.2µF low ESR) that, if slightly out of spec, would lead to this overcurrent condition?
Does the H743IIT6 require a specific power-up sequence for the VDDA/VDD pins to prevent the latch-up I am observing?
I look forward to your expert analysis of this issue.
Best regards,
Amir M
