mirror of
https://github.com/Klipper3d/klipper.git
synced 2026-01-03 21:40:38 -07:00
samd_sercom: Specify the sercom explicitly in a config option
Do not infer the sercom from the config section name, as that prevents one from using SPI buses on multiple samd mcus. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
parent
df43c9e9bf
commit
d1bdde56cc
3 changed files with 18 additions and 11 deletions
|
|
@ -3793,13 +3793,17 @@ i2c_address:
|
|||
## [samd_sercom]
|
||||
|
||||
SAMD SERCOM configuration to specify which pins to use on a given
|
||||
SERCOM. One may define one section with the "samd_sercom" prefix per
|
||||
SERCOM available. Each SERCOM must be configured prior to using it as
|
||||
SPI or I2C peripheral. Place this config section above any other
|
||||
section that makes use of SPI or I2C buses.
|
||||
SERCOM. One may define any number of sections with a "samd_sercom"
|
||||
prefix. Each SERCOM must be configured prior to using it as SPI or I2C
|
||||
peripheral. Place this config section above any other section that
|
||||
makes use of SPI or I2C buses.
|
||||
|
||||
```
|
||||
[samd_sercom sercom0]
|
||||
[samd_sercom my_sercom]
|
||||
sercom:
|
||||
# The name of the sercom bus to configure in the micro-controller.
|
||||
# Available names are "sercom0", "sercom1", etc.. This parameter
|
||||
# must be provided.
|
||||
tx_pin:
|
||||
# MOSI pin for SPI communication, or SDA (data) pin for I2C
|
||||
# communication. The pin must have a valid pinmux configuration
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue