To handle different revisions of the board with same configuration, one ADC channel was added to the configuration and the last two ADC lines were reordered. It shouldn't affect existing applications.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
- GPIO2 (LED1_PIN) is used as SPI signal, not only if `sdcard_spi` is enabled. herefore, it must not be defined as LED pin if `periph_spi` is used.
- GIO4 (LED2_PIN) is used by the SDMMC Host Controller as SD Card DAT1 signal and must not be defined as LED pin in that case.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
Migration to the new Arduino I/O mapping, which was not fully covered in PR #19759 when the new Arduino I/O mapping was introduced and the feature handling was changed.
The channel of PWM_DEV(0) that conflicts with the I2C SCA signal is replaced by another channel. PWM_DEV(1) is defined in addition if `periph_spi` is not used.
At least on the samr21-xpro used for hardware in the loop testing, the
terminal did not attach in time after the reset to capture all of the
output.
This adds the `test_utils_interactive_sync` module to wait for an `s`
to be received via `stdio` before starting to print to sync with the
test scripting.
The Adafruit Clue and Itsybitsy nRF52 also use the Adafruit nRF52
Bootloader which has a common module that can be used.
Especially the Itsybitsy nRF52 (mis)uses the nrfutil programmer
target and has a lot of redundant code.
Furthermore, the Double Tap Magic Value used by both boards
is incorrect for using the USB Bootloader.
When using `OUTPUT=COLORTEST` the return value of the unit test's
`main()` on failure was `0`, while it should be `1`. As a result,
running the unit tests from a script using
$ OUTPUT=COLORTEXT make BOARD=native64 RIOT_TERMINAL=native -j32 flash term -C tests/unittests
would not catch a test failure.
This commit changes the behavior so that `0` is returned on success
and `1` on failure for both regular and colored text output.
This allows using and compiling the URL handling functions of sock_util
without a network stack used.
Co-authored-by: benpicco <benpicco@googlemail.com>
Use pseudomodules to add a dependency on the relevant feature:
periph_spi if the abp2_spi pseudomodule is selected,
or periph_i2c if the abp2_i2c pseudomodule is selected.
