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.

Sign up for GitHub

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

Jump to bottom

boards/common/blxxxpill: Fix pin conflicts in periph_conf #18785

Merged
merged 4 commits into from
Oct 27, 2022
Merged

boards/common/blxxxpill: Fix pin conflicts in periph_conf #18785

merged 4 commits into from
Oct 27, 2022
+9,047 −66

Commits on Oct 27, 2022

  1. makefiles/cflags.inc.mk: Add -Wno-missing-field-initializers to CXXFLAGS 

    This allows including C headers from C++. It sadly reduced the
diagnostics on C++ code as well, were there warning may make sense as
unintended side effect. We may be able to drop that later on, when more
C APIs are properly wrapped in native C++ APIs, so that C headers do no
longer need to be compatible with C++ compilers.
    @maribu
    maribu committed Oct 27, 2022
    Configuration menu
    Copy the full SHA
    16df27c View commit details
    Browse the repository at this point in the history

  2. cpu/stm32/periph_qdec: support pin remap for F1 

    Add support to route peripheral to alternative pins for the STM32F1
family.
    @maribu
    maribu committed Oct 27, 2022
    Configuration menu
    Copy the full SHA
    b6845ce View commit details
    Browse the repository at this point in the history

  3. cpu/stm32/periph_pwm: support pin remap for F1 

    Add support to route timer peripheral to alternative pins for the
STM32F1.
    @maribu
    maribu committed Oct 27, 2022
    Configuration menu
    Copy the full SHA
    5ddc332 View commit details
    Browse the repository at this point in the history

  4. boards/common/blxxxpill: rework periph configuration 

    The peripheral configuration has been completely reworked to resolve
pin conflicts while provided as much of the peripherals as possible.
The changes include:

- Move `I2C_DEV(0)` from PB6/PB7 to PB8/PB9 to solve pin conflict with
  `QDEC_DEV(2)`.
- Use pins PB0, PB1, PB4, and PB5 for PWM instead PA8, PA9, PA10, and
  PA11
    - PA9 and PA10 is in pin conflict with `UART_DEV(0)` which is used
      for stdio with `stdio_uart`, PA8 was in conflict with
      `QDEC_DEV(0)`, PA11 was in conflict with USB D-
- Use PB6, PB7 as `QDEC_DEV(0)` (previously `QDEC_DEV(2)`), as this is
  the only completely conflict free setting
- Use PB4/PB5 instead of PA6/PA7 for QDEC_DEV(1)
    - This fixes a pin conflict with `SPI_DEV(0)` MISO (and
      `ADC_LINE(4)`)
- Only provide QDEC at PB4/PB5 when PWM is not used to avoid conflict
- Only provide QDEC at PA8/PA9 when UART is not used to avoid conflict
- Use SPI2 (PB15, PB14, PB13, PB12) as `SPI_DEV(0)` instead of SPI1,
  use SPI1 (PA7, PA6, PA5, PA4) as `SPI_DEV(1)`
- Only provide `SPI_DEV(1)` if the ADC is not in used to resolve a
  pin conflict
- Move PB0 and PB1 at the end of the ADC lines (previously
  `ADC_LINE(6)` and `ADC_LINE(7)`, now `ADC_LINE(8)` and `ADC_LINE(9)`)
   - Only provide them when PWM is not in use (to resolve pin conflict
     with PWM)
   - Also do not provide them for the Blackpill boards, which are
     missing pins PB0 and PB1 on the headers

To make life of users easier, a Pinout diagram with the new
configuration was added.
    @maribu
    maribu committed Oct 27, 2022
    Configuration menu
    Copy the full SHA
    051a1f1 View commit details
    Browse the repository at this point in the history