We should update `sw/device/silicon_creator/rom/keys/README.md` or any other relevant documents to describe how this works. There are downstream integrators trying to reproduce this as part of their post-silicon prep plan.
Open
Nobody has claimed this yet.
Component:Doc
Earlgrey-PROD Candidate
Priority:P2
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
We should update `sw/device/silicon_creator/rom/keys/README.md` or any other relevant documents to describe how this works. There are downstream integrators trying to reproduce this as part of their post-silicon prep plan.
Downstream integrators are usually not familiar enough with the codebase to poke around Bazel config files.
Originally posted by @moidx in https://github.com/lowRISC/opentitan/pull/18675#discussion_r1198444236
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with sw/device/silicon_creator/rom/keys/README.md, then inspect the relevant Bazel configuration to understand how the process works. Document the steps and configuration downstream integrators need to reproduce it for post-silicon preparation, using any other relevant documents identified during that review.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100