2025-10-23 1:55 PM
We have a batch of custom boards using the STM32H725IGK3 and have experienced several failures getting started with them as the SWD interface appears to be fried. Initially we thought just bad luck with the first couple (inexperienced engineers or ?) but the most recent unit failed after a few successful programming and debugging sessions.
Do these processors need special handling or design considerations ? Our debug header follows previous designs, with Vcc, GND, nRST, SWDIO, SWCLK provided. nRST is gated with a couple other inputs to the MCU while SWDIO and SWCLK just have 100R series resistors to protect possible voltage conflict. So far just default 3v3 supply.
When the boards were working, SWDIO showed Vcc while SWCLK showed 0V before any connections (expected based on internal pullups) while now the pins show about 0.8V until the STLINK/V2 is connected (upon which its pullup/downs take over).
The STLINK pod has been tested and working on a NUCLEO_H723.
It looks like we'll need the MCUs replaced (BGAs, ughh :( but we're not going to get far if they only last a day ...
2025-10-23 4:02 PM - edited 2025-10-23 4:04 PM
> custom boards using the STM32H725IGK3 and have experienced several failures
Perhaps an issue in the schematic design. Post it if you can. Look at VDD voltages. Ensure VCAP pins are 1.2 V and has decoupling caps. Connect all VSS pins.
The processors are quite robust.
Nucleo boards have a good hardware design. If you have the same design as those, they won't fail after a day.