RFC-0669: MCU firmware descriptor in the manifest - #640
Merged
Conversation
Files RFC-0669, an optional Layer-1 `firmware` descriptor (series, core, version, software components) so a manifest can state which firmware identity an MCU node runs, complementing RFC-0018 `minimal_node`. The field set comes directly from the request-for-comment exchange with STMicroelectronics engineers on STM32CubeF4#203, who spelled out what an STM32 firmware description should carry and argued for per-series scope. This RFC generalizes their four fields to any MCU vendor (STM32 is the motivating instance; ESP32 and nRF are declarable too), keeps per-series as per-manifest, and adds no primitive. Draft for maintainer decision; the companion part-number hardware descriptor they also described is scoped out to a follow-on RFC. Additive and pre-v1.0: every existing manifest stays valid, manifest_version stays 0.1. No schema change lands with this Draft; acceptance and implementation are separate gated steps. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Ido Yahalomi <greenvh@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Files RFC-0669 (Draft, Spec): an optional Layer-1
firmwaredescriptor block (series,core,version, softwarecomponents) so a manifest can state which firmware identity an MCU node runs, complementing RFC-0018minimal_node.Why
The field set comes directly from a request-for-comment exchange with STMicroelectronics engineers on STM32CubeF4#203, who specified what an STM32 firmware description should carry and argued it should be per-series. This RFC generalizes their four fields to any MCU vendor (STM32 is the motivating instance; ESP32 and nRF are declarable), keeps per-series as per-manifest, and adds no primitive.
Adding manifest fields is a one-way door, so this is filed as a Draft for maintainer decision, not an implemented schema change. The companion part-number hardware descriptor ST also described is scoped out to a follow-on (Alternative 3).
Scope
manifest_versionstays0.1.docs/rfcs/README.md(Kind: Spec, State: Draft).Rollback
Revert the single commit; it is a new doc plus one index row.
🤖 Generated with Claude Code