Skip to content

Commit ed46779

Browse files
committed
[ot] docs/opentitan: keymgr.md: Document new keymgr property
Signed-off-by: Alex Jones <[email protected]>
1 parent 591848e commit ed46779

File tree

2 files changed

+18
-0
lines changed

2 files changed

+18
-0
lines changed

docs/opentitan/earlgrey.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -206,6 +206,10 @@ There are two modes to handle address remapping, with different limitations:
206206
whenever possible. To enable this legacy mode, set the `alias-mode` property to true:
207207
`-global ot-ibex_wrapper.alias-mode=true`
208208

209+
### Keymgr
210+
211+
See documentation in [`keymgr.md`](./keymgr.md).
212+
209213
### OTBN
210214

211215
* `-global ot-otbn.logfile=<filename>` output OTBN execution message to the specified logfile. When

docs/opentitan/keymgr.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# OpenTitan Key Manager support
2+
3+
## Properties
4+
5+
- `-global ot-keymgr.disable-flash-seed-check=true` can be used to disable the
6+
data validity check in the Keymgr for loaded flash secrets (the owner and
7+
creator seed). This validity check ensures that the loaded key is not all-zero
8+
or all-one (and thus probably uninitialized). When emulating OpenTitan, it may
9+
be useful to be able to advance using uninitialized keys due to a lack of flash
10+
info splicing, to bypass the need to run through an entire provisioning flow.
11+
- Note also that the fatal Keymgr alert caused by failing this check should
12+
not appear for unprovisioned flash if flash scrambling is implemented (and
13+
enabled). This is because the garbage unscrambled data that is read will not
14+
pass this check.

0 commit comments

Comments
 (0)