From 39ea73d48d6ed03d1eac3ef2c23699ec7b6383c6 Mon Sep 17 00:00:00 2001 From: Alexandre Abadie Date: Mon, 23 Mar 2020 09:39:01 +0100 Subject: [PATCH] dist/testbed-support: use BINFILE for flashing on iotlab This is a new feature in cli-tools v3 and is supported by all boards except wsn430 and firefly --- dist/testbed-support/makefile.iotlab.single.inc.mk | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/dist/testbed-support/makefile.iotlab.single.inc.mk b/dist/testbed-support/makefile.iotlab.single.inc.mk index 0f29adff44..9bb279a0b2 100644 --- a/dist/testbed-support/makefile.iotlab.single.inc.mk +++ b/dist/testbed-support/makefile.iotlab.single.inc.mk @@ -94,6 +94,14 @@ else _NODES_DEPLOYED = $(shell iotlab-experiment --jmespath='"0"' --format='" ".join' get $(_IOTLAB_EXP_ID) --deployment) _NODES_LIST_OPTION = --nodes _NODES_FLASH_OPTION = --flash + ifneq (,$(filter-out wsn430-% firefly,$(BOARD))) + # All boards in IoT-LAB except firefly and WSN430 can be flashed using $(BINFILE). + # On IoT-LAB, firefly only accepts $(ELFFILE) and WSN320 boards on accept $(HEXFILE). + # Using $(BINFILE) speeds up the firmware upload since the file is much + # smaller than an elffile. + # This feature is only available in cli-tools version >= 3. + FLASHFILE = $(BINFILE) + endif endif # Try detecting the node automatically