

Blueaudio puck
Turn wired headphones wireless: an ESP32 Bluetooth audio receiver (A2DP sink) with I2S DAC output, parametric EQ, AVRCP remote control and battery-aware power management. Built on ESP-IDF v5.5.
- Size
- 60 × 64 mm
- Copper layers
- 2
- Thickness
- 1.6 mm
- Parts
- 50
- Nets
- 34
- Pads
- 220
- Tracks, vias
- 195, 60
- Pours
- 2
- Routed
- Yes
- KiCad
- KiCad 10.0 (file 20260206)
- Created
- 30 Aug 2026
- Updated
- 31 Aug 2026
Overview
Blueaudio puck is an open-source printed circuit board by Zektopic, from the Zektopic/esp32-blue-audio-puck repository on GitHub, published under the MIT licence. It is a 2-layer board of 60 × 64 mm with 50 parts on 34 nets, routed with 195 tracks and 60 vias.
It is built around the ESP32-WROOM-32U, AP2112K-3.3 and LP2985-33DBV, with the PCM5102APW, MMBT3904 and BT3 among its other parts. Its parts include 18 capacitors, 9 resistors, 5 ICs, 5 connectors and 5 switches. It belongs with the audio and music and radio and wireless boards and the ESP32 boards of this library.
Main components
6ESP32-WROOM-32U
SMD,19.2x18mm-40℃~+85℃ -97dBm 2.4GHz 20.5dBm 3V~3.6V Bluetooth4.2 ESP32-DOWD UART、SDIO、SPI、I2C、GPIO、PWM、ADC、DAC、CAN SMD,19.2x18mm WiFi Modules ROHSEspressif SystemsWiFi ModulesAP2112K-3.3
SOT253.3V 600mA CMOS Low Dropout Linear Regulator with EnableDiodes IncorporatedUncategorisedLP2985-33DBV
SOT-23-5-40℃~+125℃@(Tj) 1 150mA 16V 3.3V 30uVrms 45dB@(1kHz) 575mV@(150mA) 850uA Fixed Over Current Protection、Short Circuit Protection、Thermal shutdown、Enable control、Noise bypass terminal Positive SOT-23-5 Voltage Regulators - Linear, Low Drop Out (LDO) Regulators ROHSTexas InstrumentsVoltage Regulators - Linear, Low Drop Out (LDO) RegulatorsPCM5102APW
TSSOP-20-25℃~+85℃ 1.8V~3.3V 2 32 384kHz 500uA 50MHz Audio Decoder Digital filtering、Power-down mode I2S TSSOP-20 ADCs/DACs - Special Purpose ROHSTexas InstrumentsADCs/DACs - Special PurposeMMBT3904
SOT-23-55℃~+150℃ 1 NPN 100 100nA 200mA 200mW 300MHz 300mV 40V 6V NPN SOT-23 Bipolar (BJT) ROHSJiangsu Changjing Electronics Technology (CJ)Bipolar (BJT)BT3
-- Switch Accessories / Caps ROHSAltechSwitch Accessories / Caps
README
hardware/README.mdBlueAudio Puck carrier board, rev A
KiCad 10 schematic and PCB for a single-board version of the puck: ESP32-WROOM-32U, PCM5102A DAC, Li-po charging, two separate 3V3 rails, OLED header, three user buttons and a 3.5 mm output — 60 × 64 mm, drawn to JLCPCB's two-layer rules.
| File | What it is |
|---|---|
blueaudio-puck.kicad_pro | Project — open this |
blueaudio-puck.kicad_sch | Schematic |
blueaudio-puck.kicad_pcb | Board |
bom.csv | Bill of materials |
preview/ | SVG renders of both |
scripts/ | The generator — see below |
Read this before you order anything
[!CAUTION] Not finished: eight nets still need routing by hand.
Everything the generator lays is DRC-clean — zero clearance violations, zero shorts, zero hole-clearance errors under JLCPCB's rules. But 25 of 33 nets are routed, not 33, and the remaining eight are unconnected copper:
+3V3A·AUDIO_L·CC1·CC2·DAC_LDOO·DAC_VNEG·I2S_BCK·I2S_LRCKAll eight are around the two fine-pitch parts — the TSSOP-20 DAC and the USB-C receptacle. Open the board in Pcbnew and its interactive router will finish them far faster and better than the one in
scripts/. Do not order anything until DRC reports zero unconnected items.
[!WARNING] Nothing here has been fabricated or tested. It passes ERC and the DRC checks that apply to an unrouted board. It has never been a physical object. Review the schematic against the datasheets before you spend money.
Verification
Actually run, with the output quoted rather than summarised:
$ kicad-cli sch erc --severity-error --severity-warning
Found 4 violations # all lib_symbol_mismatch, see below
$ kicad-cli pcb drc --severity-error --severity-warning
Found 25 violations
Found 22 unconnected itemsThe schematic is clean: zero electrical errors, no unconnected pins, no
dangling labels, no malformed outline. All four ERC warnings are
lib_symbol_mismatch on KiCad's derived symbols — the two regulators and the
two transistors. Cosmetic; see below.
The board has no electrical errors either. Breaking the 25 down:
| Count | Kind | Status |
|---|---|---|
| 22 | unconnected_items | Must fix — the eight unrouted nets |
| 15 | silk_over_copper | Cosmetic; every fab ignores it |
| 10 | silk_overlap | Cosmetic |
No clearance, no shorting_items, no hole_clearance. That took three fixes
to the router's geometry, each of which had produced copper that looked right
and was not — they are written up in the file that makes them:
- A track is not a point. A 0.4 mm power track centred on a 0.25 mm grid cell spills into its neighbours; checking only the cell it steps through let it sit 0.15 mm from a pad. Same for vias, which are 0.6 mm across — one landed on top of another net's track.
- Clearance belongs in the check, not the map. Growing a clearance halo around every pad and checking a track's own clearance against it demanded the gap twice, which makes escaping a 0.65 mm pitch TSSOP impossible.
- Holes are stricter than copper. Copper-to-hole is 0.25 mm where copper-to-copper is 0.15 mm, so drilled pads are claimed slightly larger than their copper.
The router still gets 25 of 33 nets rather than all of them. It routes in order and never rips up an earlier net to make room, which is the difference between it and a real autorouter.
The two ERC warnings are lib_symbol_mismatch on AP2112K-3.3 and
LP2985-3.3. Both are KiCad derived symbols (extends), and the generator
flattens them to embed them; the flattened copy differs cosmetically from the
library's. Connectivity and pin numbering are unaffected. Eeschema's
Update Symbols from Library clears it.
The silkscreen warnings are reference designators sitting over pads. Normal for auto-placed boards, ignored by every fab, and worth tidying only once placement is final.
How it is generated
Both files come from one netlist, in scripts/design.py.
That matters more than it sounds. A schematic and a PCB authored separately disagree about connectivity, and KiCad does not tell you until someone runs ERC and gets a wall of errors. One source, two emitters, no drift.
scripts/design.py parts, nets, no-connects, board size <- edit this
scripts/kisym.py pulls symbols out of the KiCad libraries
scripts/check_sheet.py catches stubs from different nets touching
scripts/gen_schematic.py emits the .kicad_sch
scripts/gen_pcb.py emits the .kicad_pcb (needs KiCad's python)To regenerate:
cd hardware/scripts
python design.py # netlist self-check
python check_sheet.py # no two nets touching
python gen_schematic.py
"C:/Users/manup/AppData/Local/Programs/KiCad/10.0/bin/python.exe" gen_pcb.pygen_pcb.py needs KiCad's bundled interpreter — pcbnew lives only there.
Symbols and footprints are copied from the installed libraries rather than transcribed, so the output files are self-contained and open on a machine with no libraries configured. A hand-typed pin table is exactly the kind of error nothing but a human eye can catch.
Once you edit it by hand
The generators overwrite their outputs. Move the files out of hardware/, or
stop regenerating, once you start editing in KiCad — which you will, because
routing is the next step.
The design
USB-C ──> MCP73831 ──> Li-po ──┬──> AP2112K ──> +3V3 ──> ESP32, OLED, DAC digital
└──> LP2985 ──> +3V3A ──> DAC analogueTwo regulators from the cell, not one. The DAC's analogue rail gets its own
low-noise LP2985 with a bypass capacitor. Sharing a rail with a Bluetooth radio
is what makes a DAC hiss, and docs/hardware.md said so before this board
existed.
No MCLK. The PCM5102A has SCK grounded and runs from its internal PLL,
matching the hand-built prototype and what the firmware expects.
JP1 sits in series with I²S data on GPIO 2. That pin is a boot strapping pin, and a DAC loading it is why the prototype needs BOOT held to flash. Lift the jumper and the board flashes normally.
Battery sense is R7/R8, a 2:1 divider into GPIO 35, matching
PUCK_BATTERY_DIVIDER_RATIO_X100=200.
Three user buttons on GPIO 32/33/27, matching the firmware — SW1 is BT1 (next / volume up), SW2 is BT2 (play-pause / pairing), SW3 is BT3 (previous / volume down). All active low straight to ground; the ESP32's internal pull-ups mean no external resistors. SW4 and SW5 are RESET and BOOT.
Note there is no LED on GPIO 27 on this board. The Kconfig help for
PUCK_LED_GPIO suggests 27 for an external status LED, which would collide
with BT3 on a breadboard. Here the only LED is D1, the charge indicator on
CHG_STAT, so GPIO 27 is unambiguously BT3.
Where it departs from docs/hardware.md
Both departures are deliberate and both are rev B work:
No buck-boost. docs/hardware.md specifies a TPS63020 for efficiency —
roughly 20–25% more runtime than an LDO. KiCad's standard library has no symbol
for it, and inventing one is precisely the silent error this generator exists to
avoid. Rev A uses LDOs and pays the efficiency.
No headphone amplifier. The PCM5102A is line level: audible on 32 Ω headphones but quiet, exactly as the docs warn. A TPA6132A2 is the rev B addition, and it is QFN-16 — it would make this board far harder to hand-build.
Manufacturing rules
Written into the project file, so DRC enforces them rather than leaving them as folklore. JLCPCB's standard two-layer process, with margin:
| JLC minimum | Used here | |
|---|---|---|
| Track width | 0.127 mm | 0.20 mm |
| Clearance | 0.127 mm | 0.15 mm |
| Via drill | 0.20 mm | 0.30 mm |
| Via diameter | drill + 0.26 | 0.60 mm |
| Annular ring | 0.13 mm | 0.15 mm |
| Hole to hole | 0.50 mm | 0.50 mm |
| Track to outline | 0.20 mm | 0.50 mm |
Only clearance sits near a limit, and it is still 18% above JLC's floor. The 0.05 mm it frees up per side compared with KiCad's 0.2 mm default is most of what lets the congested area route at all.
Teardrops are configured but not generated. The parameters are in the project file; KiCad adds the actual teardrops on demand. Run Edit → Teardrops → Add Teardrops in Pcbnew once routing is finished — doing it before then would only have to be redone.
What is left to do
- Route the last eight nets in Pcbnew:
+3V3A,AUDIO_L,CC1,CC2,DAC_LDOO,DAC_VNEG,I2S_BCK,I2S_LRCK. All are around the TSSOP-20 DAC and the USB-C part. The interactive router will do this in minutes. - Add teardrops once routing is done.
- Check the antenna keep-out. The WROOM-32U has an external connector so there is no PCB antenna to clear, but leave the module's edge unpoured.
- Re-run DRC and get it to zero before ordering anything.
- Review against datasheets. Especially the MCP73831 programming resistor (R5 = 2 kΩ, about 500 mA) against your cell's charge rate.
- Rounded corners were dropped — arcs whose endpoints did not meet left the outline open, and KiCad will not guess. Add them in Pcbnew, where the editor keeps the ends joined.
Parts
50| Qty | Value | Footprint | References |
|---|---|---|---|
| 6 | 100n | C_0805_2012Metric | C1, C4, C5, C7, C10, C18 |
| 6 | 1u | C_0805_2012Metric | C3, C8, C9, C11, C13, C15 |
| 4 | H1, H2, H3, H4 | ||
| 4 | 10u | C_0805_2012Metric | C2, C6, C14, C16 |
| 3 | 10k | R_0805_2012Metric | R1, R2, R9 |
| 2 | 100k | R_0805_2012Metric | R7, R8 |
| 2 | 5k1 | R_0805_2012Metric | R3, R4 |
| 2 | MMBT3904 | SOT-23 | Q1, Q2 |
| 1 | 0R | R_0805_2012Metric | JP1 |
| 1 | 10n | C_0805_2012Metric | C17 |
| 1 | 1k | R_0805_2012Metric | R6 |
| 1 | 2k | R_0805_2012Metric | R5 |
| 1 | 3.5mm | Jack_3.5mm_CUI_SJ1-3513N_Horizontal | J2 |
| 1 | 4u7 | C_0805_2012Metric | C12 |
| 1 | AP2112K-3.3 | SOT-23-5 | U4 |
| 1 | BATT | JST_PH_S2B-PH-K_1x02_P2.00mm_Horizontal | J4 |
| 1 | BOOT | Panasonic_EVQPUJ_EVQPUA | SW5 |
| 1 | BT1 | Panasonic_EVQPUJ_EVQPUA | SW1 |
| 1 | BT2 | Panasonic_EVQPUJ_EVQPUA | SW2 |
| 1 | BT3 | Panasonic_EVQPUJ_EVQPUA | SW3 |
| 1 | CHG | LED_0805_2012Metric | D1 |
| 1 | ESP32-WROOM-32U | ESP32-WROOM-32U | U1 |
| 1 | LP2985-3.3 | SOT-23-5 | U5 |
| 1 | MCP73831-2-OT | SOT-23-5 | U3 |
| 1 | OLED | PinHeader_1x04_P2.54mm_Vertical | J3 |
| 1 | PCM5102A | TSSOP-20_4.4x6.5mm_P0.65mm | U2 |
| 1 | PROG | PinHeader_1x06_P2.54mm_Vertical | J5 |
| 1 | RESET | Panasonic_EVQPUJ_EVQPUA | SW4 |
| 1 | USB-C | USB_C_Receptacle_HRO_TYPE-C-31-M-12 | J1 |
Similar boards
- 4 layers31.8 × 37.3 mm

- 2 layers45 × 99.5 mm

- 4 layers80 × 54 mm

Poket
kaorii-ako/Poket
ESP32-S3 Bluetooth MP3 player - custom PCB + 3D-printed case, built from scratch
104 parts - 2 layers230 × 160 mm

- 2 layers39.1 × 68.9 mm

BaseChipOnly
ZonatedCord/Yggdrasill
Smart LED plant pot — ESP32 PCB, WS2812B/SK6812 LEDs, WLED firmware, modular 3D-printed vase, and a native iOS app with Apple's Liquid Glass design.
34 parts1 - 2 layers129.6 × 89.8 mm

PowerMeter REV36
dj1yr/LJ-RF-Powermeter-Teensy-4.1
Here is a collection of files for the RF Powermeter with Teensy 4.0/4.1. Since I could not find any source files for the PCB, I designed two boards based on Robert Entwistle (WA2T) and the really impressive software by…
75 parts - 2 layers43.9 × 44.5 mm

- 2 layers69 × 58.7 mm

Questions
How big is the Blueaudio puck PCB?
It measures 60 × 64 mm and has 2 copper layers, 1.6 mm thick.
What parts does the Blueaudio puck use?
50 parts, built around the ESP32-WROOM-32U, AP2112K-3.3, LP2985-33DBV and PCM5102APW. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
Where can I download the Blueaudio puck KiCad files?
From the Zektopic/esp32-blue-audio-puck repository on GitHub, at the commit this page was made from: the board is hardware/blueaudio-puck.kicad_pcb and its schematic hardware/blueaudio-puck.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Can I use the Blueaudio puck design in my own project?
Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).