boards/nucleo64: Add Compile Warning about LED0 when using SPI#21338
boards/nucleo64: Add Compile Warning about LED0 when using SPI#21338maribu merged 1 commit intoRIOT-OS:masterfrom
Conversation
|
The CI was unhappy because the warning was printed to @mguetschow suggested to print the warning to stderr, that's what the fixup now does. One thing that remains is that the warning will be printed a lot for commands like I added the "Nucleo64" remark so that it's a bit more obvious what causes the warning. |
Reminds me of this printout for PSA Crypto having the same issue. RIOT/makefiles/dependency_resolution.inc.mk Lines 124 to 129 in a3a53fb I'd say fixing this is an exercise for a potential follow-up PR. Please squash! |
|
It would be possible to exclude the warning for Also it would be possible to exclude the CI by checking |
e026b75 to
a74927f
Compare
|
Thanks for helping with the CI errors :) |
Contribution description
The issue #21336 by @tanneberger raised the issue that the buildsystem will quietly disable LED0 when using
periph_spi. While this is unavoidable, it is unfortunate that this is done quietly.Therefore this PR adds a red warning when using
periph_spito notify the user about this behavior.Further documentation will be added in #21337, because the
boards/common/nucleo64/doc.mddoes not exist yet where this information would belong to.During the development of this PR I noticed that
periph_init_led0got added toDISABLE_MODULEthree times. While this doesn't hurt anything, it doesn't help anything either. Since I wanted to avoid that the warning is printed three times as well, I added a check to only add it once.Testing procedure
Compile an application of your choice for a Nucleo64 board of your choice, enabling
periph_spi.Issues/PRs references
Fixes #21336.