ESP32-S3 LED Matrix Board


I’m sorry—you should not have been left waiting. I cannot view engineering’s response or ticket status from the internal feedback submission, so I have no confirmed outcome to report.
The routing bug remains the blocker recorded here: the existing auto-route job is stuck as outOfCredit, while attempting to resume it returns an internal error. Please escalate it through Contact Support, including:
  • Project: AMOLED Bandido
  • Failed job ID: auto-layout-a3644dbe-f17a-4b09-8b75-b4fd5c3f162f
  • Symptom: starting says a job already exists; resuming produces ResumeInternalError
  • Impact: 33 airwires remain, preventing the final STEP export
The project itself is intact; this is a routing-job/platform issue rather than lost design data.
Create a concise support-ticket summary with the job ID, errors, and project impact.
Subject: Auto-route job stuck and cannot resume — AMOLED Bandido
Project: AMOLED Bandido
URL: /bradbitler/amoled-bandido
Job ID: auto-layout-a3644dbe-f17a-4b09-8b75-b4fd5c3f162f
Issue: The auto-route job is stuck with status outOfCredit. Starting a new job fails because the existing job is still active. Resuming it returns FiberFailure / ResumeInternalError: Unable to resume auto-layout job.
Impact: The PCB has 33 remaining airwires. Other blocking DRC checks are clear, the 46 × 60 mm outline is closed, and component 3D models are present. The failure prevents routing completion, final DRC validation, and STEP export.
Please reset, repair, or make the existing routing job resumable without discarding completed routing.
Prepare support ticket
Document routing blocker
Export current STEP

Project Specification
Project Overview
  • Status: AMOLED architecture review; schematic migration not yet authorized.
  • Bandido is a compact ESP32-S3 AI companion with an exposed black AMOLED touchscreen in a textile/soft-touch body.
  • Target envelope: approximately 52 × 75 × 17 mm.
  • The former discrete RGB matrix, diffuser, central LED island, and touch ring are superseded.
Intended Use
  • All-day portable companion with short interactive sessions.
  • Character animation, eyes, expressions, waveforms, simple icons/text, touch, voice, motion, haptics, BLE, and duty-cycled Wi-Fi.
  • Primary AI runs through cloud services or a paired phone; local hardware provides UI, audio, sensing, connectivity, and lightweight DSP/wake-word support.
  • First integrated build target is 5–10 EVT units after display-module bench qualification.
What the Device Should Do
  • Render 30–60 FPS character animation on a 2.0–2.1 inch AMOLED.
  • Support capacitive touch, microphone capture, speaker playback, orientation/motion wake, refined haptics, and one wake-capable side action button.
  • Charge and operate through USB-C from a protected 600–800 mAh 1S Li-Po.
  • Sleep aggressively when inactive and share a hardware-abstraction/software architecture with the M5Stack development puck.
Main Features
  • ESP32-S3 module with 16 MB flash, 8 MB PSRAM, native USB, Wi-Fi, and BLE.
  • Replaceable FPC-connected AMOLED/touch module, preferably ~368 × 448, 600–800+ nit, QSPI, CO5300-class display controller, and CST820-class touch.
  • Audio codec plus efficient class-D speaker stage, low-power 6-axis IMU, and LRA haptics.
  • Charger with power path, protected cell, fuel gauge, battery-temperature provision, USB ESD, and switched peripheral rails.
System Architecture

Diagram


USB-C 5 V and native USB Charger and power path Protected node_1S Li-Po 600-800 mAh System rail 3.3 V buck-buck/boost logic rail Switched AMOLED rail or rails Switched audio power ESP32-S3 N16R8 module QSPI AMOLED via replaceable FPC Integrated capacitive touch Audio codec MEMS microphone Class-D amplifier Rear or side speaker BMI270-class IMU DRV2605L plus LRA Side action button Fuel gauge and battery temperature
Hardware Subsystems
Display and Touch
  • Preferred module class: 2.0–2.1 inch, ~368 × 448, QSPI AMOLED, integrated/bonded touch, exposed cover surface.
  • Required display signals: OLED_CS, OLED_SCK, OLED_D0–D3, OLED_TE, OLED_RST, power, grounds, and optional enable.
  • Touch signals: TOUCH_SDA, TOUCH_SCL, TOUCH_INT, TOUCH_RST.
  • Exact module MPN, FPC pinout, voltage domains, initialization commands, connector orientation, and lifecycle must be frozen before schematic capture.
  • Avoid MIPI-DSI-only panels unless ESP32-S3 is intentionally replaced.
Compute and Wireless
  • Preferred module: ESP32-S3-WROOM-1-N16R8 or pin-compatible approved variant.
  • Reserve native USB, boot/reset access, and valid states for GPIO0/GPIO45/GPIO46.
  • Do not allocate GPIO35–42 where occupied by module flash/Octal PSRAM.
  • Place module antenna at the top exterior edge with the complete manufacturer keepout clear of copper, battery foil, display metal, speaker magnet, haptic actuator, fasteners, and conductive textile.
