debuggers: import openocd-0.7.0

Initial check-in of openocd-0.7.0 as it can be downloaded from
http://sourceforge.net/projects/openocd/files/openocd/0.7.0/

Any modifications will follow.

Change-Id: I6949beaefd589e046395ea0cb80f4e1ab1654d55

debuggers/openocd/tcl/interface/altera-usb-blaster.cfg

@@ -0,0 +1,10 @@
+#
+# Altera USB-Blaster
+#
+# http://www.altera.com/literature/ug/ug_usb_blstr.pdf
+#
+
+interface usb_blaster
+# These are already the defaults.
+# usb_blaster_vid_pid 0x09FB 0x6001
+# usb_blaster_device_desc "USB-Blaster"

debuggers/openocd/tcl/interface/arm-jtag-ew.cfg

@@ -0,0 +1,8 @@
+#
+# Olimex ARM-JTAG-EW
+#
+# http://www.olimex.com/dev/arm-jtag-ew.html
+#
+
+interface arm-jtag-ew
+

debuggers/openocd/tcl/interface/at91rm9200.cfg

@@ -0,0 +1,9 @@
+#
+# Various Atmel AT91RM9200 boards
+#
+# TODO: URL?
+#
+
+interface at91rm9200
+at91rm9200_device rea_ecr
+

debuggers/openocd/tcl/interface/axm0432.cfg

@@ -0,0 +1,11 @@
+#
+# Axiom axm0432
+#
+# http://www.axman.com
+#
+
+interface ft2232
+ft2232_device_desc "Symphony SoundBite"
+ft2232_layout "axm0432_jtag"
+ft2232_vid_pid 0x0403 0x6010
+

debuggers/openocd/tcl/interface/busblaster.cfg

@@ -0,0 +1,14 @@
+#
+# Dangerous Prototypes - Bus Blaster
+#
+# The Bus Blaster has a configurable buffer between the FTDI FT2232H and the
+# JTAG header which allows it to emulate various debugger types. It comes
+# configured as a JTAGkey device.
+#
+# http://dangerousprototypes.com/docs/Bus_Blaster
+#
+
+interface ft2232
+ft2232_device_desc "Dual RS232-HS"
+ft2232_layout jtagkey
+ft2232_vid_pid 0x0403 0x6010

debuggers/openocd/tcl/interface/buspirate.cfg

@@ -0,0 +1,26 @@
+#
+# Buspirate with OpenOCD support
+#
+# http://dangerousprototypes.com/bus-pirate-manual/
+#
+
+interface buspirate
+
+# you need to specify port on which BP lives
+#buspirate_port /dev/ttyUSB0
+
+# communication speed setting
+buspirate_speed normal ;# or fast
+
+# voltage regulator Enabled = 1 Disabled = 0
+#buspirate_vreg 0
+
+# pin mode normal or open-drain
+#buspirate_mode normal
+
+# pullup state Enabled = 1 Disabled = 0
+#buspirate_pullup 0
+
+# this depends on the cable, you are safe with this option
+reset_config srst_only
+

debuggers/openocd/tcl/interface/calao-usb-a9260-c01.cfg

@@ -0,0 +1,13 @@
+#
+# CALAO Systems USB-A9260-C01
+#
+# http://www.calao-systems.com/
+#
+
+interface ft2232
+ft2232_layout jtagkey
+ft2232_device_desc "USB-A9260"
+ft2232_vid_pid 0x0403 0x6010
+script interface/calao-usb-a9260.cfg
+script target/at91sam9260minimal.cfg
+

debuggers/openocd/tcl/interface/calao-usb-a9260-c02.cfg

@@ -0,0 +1,13 @@
+#
+# CALAO Systems USB-A9260-C02
+#
+# http://www.calao-systems.com/
+#
+
+interface ft2232
+ft2232_layout jtagkey
+ft2232_device_desc "USB-A9260"
+ft2232_vid_pid 0x0403 0x6001
+script interface/calao-usb-a9260.cfg
+script target/at91sam9260minimal.cfg
+

debuggers/openocd/tcl/interface/calao-usb-a9260.cfg

@@ -0,0 +1,11 @@
+#
+# CALAO Systems USB-A9260 common -C01 -C02 setup
+#
+# http://www.calao-systems.com/
+#
+# See calao-usb-a9260-c01.cfg and calao-usb-a9260-c02.cfg.
+#
+
+adapter_nsrst_delay 200
+jtag_ntrst_delay 200
+

debuggers/openocd/tcl/interface/chameleon.cfg

@@ -0,0 +1,9 @@
+#
+# Amontec Chameleon POD
+#
+# http://www.amontec.com/chameleon.shtml
+#
+
+interface parport
+parport_cable chameleon
+

debuggers/openocd/tcl/interface/cortino.cfg

@@ -0,0 +1,11 @@
+#
+# Hitex Cortino
+#
+# http://www.hitex.com/index.php?id=cortino
+#
+
+interface ft2232
+ft2232_device_desc "Cortino"
+ft2232_layout cortino
+ft2232_vid_pid 0x0640 0x0032
+

debuggers/openocd/tcl/interface/digilent-hs1.cfg

@@ -0,0 +1,15 @@
+#
+# Digilent HS1
+#
+# The Digilent HS1 is a high-speed FT2232H-based adapter, compliant with the
+# Xilinx JTAG 14-pin pinout.
+# It does not support ARM reset signals (SRST and TRST) but can still be used for
+# hardware debugging, with some limitations.
+#
+# http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,395,922&Prod=JTAG-HS1
+#
+
+interface ft2232
+ft2232_device_desc "Digilent Adept USB Device"
+ft2232_layout digilent-hs1
+ft2232_vid_pid 0x0403 0x6010

debuggers/openocd/tcl/interface/dlp-usb1232h.cfg

