#
adapter driver ftdi
-ftdi_device_desc "Digilent USB Device"
-ftdi_vid_pid 0x0403 0x6014
+ftdi device_desc "Digilent USB Device"
+ftdi vid_pid 0x0403 0x6014
-ftdi_layout_init 0x8008 0x800b
+ftdi layout_init 0x8008 0x800b
adapter speed 25000
adapter driver ftdi
adapter speed 30000
-ftdi_device_desc "Digilent USB Device"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "Digilent USB Device"
+ftdi vid_pid 0x0403 0x6010
# channel 0 is dedicated for Digilent's DPTI Interface
# channel 1 is used for JTAG
-ftdi_channel 1
+ftdi channel 1
# just TCK TDI TDO TMS, no reset
-ftdi_layout_init 0x0088 0x008b
+ftdi layout_init 0x0088 0x008b
reset_config none
# Enable sampling on falling edge for high JTAG speeds.
-ftdi_tdo_sample_edge falling
+ftdi tdo_sample_edge falling
transport select jtag
#
source [find interface/ftdi/dp_busblaster.cfg]
-ftdi_channel 1
+ftdi channel 1
jtag newtap xc2c32a tap -expected-id 0x06e1c093 -irlen 8
#
source [find interface/ftdi/dp_busblaster.cfg]
-ftdi_channel 1
+ftdi channel 1
jtag newtap xc2c64a tap -expected-id 0x06e5c093 -irlen 8
# JTAG for the STM32F4x chip used on the Gumstix AeroCore is available on
# the first interface of a Quad FTDI chip. nTRST is bit 4.
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6011
+ftdi vid_pid 0x0403 0x6011
-ftdi_layout_init 0x0000 0x001b
-ftdi_layout_signal nTRST -data 0x0010
+ftdi layout_init 0x0000 0x001b
+ftdi layout_signal nTRST -data 0x0010
source [find target/stm32f4x.cfg]
reset_config trst_only
adapter driver ftdi
-ftdi_device_desc "Quad RS232-HS"
-ftdi_vid_pid 0x0403 0x6011
-ftdi_channel 0
-ftdi_layout_init 0x0008 0x000b
+ftdi device_desc "Quad RS232-HS"
+ftdi vid_pid 0x0403 0x6011
+ftdi channel 0
+ftdi layout_init 0x0008 0x000b
# adapter usb location 1:8
reset_config none
arm11 memwrite burst disable
adapter speed 1000
-ftdi_tdo_sample_edge falling
+ftdi tdo_sample_edge falling
proc kindle2_init {} {
imx3x_reset
adapter speed 10000
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0c08 0x0f1b
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
reset_config srst_only
source [find target/nds32v5.cfg]
# Therefore, prefer external power supply.
adapter driver ftdi
-ftdi_device_desc "Mimas Artix 7 FPGA Module"
-ftdi_vid_pid 0x2a19 0x1009
+ftdi device_desc "Mimas Artix 7 FPGA Module"
+ftdi vid_pid 0x2a19 0x1009
# channel 0 is for custom purpose by users (like uart, fifo etc)
# channel 1 is reserved for JTAG (by-default) or SPI (possible via changing solder jumpers)
-ftdi_channel 1
-ftdi_tdo_sample_edge falling
+ftdi channel 1
+ftdi tdo_sample_edge falling
# FTDI Pin Layout
# OE_N is JTAG buffer output enable signal (active-low)
# PROG_B is not used, so left as input to FTDI.
#
-ftdi_layout_init 0x0008 0x004b
+ftdi layout_init 0x0008 0x004b
reset_config none
adapter speed 30000
# the board has an onboard FTDI FT232H chip
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6014
-ftdi_channel 0
+ftdi vid_pid 0x0403 0x6014
+ftdi channel 0
-ftdi_layout_init 0x0000 0x030b
-ftdi_layout_signal nTRST -data 0x0100 -noe 0x0100
+ftdi layout_init 0x0000 0x030b
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0100
source [find target/quark_d20xx.cfg]
# which features an Artix 7 FPGA.
adapter driver ftdi
-ftdi_device_desc "Quad RS232-HS"
-ftdi_vid_pid 0x0403 0x6011
-ftdi_channel 0
+ftdi device_desc "Quad RS232-HS"
+ftdi vid_pid 0x0403 0x6011
+ftdi channel 0
# Use this to distinguish multiple boards by topology
#adapter usb location 5:1
# sampling on falling edge generally seems to work and accelerates things but
# is not fully tested
-#ftdi_tdo_sample_edge falling
+#ftdi tdo_sample_edge falling
# EN_USB_JTAG on ADBUS7: out, high
# USB_nTRST on ADBUS4: out, high, but R46 is DNP
-ftdi_layout_init 0x0098 0x008b
-#ftdi_layout_signal EN_USB -data 0x0080
-#ftdi_layout_signal nTRST -data 0x0010
+ftdi layout_init 0x0098 0x008b
+#ftdi layout_signal EN_USB -data 0x0080
+#ftdi layout_signal nTRST -data 0x0010
reset_config none
adapter speed 5000
flash bank spi0 fespi 0x40000000 0 0 0 $_TARGETNAME.0 0x20004000
init
if {[ info exists pulse_srst]} {
- ftdi_set_signal nSRST 0
- ftdi_set_signal nSRST z
+ ftdi set_signal nSRST 0
+ ftdi set_signal nSRST z
}
halt
flash protect 0 64 last off
flash bank spi0 fespi 0x40000000 0 0 0 $_TARGETNAME.0 0x20004000
init
if {[ info exists pulse_srst]} {
- ftdi_set_signal nSRST 0
- ftdi_set_signal nSRST z
+ ftdi set_signal nSRST 0
+ ftdi set_signal nSRST z
}
halt
flash protect 0 64 last off
adapter speed 10000
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "Dual RS232-HS"
+ftdi vid_pid 0x0403 0x6010
-ftdi_layout_init 0x0008 0x001b
-ftdi_layout_signal nSRST -oe 0x0020 -data 0x0020
+ftdi layout_init 0x0008 0x001b
+ftdi layout_signal nSRST -oe 0x0020 -data 0x0020
#Reset Stretcher logic on FE310 is ~1 second long
#This doesn't apply if you use
-# ftdi_set_signal, but still good to document
+# ftdi set_signal, but still good to document
#adapter srst delay 1500
set _CHIPNAME riscv
init
#reset -- This type of reset is not implemented yet
if {[ info exists pulse_srst]} {
- ftdi_set_signal nSRST 0
- ftdi_set_signal nSRST z
+ ftdi set_signal nSRST 0
+ ftdi set_signal nSRST z
#Wait for the reset stretcher
#It will work without this, but
#will incur lots of delays for later commands.
# xds100v2 config says add this to the end
init
-ftdi_set_signal PWR_RST 1
+ftdi set_signal PWR_RST 1
jtag arp_init
#
adapter driver ftdi
-ftdi_device_desc "USB<=>JTAG&RS232"
-ftdi_vid_pid 0x1457 0x5118
+ftdi device_desc "USB<=>JTAG&RS232"
+ftdi vid_pid 0x1457 0x5118
-ftdi_layout_init 0x0f08 0x0f1b
-ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800
-ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_init 0x0f08 0x0f1b
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "Symphony SoundBite"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0c08 0x0c2b
+ftdi layout_signal nTRST -data 0x0800
+ftdi layout_signal nSRST -data 0x0400
# http://www.ftdichip.com/Support/Documents/AppNotes/AN_129_FTDI_Hi_Speed_USB_To_JTAG_Example.pdf
adapter driver ftdi
-#ftdi_device_desc "C232HM-DDHSL-0"
-#ftdi_device_desc "C232HM-EDHSL-0"
+#ftdi device_desc "C232HM-DDHSL-0"
+#ftdi device_desc "C232HM-EDHSL-0"
# Common PID for FT232H
-ftdi_vid_pid 0x0403 0x6014
+ftdi vid_pid 0x0403 0x6014
# Layout
# High data byte 0x40 configures red LED on ACBUS6 initially high (unlit, since active-low)
# Low data byte 0x08 configures TMS on ACBUS3 initially high (asserted); TCK, TDI low
# High direction byte 0x40 configures red LED on ACBUS6 as high (output)
# Low direction byte 0x0b configures TDO on ACBUS2 as low (input)
-ftdi_layout_init 0x4008 0x400b
+ftdi layout_init 0x4008 0x400b
# ---A*BUS-------CCCCCCCC|DDDDDDDD
# --------\______76543210|76543210
#GPIOL2 0x0040 = 00000000|01000000 = ADBUS6
#GPIOL3 0x0080 = 00000000|10000000 = ADBUS7
# -ndata treats the LED as active-low for expected behavior (toggle when transferring)
-ftdi_layout_signal LED -ndata 0x4000
+ftdi layout_signal LED -ndata 0x4000
# Available for aliasing as desired
-ftdi_layout_signal GPIOL0 -data 0x0010 -oe 0x0010
-ftdi_layout_signal GPIOL1 -data 0x0020 -oe 0x0020
-ftdi_layout_signal GPIOL2 -data 0x0040 -oe 0x0040
-ftdi_layout_signal GPIOL3 -data 0x0080 -oe 0x0080
+ftdi layout_signal GPIOL0 -data 0x0010 -oe 0x0010
+ftdi layout_signal GPIOL1 -data 0x0020 -oe 0x0020
+ftdi layout_signal GPIOL2 -data 0x0040 -oe 0x0040
+ftdi layout_signal GPIOL3 -data 0x0080 -oe 0x0080
# C232HM FT232H JTAG/Other
# Num Color Name Func
echo "as working or fixed."
adapter driver ftdi
-ftdi_device_desc "USB-A9260"
-ftdi_vid_pid 0x0403 0x6010
+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
+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
echo "as working or fixed."
adapter driver ftdi
-ftdi_device_desc "USB-A9260"
-ftdi_vid_pid 0x0403 0x6001
+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
+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
#
adapter driver ftdi
-ftdi_device_desc "Cortino"
-ftdi_vid_pid 0x0640 0x0032
+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
+ftdi layout_init 0x0108 0x010b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0200 -oe 0x0200
# (the later being the OEM on-board version)
adapter driver ftdi
-ftdi_device_desc "Digilent Adept USB Device"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "Digilent Adept USB Device"
+ftdi vid_pid 0x0403 0x6010
# channel 1 does not have any functionality
-ftdi_channel 0
+ftdi channel 0
# just TCK TDI TDO TMS, no reset
-ftdi_layout_init 0x0088 0x008b
+ftdi layout_init 0x0088 0x008b
reset_config none
# this supports JTAG-HS2 (and apparently Nexys4 as well)
adapter driver ftdi
-ftdi_device_desc "Digilent Adept USB Device"
-ftdi_vid_pid 0x0403 0x6014
+ftdi device_desc "Digilent Adept USB Device"
+ftdi vid_pid 0x0403 0x6014
-ftdi_channel 0
-ftdi_layout_init 0x00e8 0x60eb
+ftdi channel 0
+ftdi layout_init 0x00e8 0x60eb
reset_config none
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6014
-ftdi_device_desc "Digilent USB Device"
+ftdi vid_pid 0x0403 0x6014
+ftdi device_desc "Digilent USB Device"
# From Digilent support:
# The SRST pin is [...] 0x20 and 0x10 is the /OE (active low output enable)
-ftdi_layout_init 0x2088 0x308b
-ftdi_layout_signal nSRST -data 0x2000 -noe 0x1000
+ftdi layout_init 0x2088 0x308b
+ftdi layout_signal nSRST -data 0x2000 -noe 0x1000
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6014
+ftdi vid_pid 0x0403 0x6014
-ftdi_layout_init 0x20e8 0x3feb
-ftdi_layout_signal nSRST -data 0x2000
-ftdi_layout_signal GPIO2 -data 0x2000
-ftdi_layout_signal GPIO1 -data 0x0200
-ftdi_layout_signal GPIO0 -data 0x0100
+ftdi layout_init 0x20e8 0x3feb
+ftdi layout_signal nSRST -data 0x2000
+ftdi layout_signal GPIO2 -data 0x2000
+ftdi layout_signal GPIO1 -data 0x0200
+ftdi layout_signal GPIO0 -data 0x0100
# https://www.xilinx.com/products/boards-and-kits/kcu105.html#documentation
#
# Note that the digilent_jtag_smt2 layout does not work and hangs while
-# the ftdi_device_desc from digilent_hs2 is wrong.
+# the ftdi device_desc from digilent_hs2 is wrong.
adapter driver ftdi
-ftdi_device_desc "Digilent USB Device"
-ftdi_vid_pid 0x0403 0x6014
-ftdi_channel 0
-ftdi_layout_init 0x00e8 0x60eb
+ftdi device_desc "Digilent USB Device"
+ftdi vid_pid 0x0403 0x6014
+ftdi channel 0
+ftdi layout_init 0x00e8 0x60eb
reset_config none
echo "mailing list, so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0008 0x000b
+ftdi layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi layout_signal nSRST -data 0x0040 -oe 0x0040
and use dp_busblaster_kt-link.cfg instead"
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0c08 0x0f1b
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
#
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "Dual RS232-HS"
+ftdi vid_pid 0x0403 0x6010
-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
-ftdi_layout_signal SWD_EN -ndata 0x0020 -oe 0x2000
-ftdi_layout_signal SWDIO_OE -ndata 0x1000
+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
+ftdi layout_signal SWD_EN -ndata 0x0020 -oe 0x2000
+ftdi layout_signal SWDIO_OE -ndata 0x1000
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0008 0x000b
+ftdi layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi layout_signal nSRST -data 0x0040 -oe 0x0040
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6010
-ftdi_device_desc "FLOSS-JTAG"
-#ftdi_serial "FJ000001"
+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
+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
#
adapter driver ftdi
-ftdi_device_desc "Flyswatter"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0818 0x0cfb
+ftdi layout_signal nTRST -data 0x0010
+ftdi layout_signal nSRST -oe 0x0020
+ftdi layout_signal LED -data 0x0c00
#
adapter driver ftdi
-ftdi_device_desc "Flyswatter2"
-ftdi_vid_pid 0x0403 0x6010
+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
+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
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6014
+ftdi vid_pid 0x0403 0x6014
# data MSB..LSB direction (1:out) MSB..LSB
# 0000'0000'0011'0000 0000'0000'0011'1011
-ftdi_layout_init 0x0030 0x003b
+ftdi layout_init 0x0030 0x003b
# 0xfff8 0xfffb
# Those signal are only required on some platforms or may required to be
# enabled explicitly (e.g. nrf5x chips).
-ftdi_layout_signal nSRST -data 0x0010 -oe 0x0010
-ftdi_layout_signal nTRST -data 0x0020 -oe 0x0020
+ftdi layout_signal nSRST -data 0x0010 -oe 0x0010
+ftdi layout_signal nTRST -data 0x0020 -oe 0x0020
# swd enable
-ftdi_layout_signal SWD_EN -data 0
+ftdi layout_signal SWD_EN -data 0
# tri-state (configure as input) TDO/TIO when reading
-ftdi_layout_signal SWDIO_OE -data 0
+ftdi layout_signal SWDIO_OE -data 0
transport select swd
# re-configure TDO as tri-state
-#ftdi_layout_signal TDO -data 0x0002 -oe 0x0002
-#ftdi_layout_signal TDI -data 0x0004
+#ftdi layout_signal TDO -data 0x0002 -oe 0x0002
+#ftdi layout_signal TDI -data 0x0004
# Adafruit FT232H JTAG SWD
# Name Pin Name Func Func
#
adapter driver ftdi
-ftdi_device_desc "USB-JTAG"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "USB-JTAG"
+ftdi vid_pid 0x0403 0x6010
-ftdi_layout_init 0x0058 0x007b
-ftdi_layout_signal nTRST -data 0x0010
-ftdi_layout_signal nSRST -oe 0x0020
+ftdi layout_init 0x0058 0x007b
+ftdi layout_signal nTRST -data 0x0010
+ftdi layout_signal nSRST -oe 0x0020
#
adapter driver ftdi
-ftdi_channel 0
-ftdi_vid_pid 0x0403 0x6014
-ftdi_device_desc "HIE JTAG Debugger"
+ftdi channel 0
+ftdi vid_pid 0x0403 0x6014
+ftdi device_desc "HIE JTAG Debugger"
-ftdi_layout_init 0x0c08 0x4f1b
+ftdi layout_init 0x0c08 0x4f1b
# define both Reset signals
-ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
-ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
# Toggle USB LED
-ftdi_layout_signal LED -ndata 0x4000
+ftdi layout_signal LED -ndata 0x4000
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "NXHX 10-ETM"
-ftdi_vid_pid 0x0640 0x0028
+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
+ftdi layout_init 0x0308 0x030b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0200
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "NXHX 500-ETM"
-ftdi_vid_pid 0x0640 0x0028
+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
+ftdi layout_init 0x0308 0x030b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0200
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "NXHX 500-RE"
-ftdi_vid_pid 0x0640 0x0028
+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
+ftdi layout_init 0x0308 0x030b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0200
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "NXHX 50-ETM"
-ftdi_vid_pid 0x0640 0x0028
+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
+ftdi layout_init 0x0308 0x030b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0200
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "NXHX50-RE"
-ftdi_vid_pid 0x0640 0x0028
+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
+ftdi layout_init 0x0308 0x030b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0200
adapter driver ftdi
-ftdi_device_desc "LPC1768-Stick"
-ftdi_vid_pid 0x0640 0x0026
+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
+ftdi layout_init 0x0388 0x038b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0080 -noe 0x200
#
adapter driver ftdi
-ftdi_device_desc "STR9-comStick"
-ftdi_vid_pid 0x0640 0x002c
+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
+ftdi layout_init 0x0108 0x010b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0200 -oe 0x0200
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "ICEbear JTAG adapter"
-ftdi_vid_pid 0x0403 0xc140
+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
+ftdi layout_init 0x0028 0x002b
+ftdi layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi layout_signal nSRST -data 0x0020
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6011
-ftdi_channel 0
+ftdi vid_pid 0x0403 0x6011
+ftdi channel 0
-ftdi_layout_init 0x00f8 0x000b
+ftdi layout_init 0x00f8 0x000b
-ftdi_layout_signal RESET_B -data 0x0010 -oe 0x0010
+ftdi layout_signal RESET_B -data 0x0010 -oe 0x0010
# Called SYS_nRST in schematics
-ftdi_layout_signal nSRST -data 0x0020 -oe 0x0020
-ftdi_layout_signal IO_nRST -data 0x0040 -oe 0x0040
-ftdi_layout_signal ONOFF_B -data 0x0080 -oe 0x0080
+ftdi layout_signal nSRST -data 0x0020 -oe 0x0020
+ftdi layout_signal IO_nRST -data 0x0040 -oe 0x0040
+ftdi layout_signal ONOFF_B -data 0x0080 -oe 0x0080
-ftdi_layout_signal GPIO1 -data 0x0100 -oe 0x0100
-ftdi_layout_signal GPIO2 -data 0x0200 -oe 0x0200
-ftdi_layout_signal GPIO3 -data 0x0400 -oe 0x0400
-ftdi_layout_signal GPIO4 -data 0x0800 -oe 0x0800
+ftdi layout_signal GPIO1 -data 0x0100 -oe 0x0100
+ftdi layout_signal GPIO2 -data 0x0200 -oe 0x0200
+ftdi layout_signal GPIO3 -data 0x0400 -oe 0x0400
+ftdi layout_signal GPIO4 -data 0x0800 -oe 0x0800
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6010
+ftdi vid_pid 0x0403 0x6010
-ftdi_layout_init 0x0508 0x0f1b
-ftdi_layout_signal nSRST -noe 0x0400 -data 0x0800
-ftdi_layout_signal nTRST -noe 0x0100 -data 0x0200
+ftdi layout_init 0x0508 0x0f1b
+ftdi layout_signal nSRST -noe 0x0400 -data 0x0800
+ftdi layout_signal nTRST -noe 0x0100 -data 0x0200
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0008 0x000b
+ftdi layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi layout_signal nSRST -data 0x0040 -oe 0x0040
# 5 kV isolated JTAG/SWD + UART adapter by Unjo AB
adapter driver ftdi
-ftdi_vid_pid 0x22b7 0x150d
+ftdi vid_pid 0x22b7 0x150d
-ftdi_layout_init 0x0ff8 0xfffb
+ftdi layout_init 0x0ff8 0xfffb
-ftdi_layout_signal LED -ndata 0x0100
-ftdi_layout_signal nTRST -data 0x0200
-ftdi_layout_signal nSRST -noe 0x0400
-ftdi_layout_signal SWDIO_OE -data 0x0008
+ftdi layout_signal LED -ndata 0x0100
+ftdi layout_signal nTRST -data 0x0200
+ftdi layout_signal nSRST -noe 0x0400
+ftdi layout_signal SWDIO_OE -data 0x0008
# Mode signals, either of these needs to be high to drive the JTAG/SWD pins.
# The power-on state is low for both signals but the init setting above sets
# JTAG_EN high.
-ftdi_layout_signal SWD_EN -data 0x1000
-ftdi_layout_signal JTAG_EN -data 0x0800
+ftdi layout_signal SWD_EN -data 0x1000
+ftdi layout_signal JTAG_EN -data 0x0800
# In SWD mode, the JTAG_EN signal doubles as SWO_EN_N which switches the
# second FTDI channel UART RxD to the SWO pin instead of the separate RxD
# pin. Note that the default init state has this pin high so when OpenOCD
# starts in SWD mode, SWO is by default disabled. To enable SWO tracing,
-# issue the command 'ftdi_set_signal SWO_EN 1' where tracing is configured.
+# issue the command 'ftdi set_signal SWO_EN 1' where tracing is configured.
# To switch back to using the separate UART, SWO_EN needs to be disabled
# before exiting OpenOCD, or the adapter replugged.
-ftdi_layout_signal SWO_EN -nalias JTAG_EN
+ftdi layout_signal SWO_EN -nalias JTAG_EN
#
adapter driver ftdi
-ftdi_device_desc "JTAG-lock-pick Tiny 2"
-ftdi_vid_pid 0x0403 0x8220
+ftdi device_desc "JTAG-lock-pick Tiny 2"
+ftdi vid_pid 0x0403 0x8220
-ftdi_layout_init 0x8c28 0xff3b
-ftdi_layout_signal SWD_EN -ndata 0x0020 -oe 0x2000
-ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
-ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800
-ftdi_layout_signal SWDIO_OE -ndata 0x1000
-ftdi_layout_signal LED -ndata 0x8000
+ftdi layout_init 0x8c28 0xff3b
+ftdi layout_signal SWD_EN -ndata 0x0020 -oe 0x2000
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
+ftdi layout_signal SWDIO_OE -ndata 0x1000
+ftdi layout_signal LED -ndata 0x8000
#
adapter driver ftdi
-ftdi_device_desc "Amontec JTAGkey"
-ftdi_vid_pid 0x0403 0xcff8
+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
+ftdi layout_init 0x0c08 0x0f1b
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
#
adapter driver ftdi
-ftdi_device_desc "Amontec JTAGkey-2"
-ftdi_vid_pid 0x0403 0xcff8
+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
+ftdi layout_init 0x0c08 0x0f1b
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
#
adapter driver ftdi
-ftdi_device_desc "Amontec JTAGkey-2P"
-ftdi_vid_pid 0x0403 0xcff8
+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
+ftdi layout_init 0x0c08 0x0f1b
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
#
adapter driver ftdi
-ftdi_device_desc "KT-LINK"
-ftdi_vid_pid 0x0403 0xbbe2
+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
-ftdi_layout_signal SWD_EN -ndata 0x0020 -oe 0x2000
-ftdi_layout_signal SWDIO_OE -ndata 0x1000
+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
+ftdi layout_signal SWD_EN -ndata 0x0020 -oe 0x2000
+ftdi layout_signal SWDIO_OE -ndata 0x1000
echo "mailing list, so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "Lisa/L"
-ftdi_vid_pid 0x0403 0x6010
-ftdi_channel 1
+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
+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
#
adapter driver ftdi
-ftdi_device_desc "Luminary Micro ICDI Board"
-ftdi_vid_pid 0x0403 0xbcda
+ftdi device_desc "Luminary Micro ICDI Board"
+ftdi vid_pid 0x0403 0xbcda
-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
+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
#
adapter driver ftdi
-ftdi_device_desc "LM3S811 Evaluation Board"
-ftdi_vid_pid 0x0403 0xbcd9
+ftdi device_desc "LM3S811 Evaluation Board"
+ftdi vid_pid 0x0403 0xbcd9
-ftdi_layout_init 0x0088 0x008b
-ftdi_layout_signal nSRST -data 0x0020 -oe 0x0020
-ftdi_layout_signal SWD_EN -ndata 0x0080
-ftdi_layout_signal SWDIO_OE -data 0x0008
+ftdi layout_init 0x0088 0x008b
+ftdi layout_signal nSRST -data 0x0020 -oe 0x0020
+ftdi layout_signal SWD_EN -ndata 0x0080
+ftdi layout_signal SWDIO_OE -data 0x0008
#
adapter driver ftdi
-ftdi_device_desc "Stellaris Evaluation Board"
-ftdi_vid_pid 0x0403 0xbcd9
+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
+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
#
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "Dual RS232-HS"
+ftdi vid_pid 0x0403 0x6010
-ftdi_channel 0
-ftdi_layout_init 0x0008 0x000b
-ftdi_layout_signal nTRST -data 0x0010 -oe 0x0010
-ftdi_layout_signal nSRST -data 0x0020 -oe 0x0020
+ftdi channel 0
+ftdi layout_init 0x0008 0x000b
+ftdi layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi layout_signal nSRST -data 0x0020 -oe 0x0020
#
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "Dual RS232-HS"
+ftdi vid_pid 0x0403 0x6010
-ftdi_layout_init 0x0008 0x000b
+ftdi layout_init 0x0008 0x000b
#Select your module type and channel
-#ftdi_device_desc "FT2232H MiniModule"
-ftdi_vid_pid 0x0403 0x6010
-#ftdi_channel 1
+#ftdi device_desc "FT2232H MiniModule"
+ftdi vid_pid 0x0403 0x6010
+#ftdi channel 1
-#ftdi_device_desc "FT4232H MiniModule"
-#ftdi_vid_pid 0x0403 0x6011
-#ftdi_channel 1
+#ftdi device_desc "FT4232H MiniModule"
+#ftdi vid_pid 0x0403 0x6011
+#ftdi channel 1
-ftdi_layout_init 0x0000 0x000b
-ftdi_layout_signal nSRST -data 0x0010 -oe 0x0010
-ftdi_layout_signal SWD_EN -data 0
-ftdi_layout_signal SWDIO_OE -data 0
+ftdi layout_init 0x0000 0x000b
+ftdi layout_signal nSRST -data 0x0010 -oe 0x0010
+ftdi layout_signal SWD_EN -data 0
+ftdi layout_signal SWDIO_OE -data 0
transport select swd
#
adapter driver ftdi
-ftdi_device_desc "FT2232H MiniModule"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "FT2232H MiniModule"
+ftdi vid_pid 0x0403 0x6010
# Every pin set as high impedance except TCK, TDI, TDO and TMS
-ftdi_layout_init 0x0008 0x000b
+ftdi layout_init 0x0008 0x000b
# nSRST defined on pin CN2-13 of the MiniModule (pin ADBUS5 [AD5] on the FT2232H chip)
# This choice is arbitrary. Use other GPIO pin if desired.
-ftdi_layout_signal nSRST -data 0x0020 -oe 0x0020
+ftdi layout_signal nSRST -data 0x0020 -oe 0x0020
adapter driver ftdi
# The miniSpartan6+ sadly doesn't have a custom device description, so we just
# have to hope you got it right.
-#ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+#ftdi device_desc "Dual RS232-HS"
+ftdi vid_pid 0x0403 0x6010
# interface 1 is the uart
-ftdi_channel 0
+ftdi channel 0
# just TCK TDI TDO TMS, no reset
-ftdi_layout_init 0x0008 0x000b
+ftdi layout_init 0x0008 0x000b
reset_config none
# this generally works fast: the fpga can handle 30MHz, the spi flash can handle
# 54MHz with simple read, no dummy cycles, and wait-for-write-completion
#
adapter driver ftdi
-ftdi_device_desc "DAS JDS miniWiggler V3.1"
-ftdi_vid_pid 0x058b 0x0043
+ftdi device_desc "DAS JDS miniWiggler V3.1"
+ftdi vid_pid 0x058b 0x0043
-ftdi_channel 0
-ftdi_layout_init 0x0008 0x001b
-ftdi_layout_signal nTRST -data 0x0100 -oe 0x0100
-ftdi_layout_signal nSRST -data 0x0200 -oe 0x0200
+ftdi channel 0
+ftdi layout_init 0x0008 0x001b
+ftdi layout_signal nTRST -data 0x0100 -oe 0x0100
+ftdi layout_signal nSRST -data 0x0200 -oe 0x0200
#
adapter driver ftdi
-ftdi_device_desc "Debug Board for Neo1973"
-ftdi_vid_pid 0x1457 0x5118
+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
+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
echo "as working or fixed."
adapter driver ftdi
-ftdi_device_desc "NGX JTAG"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0508 0x0f1b
+ftdi layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi layout_signal nSRST -data 0x0800 -noe 0x0400
transport select swd
-ftdi_layout_signal SWD_EN -nalias nTRST
-ftdi_layout_signal SWDIO_OE -alias TMS
+ftdi layout_signal SWD_EN -nalias nTRST
+ftdi layout_signal SWDIO_OE -alias TMS
#
adapter driver ftdi
-ftdi_device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
-ftdi_vid_pid 0x15ba 0x002b
+ftdi device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
+ftdi vid_pid 0x15ba 0x002b
-ftdi_layout_init 0x0908 0x0b1b
-ftdi_layout_signal nSRST -oe 0x0200
-ftdi_layout_signal nTRST -data 0x0100
-ftdi_layout_signal LED -data 0x0800
+ftdi layout_init 0x0908 0x0b1b
+ftdi layout_signal nSRST -oe 0x0200
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal LED -data 0x0800
#
adapter driver ftdi
-ftdi_device_desc "Olimex OpenOCD JTAG"
-ftdi_vid_pid 0x15ba 0x0003
+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
+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
#
adapter driver ftdi
-ftdi_device_desc "Olimex OpenOCD JTAG ARM-USB-TINY-H"
-ftdi_vid_pid 0x15ba 0x002a
+ftdi device_desc "Olimex OpenOCD JTAG ARM-USB-TINY-H"
+ftdi vid_pid 0x15ba 0x002a
-ftdi_layout_init 0x0808 0x0a1b
-ftdi_layout_signal nSRST -oe 0x0200
-ftdi_layout_signal nTRST -data 0x0100 -oe 0x0100
-ftdi_layout_signal LED -data 0x0800
+ftdi layout_init 0x0808 0x0a1b
+ftdi layout_signal nSRST -oe 0x0200
+ftdi layout_signal nTRST -data 0x0100 -oe 0x0100
+ftdi layout_signal LED -data 0x0800
#
adapter driver ftdi
-ftdi_device_desc "Olimex OpenOCD JTAG TINY"
-ftdi_vid_pid 0x15ba 0x0004
+ftdi device_desc "Olimex OpenOCD JTAG TINY"
+ftdi vid_pid 0x15ba 0x0004
-ftdi_layout_init 0x0808 0x0a1b
-ftdi_layout_signal nSRST -oe 0x0200
-ftdi_layout_signal nTRST -data 0x0100 -oe 0x0100
-ftdi_layout_signal LED -data 0x0800
+ftdi layout_init 0x0808 0x0a1b
+ftdi layout_signal nSRST -oe 0x0200
+ftdi layout_signal nTRST -data 0x0100 -oe 0x0100
+ftdi layout_signal LED -data 0x0800
echo "as working or fixed."
adapter driver ftdi
-ftdi_device_desc "OOCDLink"
-ftdi_vid_pid 0x0403 0xbaf8
+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
+ftdi layout_init 0x0508 0x0f1b
+ftdi layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi layout_signal nSRST -data 0x0800 -noe 0x0400
#
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
-ftdi_channel 1
+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
+ftdi layout_init 0x0c08 0x0f1b
+ftdi layout_signal nTRST -data 0x0100 -noe 0x0400
+ftdi layout_signal nSRST -data 0x0200 -noe 0x0800
#
adapter driver ftdi
-ftdi_device_desc "Dual RS232-HS"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0508 0x0f1b
+ftdi layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi layout_signal nSRST -data 0x0800 -noe 0x0400
#
adapter driver ftdi
-ftdi_device_desc "Dual RS232"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0508 0x0f1b
+ftdi layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi layout_signal nSRST -data 0x0800 -noe 0x0400
#
adapter driver ftdi
-ftdi_device_desc "OpenRD JTAGKey FT2232D B"
-ftdi_vid_pid 0x0403 0x9e90
-ftdi_channel 0
+ftdi device_desc "OpenRD JTAGKey FT2232D B"
+ftdi vid_pid 0x0403 0x9e90
+ftdi channel 0
-ftdi_layout_init 0x0608 0x0f1b
-ftdi_layout_signal nTRST -data 0x0200
-ftdi_layout_signal nSRST -noe 0x0400
+ftdi layout_init 0x0608 0x0f1b
+ftdi layout_signal nTRST -data 0x0200
+ftdi layout_signal nSRST -noe 0x0400
# http://pipistrello.saanlima.com/
# http://www.saanlima.com/download/pipistrello-v2.0/pipistrello_v2_schematic.pdf
adapter driver ftdi
-ftdi_device_desc "Pipistrello LX45"
-ftdi_vid_pid 0x0403 0x6010
+ftdi device_desc "Pipistrello LX45"
+ftdi vid_pid 0x0403 0x6010
# interface 1 is the uart
-ftdi_channel 0
+ftdi channel 0
# just TCK TDI TDO TMS, no reset
-ftdi_layout_init 0x0008 0x000b
+ftdi layout_init 0x0008 0x000b
reset_config none
# this generally works fast: the fpga can handle 30MHz, the spi flash can handle
# 54MHz with simple read, no dummy cycles, and wait-for-write-completion
#
adapter driver ftdi
-ftdi_device_desc "PLS USB/JTAG Adapter for SPC5xxx"
-ftdi_vid_pid 0x263d 0x4001
+ftdi device_desc "PLS USB/JTAG Adapter for SPC5xxx"
+ftdi vid_pid 0x263d 0x4001
-ftdi_channel 0
-ftdi_layout_init 0x0008 0x000b
-ftdi_layout_signal nTRST -data 0x0100 -oe 0x0100
-ftdi_layout_signal nSRST -ndata 0x2000 -oe 0x2000
+ftdi channel 0
+ftdi layout_init 0x0008 0x000b
+ftdi layout_signal nTRST -data 0x0100 -oe 0x0100
+ftdi layout_signal nSRST -ndata 0x2000 -oe 0x2000
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6010
+ftdi vid_pid 0x0403 0x6010
-ftdi_layout_init 0x0c08 0x0c2b
-ftdi_layout_signal nTRST -data 0x0800
-ftdi_layout_signal nSRST -data 0x0400
+ftdi layout_init 0x0c08 0x0c2b
+ftdi layout_signal nTRST -data 0x0800
+ftdi layout_signal nSRST -data 0x0400
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6010
-ftdi_channel 1
+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
+ftdi layout_init 0x0c08 0x0c2b
+ftdi layout_signal nTRST -data 0x0800
+ftdi layout_signal nSRST -data 0x0400
transport select swd
-ftdi_layout_signal SWD_EN -nalias nTRST
-ftdi_layout_signal SWDIO_OE -alias TMS
+ftdi layout_signal SWD_EN -nalias nTRST
+ftdi layout_signal SWDIO_OE -alias TMS
#
adapter driver ftdi
-ftdi_device_desc "SheevaPlug JTAGKey FT2232D B"
-ftdi_vid_pid 0x9e88 0x9e8f
-ftdi_channel 0
+ftdi device_desc "SheevaPlug JTAGKey FT2232D B"
+ftdi vid_pid 0x9e88 0x9e8f
+ftdi channel 0
-ftdi_layout_init 0x0608 0x0f1b
-ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
-ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400
+ftdi layout_init 0x0608 0x0f1b
+ftdi layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi layout_signal nSRST -data 0x0800 -noe 0x0400
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "Signalyzer LITE"
-ftdi_vid_pid 0x0403 0xbca1
+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
+ftdi layout_init 0x0008 0x000b
+ftdi layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi layout_signal nSRST -data 0x0020 -oe 0x0020
echo "so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "Signalyzer"
-ftdi_vid_pid 0x0403 0xbca0
+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
+ftdi layout_init 0x0008 0x000b
+ftdi layout_signal nTRST -data 0x0010 -oe 0x0010
+ftdi layout_signal nSRST -data 0x0020 -oe 0x0020
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6010
-ftdi_layout_init 0x0088 0x008b
-ftdi_channel 1
+ftdi vid_pid 0x0403 0x6010
+ftdi layout_init 0x0088 0x008b
+ftdi channel 1
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x6010
+ftdi vid_pid 0x0403 0x6010
# Initial Layout
-ftdi_layout_init 0x0058 0x99fb
+ftdi layout_init 0x0058 0x99fb
# Signal Data Direction Notes
# TCK 0 1 (out)
# TDI 0 1 (out)
# Unused 0 1 (out)
# Signals definition
-ftdi_layout_signal LED -ndata 0x0010
-ftdi_layout_signal SWD_EN -data 0x0020
-ftdi_layout_signal SWDIO_OE -ndata 0x0040
-ftdi_layout_signal nSRST -oe 0x0080
+ftdi layout_signal LED -ndata 0x0010
+ftdi layout_signal SWD_EN -data 0x0020
+ftdi layout_signal SWDIO_OE -ndata 0x0040
+ftdi layout_signal nSRST -oe 0x0080
-ftdi_layout_signal GPIO_A -data 0x0200 -oe 0x0200 -input 0x0200
-ftdi_layout_signal GPIO_B -data 0x0400 -oe 0x0400 -input 0x0400
-ftdi_layout_signal GPIO_C -data 0x2000 -oe 0x2000 -input 0x2000
-ftdi_layout_signal GPIO_D -data 0x4000 -oe 0x4000 -input 0x4000
+ftdi layout_signal GPIO_A -data 0x0200 -oe 0x0200 -input 0x0200
+ftdi layout_signal GPIO_B -data 0x0400 -oe 0x0400 -input 0x0400
+ftdi layout_signal GPIO_C -data 0x2000 -oe 0x2000 -input 0x2000
+ftdi layout_signal GPIO_D -data 0x4000 -oe 0x4000 -input 0x4000
#
adapter driver ftdi
-ftdi_device_desc "STM32-PerformanceStick"
-ftdi_vid_pid 0x0640 0x002d
+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
+ftdi layout_init 0x0388 0x038b
+ftdi layout_signal nTRST -data 0x0100
+ftdi layout_signal nSRST -data 0x0080 -noe 0x200
transport select swd
-ftdi_layout_signal SWD_EN -data 0
+ftdi layout_signal SWD_EN -data 0
#
adapter driver ftdi
-ftdi_vid_pid 0x0451 0xc32a
+ftdi vid_pid 0x0451 0xc32a
-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
+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
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x8a99
+ftdi vid_pid 0x0403 0x8a99
-ftdi_layout_init 0x0038 0x087b
-ftdi_layout_signal nTRST -data 0x0020 -oe 0x0020
-ftdi_layout_signal nSRST -data 0x0010 -oe 0x0010
+ftdi layout_init 0x0038 0x087b
+ftdi layout_signal nTRST -data 0x0020 -oe 0x0020
+ftdi layout_signal nSRST -data 0x0010 -oe 0x0010
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0x8a98 0x0403 0x6010
+ftdi vid_pid 0x0403 0x8a98 0x0403 0x6010
-ftdi_layout_init 0x0038 0x087b
-ftdi_layout_signal nTRST -data 0x0020
-ftdi_layout_signal nSRST -data 0x0010
+ftdi layout_init 0x0038 0x087b
+ftdi layout_signal nTRST -data 0x0020
+ftdi layout_signal nSRST -data 0x0010
reset_config srst_push_pull
echo "mailing list, so it could be marked as working or fixed."
adapter driver ftdi
-ftdi_device_desc "Turtelizer JTAG/RS232 Adapter"
-ftdi_vid_pid 0x0403 0xbdc8
+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
+ftdi layout_init 0x0008 0x0c5b
+ftdi layout_signal nSRST -oe 0x0040
+ftdi layout_signal LED -data 0x0c00
#
adapter driver ftdi
-ftdi_device_desc "Turtelizer JTAG/RS232 Adapter"
-ftdi_vid_pid 0x0403 0xbdc8
+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
+ftdi layout_init 0x0008 0x0c7b
+ftdi layout_signal nTRST -oe 0x0020
+ftdi layout_signal nSRST -oe 0x0040
+ftdi layout_signal LED -ndata 0x0c00
#
adapter driver ftdi
-#ftdi_device_desc "UM232H"
-ftdi_vid_pid 0x0403 0x6014
+#ftdi device_desc "UM232H"
+ftdi vid_pid 0x0403 0x6014
-ftdi_layout_init 0xfff8 0xfffb
-ftdi_layout_signal nTRST -data 0x0100 -oe 0x0100
-ftdi_layout_signal nSRST -data 0x0200 -oe 0x0200
+ftdi layout_init 0xfff8 0xfffb
+ftdi layout_signal nTRST -data 0x0100 -oe 0x0100
+ftdi layout_signal nSRST -data 0x0200 -oe 0x0200
# UM232H FT232H JTAG
# Name Pin Name Func
echo "as working or fixed."
adapter driver ftdi
-ftdi_device_desc "VPACLink"
-ftdi_vid_pid 0x0403 0x6010
+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
+ftdi layout_init 0x0508 0x0f1b
+ftdi layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi layout_signal nSRST -data 0x0800 -noe 0x0400
#
adapter driver ftdi
-ftdi_vid_pid 0x0403 0xa6d0 0x0403 0x6010
+ftdi vid_pid 0x0403 0xa6d0 0x0403 0x6010
-ftdi_layout_init 0x0038 0x597b
+ftdi layout_init 0x0038 0x597b
# 8000 z - unused
# 4000 0 > CPLD loopback (all target side pins high-Z)
# changing the USB configuration to zero.)
#
-ftdi_layout_signal nTRST -data 0x0010
-ftdi_layout_signal nSRST -oe 0x0100
-ftdi_layout_signal EMU_EN -data 0x0020
-ftdi_layout_signal EMU0 -oe 0x0040
-ftdi_layout_signal EMU1 -oe 0x1000
-ftdi_layout_signal PWR_RST -data 0x0800
-ftdi_layout_signal LOOPBACK -data 0x4000
+ftdi layout_signal nTRST -data 0x0010
+ftdi layout_signal nSRST -oe 0x0100
+ftdi layout_signal EMU_EN -data 0x0020
+ftdi layout_signal EMU0 -oe 0x0040
+ftdi layout_signal EMU1 -oe 0x1000
+ftdi layout_signal PWR_RST -data 0x0800
+ftdi layout_signal LOOPBACK -data 0x4000
-echo "\nInfo : to use this adapter you MUST add ``init; ftdi_set_signal PWR_RST 1; jtag arp_init'' to the end of your config file!\n"
+echo "\nInfo : to use this adapter you MUST add ``init; ftdi set_signal PWR_RST 1; jtag arp_init'' to the end of your config file!\n"
# note: rising edge on PWR_RST is also needed after power-cycling the
# target
source [find interface/ftdi/xds100v2.cfg]
# The USB ids are different.
-ftdi_vid_pid 0x0403 0xa6d1
+ftdi vid_pid 0x0403 0xa6d1