lowRISC / lowRISC/opentitan

[keymgr, doc] Programmers guide need more details

Open
#22,344 0 comments 0 reactions 2 assignees View on GitHub

@ballifatih is already working on this.

Since Apr 11, 2024.

prodc-integration
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Description

There are plenty of missing details on how firmware/programmer shall use key manager:

  1. Example for loading secrets/keys (e.g. what ROM/ROM_EXT shall do)
  2. Example of side loading key into different engines, selecting key size if applicable
  3. Example of using key manager to get software share

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.