Skip to content

[Call for Contributors] Design Official PCB for KryonOS Device #9

Description

@Haris16-code

Overview

We are looking for hardware contributors and PCB designers to help create an official, open-source PCB for the KryonOS handheld device.

The goal is to move from breadboards/prototyping wires to a clean, reliable, modular PCB that anyone can fabricate via standard manufacturers (e.g., JLCPCB, PCBWay).


Hardware Requirements & Target Stack

  1. Microcontroller Core:

    • Module / DevBoard: ESP32-S3-WROOM-1 (N16R8 — 16MB Flash, 8MB Octal PSRAM) standard 42-pin DevKit footprint (female headers for drop-in mounting).
    • Antenna Clearance: The top PCB antenna area must remain completely clear of any copper traces or ground pours to ensure reliable Wi-Fi/Bluetooth range.
  2. Display & Touch:

    • Module: ILI9341 2.8" SPI TFT LCD with XPT2046 Resistive Touch Controller.
    • Mounting / Stability:
      • Standard 1x14 2.54mm header socket for the primary display/touch bus.
      • Dedicated mechanical support/dummy header or M2/M2.5 corner standoff mounting holes to prevent screen wobble under touch pressure.
  3. External Expansion Ports:

    • Dual I2C Ports (JST-SH 1.0mm 4-Pin / STEMMA QT / Qwiic compatible):
      • Daisy-chained in parallel on the same I2C bus.
      • Pinout standard: Pin 1: GND, Pin 2: 3.3V, Pin 3: SDA, Pin 4: SCL.
      • Shared bus pull-up resistors: Dual 4.7kΩ SMD (0805) to +3.3V.

Target Reference Pinout

Function Pin Name ESP32-S3 GPIO Notes
I2C Bus I2C_SDA GPIO 1 Shared across both JST connectors (with 4.7kΩ pull-up)
I2C Bus I2C_SCL GPIO 2 Shared across both JST connectors (with 4.7kΩ pull-up)
TFT Display TFT_CS GPIO 10 Chip Select
TFT Display TFT_DC GPIO 9 Data/Command
TFT Display TFT_RST GPIO 8 Reset
TFT Display TFT_MOSI / SDI GPIO 11 SPI Data Out
TFT Display TFT_SCK GPIO 12 SPI Clock
TFT Display TFT_LED 3.3V Backlight (or GPIO if PWM dimming is added)
Touch Controller T_CS GPIO 13 XPT2046 Chip Select
Touch Controller T_CLK GPIO 12 Shared with SPI Clock
Touch Controller T_DIN GPIO 11 Shared with SPI MOSI
Touch Controller T_DO GPIO 16 Touch MISO / Data Out
Touch Controller T_IRQ GPIO 14 (Optional) Touch Pen-Down Interrupt

Board Guidelines

We welcome diverse interpretations and form factors! Feel free to adapt the layout to your preferred manufacturing style and CAD workflow:

  • CAD Tooling: Designer's choice (EasyEDA Standard/Pro, KiCad, or Fusion/Eagle). Please include open source project files alongside Gerbers.
  • Layer Count: 2-layer or 4-layer (designer's preference based on routing complexity).
  • Form Factor & Dimensions: Open to maker interpretation. You can design a compact stacked backpack, a handheld horizontal console style, or a desktop dock.

    Tip: Staying within 100 mm x 100 mm helps keep fabrication costs low on budget prototype tiers (like JLCPCB/PCBWay).

  • Power & Ground: Ensure solid GND planes and adequate trace widths for power rails (3.3V / 5V) to handle the ESP32-S3 and display backlight smoothly.
  • Component Selection: Prefer easily sourceable basic parts (SMD 0805 or through-hole options) for easy DIY hand-soldering.

How to Contribute

  1. Comment on this issue if you are interested in drafting, proposing a form factor, or reviewing layouts. Feel free to share concept sketches, pinout suggestions, or existing prototypes/schematics below!
  2. You are welcome to design different form factors (e.g., compact stacked backpack, horizontal handheld, desktop dock) as separate community hardware variants.
  3. Submit your design files via Pull Request under the /hardware directory, including:
    • Native CAD source files (EasyEDA, KiCad, etc.)
    • Export-ready Gerber ZIP archives
    • Bill of Materials (BOM)
    • Brief assembly and soldering notes

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions