nrf52382 firmware program lose

[lulu]

After nrf52382 is written into the firmware program, the test runs OK. After it is placed for a period of time, it is checked again. It is found that it is not running. Use the JLINK tool jflash to read the data. Why is this

[Jørgen Holmefjord]

• Are you experiencing this on a DK or a custom board?
• If running on a DK, is LED5 on/blinking?
• How is the board powered?
• Have you measured that the voltage is correct when you experience this issue?
• Which FW are you running on the board? Did you make any modifications?
• Are you seeing this on a single board, or on multiple boards?
• Can the problem be recreated consistently?

[Jørgen Holmefjord]

Sounds like it could be a board-issue then. If the chip does not get power, it will not do anything useful.

Did you manage to recover the failing boards? If so, how did you do that?

Have you examined the failing boards closely, to make sure there is no shorts, etc.?

[lulu]

Find the board, re brush the program, run well

[Jørgen Holmefjord]

Not sure I understand you correctly, 

lulu said:

and there was no power when it was found out

Did you power off the board yourself, or did it power off by itself? Did a power cycle resolve the issue?

lulu said:

Find the board, re brush the program, run well

By re brush, do you mean that you programmed the application again? I assume that the board was powered and working correctly at this point ? Apart from the application possibly?

Did you debug the application before re-flashing, to see if there was any error codes reported, etc? 

[lulu]

Yes, reprogramming the IC. After reprogramming, the circuit board works normally. Does it mean that the circuit board has no problem? Test before programming, unable to connect to JLINK. If it is a crash, there should be watchdog reset

[Jørgen Holmefjord]

If reprogramming the application solves the issue, it sounds like there could be something in the application that causes this, possibly an error code or similar that puts the device in an endless loop. If you debugged the application, you should have been able to check this.

Are you doing some flashwrites or similar operations in the application, which can cause errors after a certain amount of time?