[dice,ot_certs] replace the manually-updated max-size of payload in CWT codegen
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
This is a follow-up issue of https://github.com/lowRISC/opentitan/pull/24754.
https://github.com/lowRISC/opentitan/blob/a8c0633016e90d705338b80a938742f44d12115e/sw/device/silicon_creator/lib/cert/cwt_dice_chain_entry.hjson#L13-L15
https://github.com/lowRISC/opentitan/blob/a8c0633016e90d705338b80a938742f44d12115e/sw/device/silicon_creator/lib/cert/cwt_dice_chain_entry_input.hjson#L13-L15
Currently, `cwt_dice_chain_entry.hjson` and `cwt_dice_chain_entry_input.hjson` both depend on the `max-size` of `cwt_dice_chain_entry_payload.hjson`. But that value relies on manually updating currently. If that doesn't fit, the error would be postponed until runtime check.
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/lib/cert/cwt_dice_chain_entry.hjson and cwt_dice_chain_entry_input.hjson, then review the referenced follow-up pull request and cwt_dice_chain_entry_payload.hjson. Determine how code generation currently consumes max-size and replace the manual dependency so payload-size mismatches are caught before runtime.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100