Skip to the content
4 layers100 × 100 mmDaily mirror p4, the printed circuit board in 3D

Open daily-mirror-p4.kicadpro in KiCad 10. This is an editable starting project with the connected controls schematic and 64 additional candidate components on four new schematic pages and the board.

Size
100 × 100 mm
Copper layers
4
Thickness
1.6 mm
Parts
84
Nets
9
Pads
459
Tracks, vias
0, 0
Routed
Not yet
KiCad
KiCad 10.0 (file 20260206)
Created
26 Jun 2022
Updated
21 Oct 2026

Overview

Daily mirror p4 is an open-source printed circuit board by drewhirschi, from the drewhirschi/daily_mirror repository on GitHub. It is a 4-layer board of 100 × 100 mm with 84 parts on 9 nets.

It is built around the ESP32-P4NRW32X, ESP32-C6-MINI-1-N4 and TLV62569DBVR-TP, with the TUSB320IRWBR, W25Q128JVSIQ and USBLC6-2SC6 among its other parts. Its parts include 28 capacitors, 17 resistors, 10 diodes, 9 ICs and 3 connectors. It belongs with the ESP32 and RISC-V boards of this library.

Main components

6

README

hardware/pcb-p4/README.md

Daily Mirror custom PCB - A1 component study

Open daily-mirror-p4.kicad_pro in KiCad 10. This is an editable starting project with the connected controls schematic and 64 additional candidate components on four new schematic pages and the board. It now has 80 electrical references plus four mounting holes. The imported main components have no circuit connections yet; the board has no routed traces. Do not order this board.

See sourcing.md for the part choices, 3D-model limitations and open-reference workflow. candidate-parts.csv records the new parts and their sources; it is not an order-ready BOM.

An editable, routed Olimex P4 development-board reference is in reference/olimex-esp32-p4-devkit. Open its ESP32-P4-DevKit_Rev_D1.kicad_pro separately to inspect the original connected design. It has not been merged into the Daily Mirror circuit. The previous A0 files/previews are saved in revisions/a0.

Decisions from this session

  • Keep the existing Arducam IMX519 as the camera baseline; preserve the goal of 16 MP stills. Use a purchased camera module on a ribbon cable. The image sensor and lens do not need to be integrated onto the main custom PCB.
  • USB-C wall power; a new enclosure designed around the final electronics.
  • Cost matters: favor a standard four-layer main board for the P4, common stocked components, and assembly on one side where practical. Evaluate total assembled cost, including setup and shipping, rather than promotional bare-PCB prices. No per-unit budget or production quantity has been specified yet.
  • One small four-pin RGB status indicator, plus a momentary capture/pairing button.
  • White-only emitters are preferred around the perimeter for photographs. The three-color CL651-3S modules are optional prototype parts, not a required final component. Choose documented white LEDs/modules and their current drivers once the brightness, optical layout and power budget are established.
  • Snap-in removable diffuser above the light modules. Include an opaque lens baffle, room between diffuser and emitters, and space behind the modules for a heat-spreading mount. Diffuser material, thickness, gap and clips need an optical/mechanical prototype; the current enclosure models are Pi-specific.

Important processor finding

The ESP32-P4 is still a candidate, not a confirmed solution for full-resolution IMX519 capture. Having a matching MIPI interface does not establish camera support.

Espressif's current ISP header defines ISP_LL_HSIZE_MAX as 1920. Its ISP driver rejects larger h_res values. The IMX519 full image is 4656 x 3496. Thus the ordinary P4 ISP processing path cannot process a full-width 16 MP frame. This is an image-processing-path limit, not proof that every raw CSI/DMA capture path is impossible. A bypass-and-upload approach would need a sensor driver, working DMA/buffer handling, exposure/focus control and a server image pipeline. It has not been implemented or tested here.

The official sensor list does not list a native IMX519 driver. Its Arducam PIVARIETY entry does not establish support for the user's native IMX519 module. The community IMX driver project checked lists other IMX sensors, not IMX519; its results cannot be assumed to apply to this camera.

A packed RAW10 full frame is 20,346,720 bytes (19.40 MiB); a 16-bit-per-pixel buffer takes 32,554,752 bytes (31.05 MiB), before firmware and other buffers. Capturing infrequently reduces average throughput, but not those per-frame buffer requirements. Streaming approaches must be proven separately.

