We have isuue with XBURN otp load. Some chips dont work after xburn use and we start testing with enable jtag.
We found situation , when after xburn without error chip dont boot.
We do xburn --read and compare with ok chip. Result show big issue = XBURN dont verify and with lock destruct usable chips.
Chip with trouble we xburn twice and start working.
WTF ?
Why or how XBURN dont verify
-
mmar
- XCore Addict
- Posts: 131
- Joined: Fri Jul 05, 2013 5:55 pm
-
RitchRock
- XCore Addict
- Posts: 196
- Joined: Tue Jan 17, 2017 9:25 pm
What is your command line for XBURN? Are you using AES encryption? I've used this for sometime now with products in production and no issues.
-
mmar
- XCore Addict
- Posts: 131
- Joined: Fri Jul 05, 2013 5:55 pm
Yes we use AES and too use this xburn more as 8 years ... and alltime we hope that code in OTP is verified !
But now on XUF216 this fail. And fail on around 5% from 1000 pcs.
But now on XUF216 this fail. And fail on around 5% from 1000 pcs.