5 open source boards using the MCP4728T-E/UN
Real designs built with the MCP4728T-E/UN, 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.
FPGA
Thunderscope Rev5.3
EEVengers
122.5 × 103.5 mm817 parts6LMIT1.3kRP2040/RP2350
RTShield
o7-machinehum
89 × 61 mm87 parts4LCC-BY-NC-4.012FPGA
SIG COND
Han-ZenX
122.5 × 103.5 mm817 parts6LCustom license1ESP32
Swc module
OETSolutions
54 × 102 mm105 parts4LNo license0RP2040/RP2350
Analog matrix lc1
tim4431
160 × 170 mm387 parts4LNo license0
How designs wire the MCP4728T-E/UN
Read from the KiCad layouts of 5 open source designs, one per repository: what each pin of the MCP4728T-E/UN connects to, and the resistors, capacitors and other passives placed on it.
- The SCL pin has a pull-up to 3.3V on 5 of 5 designs, most often 4.7 kΩ (then 1 kΩ).
- The SDA pin has a pull-up to 3.3V on 5 of 5 designs, most often 4.7 kΩ (then 1 kΩ).
- The RDY pin is left unconnected on 5 of 5 designs.
- The VDD pin has a decoupling capacitor on 4 of 5 designs, most often 1 µF (then 10 µF).
| Pin | Connected to | Parts on the pin |
|---|---|---|
| VDDpin 1 | Connected to: 3.3V 100% |
|
| SCLpin 2 | Connected to: MCP4452-104E 40%, the microcontroller 40% |
|
| SDApin 3 | Connected to: MCP4452-104E 40%, the microcontroller 40% |
|
| LDACNpin 4 | Connected to: GND 60% · not connected 20% · a signal 20% | — |
| RDYpin 5 | Connected to: Not connected 100% | — |
| VOUTApin 6 | Connected to: MCP4452-104E 40% |
|
| VOUTBpin 7 | Connected to: MCP4452-104E 40% |
|
| VOUTCpin 8 | Connected to: MCP4452-104E 40% |
|
| VOUTDpin 9 | Connected to: MCP4452-104E 40% |
|
| VSSpin 10 | Connected to: GND 100% | — |
Connections count pins, parts count designs; values in brackets are how many parts had that value. Designs read include Thunderscope Rev5.3 by EEVengers, RTShield by o7-machinehum, SIG COND by Han-ZenX and Swc module by OETSolutions.
The MCP4728T-E/UN in open source designs
The gallery holds 5 open source boards using the MCP4728T-E/UN from 5 GitHub repositories; a typical one measures about 122.5 × 103.5 mm and carries around 387 components.
100% use four copper layers or more, and 20% carry an open source license.
The most starred is Thunderscope Rev5.3 by EEVengers.
Parts used alongside the MCP4728T-E/UN
Microcontrollers on boards using the MCP4728T-E/UN
What boards using the MCP4728T-E/UN are built for
MCP4728T-E/UN: common questions
Where can I find a MCP4728T-E/UN reference design?
Each of the 5 boards on this page is a real design using the MCP4728T-E/UN. Open one to see how it is wired up, with the full BOM, a render of the layout and links to its KiCad files.
What pull-up resistor is used on the MCP4728T-E/UN SCL pin?
The SCL pin has a pull-up to 3.3V on 5 of 5 designs, most often 4.7 kΩ (then 1 kΩ). Counted from the KiCad layouts of 5 open source designs using the MCP4728T-E/UN.
What pull-up resistor is used on the MCP4728T-E/UN SDA pin?
The SDA pin has a pull-up to 3.3V on 5 of 5 designs, most often 4.7 kΩ (then 1 kΩ). Counted from the KiCad layouts of 5 open source designs using the MCP4728T-E/UN.
How is the MCP4728T-E/UN RDY pin connected?
The RDY pin is left unconnected on 5 of 5 designs. Counted from the KiCad layouts of 5 open source designs using the MCP4728T-E/UN.
What parts are used alongside the MCP4728T-E/UN?
The ADA4930-1YCPZ-R7, BUF802IRGTR, FIN1019MTCX, HMCAD1520 and LM27761DSGR appear in the most repositories here.
Which microcontrollers do boards using the MCP4728T-E/UN use?
Most are built on FPGA (2), RP2040/RP2350 (2) and ESP32 (1).
How big is a typical board using the MCP4728T-E/UN?
The median is 122.5 × 103.5 mm, and 0% are two-layer designs.
What is the most popular open source board using the MCP4728T-E/UN?
By GitHub stars, Thunderscope Rev5.3 by EEVengers, with 1,336 stars.
Can I simulate one of these boards using the MCP4728T-E/UN 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.