RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
f74e5e754a
RIOT/tests/riotboot_flashwrite
History
Kaspar Schleiser 8370acb2ff tests/riotboot_flashwrite: blacklist some boards 
Adding saml1[01]-xpro, nucleo-f302r8|f334r8 to
BOARDS_INSUFFICIENT_MEMORY.

The riotboot build fails because it only offers half the flash size (per
slot), compared to before where the default build would not use riotboot
at all, thus have double the flash (but being useless).
2019-07-08 16:54:43 +02:00
..
coap_handler.c tests/riotboot_flashwrite: initial commit 2019-03-15 12:32:50 +01:00
main.c tests/riotboot_flashwrite: initial commit 2019-03-15 12:32:50 +01:00
Makefile tests/riotboot_flashwrite: blacklist some boards 2019-07-08 16:54:43 +02:00
README.md tests/riotboot_flashwrite: initial commit 2019-03-15 12:32:50 +01:00

README.md

Introduction

This test application allows to test the riotboot_flashwrite module over coap.

WARNING: never use this code for anything else. It allows updating the device over network without any kind of authentication or other security!

Please see the README of examples/nanocoap_server for instructions on how to set up a network for testing.

How to test

First, compile and flash with riotboot enabled:

$ BOARD=<board> make riotboot/flash

Confirm it booted from slot 0 (it should print "Current slot=0"), then recompile in order to get an image for the second slot with a newer version number:

$ BOARD=<board> make riotboot

Then send via CoAP, for example, with libcoap's coap_client:

$ coap-client -m post coap://[<ip address of node>]/flashwrite \
   -f bin/<board>/tests_riotboot_flashwrite-slot1.riot.bin -b 64

Then reboot the node manually, confirming that it booted from slot 1.