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: 133
- Joined: Fri Jul 05, 2013 5:55 pm
-
RitchRock
- XCore Addict
- Posts: 202
- 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: 133
- 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.
-
avrobot
- Member++
- Posts: 19
- Joined: Mon Jun 04, 2018 4:26 am
Yes this a major issue for us also. Xmos not helping us and we get around 7% reject parts for last year now. We are trying now xburn from v15.3 .. will see how we go.
-
michaelf
- Member++
- Posts: 19
- Joined: Thu Mar 14, 2024 7:44 pm
What Xmos parts are you using, and have you had any better results with v15.3.0 of the tools?