Docs for the uBld.it Fiddy Plus FT2232H Board
We designed this because we got tired of getting clone chips and unnecessarily large breakout boards that were difficult to connect. This does exactly what it is supposed to with a Genuine FTDI FT2232H high-speed IC. All of the I/O is clearly labelled for SPI, JTAG, and UART use. An EEPROM is on-board that can be used for setting the FT2232H into more unusual modes.
- Genuine FTDI FT2232H
- Not a clone - no clone related driver or signal issues
- SPI Interface
- JTAG Interface
- UART Interface
In Linux (where most users will be working with this board), you need to add a udev rule to allow all users (or a specific group) to access the board unless you always want to run with sudo or as root.
The 99-fiddy.rules file should be copied to /etc/udev/rules.d/ directory then either reboot or run:
sudo udevadm control --reload-rules sudo udevadm trigger
To dump a SPI Flash Image, connect the Fiddy Plus as follows:
|Fiddy Plus||SPI Flash Chip|
|3.3V||3.3V (if not powered)|
|~WP||3.3V (may not be needed)|
|~HOLD||3.3V (may not be needed)|
Here is a Fiddy Plus connected to a Winbond W25Q32 SOIC-8 SPI FLASH IC with a Pomona IC Clip
sudo flashrom -p ft2232_spi:type=2232H,port=B
or you may need to slow it down to get a stable read depending on the chip and your setup
sudo flashrom -p ft2232_spi:type=2232H,port=B,divisor=4
It should look like this:
|SPI Write||SPI Read||SPI Diff|
To get the openocd debugger running with a connection to a JTAG ARM processor, you need to connect the JTAG pins and run openocde with the appropriate options. Here is an example using the STM32F103C8T6 on a "Blue Pill" board.
|Fiddy Plus||Blue Pill|
|TMS||IO (SWD Header)|
|TCK||CLK (SWD Header)|
|3.3V||3.3V (SWD Header)|
You will then first run the openocd server in one session:
openocd -f fiddy-jtag.cfg -f target/stm32f1x.cfg
or (if you didn't install the udev rule)
sudo openocd -f fiddy-jtag.cfg -f target/stm32f1x.cfg
The "target/stm32f1x.cfg" defines the architecture and should come with openocd
Then, in another session:
telnet localhost 4444
It should look like this:
|openocd server||openocd telnet session|
The first UART port on the Fiddy Plus's FT2232H is connected to the UART pins and associated TX / RX LEDs. In Linux, the screen command can be used to access the port on /dev/ttyUSB0 as follows with a 115,200 bps data rate. (sudo is necessary unless /dev/ttyUSB0 permissions are set to allow access by the current user)
sudo screen /dev/ttyUSB0 115200
FTDI publishes a lot of information about this chip:
- FTDI FT2232HL Main Page
- AN 113 FTDI FT2232H Hi Speed USB To I2C Example
- AN 114 FTDI FT2232H Hi Speed USB To SPI Example
- AN 124 User Guide for FTDI FT_PROG Utility
- AN 129 Interfacing FT2232H Hi-Speed Devices to a JTAG TAP
- AN 130 FT2232H Used In An FT245 Style Synchronous FIFO Mode
The FT2232H can be used for I2C, SUMP logic analyzer, and many other interfaces.
The "FT_Prog_fiddy_plus_eeprom_template.xml" template is provided as a starting point to program the EEPROM in the Fiddy Plus using FTDI's FT_Prog software.
The RTS and GND pins are mis-labelled on the Rev C and Rev D boards on the BOTTOM silkscreen. The TOP silkscreen in correct.