Hi,
I have some questions regarding the OTPMK key:
Thanks and regards,
Ronnie
Hi Ronnie,
Please see my answers below.
1. The OTPMK fuse value is programmed by NXP during chip manufacture. You cannot set this value.
2. The OTPMK key value is derived, it can be used on the device but cannot be read even by NXP or directly from fuses.
3. The main difference is that SW-GP2 is user-defined key, not provisioned by NXP. If the SWGP2 fuse is used as a key you can write and read locking of the fuse using SW_GP2_LOCK and SW_GP2_RLOCK.
I hope this helps!
Best regards,
Felipe
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored.
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
------------------------------------------------------------------------------
Thank you Felipe.
More questions:
1. Is the 'derived OTPMK' actually the 'crypto key' which is also based on the 'unique id' and possibly other stuff?
2. In otherwords the 'derived OPTMK' is tied inextricably to the chip. So I cannot download and update the KIB in the field if I needed to because it needs to be generated by the chip. The only way to do this without the same chip is to use the SW_GP2 key? I'm not saying I need to do this, I just want to confirm I understand this. And this is also the reason for the DEK blob stuff if I wanted to use that.
Kind regards,
Ronnie
Hi Ronnie,
1. OTPMK is unique secret key programmed and locked by NXP. The structure cannot be shared.
2. That is correct.
Best regards,
Felipe