cancel
Showing results for 
Search instead for 
Did you mean: 

Critical Hardware Failure: STM32H743IIT6 Permanent Damage and Overcurrent Issues

Amir2647m
Associate

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 

3 REPLIES 3
Andrew Neil
Super User

Same problem here: STM32H7A3LIH6Q — SWD permanently unresponsive after ~20 flash cycles, UART bootloader work by @mvo ?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
mƎALLEm
ST Employee

Hello @Amir2647m and welcome to the ST community,

Did you check the AN4938 "Getting started with STM32H74xI/G and STM32H75xI/G MCU hardware development"?

Did you monitor VCAP voltage according to the voltage scale you've already selected in your software? :

mALLEm_0-1778687829472.png

Knowing that STM32H743 doesn't feature SMPS. I don't know why are you talking about SMPS here..

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
AScha.3
Super User

Hi,

i am not STM...

but using this H743 cpu , and there are no problems with the cpu.

So you doing something wrong.

Now  - what you do wrong ?

Basically : anti-/static handling , common problem; curious effects coming, nobody knows why....just damaged chip by bad treatment.

When you connect/disconnect  debug or any line to cpu : is it 100% safe against any voltage spike or missing or bad ground ?

+

about SMPS: here on H743 is no smps , so also no setting, that can be wrong ...

AScha3_0-1778701360103.png

+

>Are there specific requirements for the VCAP capacitors (2.2µF low ESR) 

no. just 2u2 cer caps.

+

>Does the H743IIT6 require a specific power-up sequence for the VDDA/VDD pins 

no, just have them together, diff < 0.5 V .

+

>the repeated physical failure suggests an internal latch-up or power management issue.

Bad handling, static discharge or a problem with your power supply.

If you apply 5V to the chip, even only as a spike, it will just die. Symptom: high supply current...as you see it.

If you feel a post has answered your question, please click "Accept as Solution".
Announcement

We’re moving the ST Community to a new platform to give you a better and more reliable community experience.