rust-embedded / rust-embedded/svd2rust
RISC-V settings file is not applied when using `svd2rust@0.35.0` and `settings_file`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 857
- Forks
- 164
- PR merge metrics
- No merged PRs in 30d
Description
When using svd2rust@0.34.0 and Config.settings, the YAML configuration is loaded from the specified path and applied as expected. Upon updating to svd2rust@0.35.0 and instead using Config.settings_file with the same path, the configuration is no longer applied to the generated PAC.
Contributor guide
No contributing guide indexed for this repository
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
Compare how Config.settings and Config.settings_file are handled between svd2rust@0.34.0 and svd2rust@0.35.0, then reproduce the issue with the same YAML path and SVD input. Done means the settings file is loaded and applied to the generated PAC when using Config.settings_file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100