MfgTool fails to load updater when OTP_CRYPTO is burned

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MfgTool fails to load updater when OTP_CRYPTO is burned

743 Views
erwinw
Contributor III

Presently, updater_ivt.sb must be encrypted with one of two states (elftosb -z or elftosb -k) depending upon the initial state of the OTP hardware.

This presents two situations for failure during manufacturing:

1) A fresh FAB board will program OTP_CRYPTO and require a - z encryption to load updater_ivt.sb

2) A previously burned OTP_CRYPTO will require a -k encryption to load updater_ivt.sb

Rather than maintain two encryption states of updater_ivt.sb, the OTP_CRYPTO should be refreshed after otp_burner_ivt.sb and before updater_ivt.sb is loaded within MfgTool.

Is there a way to issue a device reset after the opt_burner_ivt.sb has been run? If not, what is the recommended way to streamline bit burning into the manufacturing process?

Again, if we can simply force an OTP refresh once burned, this would not be an issue.

Labels (1)
0 Kudos
2 Replies

569 Views
YixingKong
Senior Contributor IV

Erwin, please click Correct Answer/Helpful Answer if your question got answed.

Thanks,

Yixing

0 Kudos

569 Views
PeterChan
NXP Employee
NXP Employee

If the updater_ivt.sb is encrypted by elftosb.exe with the option "-z -kcustomkey.txt", it should work on all boards no matter OTP_CRYPTO was blown or not. Actually, the otp_burner_ivt.sb is also using the same trick.

0 Kudos