4 open source boards using the PaP_Driver_v1
Real designs built with the PaP_Driver_v1, 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.
STM32OpenEFI rev4 bkp
Churrosoft
164 × 118 mm317 parts4LCERN-OHL-S-2.08
STM32UEFI
99 × 113 mm228 parts4LCERN-OHL-S-2.08
STM32STM32F rev3
159.6 × 99.6 mm171 parts4LCERN-OHL-S-2.08
STM32ΜEFI rev2
99.9 × 99.3 mm151 parts4LCERN-OHL-S-2.08
The PaP_Driver_v1 in open source designs
The gallery holds 4 open source boards using the PaP_Driver_v1 from 1 GitHub repository; a typical one measures about 129.7 × 106.3 mm and carries around 200 components.
100% use four copper layers or more, and 100% carry an open source license.
The most starred is OpenEFI rev4 bkp by Churrosoft.
Microcontrollers on boards using the PaP_Driver_v1
PaP_Driver_v1: common questions
Where can I find a PaP_Driver_v1 reference design?
Each of the 4 boards on this page is a real design using the PaP_Driver_v1. Open one to see how it is wired up, with the full BOM, a render of the layout and links to its KiCad files.
Which microcontrollers do boards using the PaP_Driver_v1 use?
Most are built on STM32 (4).
How big is a typical board using the PaP_Driver_v1?
The median is 129.7 × 106.3 mm, and 0% are two-layer designs.
What is the most popular open source board using the PaP_Driver_v1?
By GitHub stars, OpenEFI rev4 bkp by Churrosoft, with 8 stars.
Can I simulate one of these boards using the PaP_Driver_v1 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.