[riot-notifications] [RIOT-OS/RIOT] Clarify interaction between bootloader features, test blacklists and riotboot (#14044)

chrysn notifications at github.com
Fri May 8 13:36:40 CEST 2020

#### Description

Most of the recent discussion in #13146 has been around how to get things how to pass all the tests, which leads to commits like 844a0db625bbef185c06f9d47eca9863e0c3df19 that don't actually reflect the intended statement ("This board is currently only supported for building for flashing using the nrfutil bootloader" -- which is unrelated to the selection of stdio) and instead mimic the only known working configuration (that of the adafruit-clue board) where the bootloader feature requirement is skipped for cases of non-default stdio, which so conveniently happens to disable the feature which is blacklisted for the tests (without actually changing anything about the boot process).

Part of this would be documenting the particular nrfutil_bootloader feature in the first place (cf. #7094), and maybe establishing terminology of what it means to have a bootloader "used". (Is it about making the binary located at the right position? About the method used for flashing? About how to reset the board? And which of those justifies [blacklisting USB-based bootloaders](https://github.com/RIOT-OS/RIOT/blob/e272cc920bc14323c09685fb9e8b413ea18c831e/makefiles/stdio.inc.mk#L50) just because USB-based stdio is not used in a project and stdio_null is used? After all, a project can validly not use stdio and still be flashed the same way.)

#### Desired outcome

* Documentation on the bootloader_* features
* Removal of workarounds in nrf52840dongle and other such boards

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200508/40f65482/attachment-0001.htm>

More information about the notifications mailing list