@@ -0,0 +1,14 @@
+#
+# DLP Design DLP-USB1232H USB-to-UART/FIFO interface module
+#
+# http://www.dlpdesign.com/usb/usb1232h.shtml
+#
+# Schematics for OpenOCD usage:
+# http://randomprojects.org/wiki/DLP-USB1232H_and_OpenOCD_based_JTAG_adapter
+#
+
+interface ft2232
+ft2232_device_desc "Dual RS232-HS"
+ft2232_layout usbjtag
+ft2232_vid_pid 0x0403 0x6010
+

debuggers/openocd/tcl/interface/dummy.cfg

@@ -0,0 +1,6 @@
+#
+# Dummy interface (for testing purposes)
+#
+
+interface dummy
+

debuggers/openocd/tcl/interface/estick.cfg

@@ -0,0 +1,7 @@
+#
+# eStick
+#
+# http://code.google.com/p/estick-jtag/
+#
+
+interface opendous

debuggers/openocd/tcl/interface/flashlink.cfg

@@ -0,0 +1,16 @@
+#
+# ST FlashLINK JTAG parallel cable
+#
+# http://www.st.com/internet/evalboard/product/94023.jsp
+# http://www.st.com/stonline/products/literature/um/7889.pdf
+#
+
+if { [info exists PARPORTADDR] } {
+   set _PARPORTADDR $PARPORTADDR
+} else {
+   set _PARPORTADDR 0
+}
+
+interface parport
+parport_port $_PARPORTADDR
+parport_cable flashlink

debuggers/openocd/tcl/interface/flossjtag-noeeprom.cfg

@@ -0,0 +1,19 @@
+#
+# FlossJTAG
+#
+# http://github.com/esden/floss-jtag
+#
+# This is the pre v0.3 Floss-JTAG compatible config file. It can also be used
+# for newer versions of Floss-JTAG with empty or not populated EEPROM. If you
+# have several Floss-JTAG connected you have to use the USB ID to select a
+# specific one.
+#
+# If you have a Floss-JTAG WITH EEPROM that is programmed, use the
+# flossjtag.cfg file.
+#
+
+interface ft2232
+ft2232_vid_pid 0x0403 0x6010
+ft2232_device_desc "Dual RS232-HS"
+ft2232_layout "usbjtag"
+ft2232_latency 2

debuggers/openocd/tcl/interface/flossjtag.cfg

@@ -0,0 +1,20 @@
+#
+# FlossJTAG
+#
+# http://github.com/esden/floss-jtag
+#
+# This is the v0.3 and v1.0 Floss-JTAG compatible config file. It relies on the
+# existence of an EEPROM on Floss-JTAG containing a name. If you have several
+# Floss-JTAG adapters connected you can use the serial number to select a
+# specific device.
+#
+# If your Floss-JTAG does not have an EEPROM, or the EEPROM is empty, use the
+# flossjtag-noeeprom.cfg file.
+#
+
+interface ft2232
+ft2232_vid_pid 0x0403 0x6010
+ft2232_device_desc "FLOSS-JTAG"
+#ft2232_serial "FJ000001"
+ft2232_layout "flossjtag"
+ft2232_latency 2

debuggers/openocd/tcl/interface/flyswatter.cfg

@@ -0,0 +1,10 @@
+#
+# TinCanTools Flyswatter
+#
+# http://www.tincantools.com/product.php?productid=16134
+#
+
+interface ft2232
+ft2232_device_desc "Flyswatter"
+ft2232_layout "flyswatter"
+ft2232_vid_pid 0x0403 0x6010

debuggers/openocd/tcl/interface/flyswatter2.cfg

@@ -0,0 +1,10 @@
+#
+# TinCanTools Flyswatter 2
+#
+# http://www.tincantools.com/product.php?productid=16153
+#
+
+interface ft2232
+ft2232_device_desc "Flyswatter2"
+ft2232_layout "flyswatter2"
+ft2232_vid_pid 0x0403 0x6010

debuggers/openocd/tcl/interface/ftdi/axm0432.cfg

@@ -0,0 +1,18 @@
+#
+# Axiom axm0432
+#
+# http://www.axman.com
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Symphony SoundBite"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0c08 0x0c2b
+ftdi_layout_signal nTRST -data 0x0800
+ftdi_layout_signal nSRST -data 0x0400

debuggers/openocd/tcl/interface/ftdi/calao-usb-a9260-c01.cfg

@@ -0,0 +1,22 @@
+#
+# CALAO Systems USB-A9260-C01
+#
+# http://www.calao-systems.com/
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, but is assumed to work as this"
+echo "interface uses the same layout as configs that were verified. Please report your"
+echo "experience with this file to openocd-devel mailing list, so it could be marked"
+echo "as working or fixed."
+
+interface ftdi
+ftdi_device_desc "USB-A9260"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800
+
+script interface/calao-usb-a9260.cfg
+script target/at91sam9260minimal.cfg

debuggers/openocd/tcl/interface/ftdi/calao-usb-a9260-c02.cfg

@@ -0,0 +1,22 @@
+#
+# CALAO Systems USB-A9260-C02
+#
+# http://www.calao-systems.com/
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, but is assumed to work as this"
+echo "interface uses the same layout as configs that were verified. Please report your"
+echo "experience with this file to openocd-devel mailing list, so it could be marked"
+echo "as working or fixed."
+
+interface ftdi
+ftdi_device_desc "USB-A9260"
+ftdi_vid_pid 0x0403 0x6001
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800
+
+script interface/calao-usb-a9260.cfg
+script target/at91sam9260minimal.cfg

debuggers/openocd/tcl/interface/ftdi/cortino.cfg

@@ -0,0 +1,13 @@
+#
+# Hitex Cortino
+#
+# http://www.hitex.com/index.php?id=cortino
+#
+
+interface ftdi
+ftdi_device_desc "Cortino"
+ftdi_vid_pid 0x0640 0x0032
+
+ftdi_layout_init 0x0108 0x010b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0200 -oe 0x0200

