
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.

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.
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.
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.
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.
| Reference | Circuit | Current choice |
|---|---|---|
| D1 | Common-anode RGB indicator | Project symbol preserves documented pin order: 1 blue, 2 green, 3 common positive, 4 red |
| R1-R3 | One current-limiting resistor per color | 1 kohm provisional; adjust after measuring forward voltage and brightness |
| R5-R7 | Pull each color control high while GPIO is floating | 100 kohm; high = off, low = on |
| SW1 | Normally-open momentary button | Generic 6 mm tactile footprint, 4.3 mm actuator height candidate |
| R4 / C1 | Button pull-up and filter | 10 kohm / 100 nF; approximately 1 ms RC; use firmware debounce as well |
| TP1-TP6 | Future processor/control test access | 3.3 V, ground, blue, green, red, button |
| H1-H4 | Board-only mounting holes | M3 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.
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 marking | Seller'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.
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.
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 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:
daily-mirror-p4.kicad_pro in this directory..kicad_sch for the architecture and control circuit..kicad_pcb; enable User.Drawings to see the reserved areas.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.
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.
| Label | Meaning |
|---|---|
| J1, J2 | Connectors, such as camera ribbon or USB |
| U1, U2 | Integrated circuits/chips; exact function depends on the part |
| R1, R2 | Resistors |
| C1, C2 | Capacitors; often resemble tiny resistors |
| D1 | Diode or LED |
| SW1 | Switch/button |
| TP1 | Test 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.
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:
python build_starter.py --output /tmp/daily-mirror-pcb-studySee 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.
| Qty | Value | Footprint | References |
|---|---|---|---|
| 20 | 100nF | DailyMirror:C_0603_1608Metric | C1, C2, C3, C4, C5, C10, C11, C12, C13, C14, C15, C16, C17, C19, C20, C24 +4 |
| 8 | White 5000 K / CRI90 | DailyMirror:LED_Cree-XP-G | D2, D3, D4, D5, D6, D7, D8, D9 |
| 4 | 100k | DailyMirror:R_0603_1608Metric | R5, R6, R7, R14 |
| 4 | 10uF | DailyMirror:C_0805_2012Metric | C18, C21, C22, C23 |
| 4 | MountingHole_3.2mm_M3 | MountingHole_3.2mm_M3 | H1, H2, H3, H4 |
| 3 | 10k | DailyMirror:R_0603_1608Metric | R4, R12, R13 |
| 3 | 1k (start) | DailyMirror:R_0603_1608Metric | R1, R2, R3 |
| 2 | 2.2 uH | DailyMirror:L_Coilcraft_XAL4020-XXX | L1, L2 |
| 2 | 2.2k | DailyMirror:R_0603_1608Metric | R16, R17 |
| 2 | 4.02k | DailyMirror:R_0603_1608Metric | R10, R11 |
| 2 | 499k | DailyMirror:R_0603_1608Metric | R8, R9 |
| 2 | TUNE pF | DailyMirror:C_0603_1608Metric | C27, C28 |
| 1 | +3V3 | DailyMirror:TestPoint_Pad_D1.5mm | TP1 |
| 1 | 10 uH | DailyMirror:L_Coilcraft_XAL4040-XXX | L3 |
| 1 | 1uF | DailyMirror:C_0805_2012Metric | C25 |
| 1 | 2 ohm | DailyMirror:R_0805_2012Metric | R15 |
| 1 | 22pF | DailyMirror:C_0603_1608Metric | C26 |
| 1 | 40 MHz / 10 pF | DailyMirror:Crystal_SMD_3225-4Pin_3.2x2.5mm | Y1 |
| 1 | BOOT | DailyMirror:SW_PUSH_6mm_H4.3mm | SW3 |
| 1 | ESP32-C6-MINI-1-N4 | DailyMirror:ESP32-C6-MINI-1 | U2 |
| 1 | ESP32-P4NRW32X | DailyMirror:ESP32-P4 | U1 |
| 1 | GND | DailyMirror:TestPoint_Pad_D1.5mm | TP2 |
| 1 | Momentary NO | DailyMirror:SW_PUSH_6mm_H4.3mm | SW1 |
| 1 | Pi-style CSI camera - 15 pin | DailyMirror:Molex_200528-0150_1x15-1MP_P1.00mm_Horizontal | J2 |
| 1 | RESET | DailyMirror:SW_PUSH_6mm_H4.3mm | SW2 |
| 1 | RGB common anode | DailyMirror:LED_D5.0mm-4_RGB_Wide_Pins | D1 |
| 1 | SS16-E3/61T | DailyMirror:D_SMA | D10 |
| 1 | STATUS_B_N | DailyMirror:TestPoint_Pad_D1.5mm | TP3 |
| 1 | STATUS_G_N | DailyMirror:TestPoint_Pad_D1.5mm | TP4 |
| 1 | STATUS_R_N | DailyMirror:TestPoint_Pad_D1.5mm | TP5 |
| 1 | Service UART / boot | DailyMirror:PinHeader_1x06_P2.54mm_Vertical | J3 |
| 1 | TLV62569DBVR | DailyMirror:SOT-23-5 | U5 |
| 1 | TPS22919DCKR | DailyMirror:SOT-363_SC-70-6 | U9 |
| 1 | TPS61165DBVR | DailyMirror:SOT-23-6 | U7 |
| 1 | TPS62132RGTR | DailyMirror:VQFN-16-1EP_3x3mm_P0.5mm_EP1.68x1.68mm | U4 |
| 1 | TUSB320IRWBR | DailyMirror:Texas_X2QFN-12_1.6x1.6mm_P0.4mm | U6 |
| 1 | USB-C / 5 V | DailyMirror:USB_C_Receptacle_GCT_USB4105-xx-A_16P_TopMnt_Horizontal | J1 |
| 1 | USBLC6-2SC6 | DailyMirror:SOT-23-6 | U8 |
| 1 | USER_BUTTON_N | DailyMirror:TestPoint_Pad_D1.5mm | TP6 |
| 1 | W25Q128JVSIQ | DailyMirror:SOIC-8_5.3x5.3mm_P1.27mm | U3 |

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.

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.

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


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.

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…

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

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.
It measures 100 × 100 mm and has 4 copper layers, 1.6 mm thick.
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.
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.
Its repository states no licence, so its author keeps all rights: ask drewhirschi before reusing the design.