Next hardware gate: demonstrate a full-field still from the actual IMX519 on the proposed processor, with usable exposure/focus and successful upload. If P4 raw capture cannot meet that requirement, select a processor with a validated IMX519 pipeline before drawing its main circuit. A custom board does not require a Raspberry Pi, and a P4 has not been chosen merely for size.

Source snapshot: ESP-IDF commit c712a0dde385d659a1470a136251980d31a70bc1, checked September 14, 2026. See reference/isp-limits.md.

What is actually drawn

ReferenceCircuitCurrent choice
D1Common-anode RGB indicatorProject symbol preserves documented pin order: 1 blue, 2 green, 3 common positive, 4 red
R1-R3One current-limiting resistor per color1 kohm provisional; adjust after measuring forward voltage and brightness
R5-R7Pull each color control high while GPIO is floating100 kohm; high = off, low = on
SW1Normally-open momentary buttonGeneric 6 mm tactile footprint, 4.3 mm actuator height candidate
R4 / C1Button pull-up and filter10 kohm / 100 nF; approximately 1 ms RC; use firmware debounce as well
TP1-TP6Future processor/control test access3.3 V, ground, blue, green, red, button
H1-H4Board-only mounting holesM3 clearance, provisional 92 x 92 mm spacing

The LED's common positive leg has no fourth series resistor. Three separate color resistors avoid the brightness interactions caused by sharing one resistor. The 1 kohm starting values cap direct GPIO current below 3.3 mA per channel at 3.3 V; final brightness, GPIO limits and resistor power must be checked against the chosen parts. This is only the small indicator circuit, not the COB driver.

The RGB symbol follows the existing wiring record, but the loose LED's view/orientation, lead size and lead order must be confirmed. The candidate wide-pin footprint uses formed leads at 2.54 mm pitch; it is not a claim that the unbent loose LED has that pitch. The generic button's mechanical height must also be chosen with the new faceplate.

The board is a 100 x 100 mm, four-copper-layer space study. None of those dimensions, mounting holes or layer rules is a final manufacturing specification. The PCB now contains the imported candidate footprints, including eight white emitters. The camera faceplate clearance is still a drawing guide; the separate camera module, cable, diffuser and enclosure have not been mechanically modeled. The 3D preview represents these placed components; five package types use explicitly approximate models. See the sourcing notes before using this for mechanical fit.

Existing CL651-3S prototype light modules

The final board can use white-only parts instead. The notes below apply only if the already-owned three-color modules are used for prototype measurements.

The supplied photo and the manual linked from the exact Temu listing identify a three-color, common-negative COB module. The manual explicitly maps:

Pad markingSeller's stated function
B+White positive
W+Blue positive
R+Red positive
-Shared negative

This unusual B/W assignment should be checked at low current on a current-limited bench supply before wiring a batch. Only white and negative will be used; unused red/blue positives stay unconnected.

The listing/manual states 3.2-3.7 V and warns of heating at 3.7 V. It provides no rated current, pulse current, pulse width, thermal resistance, CRI or CCT. It is not a complete electrical datasheet. Do not substitute its broad listing category <=36 V for the actual operating voltage.

Plan a controlled-current path for each white module, with default-off enable and a bounded illumination time. Do not drive COB modules from GPIO, connect them directly to USB's 5 V, or infer a current limit from voltage alone. Do not parallel bare modules behind one driver without a validated current-sharing scheme. The appropriate buck/linear topology, current sense resistor, module count, connector, copper area and USB supply rating remain unresolved.

These parts already have their own substrate. The likely integration is short two-wire connections to modules mounted around the faceplate/perimeter, with control electronics on the main PCB. Direct mechanical/electrical attachment to the main board needs measured pad positions, mounting holes and a thermal design. No guessed CL651-3S solder footprint is included.

Flash timing and diffuser

Short duty cycles reduce average heat: average electrical power = V * I * on-time * flashes-per-second for constant rectangular pulses. Peak junction temperature and safe pulse current still matter; average power alone does not establish safety. Repeated presses and a stuck-on software state must be tested. No pulse overdrive is assumed without a manufacturer rating.

The IMX519 is a rolling-shutter camera. Start with steady white illumination through the full frame exposure/readout window, then characterize the shortest uniform pulse from actual captured images. Avoid unsynchronized PWM during capture. Test for bands, face shadows, clipping, diffuser hot spots, lens flare and enclosure temperature at the maximum intended repeat rate.