debuggers/openocd/tcl/interface/ftdi/dlp-usb1232h.cfg

@@ -0,0 +1,21 @@
+#
+# DLP Design DLP-USB1232H USB-to-UART/FIFO interface module
+#
+# http://www.dlpdesign.com/usb/usb1232h.shtml
+#
+# Schematics for OpenOCD usage:
+# http://randomprojects.org/wiki/DLP-USB1232H_and_OpenOCD_based_JTAG_adapter
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on schematics and code"
+echo "in ft2232.c. Please report your experience with this file to openocd-devel"
+echo "mailing list, so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Dual RS232-HS"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0008 0x000b
+ftdi_layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi_layout_signal nSRST -data 0x0040 -oe 0x0040

debuggers/openocd/tcl/interface/ftdi/dp_busblaster.cfg

@@ -0,0 +1,23 @@
+#
+# Dangerous Prototypes - Bus Blaster
+#
+# The Bus Blaster has a configurable buffer between the FTDI FT2232H and the
+# JTAG header which allows it to emulate various debugger types. It comes
+# configured as a JTAGkey device.
+#
+# http://dangerousprototypes.com/docs/Bus_Blaster
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, but is assumed to work as this"
+echo "interface uses the same layout as configs that were verified. Please report your"
+echo "experience with this file to openocd-devel mailing list, so it could be marked"
+echo "as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Dual RS232-HS"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800

debuggers/openocd/tcl/interface/ftdi/flossjtag-noeeprom.cfg

@@ -0,0 +1,26 @@
+#
+# FlossJTAG
+#
+# http://github.com/esden/floss-jtag
+#
+# This is the pre v0.3 Floss-JTAG compatible config file. It can also be used
+# for newer versions of Floss-JTAG with empty or not populated EEPROM. If you
+# have several Floss-JTAG connected you have to use the USB ID to select a
+# specific one.
+#
+# If you have a Floss-JTAG WITH EEPROM that is programmed, use the
+# flossjtag.cfg file.
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Dual RS232-HS"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0008 0x000b
+ftdi_layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi_layout_signal nSRST -data 0x0040 -oe 0x0040

debuggers/openocd/tcl/interface/ftdi/flossjtag.cfg

@@ -0,0 +1,29 @@
+#
+# FlossJTAG
+#
+# http://github.com/esden/floss-jtag
+#
+# This is the v0.3 and v1.0 Floss-JTAG compatible config file. It relies on the
+# existence of an EEPROM on Floss-JTAG containing a name. If you have several
+# Floss-JTAG adapters connected you can use the serial number to select a
+# specific device.
+#
+# If your Floss-JTAG does not have an EEPROM, or the EEPROM is empty, use the
+# flossjtag-noeeprom.cfg file.
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_vid_pid 0x0403 0x6010
+ftdi_device_desc "FLOSS-JTAG"
+#ftdi_serial "FJ000001"
+
+ftdi_layout_init 0x0008 0x180b
+ftdi_layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi_layout_signal nSRST -data 0x0040 -oe 0x0040
+ftdi_layout_signal LED -data 0x0800
+ftdi_layout_signal LED2 -data 0x1000

debuggers/openocd/tcl/interface/ftdi/flyswatter.cfg

@@ -0,0 +1,19 @@
+#
+# TinCanTools Flyswatter
+#
+# http://www.tincantools.com/product.php?productid=16134
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on schematics and code"
+echo "in ft2232.c. Please report your experience with this file to openocd-devel"
+echo "mailing list, so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Flyswatter"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0818 0x0cfb
+ftdi_layout_signal nTRST -data 0x0010
+ftdi_layout_signal nSRST -oe 0x0020
+ftdi_layout_signal LED -data 0x0c00

debuggers/openocd/tcl/interface/ftdi/flyswatter2.cfg

@@ -0,0 +1,14 @@
+#
+# TinCanTools Flyswatter2
+#
+# http://www.tincantools.com/product.php?productid=16134
+#
+
+interface ftdi
+ftdi_device_desc "Flyswatter2"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0538 0x057b
+ftdi_layout_signal LED -ndata 0x0400
+ftdi_layout_signal nTRST -data 0x0010
+ftdi_layout_signal nSRST -data 0x0020 -noe 0x0100

debuggers/openocd/tcl/interface/ftdi/hilscher_nxhx10_etm.cfg

@@ -0,0 +1,18 @@
+#
+# Hilscher NXHX 10-ETM
+#
+# http://de.hilscher.com/products_details_hardware.html?p_id=P_4ce145a5983e6
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "NXHX 10-ETM"
+ftdi_vid_pid 0x0640 0x0028
+
+ftdi_layout_init 0x0308 0x030b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0200

debuggers/openocd/tcl/interface/ftdi/hilscher_nxhx500_etm.cfg

@@ -0,0 +1,18 @@
+#
+# Hilscher NXHX 500-ETM
+#
+# http://de.hilscher.com/files_design/8/NXHX500-ETM_description_Rev01_EN.pdf
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "NXHX 500-ETM"
+ftdi_vid_pid 0x0640 0x0028
+
+ftdi_layout_init 0x0308 0x030b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0200

debuggers/openocd/tcl/interface/ftdi/hilscher_nxhx500_re.cfg

@@ -0,0 +1,18 @@
+#
+# Hilscher NXHX 500-RE
+#
+# http://de.hilscher.com/products_details_hardware.html?p_id=P_461ff2053bad1&bs=20
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "NXHX 500-RE"
+ftdi_vid_pid 0x0640 0x0028
+
+ftdi_layout_init 0x0308 0x030b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0200

debuggers/openocd/tcl/interface/ftdi/hilscher_nxhx50_etm.cfg

