2024-05-16 03:18 AM - last edited on 2024-05-17 01:29 AM by SofLit
We have a product containing the STM32G030K8T6 MCU. The code is working like expected and the product is meeting all specifications. The product is battery powered and can be charged via USB.
If the product is assembled it will go into a burn-in test where 70 plus products will be charged and de-charged between 3 to 10 times. During this test 1 to 3 products are failing, and with failing I mean the MCU does not advance further or freeze as shown in the below picture.
It stops at the following line of code:
Currently we are at a dead end situation, does anybody has any suggestions?
Thanks a ton!
2024-05-18 03:06 PM - edited 2024-05-18 03:07 PM
You / Your team were told you to instrument Error_Handler() a month ago.
https://community.st.com/t5/stm32-mcus-products/mcu-stm32g030k8t6-hangs/m-p/665657
With __FILE__ / __LINE__ you can see exactly where it failed.
If you instrument it further it could perhaps see GPIO or MCU state information in these conditions. Or provide some interactivity so you could further query/probe the situation.