AM625: Keyrev API - keywriter

Hello,

Please refer to the following example:

https://github.com/TexasInstruments/mcupsdk-core-k3/tree/k3_main/examples/otp/runtime_keyrev/

BR, Prashant

Hi Prashant,

Thanks for the example!,

I already efused the keywriter ,Already generated the dual signed cert. As per the example ,(dual_cert_keyrev.h) how to generate the dual signed cert?

Attaching the steps i used to create the keywriter,

1 ./gen_keywr_cert.sh -g
2 /gen_keywr_cert.sh -t tifek/ti_fek_public.pem --msv 0xC0FFE -b keys/bmpk.pem 
--bmek keys/bmek.key -s keys/smpk.pem --smek keys/smek.key --keycnt 2 --keyrev 1
3 python3 ../../../../../tools/bin2c/bin2c.py final_certificate.bin keycert.h KEYCERT
4  make -sj PROFILE=debug
Im using a custom board , so i edited vpp function .

RJ DJ said:

My question is: Where can I find these addresses when creating my own certificate using the one-short format? How can I locate the lower and higher 32-bit addresses?

Regards,

RJ

Hello Prashant,

I came across example where a Python script is used to generate a dual-signed certificate. This script creates a file named dual_cert_keyrev.bin, which is then converted into dual_cert_keyrev.h.
I'm comparing this process to the keywriter, which generates a final_certificate.bin that is then converted into keycert.h. The keycert.h contains both the smpk and bmpk hash.

Are keycert.h and dual_cert_keyrev.h essentially the same file?

As I mentioned, I'm writing the keyrev from a Linux application using PTA. Could you clarify where the high and low 32-bit addresses are coming from? I've already generated the dual-signed certificate using sblkeywriter . Hope my question is clear, Am I missing something here? Can you shed some light on this?

Thanks and regards,

-RJ