Record current, measured light output and duration before deciding whether a small heat spreader is enough. Keep diffuser clips clear of the thermal path.

What the main circuit still needs

  • Camera-proven processor, package/revision and memory capacity.
  • For a P4 design: external flash, reference crystal, core regulator, PHY and other supplies/decoupling, reset/boot circuitry and programming access. Use Espressif's revision-v3-or-later reference; older revisions differ electrically.
  • Wi-Fi/BLE companion and antenna layout if using P4. ESP32-C6-MINI-1 with SDIO is the reference direction; P4 itself does not contain a Wi-Fi/BLE radio.
  • USB-C connector, CC handling, input protection, regulator and current budget. Two CC pull-downs establish a sink attachment but do not by themselves authorize a 3 A load. Detect the source's available current or negotiate PD as required.
  • Exact Arducam module SKU/revision and ribbon. Pi-style connectors can be 15-pin 1 mm or 22-pin 0.5 mm. Confirm connector-side pin numbering, contacts, supply, controls, level shifting and cable orientation before assigning the footprint.
  • CSI differential pairs routed against the chosen fabricator's stackup and Espressif's guidelines; impedance is not established by arbitrary trace widths.
  • Flash/illumination driver and any local storage required for failed uploads.

The phone experience is firmware/app work too: BLE discovery while pairing, authenticated ownership setup, transfer of Wi-Fi credentials, association and account registration, then normal capture/upload. Add long-press recovery, factory reset, signed updates and upload retry. KiCad does not implement this. The existing Pi program invokes rpicam-still; that part cannot run unchanged on the P4. Backend protocols and device states can be reused where applicable.

KiCad setup and working together

KiCad 10.0.6 was installed without its library packages. The matching official Arch packages (kicad-library and kicad-library-3d, 10.0.6-1) were downloaded, their signatures verified against the installed Arch keyring, and extracted to:

/home/drew/.local/share/kicad/10.0/official-10.0.6

This per-user install avoids the system installer's password requirement. It does not register those two library packages with pacman. KiCad's global library table references and KICAD10_* paths were updated. The previous settings are in:

/home/drew/.config/kicad/10.0/before-daily-mirror-20260914-214132

The dangling default reference to a nonexistent optional design-block library was also removed; its original table is in that backup. Design blocks are not needed for this project.

Restart KiCad once if it was already open. Then:

  1. File > Open Project and select daily-mirror-p4.kicad_pro in this directory.
  2. Open the .kicad_sch for the architecture and control circuit.
  3. Open the .kicad_pcb; enable User.Drawings to see the reserved areas.
  4. Use View > 3D Viewer to inspect the placed candidate parts.

The current 3D render is output/board-3d.png. The STEP assembly in output/daily-mirror-a0.step contains the current board and the placed component models, and can be opened in mechanical CAD for enclosure work. Neither includes the unselected processor, camera module, power connectors or white emitters.

Reading the design

The schematic describes electrical connections. Green lines are wires in that diagram; repeated net names identify the same electrical connection without drawing a long line across the page. The PCB shows real component locations and solder pads. Its connections become copper traces routed between pads; this initial board has no routed traces yet. In the PCB editor, thin ratsnest lines can show which pads still need connections; those are guides, not copper. The 3D viewer shows physical models, not schematic symbols or ratsnest lines.

LabelMeaning
J1, J2Connectors, such as camera ribbon or USB
U1, U2Integrated circuits/chips; exact function depends on the part
R1, R2Resistors
C1, C2Capacitors; often resemble tiny resistors
D1Diode or LED
SW1Switch/button
TP1Test point

For a sourced part, check three separate CAD representations: its schematic symbol (electrical pins), footprint (solder pads and holes), and STEP/3D model (physical shape). Matching physical shape alone does not prove the pin mapping or circuit works. Use exact manufacturer part numbers and package drawings.

Making a physical unit

PCB fabrication makes the patterned copper board. PCB assembly adds and solders the purchased components. An assembly order typically needs Gerbers/drill files, a bill of materials with exact part numbers, and placement/orientation data. Fabricators do not print silicon image sensors or lenses. A camera module can be purchased separately and connected after board assembly.

