Consider incorporating fixes and extensions to vendor SVD files maintained by the svd2rust related projects
Nobody has claimed this yet.
- Dominant language
- Ada
- Stars
- 71
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
The Rust embedded community maintains a considerable set of patches against vendor-supplied SVD files which add both corrections for vendor SVD errata, and also enhancements.
E.g. this repository is for stm32 "peripheral access crates" (which I believe is the most mature):
https://github.com/stm32-rs/stm32-rs
The patches are maintained at yaml files for readability.
e.g. https://github.com/stm32-rs/stm32-rs/tree/master/devices/common_patches
... and are applied against the vendor-supplied SVD files here:
https://github.com/stm32-rs/stm32-rs/tree/master/svd
... by https://github.com/rust-embedded/svd2rust
This project may want to work with the svd2rust and/or stm32-rs maintainers (there is overlap between the two) to maintain these fixes and/or get them applied to the vendor files?
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 by reviewing the stm32-rs common_patches and svd directories linked in the issue, then examine how svd2rust applies those patches. Identify the relevant svd2ada integration point and discuss scope with the svd2rust or stm32-rs maintainers. Done would require an agreed approach and incorporation of the applicable fixes or extensions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100