ESP32-S3 Wi-Fi remote STM32 flashing and logging probe. Tscircuit remains the declarative source for the schematic, exact footprints, BOM, and reviewed placement.
Remote flash probe is an open-source printed circuit board by skywalker0507, from the skywalker0507/remote-flash-probe-tscircuit repository on GitHub. It is a 4-layer board of 92 × 48 mm with 70 parts on 48 nets, routed with 501 tracks and 104 vias.
It is built around the ESP32-S3-WROOM-1-N16R8, USBLC6-2SC6 and 2N7002LT1G, with the AO3400A, AO3401A and LTST-C190KGKT among its other parts. Its parts include 22 resistors, 17 diodes, 9 capacitors, 5 ICs and 5 transistors. It belongs with the sensors and measurement boards and the ESP32 boards of this library.
ESP32-S3 Wi-Fi remote STM32 flashing and logging probe. Tscircuit remains the
declarative source for the schematic, exact footprints, BOM, and reviewed
placement. Phase 3 routing is maintained in the KiCad project under kicad/.
Target compatibility
The first hardware revision supports self-powered 3.3 V targets only:
VTREF_IN must be within 3.0 V to 3.6 V. VTREF is a sense/reference input and
never powers the target. TMUX1574 is a bidirectional switch, not a level
translator; 1.8 V and 5 V targets are not supported.
Firmware must leave GPIO9 TARGET_ENABLE low until VTREF has passed an ADC
threshold, hysteresis, and debounce check. Hardware Q4 inverts this high-active
control. A target-powered TLV803EA26RDBZR supervisor and series AO3400A add an
independent interlock: below 2.64 V, firmware cannot pull TMUX1574 /EN low.
The board uses a 92 mm × 48 mm long-form outline. USB-C enters from
the left; the exact SM08B-GHS-TB(LF)(SN) JST-GH connector exits horizontally
through the right edge.
J2 and J3 are alternate connectors for the same target nets. Use exactly one at
a time; never connect two powered targets.
Commands
powershell
npm ci
npm run verify
npm run preview
npm run check:phase3
npm run fab:jlcpcb
npm run preview generates the schematic, local static viewer, and clean
dist/index/pcb.svg / pcb.png (also copied as pcb-clean.*). The clean PCB view hides
fabrication/package annotations, retains real designators and functional
silkscreen, and automatically moves designators away from pads. The unfiltered
renderer output is retained as pcb-debug.svg / pcb-debug.png, and raw Circuit
JSON is preserved for footprint diagnostics.
Phase 3 routing state
The canonical tscircuit board intentionally remains routing-disabled so that a
rebuild cannot replace controlled copper. The routed four-layer working board is
kicad/remote-flash-probe.kicad_pcb:
F.Cu: components, USB/buck critical routes, and local signals.
In1.Cu: uninterrupted primary GND plane; no signal tracks.
In2.Cu: power distribution and selected slow signals.
B.Cu: ordinary/slow signals plus GND fill.
npm run check:phase3 runs KiCad DRC and verifies the layer policy, keepouts,
target connector maps, GND stitching, critical locked routes, and absence of
fabrication outputs. Five connectivity diagnostics are intentionally classified:
two are KiCad zone-graph reports between the In1/B GND fills, which are joined
by 50 through GND vias, and three describe the four mounting tabs of J1's one
piece metal USB shield. There are no signal clearance, short, crossing,
dangling, isolated-copper, or starved-thermal errors.
Phase 4 prototype package
The reviewed prototype board uses the JLCPCB JLC04161H-3313 four-layer stackup,
ENIG, and epoxy-filled/capped via-in-pad for the exact USB4105 footprint. The
F.Cu USB pair is specified as 90 ohm differential over the uninterrupted In1
GND plane.
npm run fab:jlcpcb regenerates and audits the bare-board upload archive at
dist/fab/jlcpcb/remote-flash-probe-rev-a-gerbers.zip. It does not upload or
order anything. See docs/jlcpcb-order-guide.md
before requesting a quote.
Mechanical enclosure/STEP sign-off is intentionally deferred for the open-board
prototype. Target-off leakage measurement is deferred until assembled hardware
exists, but it remains a mandatory gate before unattended deployment.
A compact, tool-neutral handoff for a clean atopile comparison is available at
handoff/atopile/README.md. It contains the exact
hardware specification, structured pin/board data, BOM, acceptance gates,
bootstrap prompt and comparison scorecard without the old autorouting history.
A reproducible, audit-first PCB workflow for Codex. Reviewed atopile source is the electrical authority, KiCad is the physical authority and independent validator, and KiCadRoutingTools (KRT) creates isolated routing…
Open source flight controller for FPV drones. Includes two complete hardware designs (kicad) with production files. Will include custom firmware (bare-metal cpp). In progress :-)
. ├─ 3D # STEP 3D model export ├─ Images # Pictures and renders │ ├─ kibotresources # External resources for KiBot │ ├─ colors # Color theme for KiCad │ ├─ fonts # Fonts used in the project │ ├─ scripts # External…
It measures 92 × 48 mm and has 4 copper layers, 1.6 mm thick.
What parts does the Remote flash probe use?
70 parts, built around the ESP32-S3-WROOM-1-N16R8, USBLC6-2SC6, 2N7002LT1G and AO3400A. 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 Remote flash probe KiCad files?
From the skywalker0507/remote-flash-probe-tscircuit repository on GitHub, at the commit this page was made from: the board is kicad/remote-flash-probe.kicad_pcb and its schematic kicad/remote-flash-probe.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Can I use the Remote flash probe design in my own project?
Its repository states no licence, so its author keeps all rights: ask skywalker0507 before reusing the design.