JLCPCB offers an assembly parts library and sourcing/consignment options; PCBWay offers turnkey, partial-turnkey and customer-supplied component assembly. Stock, exact packages and service eligibility must be checked before choosing the final bill of materials. Firmware flashing and functional testing require their own agreed process; soldering the board does not establish that it works.

There is no callable KiCad MCP in this session. We can edit the native files and use KiCad CLI for validation and previews. Close the affected editor before external edits and reopen it afterward; do not assume live reload. For edits made in the schematic editor, Update PCB from Schematic (F8) transfers changes. The .kicad_pro file is the project, .kicad_sch is the circuit, and .kicad_pcb is the physical board.

Small project-local symbol, footprint and 3D libraries make the study portable. The generator refuses to overwrite an existing design. Interactive KiCad files are the source of truth once editing begins. To reproduce the initial study in a separate directory:

sh
python build_starter.py --output /tmp/daily-mirror-pcb-study

Checks

See output/validation.json for the final counts. The controls schematic still has zero ERC violations and its nine nets match the board pads. All 80 schematic component pin-number sets match the footprints, with J2's additional mechanical mounting tabs explicitly accounted for. All 74 placed model references resolve. No component courtyards overlap.

The whole project has 377 ERC findings from unconnected/undriven candidate pins and 96 DRC findings (USB pad nets/connector hole clearance and silkscreen size/overlaps). The 21 unrouted controls connections remain; because the new circuits have no assigned nets, that number does not count their future routing. No Daily Mirror Gerbers, assembly order or firmware release has been produced.

Sources

Parts

84
QtyValueFootprintReferences
20100nFDailyMirror:C_0603_1608MetricC1, C2, C3, C4, C5, C10, C11, C12, C13, C14, C15, C16, C17, C19, C20, C24 +4
8White 5000 K / CRI90DailyMirror:LED_Cree-XP-GD2, D3, D4, D5, D6, D7, D8, D9
4100kDailyMirror:R_0603_1608MetricR5, R6, R7, R14
410uFDailyMirror:C_0805_2012MetricC18, C21, C22, C23
4MountingHole_3.2mm_M3MountingHole_3.2mm_M3H1, H2, H3, H4
310kDailyMirror:R_0603_1608MetricR4, R12, R13
31k (start)DailyMirror:R_0603_1608MetricR1, R2, R3
22.2 uHDailyMirror:L_Coilcraft_XAL4020-XXXL1, L2
22.2kDailyMirror:R_0603_1608MetricR16, R17
24.02kDailyMirror:R_0603_1608MetricR10, R11
2499kDailyMirror:R_0603_1608MetricR8, R9
2TUNE pFDailyMirror:C_0603_1608MetricC27, C28
1+3V3DailyMirror:TestPoint_Pad_D1.5mmTP1
110 uHDailyMirror:L_Coilcraft_XAL4040-XXXL3
11uFDailyMirror:C_0805_2012MetricC25
12 ohmDailyMirror:R_0805_2012MetricR15
122pFDailyMirror:C_0603_1608MetricC26
140 MHz / 10 pFDailyMirror:Crystal_SMD_3225-4Pin_3.2x2.5mmY1
1BOOTDailyMirror:SW_PUSH_6mm_H4.3mmSW3
1ESP32-C6-MINI-1-N4DailyMirror:ESP32-C6-MINI-1U2
1ESP32-P4NRW32XDailyMirror:ESP32-P4U1
1GNDDailyMirror:TestPoint_Pad_D1.5mmTP2
1Momentary NODailyMirror:SW_PUSH_6mm_H4.3mmSW1
1Pi-style CSI camera - 15 pinDailyMirror:Molex_200528-0150_1x15-1MP_P1.00mm_HorizontalJ2
1RESETDailyMirror:SW_PUSH_6mm_H4.3mmSW2
1RGB common anodeDailyMirror:LED_D5.0mm-4_RGB_Wide_PinsD1
1SS16-E3/61TDailyMirror:D_SMAD10
1STATUS_B_NDailyMirror:TestPoint_Pad_D1.5mmTP3
1STATUS_G_NDailyMirror:TestPoint_Pad_D1.5mmTP4
1STATUS_R_NDailyMirror:TestPoint_Pad_D1.5mmTP5
1Service UART / bootDailyMirror:PinHeader_1x06_P2.54mm_VerticalJ3
1TLV62569DBVRDailyMirror:SOT-23-5U5
1TPS22919DCKRDailyMirror:SOT-363_SC-70-6U9
1TPS61165DBVRDailyMirror:SOT-23-6U7
1TPS62132RGTRDailyMirror:VQFN-16-1EP_3x3mm_P0.5mm_EP1.68x1.68mmU4
1TUSB320IRWBRDailyMirror:Texas_X2QFN-12_1.6x1.6mm_P0.4mmU6
1USB-C / 5 VDailyMirror:USB_C_Receptacle_GCT_USB4105-xx-A_16P_TopMnt_HorizontalJ1
1USBLC6-2SC6DailyMirror:SOT-23-6U8
1USER_BUTTON_NDailyMirror:TestPoint_Pad_D1.5mmTP6
1W25Q128JVSIQDailyMirror:SOIC-8_5.3x5.3mm_P1.27mmU3

