comparison eeproms/jtag-unbuf @ 3:434806360d91

eeproms: subset import from freecalypso-hwlab
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 03 Sep 2023 18:24:27 +0000
parents
children d46ea7a3fa0c
comparison
equal deleted inserted replaced
2:17fdd0ba7a2e 3:434806360d91
1 # This EEPROM configuration is meant to be programmed into COTS FT2232D
2 # breakout boards used as unbuffered JTAG adapters. The custom USB VID:PID
3 # belongs to Falconia Partners LLC; we hereby allow the community to program
4 # this PID into generic FT2232D boards (not made by Falconia) as long as
5 # it is used for the present purpose with this full EEPROM configuration.
6 #
7 # The purpose of having a custom USB ID is to prevent the Linux kernel
8 # ftdi_sio driver from treating this FT2232D instance as a dual UART and
9 # creating a ttyUSB device for Channel A. If you wish to use Channel B
10 # as a UART (which is still available for that purpose), you will need to use
11 # a Linux kernel version with commit 6cf87e5edd9944e1d3b6efd966ea401effc304ee
12 # included, or apply that commit locally if your kernel version does not
13 # include it.
14
15 vid 0x0403 # FTDI
16 pid 0x7151 # Allocated by FTDI to Falconia Partners LLC
17 manuf FTDI
18 product Unbuffered JTAG adapter
19
20 # We program Channel A to come up in the 245 FIFO mode prior to being
21 # switched into MPSSE mode by OpenOCD, as opposed to the default 232 UART mode.
22 # If the FT2232D chip's ADBUS pins are connected directly to the JTAG target
23 # without a buffer (what we mean by an unbuffered JTAG adapter), the default
24 # 232 UART mode is NOT safe, as it will produce a fight on the ADBUS2 line
25 # between the UART RTS output and the target's TDO output. 245 FIFO mode is
26 # expected to be safer, as all 8 ADBUS lines will be inputs for as long as
27 # the ACBUS2 line is left unconnected and not driven by anything.
28
29 byte00 0x01 # Channel A: FIFO mode, D2XX driver
30 byte01 0x08 # Channel B: UART mode, VCP driver