Open maribu opened 11 months ago
@maribu I could provide configuration for SPI in nucleo-f070rb
using ONLY datasheet - I do not have access to this board.
Hmmm ... I'm looking at pinout of nucleo-l152 - and Arduino D11, D12, D13 are connected to PA7, 6 and 5. This is configured in periph_conf.h and is compatible with datasheet (page 40). What I'm missing?
Hmmm ... I'm looking at pinout of nucleo-l152 - and Arduino D11, D12, D13 are connected to PA7, 6 and 5. This is configured in periph_conf.h and is compatible with datasheet (page 40). What I'm missing?
Indeed, that looks all fine.
I guess I confused it with nucleo-l433rc
which indeed has configured the incorrect bus. I'll update the tracking accordingly.
So that I have this handy later on, I paste the crucial part of the test output on the nucleo-f446re
here:
Starting test for GPIO-IRQ (both-edges) at tests/periph/selftest_shield/main.c:588
FAILURE in tests/periph/selftest_shield/main.c:596
FAILURE in tests/periph/selftest_shield/main.c:601
FAILURE in tests/periph/selftest_shield/main.c:606
FAILURE in tests/periph/selftest_shield/main.c:611
FAILURE in tests/periph/selftest_shield/main.c:616
FAILURE in tests/periph/selftest_shield/main.c:628
FAILURE in tests/periph/selftest_shield/main.c:632
FAILURE in tests/periph/selftest_shield/main.c:637
FAILURE in tests/periph/selftest_shield/main.c:642
[FAILED]
Note: This failure is sporadic.
This is intended to track bugs found by the peripheral selftest, so that the bugs are not only found but eventually also fixed :)
nucleo-f070rb
: Missing peripheral configuration for SPI (see https://github.com/RIOT-OS/RIOT/pull/20075)nucleo-f302r8
: Missing peripheral configuration for the Arduino SPI bus (the provided bus(es) is not compatible with any Arduino shields, as it is connected to the wrong pins)boards/nucleo-l433rc
: Missing peripheral configuration for the Arduino SPI bus (the provided bus(es) is not compatible with any Arduino shields, as it is connected to the wrong pins)boards/nucleo-wl55jc
: Incorrect SPI bus declared asARDUINO_SPI_D11D12D13
(see https://github.com/RIOT-OS/RIOT/pull/20085)uart_poweroff()
is not powering off UART (see https://github.com/RIOT-OS/RIOT/pull/19926)nucleo-f103rb
: I2C test failing (see https://github.com/RIOT-OS/RIOT/pull/20100)nucleo-f303re
(or rather STM32F3): SPI clock polarity on idle level not correct (see https://github.com/RIOT-OS/RIOT/pull/20084)nucleo-f446re
(or rather STM32F4): SPI transfer is faster than possible with the requested SPI clockassert()
when the used SPI clock is faster than expected, as this violates the API contract (see https://github.com/RIOT-OS/RIOT/pull/20084 for the missingassert()
)nucleo-f446re
(or rather STM32F4): The GPIO IRQ test occasionally failsp-nucleo-wb55
: SPI clock frequency not correct (fixed by https://github.com/RIOT-OS/RIOT/pull/20089 and https://github.com/RIOT-OS/RIOT/pull/20084), clock polarity not honored (fixed by https://github.com/RIOT-OS/RIOT/pull/20084)nucleo-f303re
(or rather STM32F3): GPIO test fails while debuggingnucleo-f303re
(or rather STM32F3): Hard fault duringadc_init()
in the ADC test.ztimer
(viaperiph_adc
). Fixed by https://github.com/RIOT-OS/RIOT/pull/20096gd32vf103c-start
(or rather GD32VF103): PWM not working correctly