11 open source boards using the FT4232H
Real designs built with the FT4232H, from public GitHub projects: a quick way to see how others power, decouple and connect it. Each board comes with its KiCad files, full parts list and a render — and you can simulate its firmware on HardLabs.
QMTechBaseBoard
carlosedp
170 × 170 mm64 parts2LMIT24STM32
ASPECT2
xboxoneresearch
60 × 60 mm116 parts4LNo license17Quad serial breakout
jamesfowkes
50 × 50 mm44 parts2LNo license15Ml dev board
coon42
100 × 73.2 mm53 parts2LNo license7STM32
Base Board Design
WilliamSanchez
199.8 × 150 mm492 parts4LNo license2Motherboard
morzack
125 × 85 mm194 parts4LNo license1Replicookie
cmcquinn
184.2 × 127 mm173 parts6LCERN-OHL-S-2.01Bike line protocol
c4deszes
79.5 × 50 mm100 parts2LNo license1QuadSerial
JakBroe
43 × 42.5 mm49 parts2LMIT0LADCP interface box
pedrolpena
92 × 41 mm38 parts2LGPL-3.00Ft4232h
dragonlock2
43 × 20 mm67 parts2LApache-2.013
How designs wire the FT4232H
Read from the KiCad layouts of 10 open source designs, one per repository: what each pin of the FT4232H connects to, and the resistors, capacitors and other passives placed on it.
- The OSCI pin has a crystal on 10 of 10 designs, most often 12 MHz.
- The VREGOUT pin has a decoupling capacitor on 10 of 10 designs, most often 100 nF (then 3.3 µF).
- The OSCI pin has a capacitor to GND on 9 of 10 designs, most often 30 pF (then 27 pF).
- The VPHY pin has a capacitor to GND on 9 of 10 designs, most often 100 nF (then 4.7 µF).
| Pin | Connected to | Parts on the pin |
|---|---|---|
| GNDpin 1, 5, 11, 15, 25, 35, 47, 51 | Connected to: GND 100% | — |
| OSCIpin 2 | Connected to: Signal 100% |
|
| OSCOpin 3 | Connected to: Signal 90% |
|
| VPHYpin 4 | Connected to: Signal 90% |
|
| REFpin 6 | Connected to: Signal 100% |
|
| VPLLpin 9 | Connected to: Signal 90% |
|
| AGNDpin 10 | Connected to: GND 100% | — |
| VCOREpin 12, 37, 64 | Connected to: 1.8V 70% · a signal 30% |
|
| TESTpin 13 | Connected to: GND 100% | — |
| RESETpin 14 | Connected to: Signal 100% |
|
| ADBUS0pin 16 | Connected to: A connector 30% |
|
| ADBUS1pin 17 | Connected to: A connector 30% |
|
| ADBUS3pin 19 | Connected to: A connector 30% · not connected 40% |
|
| VCCIOpin 20, 31, 42, 56 | Connected to: 3.3V 90% |
|
| ADBUS5pin 22 | Connected to: Not connected 60% · a signal 40% | — |
| ADBUS6pin 23 | Connected to: Not connected 80% · a signal 20% | — |
| ADBUS7pin 24 | Connected to: Not connected 80% · a signal 20% | — |
| BDBUS0pin 26 | Connected to: A connector 20% · not connected 20% |
|
| BDBUS1pin 27 | Connected to: Signal 80% · not connected 20% |
|
| BDBUS2pin 28 | Connected to: A connector 20% · not connected 40% |
|
| BDBUS4pin 30 | Connected to: Not connected 70% · a signal 30% | — |
| BDBUS5pin 32 | Connected to: Not connected 70% · a signal 30% | — |
| BDBUS6pin 33 | Connected to: Not connected 80% · a signal 20% | — |
| BDBUS7pin 34 | Connected to: Not connected 80% · a signal 20% | — |
| SUSPENDpin 36 | Connected to: Not connected 90% | — |
| CDBUS0pin 38 | Connected to: A connector 30% · not connected 20% |
|
| CDBUS1pin 39 | Connected to: A connector 30% · not connected 20% |
|
| CDBUS2pin 40 | Connected to: Not connected 80% · a signal 20% | — |
| CDBUS3pin 41 | Connected to: Not connected 80% · a signal 20% | — |
| CDBUS4pin 43 | Connected to: Not connected 80% · a signal 20% | — |
| CDBUS5pin 44 | Connected to: Not connected 80% · a signal 20% | — |
| CDBUS6pin 45 | Connected to: Not connected 80% · a signal 20% | — |
| CDBUS7pin 46 | Connected to: Not connected 80% · a signal 20% | — |
| DDBUS0pin 48 | Connected to: A connector 30% · not connected 30% |
|
| VREGOUTpin 49 | Connected to: 1.8V 70% · a signal 30% |
|
| VREGINpin 50 | Connected to: 3.3V 100% |
|
| DDBUS1pin 52 | Connected to: A connector 30% · not connected 30% |
|
| DDBUS2pin 53 | Connected to: Not connected 80% · a signal 20% | — |
| DDBUS3pin 54 | Connected to: Not connected 80% · a signal 20% | — |
| DDBUS4pin 55 | Connected to: Not connected 80% · a signal 20% | — |
12 more pins vary from design to design. Connections count pins, parts count designs; values in brackets are how many parts had that value. Designs read include ASPECT2 by xboxoneresearch, Quad serial breakout by jamesfowkes, Ft4232h by dragonlock2 and Ml dev board by coon42.
The FT4232H in open source designs
The gallery holds 11 open source boards using the FT4232H from 11 GitHub repositories; a typical one measures about 92 × 60 mm and carries around 67 components.
64% are two-layer designs, the rest use four layers or more, and 45% carry an open source license.
The most starred is QMTechBaseBoard by carlosedp.
Parts used alongside the FT4232H
Microcontrollers on boards using the FT4232H
What boards using the FT4232H are built for
FT4232H: common questions
Where can I find a FT4232H reference design?
Each of the 11 boards on this page is a real design using the FT4232H. Open one to see how it is wired up, with the full BOM, a render of the layout and links to its KiCad files.
How is the FT4232H OSCI pin connected?
The OSCI pin has a crystal on 10 of 10 designs, most often 12 MHz. Counted from the KiCad layouts of 10 open source designs using the FT4232H.
What decoupling capacitors do designs use on the FT4232H VREGOUT pin?
The VREGOUT pin has a decoupling capacitor on 10 of 10 designs, most often 100 nF (then 3.3 µF). Counted from the KiCad layouts of 10 open source designs using the FT4232H.
How is the FT4232H VPHY pin connected?
The VPHY pin has a capacitor to GND on 9 of 10 designs, most often 100 nF (then 4.7 µF). Counted from the KiCad layouts of 10 open source designs using the FT4232H.
What parts are used alongside the FT4232H?
The 74HC595, 93LCxxBxxOT and 93LCxxB appear in the most repositories here.
Which microcontrollers do boards using the FT4232H use?
Most are built on STM32 (2).
How big is a typical board using the FT4232H?
The median is 92 × 60 mm, and 64% are two-layer designs.
What is the most popular open source board using the FT4232H?
By GitHub stars, QMTechBaseBoard by carlosedp, with 24 stars.
Can I simulate one of these boards using the FT4232H before building it?
Yes. HardLabs turns a board's netlist and BOM into a working simulation, so you can boot and test firmware against it with no hardware on your desk.