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-16 01:17 PM
Yes, we can try this.
2024-05-16 01:19 PM
Using the STMFlashLink Utility, we have been reading the device memory and saving to a file. Later we were comparing the saved file to the original firmware file. Both the files were identical.
2024-05-16 01:21 PM
I will get back to you reading the Option Bytes.
2024-05-16 01:21 PM
Sure. I will get back to you reading the Option Bytes.
2024-05-17 12:49 AM
Please, find the option bytes from the below picture.
2024-05-17 02:04 AM
Is that what you expect, or what you read-out from a "failed" device?
2024-05-17 02:07 AM - edited 2024-05-17 02:08 AM
@EverShine wrote:So, this proves that there is no corruption in flash.
Well, no: it shows that there wasn't corruption in the ones you examined - but it doesn't prove that it never happens.
And @PLER confirmed that they had seen occurrences of Flash corruption.
This is all in the nature of undefined behaviour ...
2024-05-17 03:22 AM
Option bytes remains same for the failed and the working device. We did not see change in the Flash contents and the option bytes.
2024-05-17 04:15 AM - edited 2024-05-17 04:54 AM
Hi,
I measured some test points on the frozen MCU and observed that some pins are behaving oddly, like this:
1. NRST:
2. MCU_TX:
3. TP9/TP10
the rest of the Test Points like
TP11/12/13/14/15/16/17/19 |
are low.
2024-05-17 05:02 AM
Is a pull-down resistor now installed at BOOT0? If no, why not?
Have you evaluated the Device Errata in the context of your problem?