oxidecomputer / oxidecomputer/hubris
`xtask flash` should get its instructions from app.toml somehow
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
xtask flash currently has a hardcoded table of board names for finding flashing config files. That's going to become annoying. It should take direction from app.toml instead.
I'm imagining something like
[flashing]
method = "openocd"
config = "../whatever.cfg"
where the paths are relative to the app.toml itself, as usual.
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 at the xtask flash entry point and find the hardcoded board-name table used to locate flashing configuration files. Inspect how app.toml is parsed and how paths are resolved relative to it. Done means flashing instructions can come from the proposed app.toml configuration instead of the board-name table, including the configured method and relative config path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, embedded-iot, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100