mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
Kaspar Schleiser
bb71e979f3
... if the riotboot feature is used. Previously, even an application that had "FEATURES_REQUIRED += riotboot" set would still flash the non-riotboot binary on "make flash". This is usualy not what the user wants. This commit set's the FLASHFILE variable to the combined "riotboot bootloader + slot0 + empty slot1" binary. This has the effect that make all, flash and flash-only will compile and/or flash a working riotboot setup. tests/riotboot and tests/riotboot_flashwrite now default to flashing the riotboot-extended binary. tests/riotboot was previously configured to use the riotboot-combined binary. This has been changed in order to not behave differently than how usual riotboot applications do. |
||
---|---|---|
.. | ||
tests | ||
main.c | ||
Makefile | ||
README.md |
RIOT bootloader test
This is a basic example how to use RIOT bootloader in your embedded application.
This test should foremost give you an overview how to use riotboot:
-
make all
build the test using the target riotboot, which generates a binary file of the application with a header on top of it, used by the bootloader to recognise a bootable image. -
make riotboot/flash
creates the binary files and flashes both riotboot and the RIOT image with headers included. This should boot as a normal application.
In this test two modules riotboot_hdr
and riotboot_slot
are used to showcase
the access to riotboot shared functions.
make test
can be executed to run the automatic Python test that checks basic functionalities of riotboot