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

AMOLED Module Selection
Recommendation
Primary: Tailor Pixels TOH204XVT-01CG
This is the best exact match for Bandido and should be the schematic design target, subject to written confirmation of connector pitch, mating connector, production availability, and initialization package.
Primary FPC pinout: 31 contacts

Table


PinSignalBandido use
1GNDGround
2TP_INTTouch interrupt / wake
3TP_RSTTouch reset
4TP_SDAI2C SDA
5TP_SCLI2C SCL
6TP_3.3VTouch supply, 2.8–3.3 V
7GNDGround
8IOVCCDisplay logic supply, 1.8–3.3 V; use 3.3 V if vendor confirms QSPI timing
9VCIVendor says leave open if unused; clarify before release
10VBATDisplay/SIBO power, use documented 3.7–4.5 V operating range
11VCL_ENLeave open if unused; confirm
12GNDGround
13MTP_PWRProgramming only; leave open or tie as vendor directs
14RESRTActive-low display reset
15CSXQSPI chip select
16SDI/RDXQSPI D0 / serial data
17DCXCommand/data for non-QSPI modes; route/test or follow vendor QSPI guidance
18WRX/SCLQSPI clock
19D(1)QSPI D3
20D(0)QSPI D2
21TETearing-effect synchronization output
22GNDGround
23–30MIPI lanes/clockNo-connect in QSPI design, per confirmed vendor rules
31GNDGround
The datasheet's naming is unusual: pins 16, 19, and 20 must be mapped against the vendor QSPI example to establish D0–D3 unambiguously before schematic release. Do not infer the fourth QSPI data path solely from the abbreviated table.
Mandatory vendor clarifications before PCB commitment
  1. FPC contact pitch and exact recommended mating connector MPN.
  2. Complete QSPI signal map for all four data lines and required IM/interface-selection state.
  3. Production initialization command table/source code for this exact panel revision.
  4. CST820 7-bit I2C address and reset/interrupt timing.
  5. Exact assembly Z thickness and cover-glass datum.
  6. VBAT operating maximum discrepancy: interface table says 4.5 V while an electrical table says 5.5 V maximum.
  7. Standby/sleep leakage and power-off backfeed limits.
  8. Minimum order quantity, sample revision control, lead time, lifecycle, and second-source policy.
Backup: Tailor Pixels TOH206BVT-01CG
This is mechanically attractive but is a weaker electrical match because the available drawing specifies conventional SPI and a 1.8 V I/O rail rather than confirmed QSPI at 3.3 V.
Why it is backup only
  • 410 × 502 increases frame transfer bandwidth by roughly 25% over 368 × 448.
  • Available documentation exposes SPI_MOSI/MISO rather than a confirmed four-data-line QSPI mode.
  • 1.8 V IOVCC likely requires level translation from ESP32-S3.
  • Power/current data is absent.
  • The 30-contact 0.35 mm board-to-board connector is less prototype-friendly than a conventional FPC connector.
Rejected Candidates
  • TT178AMC48C: only 1.78 inch, 350 nits, smaller 28.7 × 34.94 mm active area, incomplete public pinout.
  • Waveshare 1.8-inch AMOLED development-board panel: excellent firmware reference for CO5300/CST820 QSPI, but 350 nits and no independently documented raw-panel MPN/pinout.
  • TOQ206XVT-01: well-documented 2.06-inch 410 × 502 bare AMOLED with QSPI/MIPI, but it is not the exact touch/cover-glass module and requires separate touch/mechanical integration.
  • M5Stack StopWatch panel: useful software reference, but it is a 1.75-inch round 466 × 466 module and M5Stack does not publish an exact raw display module MPN.
Decision
Use TOH204XVT-01CG as the exact Bandido display target. It most closely matches the requested dimensions, 368 × 448 software architecture, high-brightness requirement, QSPI interface, integrated CST820 touch, and exposed black cover-glass aesthetic. The remaining questions are supplier-controlled production details, not a need to select a different display class.
  • Recommendation

  • Primary: Tailor Pixels TOH204XVT-01CG

  • Primary FPC pinout: 31 contacts

  • Mandatory vendor clarifications before PCB commitment

  • Backup: Tailor Pixels TOH206BVT-01CG

  • Why it is backup only

  • Rejected Candidates

  • Decision