Similar boards

  • 4 layers60 × 36 mmCamera Project, the printed circuit board in 3D

    Camera Project

    Raphi25/Camera-Project

    This project investigates the development of a low-cost wearable camera system intended to support caregivers by capturing images throughout the wearer's daily life.

    132 parts
  • 4 layers110 × 80 mmEsp32p4 extreme, the printed circuit board in 3D

    Esp32p4 extreme

    Andreuxxx1977/esp32-p4

    An open-hardware, actively cooled ESP32-P4 board for heavy multimedia work: a 2-lane MIPI camera, a 2-lane MIPI display, USB 2.0 High-Speed, 10/100 Ethernet, UHS-I microSD, 32 MB flash and 32 MB PSRAM.

    234 parts1CERN-OHL-P-2.0
  • 6 layers39.5 × 39.5 mmP4eregrine, the printed circuit board in 3D

    P4eregrine

    anticitizn/p4eregrine

    All-in-one ESP32 P4-based drone ESC, flight controller, and video processor

    359 parts21
  • 2 layers70.6 × 100 mmLogger v1, the printed circuit board in 3D

    Logger v1

    ntakao2006-web/RaceCapture

    123 parts1
  • 4 layers74.5 × 70.3 mmNest mini v2-drop in pcb, the printed circuit board in 3D

    Nest mini v2-drop in pcb

    iMike78/nest-mini-drop-in-pcb

    Drop-in PCB replacement for the Google Nest Mini v2 with ESP32-S3, ESP32-P4 and optional ESP32-C6. Inspired by Onju Voice and Home Assistant Voice PE.

    229 parts628CERN-OHL-S-2.0
  • 4 layers38 × 74 mmStratosdrone, the printed circuit board in 3D

    Stratosdrone

    equationstratos/STRATOSDRONES

    A 4-layer, 36×70 mm Tello-style portrait controller board for the STRATOSDRONE: chip-down ESP32-P4 (flight + camera + hardware H.264) with an ESP32-C6-MINI-1 Wi-Fi co-processor, IMU / barometer / ToF / optical-flow…

    115 parts
  • 4 layers42 × 42 mmVayuF7, the printed circuit board in 3D

    VayuF7

    ishantmahatopro/Vayu-F722

    Custom 42x42mm 4-layer STM32F722 FPV flight controller for 5in and 7in cinematic and telemetry quads.

    146 partsMIT
  • 6 layers98 × 64 mmLa ecp5, the printed circuit board in 3D

    La ecp5

    PaulBichl/VibePCB-LA

    A 16-channel, 100 MSa/s USB 2.0 HS logic analyzer: a Lattice ECP5 FPGA (CABGA-256 BGA) capturing into a 32 MB SDRAM (54-ball BGA), read out over an FT2232H. 98 x 64 mm, 6 layers.

    103 parts

Questions

How big is the Daily mirror p4 PCB?

It measures 100 × 100 mm and has 4 copper layers, 1.6 mm thick.

What parts does the Daily mirror p4 use?

84 parts, built around the ESP32-P4NRW32X, ESP32-C6-MINI-1-N4, TLV62569DBVR-TP and TUSB320IRWBR. 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 Daily mirror p4 KiCad files?

From the drewhirschi/daily_mirror repository on GitHub, at the commit this page was made from: the board is hardware/pcb-p4/daily-mirror-p4.kicad_pcb and its schematic hardware/pcb-p4/daily-mirror-p4.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Daily mirror p4 design in my own project?

Its repository states no licence, so its author keeps all rights: ask drewhirschi before reusing the design.