RIOT/boards/common/iotlab/Makefile.include

# define the default port depending on the host OS
PORT_LINUX ?= /dev/ttyUSB1
PORT_DARWIN ?= $(firstword $(sort $(wildcard /dev/tty.usbserial*B)))

# setup serial terminal
export BAUD = 500000
include $(RIOTMAKE)/tools/serial.inc.mk

# Using connect_assert_srst removes errors on flash from invalid state
export OPENOCD_RESET_USE_CONNECT_ASSERT_SRST ?= 1

DEBUG_ADAPTER ?= iotlab

export OPENOCD_CONFIG ?= $(RIOTBOARD)/common/iotlab/dist/openocd.cfg

# this board uses openocd
include $(RIOTMAKE)/tools/openocd.inc.mk

# add the common header files to the include path
INCLUDES += -I$(RIOTBOARD)/common/iotlab/include
boards/iotlab-a8-m3: initial implementation 2016-03-18 18:33:53 +01:00			`# define the default port depending on the host OS`
			`PORT_LINUX ?= /dev/ttyUSB1`
boards/iotlab-common: small fix to select right serial port 2016-10-11 15:23:37 +02:00			`PORT_DARWIN ?= $(firstword $(sort $(wildcard /dev/tty.usbserial*B)))`
boards/iotlab-a8-m3: initial implementation 2016-03-18 18:33:53 +01:00
			`# setup serial terminal`
			`export BAUD = 500000`
Makefiles: move to new directory /makefiles 2016-01-27 10:47:12 +01:00			`include $(RIOTMAKE)/tools/serial.inc.mk`
boards/iotlab-a8-m3: initial implementation 2016-03-18 18:33:53 +01:00
boards/iotlab: rely on OPENOCD_RESET_USE_CONNECT_ASSERT_SRST Use the new OPENOCD_RESET_USE_CONNECT_ASSERT_SRST to configure 'reset_config connect_assert_srst' when flashing and resetting only. This removes the need for a special debug configuration and should allow connecting to a running target again. 2019-09-02 16:12:55 +02:00			`# Using connect_assert_srst removes errors on flash from invalid state`
			`export OPENOCD_RESET_USE_CONNECT_ASSERT_SRST ?= 1`
boards/iotlab-m3\|a8: fix openocd configuration iotlab-m3 boards always ended up not being able to flash after time. This changes managed to fix and flash boards that where able to be flashed with the deprecated `ft2232` driver and not with the `ftdi` driver used in RIOT. It combines configuration from openocd, iot-lab, RIOT config and Alexandre Abadie feedback * http://repo.or.cz/openocd.git/blob/HEAD:/tcl/interface/ftdi/iotlab-usb.cfg * ftdi configuration * https://github.com/iot-lab/iot-lab-gateway/blob/2.4.1/gateway_code/static/iot-lab-m3.cfg * `trst_and_srst` config * Alexandre feedback and http://openocd.org/doc/html/Reset-Configuration.html * 'connect_assert_srst' reset configuration * it prevents errors in the output on first flash * should help on boards with invalid code * It was taken from what Alexandre found for board 'b-l072z-lrwan1' * It requires using '-c reset halt' instead of '-c halt' before debug * RIOT * Keep the `configure -rtos` auto 2018-04-18 17:54:07 +02:00
boards/iotlab-%: define DEBUG_ADAPTER 2020-01-28 11:56:56 +01:00			`DEBUG_ADAPTER ?= iotlab`

boards/iotlab-%: use common openocd config 2020-01-28 11:52:37 +01:00			`export OPENOCD_CONFIG ?= $(RIOTBOARD)/common/iotlab/dist/openocd.cfg`

boards/iotlab-a8-m3: initial implementation 2016-03-18 18:33:53 +01:00			`# this board uses openocd`
Makefiles: move to new directory /makefiles 2016-01-27 10:47:12 +01:00			`include $(RIOTMAKE)/tools/openocd.inc.mk`
boards/iotlab-a8-m3: initial implementation 2016-03-18 18:33:53 +01:00
			`# add the common header files to the include path`
boards/iotlab: move shared code to common/iotlab 2017-11-16 12:21:26 +01:00			`INCLUDES += -I$(RIOTBOARD)/common/iotlab/include`