Repository navigation
Require a target core for firmware generation - #50
Merged
Merged
Conversation
The firmware command becomes a parent, and the ATxmega target moves into an atxmega subcommand that carries the metadata argument and every option. A bare generate firmware now prints the help and exits 1. The article now documents the two kinds of generated file, adds a section for --ios, and warns that a second run replaces the implementation files.
glopesdev
force-pushed
the
generate-firmware-core
branch
from
September 21, 2026 22:07
b80f794 to
6434c84
Compare
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
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.
Requires a target core on
generate firmware, which mirrors the target language already required ongenerate interface.GenerateFirmwareCommandbecomes a parent that registers subcommands and nothing else, and a newGenerateATxmegaFirmwareCommandcarries the metadata argument,--ios,--implementationand--output. A baregenerate firmwareprints the help and exits 1.A metadata path now follows the core name, so
generate firmware path/to/device.ymlbecomesgenerate firmware atxmega path/to/device.ymland the help text and the article are improved alongside it.