@@ -0,0 +1,18 @@
+#
+# Hilscher NXHX 50-ETM
+#
+# http://de.hilscher.com/files_design/8/NXHX50-ETM_description_Rev01_EN.pdf
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "NXHX 50-ETM"
+ftdi_vid_pid 0x0640 0x0028
+
+ftdi_layout_init 0x0308 0x030b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0200

debuggers/openocd/tcl/interface/ftdi/hilscher_nxhx50_re.cfg

@@ -0,0 +1,18 @@
+#
+# Hilscher NXHX 50-RE
+#
+# http://de.hilscher.com/products_details_hardware.html?p_id=P_483c0f582ad36&bs=20
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "NXHX50-RE"
+ftdi_vid_pid 0x0640 0x0028
+
+ftdi_layout_init 0x0308 0x030b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0200

debuggers/openocd/tcl/interface/ftdi/hitex_lpc1768stick.cfg

@@ -0,0 +1,15 @@
+#
+# Hitex LPC1768-Stick
+#
+# http://www.hitex.com/?id=1602
+#
+
+
+interface ftdi
+ftdi_device_desc "LPC1768-Stick"
+ftdi_vid_pid 0x0640 0x0026
+
+ftdi_layout_init 0x0388 0x038b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0080 -noe 0x200
+

debuggers/openocd/tcl/interface/ftdi/hitex_str9-comstick.cfg

@@ -0,0 +1,13 @@
+#
+# Hitex STR9-comStick
+#
+# http://www.hitex.com/index.php?id=383
+#
+
+interface ftdi
+ftdi_device_desc "STR9-comStick"
+ftdi_vid_pid 0x0640 0x002c
+
+ftdi_layout_init 0x0108 0x010b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0200 -oe 0x0200

debuggers/openocd/tcl/interface/ftdi/icebear.cfg

@@ -0,0 +1,18 @@
+#
+# Section5 ICEBear
+#
+# http://section5.ch/icebear
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "ICEbear JTAG adapter"
+ftdi_vid_pid 0x0403 0xc140
+
+ftdi_layout_init 0x0028 0x002b
+ftdi_layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi_layout_signal nSRST -data 0x0020

debuggers/openocd/tcl/interface/ftdi/jtag-lock-pick_tiny_2.cfg

@@ -0,0 +1,14 @@
+#
+# DISTORTEC JTAG-lock-pick Tiny 2
+#
+# http://www.distortec.com
+#
+
+interface ftdi
+ftdi_device_desc "JTAG-lock-pick Tiny 2"
+ftdi_vid_pid 0x0403 0x8220
+
+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 -ndata 0x8000

debuggers/openocd/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

debuggers/openocd/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

debuggers/openocd/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

debuggers/openocd/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

debuggers/openocd/tcl/interface/ftdi/lisa-l.cfg

@@ -0,0 +1,20 @@
+#
+# Lisa/L
+#
+# http://paparazzi.enac.fr/wiki/Lisa
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on schematics and code"
+echo "in ft2232.c. Please report your experience with this file to openocd-devel"
+echo "mailing list, so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Lisa/L"
+ftdi_vid_pid 0x0403 0x6010
+ftdi_channel 1
+
+ftdi_layout_init 0x0008 0x180b
+ftdi_layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi_layout_signal nSRST -data 0x0040 -oe 0x0040
+ftdi_layout_signal LED -data 0x1800

debuggers/openocd/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

debuggers/openocd/tcl/interface/ftdi/luminary-lm3s811.cfg

@@ -0,0 +1,19 @@
+#
+# Luminary Micro Stellaris LM3S811 Evaluation Kit
+#
+# http://www.luminarymicro.com/products/stellaris_811_evaluation_kits.html
+#
+# NOTE:  this is only for boards *before* Rev C, which adds support
+# for SWO tracing with ADBUS_6 DBG_ENn and BDBUS_4 SWO_EN signals.
+# The "evb_lm3s811" layout doesn't set up those signals.
+#
+# Rev C boards work more like the other Stellaris eval boards.  They
+# need to use the "luminary_icdi" layout to work correctly.
+#
+
+interface ftdi
+ftdi_device_desc "LM3S811 Evaluation Board"
+ftdi_vid_pid 0x0403 0xbcd9
+
+ftdi_layout_init 0x0088 0x008b
+ftdi_layout_signal nSRST -data 0x0020 -oe 0x0020

debuggers/openocd/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 -noe 0x0020

debuggers/openocd/tcl/interface/ftdi/minimodule.cfg

@@ -0,0 +1,17 @@
+#
+# FTDI MiniModule
+#
+# http://www.ftdichip.com/Support/Documents/DataSheets/Modules/DS_FT2232H_Mini_Module.pdf
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "FT2232H MiniModule"
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0018 0x05fb
+ftdi_layout_signal nSRST -data 0x0020

debuggers/openocd/tcl/interface/ftdi/neodb.cfg

@@ -0,0 +1,19 @@
+#
+# Openmoko USB JTAG/RS232 adapter
+#
+# http://wiki.openmoko.org/wiki/Debug_Board_v3
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on schematics and code"
+echo "in ft2232.c. Please report your experience with this file to openocd-devel"
+echo "mailing list, so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Debug Board for Neo1973"
+ftdi_vid_pid 0x1457 0x5118
+
+ftdi_layout_init 0x0508 0x0f1b
+ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400
+ftdi_layout_signal nNOR_WP -data 0x0010 -oe 0x0010

debuggers/openocd/tcl/interface/ftdi/ngxtech.cfg

@@ -0,0 +1,19 @@
+#
+# NGX ARM USB JTAG
+#
+# http://shop.ngxtechnologies.com/product_info.php?cPath=26&products_id=30
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, but is assumed to work as this"
+echo "interface uses the same layout as configs that were verified. Please report your"
+echo "experience with this file to openocd-devel mailing list, so it could be marked"
+echo "as working or fixed."
+
+interface ftdi
+ftdi_device_desc "NGX JTAG"
+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

