Skip to content

[doc] Fixes and improvements for the ot-sku documentation - #22

Merged
AlexJones0 merged 5 commits into
lowRISC:mainfrom
AlexJones0:doc_improvements
Sep 14, 2026
Merged

AlexJones0 merged 5 commits into
lowRISC:mainfrom
AlexJones0:doc_improvements

Conversation

@AlexJones0

Copy link
Copy Markdown
Contributor

A pass over and improvement of most of the key documentation already checked into ot-sku:

  • Small fixes to the release flow documentation, with clarifications, additions and improvements where necessary to help avoid mistakes and troubleshoot problems. The signing logs are made more explicit in the instructions.
  • Much more information in the main README.md with relevant links, guidance on where to look for information if you run into problems, etc.
  • Missing copyright headers added to the Markdown files, which don't strictly require them but can have them just fine.

See the individual commit messages for more details.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
These can be added with comments which aren't rendered by Github and the
vast majority of modern Markdown renderers - so no reason not to add
them to these files as well, even if not strictly checked.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
Comment thread README.md Outdated

@pamaury pamaury left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @AlexJones0 , that's a nice improvement. There is a little thing about using the repository where the documentation is not up to date (blame me for forgetting to update it), it would be nice if you can update it at the same time.

* Fix the override mechanism to point to the newer `override_module`
  flow instead of the legacy `PROV_EXTS_DIR` flow.
* More links where relevant.
* Switch recommendation from `bazel` to `bazelisk`, and point out
  dependencies on OpenTitan repository if you want to manually run the
  CI flows.
* Example should be performed from the `earlgrey_1.0.0` branch.
* Link to Github release documentation, as this is the really important
  part.
* Point towards where you can acquire hsmtool, with a note on the
  current transition (intended to be deprecated in the near future).
* Add a quick link to the existing in-tree SoftHSMv2 documentation, but
  note that this is for testing flows only and not intended for real
  release flows.
* Add some extra information on licensing and further links.

Also fix the Markdown styling to conform to one-sentence-per-line.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
* Fix broken relative link to the release flow.
* Minor grammar fixes.
* Fix Markdown styling to be one sentence per line.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
* Add styling to make warnings stand out a bit more.
* Make the step 2 instructions more rigorous; specifically define the
  SKU that is being used to avoid path issues, capture the
  `OT_SKU_PATH` and `HSMTOOL` path in environment variables to make it
  easier to directly copy commands.
* Make sure that the signatures are actually staged, and add a note
  about forcefully overriding the .gitignore. Also make the note about
  adding a signing log more explicit.
* Add a short section at the end on troubleshooting with advice for
  common problems that have already been seen, or problems that we
  anticipate it might be likely to see in the future.
* Fix grammar & typos in some places.
* Fix markdown styling to be one sentence per line.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
Comment thread doc/create_release.md
popd
pushd presign_rom_ext
/path/to/hsmtool $HSMTOOL_CUSTOM_ARG exec rom_ext.json
$HSMTOOL $HSMTOOL_CUSTOM_ARG exec rom_ext.json

@AlexJones0 AlexJones0 Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pamaury @cfrantz As previously discussed, we probably need to figure out if this should be generic-per-SKU or not. The provisioning hsmtool directives are per-SKU, whereas the ROM_EXT directives are not. Unless there's a good reason, we should decide either way and make the change.

@AlexJones0
AlexJones0 merged commit ff9c7b3 into lowRISC:main Sep 14, 2026
2 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants