Skip to the content
2 layers27.9 × 48.8 mmEos esp32-devkit, the printed circuit board in 3D

Hardware designs + EE docs + Board datasheets of Multiple products

Size
27.9 × 48.8 mm
Copper layers
2
Thickness
1.6 mm
Parts
36
Nets
71
Pads
220
Tracks, vias
480, 36
Pours
2
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
7 Apr 2026
Updated
2 Nov 2026

Overview

Eos esp32-devkit is an open-source printed circuit board by embeddedos-org, from the embeddedos-org/eCAD-Hardware-Products repository on GitHub, published under the MIT licence. It is a 2-layer board of 27.9 × 48.8 mm with 36 parts on 71 nets, routed with 480 tracks and 36 vias.

It is built around the ESP32-WROOM-32E-N4, CP2102N-A02-GQFN24R and AP7361C-33E, with the SP0503BAHTG, MMBT3904LT1G and 1206L050YR among its other parts. Its parts include 12 resistors, 9 capacitors, 4 ICs, 3 diodes and 3 connectors. It belongs with the ESP32 boards of this library.

Main components

10

README

README.md

eCAD Hardware Products

CI CodeQL Scorecard License: MIT

Hardware / PCB CAD design collection for the EmbeddedOS (EoS) ecosystem. The repository organizes hardware product designs by application domain. Each domain holds one or more product lines, and each product line typically carries a product datasheet, a bill of materials (bom.csv), power-budget simulation scripts, and placeholder directories for PCB and mechanical CAD artifacts. Several product lines also include KiCad schematics (*.kicad_sch).

Status varies by design. Directories are at different maturity levels (many "Design" / "Pre-production"); PCB and CAD folders often contain .gitkeep placeholders rather than finished layouts. Check each design's own README.md and docs/ for its current state.

Domains

The repository contains 16 domain design collections:

DomainFocus
eAerospace_CAD_DesignAircraft components, avionics, UAV/drone systems, space systems
eConsumer_CAD_DesignSmart home devices, personal wearables, AR/smart devices
eCybersecurity_CAD_DesignSecurity appliances and physical security systems
eDefense_CAD_DesignSurveillance, tactical communications, protection equipment
eElectronics_CAD_DesignPCBs, embedded controllers, RF modules, FPGAs, AI accelerators
eEnergy_CAD_DesignBattery products, renewable energy systems, power electronics
eHealth365_CAD_DesignTwo-device health monitoring system (smart patch / smart ring)
eIndustrial_CAD_DesignSensors, industrial electronics, infrastructure equipment
eMedical_CAD_DesignDiagnostic, surgical, patient-care, laboratory equipment
eMining_CAD_DesignAutonomous mining/construction equipment, industrial safety systems
ePAM_CAD_DesignPersonal air/ground mobility — solar-hybrid transport, 4-product line
eRadar360_CAD_Design360° automotive safety radar + laser + V2X + AI threat detection
eRobotics_CAD_DesignIndustrial robots, autonomous systems, robot components
eSmartCity_CAD_DesignUrban infrastructure, utilities, telecommunications
eTransport_CAD_DesignAutomotive electronics, rail systems, maritime systems
eosHealth_CAD_DesignFour-device wearable health platform

Plus:

  • future_designs/ — early/prospective concepts (e.g. eBCI-Lite)
  • docs/ — repository-level documentation

Typical design layout

Most domains follow a common structure, for example:

text
eAerospace_CAD_Design/
  README.md
  docs/                      business_plan.md, regulatory_path.md
  ebuild_simulation/         eBuild simulation notes
  <product_line>/
    product_datasheet.md
    bom.csv
    simulation/power_budget_sim.py
    hardware/
      pcb/  cad/  antenna/   (artifact folders; often .gitkeep placeholders)

Artifact formats present in the repo include Markdown datasheets, CSV BOMs, Python simulation scripts, and KiCad schematics (*.kicad_sch). Some product lines also include TypeScript/Dart companion app sources and 3D-model notes.

Simulations

Power-budget simulations are plain Python scripts, runnable per product line:

bash
cd eAerospace_CAD_Design/<product_line>/simulation/
python3 power_budget_sim.py

Design docs reference the EoSim digital-twin platform for hardware-in-the-loop testing. Running one script alone does not establish that a product is validated.

Evidence-backed product validation

The committed tools/catalog/product_inventory.json is the complete product execution set. The v1 contract schemas and policy requirements are documented in docs/hardware-validation-contract-v1.md.

Discover inventory drift and inspect local tool capabilities:

bash
python3 tools/validate_products.py discover
python3 tools/validate_products.py capabilities

Execute V0-V4 for every inventoried product and write hash-bound receipts:

bash
python3 tools/validate_products.py validate \
  --all \
  --output /tmp/ecad-validation \
  --mode evidence
python3 tools/validate_products.py verify-bundle \
  /tmp/ecad-validation/bundle.json

--mode evidence succeeds when the selected inventory was executed and valid receipts were written. Individual products may still be honestly FAIL, BLOCKED, INCONCLUSIVE, or NOT_RUN. Use --mode gate for a release check; it succeeds only when every selected product has real PASS evidence for V0, V1, V2, V3, and V4. Historical baseline entries never waive a failed or missing requirement.

CAD dataset and engineering model

datasets/cad/ holds CAD dataset items for the multi-domain validation work in issue #27. Each item is a STEP design, the design intent the CAD cannot carry, and machine-readable requirements; the pipeline extracts it with the OpenCASCADE kernel, builds an engineering model in which every value states its source and status, and runs V0-V4 with domain simulators. UNKNOWN values are never filled in: a requirement that depends on one is BLOCKED.

bash
python3 -m pip install -r tools/requirements.txt -r tools/requirements-cad.txt
python3 tools/cad_dataset.py check    datasets/cad/robotic_joint_001
python3 tools/cad_dataset.py validate datasets/cad/robotic_joint_001 --output /tmp/joint-run

See datasets/cad/README.md and docs/cad-dataset-engineering-model-v1.md.

License

MIT — see LICENSE.

One exception: the EmbeddedOS original boards in boards/eos, their design files and the footprint library drawn for them are Copyright (c) 2026 Kartikeydheer Srivastava, all rights reserved, and are not under the MIT licence. The exact files are listed in boards/eos/README.md.

Parts

36
QtyValueFootprintReferences
410kResistor_SMD:R_0402_1005MetricR4, R5, R10, R11
44.7uCapacitor_SMD:C_0603_1608MetricC1, C2, C6, C8
3100nCapacitor_SMD:C_0402_1005MetricC3, C7, C9
35.1kResistor_SMD:R_0402_1005MetricR1, R2, R12
2MMBT3904Package_TO_SOT_SMD:SOT-23Q1, Q2
11kResistor_SMD:R_0402_1005MetricR7
11uCapacitor_SMD:C_0402_1005MetricC5
122.1kResistor_SMD:R_0402_1005MetricR8
122uCapacitor_SMD:C_0805_2012MetricC4
147.5kResistor_SMD:R_0402_1005MetricR9
1500mAFuse:Fuse_1206_3216MetricF1
1680Resistor_SMD:R_0402_1005MetricR6
1750Resistor_SMD:R_0402_1005MetricR3
1AP7361C-33Package_TO_SOT_SMD:SOT-223-3_TabPin2U3
1BOOTButton_Switch_SMD:SW_Push_1P1T_NO_CK_KMR2SW2
1CP2102N-A02-GQFN24Package_DFN_QFN:QFN-24-1EP_4x4mm_P0.5mm_EP2.6x2.6mmU4
1ENButton_Switch_SMD:SW_Push_1P1T_NO_CK_KMR2SW1
1ESP32-WROOM-32E-N4RF_Module:ESP32-WROOM-32EU1
1IO4LED_SMD:LED_0603_1608MetricD3
1J2Connector_PinHeader_2.54mm:PinHeader_1x19_P2.54mm_VerticalJ2
1J3Connector_PinHeader_2.54mm:PinHeader_1x19_P2.54mm_VerticalJ3
1PMEG6010CEHDiode_SMD:D_SOD-123FD1
1PWRLED_SMD:LED_0603_1608MetricD2
1SP0503BAHTGPackage_TO_SOT_SMD:SOT-143U2
1USB-CConnector_USB:USB_C_Receptacle_HRO_TYPE-C-31-M-12J1

More from embeddedos-org/eCAD-Hardware-Products

12
  • 2 layers161 × 132 mmSparkFun BMV080 panelized, the printed circuit board in 3D

    SparkFun BMV080 panelized

    embeddedos-org/eCAD-Hardware-Products

    Hardware designs + EE docs + Board datasheets of Multiple products

    2,869 parts8MIT
  • 12 layers86.4 × 54.6 mmBeaglebone ai rev a2, the printed circuit board in 3D

    Beaglebone ai rev a2

    embeddedos-org/eCAD-Hardware-Products

    Hardware designs + EE docs + Board datasheets of Multiple products

    766 parts8MIT
  • 16 layers280 × 200 mmQuantum control, the printed circuit board in 3D

    Quantum control

    embeddedos-org/eCAD-Hardware-Products

    Hardware designs + EE docs + Board datasheets of Multiple products

    740 parts8MIT
  • 12 layers86.4 × 54.6 mmBeaglebone ai, the printed circuit board in 3D

    Beaglebone ai

    embeddedos-org/eCAD-Hardware-Products

    Hardware designs + EE docs + Board datasheets of Multiple products

    718 parts8MIT
  • 12 layers160 × 120 mmBioelectronics, the printed circuit board in 3D

    Bioelectronics

    embeddedos-org/eCAD-Hardware-Products

    Hardware designs + EE docs + Board datasheets of Multiple products

    641 parts8MIT
  • 16 layers420 × 300 mmInference servers, the printed circuit board in 3D

    Inference servers

    embeddedos-org/eCAD-Hardware-Products

    Hardware designs + EE docs + Board datasheets of Multiple products

    637 parts8MIT
  • 16 layers280 × 200 mmSigint systems, the printed circuit board in 3D

    Sigint systems

    embeddedos-org/eCAD-Hardware-Products

    Hardware designs + EE docs + Board datasheets of Multiple products

    631 parts8MIT
  • 2 layers131.8 × 131.8 mm13738-Lumenati 4-pack panel.v10, the printed circuit board in 3D

    13738-Lumenati 4-pack panel.v10

    embeddedos-org/eCAD-Hardware-Products

    Hardware designs + EE docs + Board datasheets of Multiple products

    553 parts8MIT

Similar boards

  • 2 layers57 × 32 mmAvalanche Laser Driver, the printed circuit board in 3D

    Avalanche Laser Driver

    hannesduske/Avalanche_Laser_Driver

    An open-hardware avalanche transistor based nanosecond laser driver with integrated high-voltage supply capable of generating 150 A peak current pulses.

    65 parts1CERN-OHL-P-2.0
  • 2 layers51.5 × 48.9 mmESP32 IoT Sensor Controller, the printed circuit board in 3D

    ESP32 IoT Sensor Controller

    ehasunchy/kicad-pcb-projects

    KiCad PCB design portfolio featuring ESP32 IoT hardware, power regulation, USB interfaces, schematics, PCB layouts, and manufacturing files.

    36 parts
  • 4 layers83 × 109 mmD4 small pcb panel, the printed circuit board in 3D

    D4 small pcb panel

    unsurv/unsurv-offline

    Offline portable GNSS device based on the ESP32

    522 parts72
  • 4 layers104 × 144 mmWQ PCB, the printed circuit board in 3D

    WQ PCB

    332753-art/Water_Quality_Monitoring

    portable Water Quality Monitoring System for Live Fish Transport

    78 partsApache-2.0
  • 6 layers36 × 124 mmOpenDual Reader, the printed circuit board in 3D

    OpenDual Reader

    nuerolynx/embedded-systems-lab

    Arduino UNO R4 WiFi and ESP32 prototypes for access control, automation, displays, monitoring, and Bluetooth audio.

    74 parts4
  • 4 layers54.6 × 54.6 mmECP5, the printed circuit board in 3D

    ECP5

    gildobjanschi/ECP5_BGA381_RISCV

    ECP5 FPGA with 8MB PSRAM and extension header

    115 parts1MIT
  • 4 layers54.6 × 54.6 mmECP5, the printed circuit board in 3D

    ECP5

    gildobjanschi/ECP5_BGA381_RISCV_EXT

    Extension board for ECP5_BGA381_RISCV

    78 parts1MIT

Questions

How big is the Eos esp32-devkit PCB?

It measures 27.9 × 48.8 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Eos esp32-devkit use?

36 parts, built around the ESP32-WROOM-32E-N4, CP2102N-A02-GQFN24R, AP7361C-33E and SP0503BAHTG. 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 Eos esp32-devkit KiCad files?

From the embeddedos-org/eCAD-Hardware-Products repository on GitHub, at the commit this page was made from: the board is boards/eos/eos-esp32-devkit/hardware/eos-esp32-devkit.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.

Can I use the Eos esp32-devkit 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).