Adding mint, a CLI for firmware parametrisation - #533
Merged
Conversation
tomrford
requested review from
a team,
RandomInsano,
berkus and
rahul-thakoor
as code owners
August 18, 2026 19:57
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
2 participants
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.
I'd like to add mint to the list of tools. Mint is the culmination of a year or so of trying to build 'the best way' to enable parametrisation of embedded firmware. The entire CLI is built in rust and also provides a mint-core crate to bring the functionality into your own apps. It's tailored more towards embedded C than rust with support for header generation, schema fingerprinting, native fixed point support and a few different ABIs for the microcontrollers I'm targeting (more suggestions are always welcome). You can use mint as your single source of truth for configuration structs and get compile-time validity guarantees and free runtime compatibility checks that CRCs or other simpler methods can't provide.