FreeCalypso > hg > freecalypso-hwlab
comparison eeproms/jtag-unbuf @ 52:ace3ed1d5ddf
Unbuffered FT2232x JTAG article written
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Tue, 23 Apr 2019 01:22:41 +0000 |
parents | 60b8cf977c3f |
children | 1d38af6d7be8 |
comparison
equal
deleted
inserted
replaced
51:311c800268b8 | 52:ace3ed1d5ddf |
---|---|
21 # If the FT2232D chip's ADBUS pins are connected directly to the JTAG target | 21 # If the FT2232D chip's ADBUS pins are connected directly to the JTAG target |
22 # without a buffer (what we mean by an unbuffered JTAG adapter), the default | 22 # without a buffer (what we mean by an unbuffered JTAG adapter), the default |
23 # 232 UART mode is NOT safe, as it will produce a fight on the ADBUS2 line | 23 # 232 UART mode is NOT safe, as it will produce a fight on the ADBUS2 line |
24 # between the UART RTS output and the target's TDO output. 245 FIFO mode is | 24 # between the UART RTS output and the target's TDO output. 245 FIFO mode is |
25 # expected to be safer, as all 8 ADBUS lines will be inputs for as long as | 25 # expected to be safer, as all 8 ADBUS lines will be inputs for as long as |
26 # ACBUS2 and ACBUS2 are left unconnected and not driven by anything. | 26 # the ACBUS2 line is left unconnected and not driven by anything. |
27 | 27 |
28 byte00 0x01 # Channel A: FIFO mode, D2XX driver | 28 byte00 0x01 # Channel A: FIFO mode, D2XX driver |
29 byte01 0x08 # Channel B: UART mode, VCP driver | 29 byte01 0x08 # Channel B: UART mode, VCP driver |