Audio
  • Preferred architecture: ES8311-class low-power codec on I2S/I2C, analog MEMS microphone, and a separate efficient ~1 W class-D amplifier.
  • Validate codec/amp availability and noise performance before release; retain a digital-microphone plus I2S-amplifier fallback if codec sourcing or analog layout risk is unacceptable.
  • Provide a sealed speaker back volume, controlled vent, acoustic mesh, microphone gasket/channel, amplifier shutdown, and pop suppression.
Motion and Haptics
  • Preferred IMU: BMI270, with interrupt-based motion wake.
  • Preferred haptics: DRV2605L + compact LRA; ERM remains a lower-cost fallback.
  • Mechanically isolate the IMU and microphone from the actuator and speaker cavity.
Power
  • USB-C sink with native USB data, CC pull-downs, ESD, and source-current detection/limiting assumptions.
  • Preferred baseline: BQ25622-class charger/power path, protected 1S Li-Po, MAX17048/MAX17049-class gauge, and TPS63802-class 3.3 V buck-boost. Final selection requires a completed state-based load table and cell qualification.
  • Provide switched display and audio domains, ship mode/hard-off strategy, undervoltage and thermal lockouts, current/rail test points, and battery NTC provision.
Interfaces and Connections
  • QSPI AMOLED: 6 data/clock/select signals plus TE, reset, and optional enable.
  • I2C: touch, IMU, haptic driver, fuel gauge, charger controls, and codec control; confirm addresses and bus capacitance.
  • I2S: codec audio stream; optional second digital-audio path only if ESP32 peripheral allocation permits.
  • USB: native D+/D− with ESD and controlled routing.
  • GPIO: side button, wake interrupts, rail enables, display reset/TE, amplifier enable, and debug.
Power and Runtime Expectations
  • Target battery: 600–800 mAh, protected and documented for the selected charge rate.
  • Deep-sleep target at battery: <0.3 mA, stretch target <0.15 mA.
  • Connected idle target: 20–80 mA average, depending on BLE/Wi-Fi duty cycle.
  • Typical active interaction planning range: 0.8–2.0 W; short audio/Wi-Fi/display peaks may approach 3 W until measured.
  • A 700 mAh, 3.7 V cell stores ~2.6 Wh nominal. All-day use is plausible if the screen is off most of the time, Wi-Fi is duty-cycled, and active sessions remain short.
  • Regulator, charger, cell, connector, and thermal sizing must use measured peak/average loads and worst-case depleted-cell voltage.
Manufacturing and Assembly Expectations
  • Prefer one 4-layer main PCB plus a purchased display/touch assembly on replaceable FPC.
  • Consider 6 layers only if routing, return paths, EMC, or form-factor pressure justify it.
  • EVT enclosure: SLA/MJF/CNC with replaceable display adhesive frame and serviceable battery.
  • Include accessible programming and rail test points, serial-number traceability, and board-level display/touch/audio/RF test fixtures.
Firmware-Relevant Hardware Requirements
  • Bandido Runtime HAL: Display, Touch, Audio, Motion, Haptics, Power, Connectivity, and Character Engine.
  • UI/character code must not depend directly on puck versus custom display geometry.
  • ESP-IDF preferred; support PSRAM-backed assets/framebuffers, OTA, native USB recovery, deep sleep, wake sources, and power-domain sequencing.
Physical Design Expectations
  • Exposed glossy black display; textile or soft-touch material terminates cleanly at the display perimeter.
  • Landscape display orientation within a portrait body.
  • Top attachment hole, one side action button, USB-C, and rear/side speaker vent; no front physical buttons.
  • Freeze the exact display, battery, speaker, LRA, antenna keepout, and FPC bend before board outline and enclosure tooling.
Important Design Decisions
  • AMOLED replaces the complete discrete-RGB architecture.
  • ESP32-S3 N16R8 module and QSPI display preserve compatibility with the development puck.
  • One main PCB is preferred; a daughterboard is allowed only for a clear packaging advantage.
  • LRA haptics and codec-based audio are preferred for product quality, subject to EVT validation.
  • Existing 417-component RGB schematic is retained only as historical validation work until migration is approved.
Assumptions and Open Gates
  • No exact AMOLED MPN has yet been independently qualified; module purchase and bench validation are the first gate.
  • Display and battery pricing remain estimates until supplier RFQs and lifecycle evidence are obtained.
  • Final GPIO allocation waits for exact display FPC and ESP32 module confirmation.
  • Product is not waterproof in EVT.
Change Notes
  • Replaced textile-covered RGB matrix requirements with an exposed AMOLED touchscreen architecture.
  • Removed TLC59581, row switching, high-current LED rail, LED island, touch ring, diffuser, and display blanking requirements.
  • Added Bandido Runtime compatibility, codec-based audio direction, 600–800 mAh battery target, and one-main-PCB preference.
  • Project Overview

  • Intended Use

  • What the Device Should Do

  • Main Features

  • System Architecture

  • Hardware Subsystems

  • Display and Touch

  • Compute and Wireless

  • Audio

  • Motion and Haptics

  • Power

  • Interfaces and Connections

  • Power and Runtime Expectations

  • Manufacturing and Assembly Expectations

  • Firmware-Relevant Hardware Requirements

  • Physical Design Expectations

  • Important Design Decisions

  • Assumptions and Open Gates

  • Change Notes