cfg: Add config file variants using the ftdi driver instead of ft2232

part 1 - files that were tested an verified as working fine

Change-Id: If5986853a1cf118a9eb3b4c13b036d0f71c39624
Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com>
Signed-off-by: Freddie Chopin <freddie.chopin@gmail.com>
Reviewed-on: http://openocd.zylin.com/534
Tested-by: jenkins

tcl/interface/ftdi/jtagkey.cfg

@@ -0,0 +1,13 @@
+#
+# Amontec JTAGkey
+#
+# http://www.amontec.com/jtagkey.shtml
+#
+
+interface ftdi
+ftdi_device_desc "Amontec JTAGkey"
+ftdi_vid_pid 0x0403 0xcff8
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800

tcl/interface/ftdi/jtagkey2.cfg

@@ -0,0 +1,13 @@
+#
+# Amontec JTAGkey2
+#
+# http://www.amontec.com/jtagkey2.shtml
+#
+
+interface ftdi
+ftdi_device_desc "Amontec JTAGkey-2"
+ftdi_vid_pid 0x0403 0xcff8
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800

tcl/interface/ftdi/jtagkey2p.cfg

@@ -0,0 +1,13 @@
+#
+# Amontec JTAGkey2P
+#
+# http://www.amontec.com/jtagkey2p.shtml
+#
+
+interface ftdi
+ftdi_device_desc "Amontec JTAGkey-2P"
+ftdi_vid_pid 0x0403 0xcff8
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800

tcl/interface/ftdi/kt-link.cfg

@@ -0,0 +1,14 @@
+#
+# Kristech KT-Link
+#
+# http://www.kristech.eu
+#
+
+interface ftdi
+ftdi_device_desc "KT-LINK"
+ftdi_vid_pid 0x0403 0xbbe2
+
+ftdi_layout_init 0x8c28 0xff3b
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800
+ftdi_layout_signal LED -data 0x8000

tcl/interface/ftdi/luminary-icdi.cfg

@@ -0,0 +1,23 @@
+#
+# Luminary Micro Stellaris LM3S9B9x Evaluation Kits
+# In-Circuit Debug Interface (ICDI) Board
+#
+# Essentially all Luminary debug hardware is the same, (with both
+# JTAG and SWD support compatible with ICDI boards.  This ICDI adapter
+# configuration is JTAG-only, but the same hardware handles SWD too.
+#
+# This is a discrete ftdi based debug board which supports ARM's
+# JTAG/SWD connectors in both backwards-compatible 20-pin format and
+# in the new-style compact 10-pin.  There's also an 8-pin connector
+# with serial port support.  It's included with LM3S9B9x eval boards.
+#
+# http://www.luminarymicro.com/products/ek-lm3s9b90.html
+# http://www.luminarymicro.com/products/ek-lm3s9b92.html
+#
+
+interface ftdi
+ftdi_device_desc "Luminary Micro ICDI Board"
+ftdi_vid_pid 0x0403 0xbcda
+
+ftdi_layout_init 0x00a8 0x00eb
+ftdi_layout_signal nSRST -noe 0x0020

tcl/interface/ftdi/luminary.cfg

@@ -0,0 +1,32 @@
+#
+# 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.
+#
+
+interface ftdi
+ftdi_device_desc "Stellaris Evaluation Board"
+ftdi_vid_pid 0x0403 0xbcd9
+
+ftdi_layout_init 0x00a8 0x00eb
+ftdi_layout_signal nSRST -data 0x0020

tcl/interface/ftdi/olimex-arm-usb-ocd-h.cfg

@@ -0,0 +1,14 @@
+#
+# Olimex ARM-USB-OCD-H
+#
+# http://www.olimex.com/dev/arm-usb-ocd-h.html
+#
+
+interface ftdi
+ftdi_device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
+ftdi_vid_pid 0x15ba 0x002b
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nSRST -oe 0x0200
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal LED -data 0x0800

tcl/interface/ftdi/olimex-arm-usb-ocd.cfg

@@ -0,0 +1,14 @@
+#
+# Olimex ARM-USB-OCD
+#
+# http://www.olimex.com/dev/arm-usb-ocd.html
+#
+
+interface ftdi
+ftdi_device_desc "Olimex OpenOCD JTAG"
+ftdi_vid_pid 0x15ba 0x0003
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nSRST -oe 0x0200
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal LED -data 0x0800

tcl/interface/ftdi/openocd-usb.cfg

@@ -0,0 +1,13 @@
+#
+# Hubert Hoegl's USB to JTAG
+#
+# http://www.hs-augsburg.de/~hhoegl/proj/usbjtag/usbjtag.html
+#
+
+interface ftdi
+ftdi_device_desc "Dual RS232"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0508 0x0f1b
+ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400