WolfSSL
/
wolfBoot
mirror of https://github.com/wolfSSL/wolfBoot.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Integrated documentation for otpgen

pull/468/head
Daniele Lacamera 2024-07-09 09:35:14 +02:00
parent 2082bd003c
commit b59f11bc88
1 changed files with 19 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/flash-OTP.md
View File

@ -20,9 +20,26 @@ The public keys are stored in the OTP area, after an initial 16-byte header that
keys stored, the size of each key, and other information.
In order for wolfBoot to start authenticating the firmware images at boot and upon update, the public keys
must be provisioned to the OTP area in a separate step, as described in the next section.
must be provisioned to the OTP area in a separate step, as described in the next sections.
### Provisioning the public keys to the OTP area
Depending on the target device, you can either prepare a binary image of the OTP area content, or use `otp-keystore-primer` firmware to directly provision the keys on the target.
### Creating an image of the OTP area content
It is possible to create a binary image of the content for the OTP area. The resulting file (otp.bin) can be manually provisioned using any external tool that allows writing to the target OTP area.
To compile the otp-keystore-gen tool using the current keystore content:
```
make otpgen
```
And then, to create the image file `otp.bin`:
tools/keytools/otp/otp-keystore-gen
### Directly provisioning the public keys to the OTP area (primer)
After enabling the `FLASH_OTP_KEYSTORE` option in your `.config` file, when you compile wolfBoot by running "make",
an additional application called `otp-keystore-primer` is generated under `tools/keytools/otp`. This application is used to