[riot-notifications] [RIOT-OS/RIOT] riotboot, mcuboot: Use canned recipe for flashing. (#11110)

Gaƫtan Harter notifications at github.com
Wed Mar 6 16:34:03 CET 2019

For `riotboot` I tested the whole functionality with `iotlab-m3`.
I also checked that the output uses the correct file. Here there are no changes with env variables so no need for a dedicated test.

This test procedure successfully executes:

# Erase what was there
BOARD=iotlab-m3 make -C examples/gnrc_networking flash
# Boot slot 0 with correct version
APP_VER=20 BOARD=iotlab-m3 make -C tests/riotboot riotboot/flash-combined-slot0

# Erase what was there
BOARD=iotlab-m3 make -C examples/gnrc_networking flash

# Flash only bootloader, then slot 1, it  boot with slot1 (not slot 0)
BOARD=iotlab-m3 make -C tests/riotboot riotboot/flash-bootloader
APP_VER=11 BOARD=iotlab-m3 make -C tests/riotboot riotboot/flash-slot1

# Flash slot 0 with a newer version, it uses it
APP_VER=12 BOARD=iotlab-m3 make -C tests/riotboot riotboot/flash-slot0

# Then slot1 again to be sure with a new version, it uses it
APP_VER=13 BOARD=iotlab-m3 make -C tests/riotboot riotboot/flash-slot1

# Use the extended version with a lower `APP_VER`. It correctly boots slot0
APP_VER=1 BOARD=iotlab-m3 make -C tests/riotboot riotboot/flash-extended-slot0

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/20190306/8a6f584c/attachment-0001.html>

More information about the notifications mailing list