openocd/tcl/interface/ftdi/luminary.cfg
Antonio Borneo 3bccc77999 tcl/interface: add SPDX tag
For historical reasons, no license information was added to the
tcl files. This makes trivial adding the SPDX tag through script:
	fgrep -rL SPDX tcl/interface | while read a;do \
	sed -i '1{i# SPDX-License-Identifier: GPL-2.0-or-later\n
	}' $a;done

With no specific license information from the author, let's extend
the OpenOCD project license GPL-2.0-or-later to the files.

Change-Id: I7bd6a628e9e153fc477cddf9b97087a39ec48aa7
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: https://review.openocd.org/c/openocd/+/7029
Tested-by: jenkins
2022-06-24 21:54:01 +00:00

37 lines
1.3 KiB
INI

# SPDX-License-Identifier: GPL-2.0-or-later
#
# Luminary Micro Stellaris Evaluation Kits
#
# http://www.luminarymicro.com/products/evaluation_kits.html
#
# There are a number of evaluation kits for Stellaris Cortex-M3 chips.
# Currently they all bundle ftdi based debug support. When that is
# used (instead of an external adapter), use this config file in one
# of these two modes:
#
# - Eval board debug ... debug of the Stellaris chip via port A.
#
# - Other board debug ... same thing, but the board acts as a debug
# adapter for another board (using a standard ARM JTAG connector).
# The Stellaris chip stays in reset.
#
# Those support both JTAG and SWD. SWD is an ARM-only two-wire debug
# protocol; in 2009, OpenOCD does not support SWD.
#
# Port B of the ftdi chip is normally used as a serial link to the
# Stellaris chip. On most boards (but not older LM3S811 eval boards),
# when SWD is used Port B may instead be used to read low-bandwidth
# "SWO trace" data, including so-called "printf style" output from
# firmware via the ITM module as well as profile data.
#
adapter driver ftdi
ftdi device_desc "Stellaris Evaluation Board"
ftdi vid_pid 0x0403 0xbcd9
ftdi layout_init 0x00a8 0x00eb
ftdi layout_signal nSRST -noe 0x0020
ftdi layout_signal SWD_EN -ndata 0x0080
ftdi layout_signal SWDIO_OE -data 0x0008