2025-02-11 02:09 PM
We are on the second generation of prototype here.
On the first generation I had an MCU fail for reasons I couldn't trace. This was from a set of six.
I have now powered seven of the second generation two have had MCU failures. The second failure was on the prototype's initial turn on. No code had been loaded into it. A hole blew out of the part when power was applied.
All failed parts then shunted the VCC to ground with a low impedance, less than 100 ohms.
I have included part of our schematic. Do you see anything that could explain this failure?
Best regards,
Bill Grimm - Zdiode
2025-02-11 02:23 PM
> The second failure was on the prototype's initial turn on. No code had been loaded into it. A hole blew out of the part when power was applied.
Definitely suggests overvoltage on a pin.
Schematic looks okay.
I would guess one of the signals coming in exceeds the allowable voltage, possibly due to a spike on startup.
If parts are still responsive, you may be able to determine which pin or port is blown by set each pin high (set pin as output and set GPIO->ODR) and see which one still reads low (read GPIO->IDR).
Probably this spike is happening on the other parts too but it just hasn't caused failure (yet). Putting a scope on each incoming pin and monitoring during startup may be informative.
1/6 and 2/7 are way above the expected failure rate of the chip.
2025-02-11 03:14 PM
@TDK wrote:Definitely suggests overvoltage on a pin.
+1
@TDK wrote:I would guess one of the signals coming in exceeds the allowable voltage, possibly due to a spike on startup..
+1
The schematic shows that there is (at least) 24V elsewhere in the system; also lots of external connections with "motor" in the name...
And no sign of any protection or suppression on any of the external connections.