rust-embedded / rust-embedded/svd2rust
Some core peripherals get an API
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 857
- Forks
- 164
- PR merge metrics
- No merged PRs in 30d
Description
I think #74 was supposed to fix that. However, in the STM32l4x2.svd that I use, there are peripheral definitions for STK (the systick, SYST) as well as for FPU_CPACR and SCB_ACTRL. I do not know how common such discrepancies are, but what's the best way to fix them?
My guess:
- For
STK, the peripheral should be renamed to the properSYST, like in @adamgreig's stm32-rs project - For those peripherals with multiple separate register blocks, detect whether one of the known core peripherals is a prefix of the peripheral name
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
Start by reading issue #74 and comparing the STK, SYST, FPU_CPACR, and SCB_ACTRL definitions in STM32l4x2.svd with the behavior expected by the generator. Review the corresponding naming and core-peripheral handling in the stm32-rs project. Done means the intended handling of these peripheral definitions is agreed and discrepancies are covered by the generator's tests.
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
- Needs clarification
- Newbie friendliness
- 25/100