debuggers/openocd/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

debuggers/openocd/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

debuggers/openocd/tcl/interface/ftdi/olimex-arm-usb-tiny-h.cfg

@@ -0,0 +1,20 @@
+#
+# Olimex ARM-USB-TINY-H
+#
+# http://www.olimex.com/dev/arm-usb-tiny-h.html
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, but is assumed to work as this"
+echo "interface uses the same layout as configs that were verified. Please report your"
+echo "experience with this file to openocd-devel mailing list, so it could be marked"
+echo "as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Olimex OpenOCD JTAG ARM-USB-TINY-H"
+ftdi_vid_pid 0x15ba 0x002a
+
+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

debuggers/openocd/tcl/interface/ftdi/olimex-jtag-tiny.cfg

@@ -0,0 +1,14 @@
+#
+# Olimex ARM-USB-TINY
+#
+# http://www.olimex.com/dev/arm-usb-tiny.html
+#
+
+interface ftdi
+ftdi_device_desc "Olimex OpenOCD JTAG TINY"
+ftdi_vid_pid 0x15ba 0x0004
+
+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

debuggers/openocd/tcl/interface/ftdi/oocdlink.cfg

@@ -0,0 +1,19 @@
+#
+# Joern Kaipf's OOCDLink
+#
+# http://www.joernonline.de/contrexx2/cms/index.php?page=126
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, but is assumed to work as this"
+echo "interface uses the same layout as configs that were verified. Please report your"
+echo "experience with this file to openocd-devel mailing list, so it could be marked"
+echo "as working or fixed."
+
+interface ftdi
+ftdi_device_desc "OOCDLink"
+ftdi_vid_pid 0x0403 0xbaf8
+
+ftdi_layout_init 0x0508 0x0f1b
+ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400

debuggers/openocd/tcl/interface/ftdi/opendous_ftdi.cfg

@@ -0,0 +1,17 @@
+#
+# Opendous
+#
+# http://code.google.com/p/opendous/wiki/JTAG
+#
+# According to the website, it is similar to jtagkey, but it uses channel B
+# (and it has a different pid number).
+#
+
+interface ftdi
+ftdi_device_desc "Dual RS232-HS"
+ftdi_vid_pid 0x0403 0x6010
+ftdi_channel 1
+
+ftdi_layout_init 0x0c08 0x0f1b
+ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800

debuggers/openocd/tcl/interface/ftdi/openocd-usb-hs.cfg

@@ -0,0 +1,13 @@
+#
+# embedded projects openocd usb adapter v3
+#
+# http://shop.embedded-projects.net/index.php?module=artikel&action=artikel&id=14
+#
+
+interface ftdi
+ftdi_device_desc "Dual RS232-HS"
+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

debuggers/openocd/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

debuggers/openocd/tcl/interface/ftdi/openrd.cfg

@@ -0,0 +1,19 @@
+#
+# Marvell OpenRD
+#
+# http://www.marvell.com/products/embedded_processors/developer/kirkwood/openrd.jsp
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "OpenRD JTAGKey FT2232D"
+ftdi_vid_pid 0x0403 0x9e90
+ftdi_channel 1
+
+ftdi_layout_init 0x0608 0x0f1b
+ftdi_layout_signal nTRST -data 0x0200
+ftdi_layout_signal nSRST -noe 0x0400

debuggers/openocd/tcl/interface/ftdi/redbee-econotag.cfg

@@ -0,0 +1,21 @@
+#
+# Redwire Redbee-Econotag
+#
+# http://www.redwirellc.com/store/node/1
+#
+# The Redbee-Econotag has an onboard FT2232H with:
+#  - FT2232H channel A wired to mc13224v JTAG
+#  - FT2232H channel B wired to mc13224v UART1
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_vid_pid 0x0403 0x6010
+
+ftdi_layout_init 0x0c08 0x0c2b
+ftdi_layout_signal nTRST -data 0x0800
+ftdi_layout_signal nSRST -data 0x0400

debuggers/openocd/tcl/interface/ftdi/redbee-usb.cfg

@@ -0,0 +1,22 @@
+#
+# Redwire Redbee-USB
+#
+# http://www.redwirellc.com
+#
+# The Redbee-USB has an onboard FT2232H with:
+#  - FT2232H channel B wired to mc13224v JTAG
+#  - FT2232H channel A wired to mc13224v UART1
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_vid_pid 0x0403 0x6010
+ftdi_channel 1
+
+ftdi_layout_init 0x0c08 0x0c2b
+ftdi_layout_signal nTRST -data 0x0800
+ftdi_layout_signal nSRST -data 0x0400

debuggers/openocd/tcl/interface/ftdi/sheevaplug.cfg

@@ -0,0 +1,19 @@
+#
+# Marvel SheevaPlug Development Kit
+#
+# http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "SheevaPlug JTAGKey FT2232D"
+ftdi_vid_pid 0x9e88 0x9e8f
+ftdi_channel 1
+
+ftdi_layout_init 0x0608 0x0f1b
+ftdi_layout_signal nTRST -data 0x0200
+ftdi_layout_signal nSRST -noe 0x0400

debuggers/openocd/tcl/interface/ftdi/signalyzer-lite.cfg

@@ -0,0 +1,18 @@
+#
+# Xverve Signalyzer LITE (DT-USB-SLITE)
+#
+# http://www.signalyzer.com
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Signalyzer LITE"
+ftdi_vid_pid 0x0403 0xbca1
+
+ftdi_layout_init 0x0008 0x000b
+ftdi_layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi_layout_signal nSRST -data 0x0020 -oe 0x0020

debuggers/openocd/tcl/interface/ftdi/signalyzer.cfg

@@ -0,0 +1,18 @@
+#
+# Xverve Signalyzer Tool (DT-USB-ST)
+#
+# http://www.signalyzer.com
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on code in ft2232.c."
+echo "Please report your experience with this file to openocd-devel mailing list,"
+echo "so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Signalyzer"
+ftdi_vid_pid 0x0403 0xbca0
+
+ftdi_layout_init 0x0008 0x000b
+ftdi_layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi_layout_signal nSRST -data 0x0020 -oe 0x0020

debuggers/openocd/tcl/interface/ftdi/stm32-stick.cfg

@@ -0,0 +1,13 @@
+#
+# Hitex STM32-PerformanceStick
+#
+# http://www.hitex.com/index.php?id=340
+#
+
+interface ftdi
+ftdi_device_desc "STM32-PerformanceStick"
+ftdi_vid_pid 0x0640 0x002d
+
+ftdi_layout_init 0x0388 0x038b
+ftdi_layout_signal nTRST -data 0x0100
+ftdi_layout_signal nSRST -data 0x0080 -noe 0x200

debuggers/openocd/tcl/interface/ftdi/turtelizer2-revB.cfg

@@ -0,0 +1,18 @@
+#
+# egnite Turtelizer 2 rev B (with SRST only)
+#
+# http://www.ethernut.de/en/hardware/turtelizer/index.html
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on schematics and code"
+echo "in ft2232.c. Please report your experience with this file to openocd-devel"
+echo "mailing list, so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Turtelizer JTAG/RS232 Adapter"
+ftdi_vid_pid 0x0403 0xbdc8
+
+ftdi_layout_init 0x0008 0x0c5b
+ftdi_layout_signal nSRST -oe 0x0040
+ftdi_layout_signal LED -data 0x0c00

debuggers/openocd/tcl/interface/ftdi/turtelizer2-revC.cfg

@@ -0,0 +1,19 @@
+#
+# egnite Turtelizer 2 revC (with TRST and SRST)
+#
+# http://www.ethernut.de/en/hardware/turtelizer/index.html
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on schematics and code"
+echo "in ft2232.c. Please report your experience with this file to openocd-devel"
+echo "mailing list, so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Turtelizer JTAG/RS232 Adapter"
+ftdi_vid_pid 0x0403 0xbdc8
+
+ftdi_layout_init 0x0008 0x0c7b
+ftdi_layout_signal nTRST -oe 0x0020
+ftdi_layout_signal nSRST -oe 0x0040
+ftdi_layout_signal LED -ndata 0x0c00

debuggers/openocd/tcl/interface/ftdi/vpaclink.cfg

@@ -0,0 +1,19 @@
+#
+# Voipac VPACLink
+#
+# http://voipac.com/27M-JTG-000
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, but is assumed to work as this"
+echo "interface uses the same layout as configs that were verified. Please report your"
+echo "experience with this file to openocd-devel mailing list, so it could be marked"
+echo "as working or fixed."
+
+interface ftdi
+ftdi_device_desc "VPACLink"
+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

debuggers/openocd/tcl/interface/ftdi/xds100v2.cfg

@@ -0,0 +1,23 @@
+#
+# Texas Instruments XDS100v2
+#
+# http://processors.wiki.ti.com/index.php/XDS100#XDS100v2_Features
+#
+
+echo "WARNING!"
+echo "This file was not tested with real interface, it is based on schematics and code"
+echo "in ft2232.c. Please report your experience with this file to openocd-devel"
+echo "mailing list, so it could be marked as working or fixed."
+
+interface ftdi
+ftdi_device_desc "Texas Instruments Inc.XDS100 Ver 2.0"
+ftdi_vid_pid 0x0403 0xa6d0
+
+ftdi_layout_init 0x0838 0x597b
+ftdi_layout_signal nTRST -data 0x0010
+ftdi_layout_signal nSRST -oe 0x0100
+ftdi_layout_signal nEMU_EN -data 0x0020
+ftdi_layout_signal nEMU0 -data 0x0040
+ftdi_layout_signal nEMU1 -data 0x1000
+ftdi_layout_signal PWR_RST -data 0x0800
+ftdi_layout_signal LOOPBACK -data 0x4000

debuggers/openocd/tcl/interface/hilscher_nxhx10_etm.cfg

@@ -0,0 +1,11 @@
+#
+# Hilscher NXHX 10-ETM
+#
+# http://de.hilscher.com/products_details_hardware.html?p_id=P_4ce145a5983e6
+#
+
+interface ft2232
+ft2232_device_desc "NXHX 10-ETM"
+ft2232_layout comstick
+ft2232_vid_pid 0x0640 0x0028
+adapter_khz 6000

debuggers/openocd/tcl/interface/hilscher_nxhx500_etm.cfg

@@ -0,0 +1,11 @@
+#
+# Hilscher NXHX 500-ETM
+#
+# http://de.hilscher.com/files_design/8/NXHX500-ETM_description_Rev01_EN.pdf
+#
+
+interface ft2232
+ft2232_device_desc "NXHX 500-ETM"
+ft2232_layout comstick
+ft2232_vid_pid 0x0640 0x0028
+adapter_khz 6000

debuggers/openocd/tcl/interface/hilscher_nxhx500_re.cfg

@@ -0,0 +1,11 @@
+#
+# Hilscher NXHX 500-RE
+#
+# http://de.hilscher.com/products_details_hardware.html?p_id=P_461ff2053bad1&bs=20
+#
+
+interface ft2232
+ft2232_device_desc "NXHX 500-RE"
+ft2232_layout comstick
+ft2232_vid_pid 0x0640 0x0028
+adapter_khz 6000

debuggers/openocd/tcl/interface/hilscher_nxhx50_etm.cfg

@@ -0,0 +1,11 @@
+#
+# Hilscher NXHX 50-ETM
+#
+# http://de.hilscher.com/files_design/8/NXHX50-ETM_description_Rev01_EN.pdf
+#
+
+interface ft2232
+ft2232_device_desc "NXHX 50-ETM"
+ft2232_layout comstick
+ft2232_vid_pid 0x0640 0x0028
+adapter_khz 6000

debuggers/openocd/tcl/interface/hilscher_nxhx50_re.cfg

@@ -0,0 +1,11 @@
+#
+# Hilscher NXHX 50-RE
+#
+# http://de.hilscher.com/products_details_hardware.html?p_id=P_483c0f582ad36&bs=20
+#
+
+interface ft2232
+ft2232_device_desc "NXHX50-RE"
+ft2232_layout comstick
+ft2232_vid_pid 0x0640 0x0028
+adapter_khz 6000

debuggers/openocd/tcl/interface/hitex_str9-comstick.cfg

@@ -0,0 +1,11 @@
+#
+# Hitex STR9-comStick
+#
+# http://www.hitex.com/index.php?id=383
+#
+
+interface ft2232
+ft2232_device_desc "STR9-comStick"
+ft2232_layout comstick
+ft2232_vid_pid 0x0640 0x002c
+

debuggers/openocd/tcl/interface/icebear.cfg

@@ -0,0 +1,11 @@
+#
+# Section5 ICEBear
+#
+# http://section5.ch/icebear
+#
+
+interface ft2232
+ft2232_device_desc "ICEbear JTAG adapter"
+ft2232_layout icebear
+ft2232_vid_pid 0x0403 0xc140
+

debuggers/openocd/tcl/interface/jlink.cfg

@@ -0,0 +1,8 @@
+#
+# Segger J-Link
+#
+# http://www.segger.com/jlink.html
+#
+
+interface jlink
+

debuggers/openocd/tcl/interface/jtag-lock-pick_tiny_2.cfg

@@ -0,0 +1,10 @@
+#
+# DISTORTEC JTAG-lock-pick Tiny 2
+#
+# http://www.distortec.com
+#
+
+interface ft2232
+ft2232_device_desc "JTAG-lock-pick Tiny 2"
+ft2232_layout ktlink
+ft2232_vid_pid 0x0403 0x8220

debuggers/openocd/tcl/interface/jtagkey-tiny.cfg

@@ -0,0 +1,9 @@
+#
+# Amontec JTAGkey-tiny
+#
+# http://www.amontec.com/jtagkey-tiny.shtml
+#
+
+# The JTAGkey-tiny uses exactly the same config as the JTAGkey.
+source [find interface/jtagkey.cfg]
+

debuggers/openocd/tcl/interface/jtagkey.cfg

@@ -0,0 +1,11 @@
+#
+# Amontec JTAGkey
+#
+# http://www.amontec.com/jtagkey.shtml
+#
+
+interface ft2232
+ft2232_device_desc "Amontec JTAGkey"
+ft2232_layout jtagkey
+ft2232_vid_pid 0x0403 0xcff8
+

debuggers/openocd/tcl/interface/jtagkey2.cfg

@@ -0,0 +1,11 @@
+#
+# Amontec JTAGkey2
+#
+# http://www.amontec.com/jtagkey2.shtml
+#
+
+interface ft2232
+ft2232_device_desc "Amontec JTAGkey-2"
+ft2232_layout jtagkey
+ft2232_vid_pid 0x0403 0xCFF8
+

debuggers/openocd/tcl/interface/jtagkey2p.cfg

@@ -0,0 +1,11 @@
+#
+# Amontec JTAGkey2P
+#
+# http://www.amontec.com/jtagkey2p.shtml
+#
+
+interface ft2232
+ft2232_device_desc "Amontec JTAGkey-2P"
+ft2232_layout jtagkey
+ft2232_vid_pid 0x0403 0xCFF8
+

debuggers/openocd/tcl/interface/kt-link.cfg

@@ -0,0 +1,10 @@
+#
+# Kristech KT-Link
+#
+# http://www.kristech.eu
+#
+
+interface ft2232
+ft2232_device_desc "KT-LINK"
+ft2232_layout ktlink
+ft2232_vid_pid 0x0403 0xBBE2

debuggers/openocd/tcl/interface/lisa-l.cfg

@@ -0,0 +1,11 @@
+#
+# Lisa/L
+#
+# http://paparazzi.enac.fr/wiki/Lisa
+#
+
+interface ft2232
+ft2232_vid_pid 0x0403 0x6010
+ft2232_device_desc "Lisa/L"
+ft2232_layout "lisa-l"
+ft2232_latency 2

debuggers/openocd/tcl/interface/luminary-icdi.cfg

@@ -0,0 +1,21 @@
+#
+# 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 FT2232 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 ft2232
+ft2232_device_desc "Luminary Micro ICDI Board"
+ft2232_layout luminary_icdi
+ft2232_vid_pid 0x0403 0xbcda

debuggers/openocd/tcl/interface/luminary-lm3s811.cfg

@@ -0,0 +1,18 @@
+#
+# Luminary Micro Stellaris LM3S811 Evaluation Kit
+#
+# http://www.luminarymicro.com/products/stellaris_811_evaluation_kits.html
+#
+# NOTE:  this is only for boards *before* Rev C, which adds support
+# for SWO tracing with ADBUS_6 DBG_ENn and BDBUS_4 SWO_EN signals.
+# The "evb_lm3s811" layout doesn't set up those signals.
+#
+# Rev C boards work more like the other Stellaris eval boards.  They
+# need to use the "luminary_icdi" layout to work correctly.
+#
+
+interface ft2232
+ft2232_device_desc "LM3S811 Evaluation Board"
+ft2232_layout evb_lm3s811
+ft2232_vid_pid 0x0403 0xbcd9
+

debuggers/openocd/tcl/interface/luminary.cfg

@@ -0,0 +1,31 @@
+#
+# 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 FT2232 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 FT2232 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 ft2232
+ft2232_device_desc "Stellaris Evaluation Board"
+ft2232_layout luminary_icdi
+ft2232_vid_pid 0x0403 0xbcd9
+

