My STM32 device is overheating and has malfunctioned

[Wadeva]

Hello,

We’ve designed a device that uses an STM32 microcontroller to manage various features such as I2C, UART, ADC, IWDG, DMA, Flash memory handling etc. After running smoothly for a month, the device began malfunctioning, drawing 220 mA of current and heating up noticeably. I’m trying to determine the root cause of this issue. Could you provide insights into the possible reasons for this behavior?

Thank you.

[Andrew Neil]

---

@Wadeva wrote:

Could you provide insights into the possible reasons for this behavior?

---

1. A hardware failure in your external hardware
2. A design error (software and/or hardware) over-stressing the part (or allowing it to get over-stressed).

 

For anything more specific, you're going to have to give a lot more detail!

 

[Wadeva]

Dear Andrew,

Our design involves numerous components, making it difficult to specify each one. We are using the STM32G070CBT microcontroller.

I’m unsure what might be causing this issue, as all peripherals and features seem to be functioning normally—no signs of overcurrent or short circuits. However, I’m curious if this type of malfunction could be related to something specific, like overcurrent in a peripheral or excessive heat.

I will try to narrow down the issue by individually testing each peripheral and reviewing our software.

 

[Andrew Neil]

---

@Wadeva wrote:

Our design involves numerous components, making it difficult to specify each one.

---

Your design should fully specify all of them!

 

---

@Wadeva wrote:

I’m curious if this type of malfunction could be related to something specific, like overcurrent in a peripheral or excessive heat.

---

Yes - as I said, over-stressing the part.

The primary result of overcurrent is overheating!

[TDK]

Look for possible places where the chip might have been overstressed, perhaps on powerup, perhaps by an external component through a long (inductive) wire, or ESD damage, or something of the sort.

When the chip is overstressed, the protection diodes can fail and cause the chip to sink a massive amount of current, sometimes while otherwise working okay.

[Wadeva]

Thank you TDK.

I will look and search with my team and tell you if we found the main reason.

 

[White_Fox]

How do you have your output pins configured?

Just try to config all as open drain with pull-up, be carefully that e.g. pwm stages may stop working correctly. If all pins are going high, you can exclude that your periphery is broken.

Next tests and other cases are more difficult, but also more rare I guess.

[Wadeva]

 

We are using both push-pull and open-drain configurations on different pins. Additionally, some pins have internal pull-up or pull-down resistors activated.

 

An interesting test. I will give it a try but as you said my problem might be the rare one.

[AScha.3]

Hi,

in such "cases" , i just power the board and watch it with an IR cam ->

you see, where the power goes -- or only cpu gets hot, then you damaged it (if your program was working before, without heating, otherwise try the simple test setup with all pins unused or inputs.)

[Wadeva]

Hello everyone, after reviewing our design, I discovered an unprotected pin that is connected to the chassis ground of the device. I’ll need to check if there are any other similar pins. It must be the problem.

 

[White_Fox]

---

@Wadeva wrote:

Hello everyone, after reviewing our design, I discovered an unprotected pin that is connected to the chassis ground of the device. I’ll need to check if there are any other similar pins. It must be the problem.

 

---

In this case, you better provide more information. In special the (important parts of the) schematic. A new thread is a good idea - with linking here to it.

[Andrew Neil]

New thread is here:

https://community.st.com/t5/stm32-mcus-products/protect-the-mcu-without-making-hardware-changes/td-p/725191