We need to be able to change board names on update
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- embedded-iot
Research direction
Start by reviewing the update-server board-name validation and how board names are represented in caboose BORD chunks. Clarify the desired compatibility rules for current and future board revisions, then define tests covering accepted and rejected firmware updates.
Written by the indexing model from the issue text.
Description
Currently, update-server won't accept an update if the board name in the caboose doesn't match the board name of the current image. This is generally good and right.
However, it's becoming apparent that this might need to change. The Gimlet E/F revs are not different to firmware, so we'd sure like to make a combined gimlet-ef image that covers both -- but the gimlet-e boards currently deployed wouldn't accept such a thing. For now, we're going to make separate E and F images.
One possible approach to this: include multiple BORD chunks in the caboose of the firmware and accept the image if any one names the current board. That isn't future-proof though, where if we make a mostly-identical G rev for design-for-manufacturing reasons, it should be able to run the existing E/F firmware... but its name won't be in the caboose yet.
So, maybe we need something more nuanced.
@Aaron-Hartwig @labbott @mkeeter @jgallagher
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
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.
More from oxidecomputer/hubris
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oxidecomputer/hubris#2593 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oxidecomputer/hubris#2577 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
oxidecomputer/hubris#2699 ·
-
⚠️ ereport control-plane-agent root-of-trust service processor
Difficulty 5/5 Over a week Newbie friendliness 25/100
oxidecomputer/hubris#2698 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
oxidecomputer/hubris#2689 ·
All issues in oxidecomputer/hubris
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100