Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial WB55 support. #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Initial WB55 support. #2

wants to merge 1 commit into from

Conversation

rubdos
Copy link

@rubdos rubdos commented Sep 27, 2019

  • Where does the SVD come from?
  • feature flags on all relevant peripherals (is there a way to automate this?)

Accompanies drone-os/drone#1

@valff
Copy link
Member

valff commented Sep 27, 2019

In my experience there are always many small differences in peripherals across STM32 families. I doubt it will even compile if we enable them all. I propose to start without any peripheral (in Drone terms) mappings. So this crate will initially provide just register and interrupt mappings.

@valff
Copy link
Member

valff commented Sep 27, 2019

If you wonder, we use so many crates here because they dramatically reduce compile times. Register mappings generation parallelizes nicely.

@valff
Copy link
Member

valff commented Sep 27, 2019

To clarify, periph-* crates just group registers by peripherals. For example this allows you to write code generic over UART1, UART2, ..., LPUART1. The problem is that often these peripherals have small differences, so they should be addressed by peripheral crates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants