[sw,silicon_creator] The current boot log is Earlgrey specific
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
The current silicon creator boot log make assumptions that are Earlgrey specific:
- Three boot stages (
ROM,ROM_EXTandBL0) ROM_EXTandBL0have two slots, which assumes those artefacts are stored in separate, trusted flash slots.
Neither of those apply to Darjeeling, so I think we'd need to either define top specific boot log formats or expand the current structure to support other tops. Unfortunately it is not versioned so it may be difficult to introduce breaking changes. @cfrantz WDYT?
cc @pamaury @Razer6
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 by locating the current silicon creator boot-log format and its handling of Earlgrey's ROM, ROM_EXT, and BL0 stages and slots. Compare those assumptions with Darjeeling's boot flow, then determine whether top-specific formats or a backward-compatible expanded structure is needed; done means the format supports both tops without an untracked breaking change.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100