I am provisioning my PFR keystore as follows:
$BLHOST_COMMAND key-provisioning enroll
$BLHOST_COMMAND key-provisioning set_key 12 32 #UDS Code
$BLHOST_COMMAND key-provisioning set_user_key 3 "$SBKEK_REVERSED" #SBKEK for SB2p1 Images
$BLHOST_COMMAND key-provisioning set_user_key 11 "$USERKEK_REVERSED" #USERKEK for SB2p1 Images
$BLHOST_COMMAND key-provisioning set_key 7 16 #PRINCE region 0 Key
$BLHOST_COMMAND key-provisioning set_key 8 16 #PRINCE region 1 Key
$BLHOST_COMMAND key-provisioning set_key 9 16 #PRINCE region 2 Key
$BLHOST_COMMAND key-provisioning write_key_nonvolatile 0 #Commit keys to PFR
This seems to work for the SBKEK, USERKEK, and PRINCE keys. However, when I go to load the UDS code, it appears that it has an index of "15" and is therefore sent to the AHB.
Upon re-construction of the UDS code, I get all zeros. What am I doing wrong?
Hi @awseiger
I hope you are doing well! According your results after reconstructing the UDS , it could be the case that the PUF is blocking the output of key data (see 2.11 PUF DisableSetKey from AN12324).
To narrow down this: Could you try to use the elftosb gui to provision the Key ?
Download link:
https://www.nxp.com/webapp/Download?colCode=elftosb_gui_1.0.12&appType=license&location=null
My apologies for the delay,
Best regards,
Diego