mirror of
https://review.coreboot.org/flashrom.git
synced 2025-07-01 14:11:15 +02:00
ft2232_spi: Add support for Tin Can Tools Flyswatter/Flyswatter 2
The Tin Can Tools Flyswatter and Flyswatter 2 have a FT2232H with a JTAG interface wired to port A. The buffers that drive the JTAG pins need to be enabled with an nOE signal from the FT2232H ADBUS6 and ADBUS7 pins. Flyswatter has an ARM-14 JTAG interface and Flyswatter 2 has an ARM-20 JTAG interface. Change-Id: I56b1fb76dcda32bb02980cd54a2853506bfc9dfd Signed-off-by: Russ Dill <Russ.Dill@gmail.com> Reviewed-on: https://review.coreboot.org/c/flashrom/+/36896 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Angel Pons <th3fanbus@gmail.com>
This commit is contained in:

committed by
David Hendricks

parent
e28d75ed72
commit
7bd31a435b
@ -269,6 +269,12 @@ int ft2232_spi_init(void)
|
||||
} else if (!strcasecmp(arg, "google-servo-v2-legacy")) {
|
||||
ft2232_vid = GOOGLE_VID;
|
||||
ft2232_type = GOOGLE_SERVO_V2_PID0;
|
||||
} else if (!strcasecmp(arg, "flyswatter")) {
|
||||
ft2232_type = FTDI_FT2232H_PID;
|
||||
channel_count = 2;
|
||||
/* Flyswatter and Flyswatter-2 require GPIO bits 0x80
|
||||
* and 0x40 to be driven low to enable output buffers */
|
||||
pindir = 0xcb;
|
||||
} else {
|
||||
msg_perr("Error: Invalid device type specified.\n");
|
||||
free(arg);
|
||||
|
Reference in New Issue
Block a user