cyberblak said:hi cdc
it could be a latchup, but it depends on what's connected to it. If it's I/O is connected to a couple of loads that source/sink a high current and the firmware froze with those I/O active, it could lead to an overheating.
However, you must make sure that the MCU can withstand the environmental conditions it will be in and that it will reset properly if it loses its power for a few seconds.
Hope this helps,
cyberblak
ravimarcus said:MCU latch up can occur due to EMI, RFI and noise. If the MCU has a WDT, it is better to enable it so that when a latch up occurs, the WDT will reset the uC and the uC can start executing the code again.
Cheers
Ravi
PaulHolland said:Hi, This is clearly a latch-up situation in which all CMOS ports inside your MCU are conducting ant that is why the unit is so hot.
If you have long cables connected to I/O pins use small resistors between your I/O lines (1 - 10K) and your external device (only on input pins !). You can also connect a diode to power supply rail or a zener diode of 5.1 V to ground from I/O pin (input).
If your reset line of your MCU is floating make sure it is connected to a logical high or low level whatever is needed.
This will solve your problems.
Paul.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?