debuggers/openocd/tcl/interface/minimodule.cfg

@@ -0,0 +1,10 @@
+#
+# FTDI MiniModule
+#
+# http://www.ftdichip.com/Support/Documents/DataSheets/Modules/DS_FT2232H_Mini_Module.pdf
+#
+
+interface ft2232
+ft2232_device_desc "FT2232H MiniModule"
+ft2232_layout "minimodule"
+ft2232_vid_pid 0x0403 0x6010

debuggers/openocd/tcl/interface/neodb.cfg

@@ -0,0 +1,10 @@
+#
+# Openmoko USB JTAG/RS232 adapter
+#
+# http://wiki.openmoko.org/wiki/Debug_Board_v3
+#
+
+interface ft2232
+ft2232_device_desc "Debug Board for Neo1973"
+ft2232_layout jtagkey
+ft2232_vid_pid 0x1457 0x5118

debuggers/openocd/tcl/interface/ngxtech.cfg

@@ -0,0 +1,10 @@
+#
+# NGX ARM USB JTAG
+#
+# http://shop.ngxtechnologies.com/product_info.php?cPath=26&products_id=30
+#
+
+interface ft2232
+ft2232_device_desc "NGX JTAG A"
+ft2232_vid_pid 0x0403 0x6010
+ft2232_layout "oocdlink"

debuggers/openocd/tcl/interface/olimex-arm-usb-ocd-h.cfg

@@ -0,0 +1,11 @@
+#
+# Olimex ARM-USB-OCD-H
+#
+# http://www.olimex.com/dev/arm-usb-ocd.html
+#
+
+interface ft2232
+ft2232_device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
+ft2232_layout olimex-jtag
+ft2232_vid_pid 0x15ba 0x002b
+

debuggers/openocd/tcl/interface/olimex-arm-usb-ocd.cfg

@@ -0,0 +1,11 @@
+#
+# Olimex ARM-USB-OCD
+#
+# http://www.olimex.com/dev/arm-usb-ocd.html
+#
+
+interface ft2232
+ft2232_device_desc "Olimex OpenOCD JTAG"
+ft2232_layout olimex-jtag
+ft2232_vid_pid 0x15ba 0x0003
+

debuggers/openocd/tcl/interface/olimex-arm-usb-tiny-h.cfg

@@ -0,0 +1,11 @@
+#
+# Olimex ARM-USB-TINY-H
+#
+# http://www.olimex.com/dev/arm-usb-tiny-h.html
+#
+
+interface ft2232
+ft2232_device_desc "Olimex OpenOCD JTAG ARM-USB-TINY-H"
+ft2232_layout olimex-jtag
+ft2232_vid_pid 0x15ba 0x002a
+

debuggers/openocd/tcl/interface/olimex-jtag-tiny.cfg

@@ -0,0 +1,11 @@
+#
+# Olimex ARM-USB-TINY
+#
+# http://www.olimex.com/dev/arm-usb-tiny.html
+#
+
+interface ft2232
+ft2232_device_desc "Olimex OpenOCD JTAG TINY"
+ft2232_layout olimex-jtag
+ft2232_vid_pid 0x15ba 0x0004
+

debuggers/openocd/tcl/interface/oocdlink.cfg

@@ -0,0 +1,12 @@
+#
+# Joern Kaipf's OOCDLink
+#
+# http://www.joernonline.de/contrexx2/cms/index.php?page=126
+#
+
+interface ft2232
+ft2232_device_desc "OOCDLink"
+ft2232_layout oocdlink
+ft2232_vid_pid 0x0403 0xbaf8
+adapter_khz 5
+

debuggers/openocd/tcl/interface/opendous.cfg

@@ -0,0 +1,7 @@
+#
+# opendous-jtag
+#
+# http://code.google.com/p/opendous-jtag/
+#
+
+interface opendous

debuggers/openocd/tcl/interface/opendous_ftdi.cfg

@@ -0,0 +1,15 @@
+#
+# Opendous
+#
+# http://code.google.com/p/opendous/wiki/JTAG
+#
+# According to the website, it is similar to jtagkey, but it uses channel B
+# (and it has a different pid number).
+#
+
+interface ft2232
+ft2232_device_desc "Dual RS232-HS"
+ft2232_layout jtagkey
+ft2232_vid_pid 0x0403 0x6010
+ft2232_channel 2
+

debuggers/openocd/tcl/interface/openocd-usb-hs.cfg

@@ -0,0 +1,11 @@
+#
+# embedded projects openocd usb adapter v3
+#
+# http://shop.embedded-projects.net/index.php?module=artikel&action=artikel&id=14
+#
+
+interface ft2232
+ft2232_vid_pid 0x0403 0x6010
+ft2232_device_desc "Dual RS232-HS"
+ft2232_layout "oocdlink"
+ft2232_latency 2

debuggers/openocd/tcl/interface/openocd-usb.cfg

@@ -0,0 +1,11 @@
+#
+# Hubert Hoegl's USB to JTAG
+#
+# http://www.hs-augsburg.de/~hhoegl/proj/usbjtag/usbjtag.html
+#
+
+interface ft2232
+ft2232_vid_pid 0x0403 0x6010
+ft2232_device_desc "Dual RS232"
+ft2232_layout "oocdlink"
+ft2232_latency 2

debuggers/openocd/tcl/interface/openrd.cfg

@@ -0,0 +1,12 @@
+#
+# Marvell OpenRD
+#
+# http://www.marvell.com/products/embedded_processors/developer/kirkwood/openrd.jsp
+#
+
+interface ft2232
+ft2232_layout sheevaplug
+ft2232_vid_pid 0x0403 0x9e90
+ft2232_device_desc "OpenRD JTAGKey FT2232D B"
+adapter_khz 3000
+