RIOT/boards/iotlab-m3/dist/openocd.cfg

source [find interface/ftdi/iotlab-usb.cfg]
source [find target/stm32f1x.cfg]

# use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst

$_TARGETNAME configure -rtos auto
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			`source [find interface/ftdi/iotlab-usb.cfg]`
			`source [find target/stm32f1x.cfg]`
cpu: initial import of stm32f1 2014-06-11 14:59:24 +02:00
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			`# use combined on interfaces or targets that can't set TRST/SRST separately`
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			`reset_config trst_and_srst`
board/iot-lab_M3: specify target CPU for openocd 2015-02-09 11:41:39 +01:00
cortex_m: Add debug symbols for OpenOCD/GDB thread support 2015-10-06 11:37:49 +02:00			`$_TARGETNAME configure -rtos auto`