Board Routing Complete

flux

Board routing is complete. All 29 airwires are resolved, including the two USB-C differential breakout stubs; final verification reports 0 airwires, 0 dangling traces, and no open routing DRC errors or warnings.
Suggested next steps
  1. Review USB differential-pair geometry and return path.
  2. Add or verify ground pours.
  3. Clean up silkscreen.
  4. Run manufacturing export checks.
B

brianbenchoff

are there netclasses for this board; when you route the USB_D-_CONN, it seems like that's not the right for a diff pair

flux

I’ll inspect the board’s net-class/impedance rules and the actual USB_D±_CONN routing to verify whether that segment is configured and routed as a differential pair.

flux

You’re correct. There are no USB-specific net classes; only global 0.15 mm routing/escape-width rules exist.
USB_D±_CONN were not recognized as a valid pair, so they were routed independently:
  • D−: top layer, no vias
  • D+: two vias and a Mid-Layer 1 segment
  • The router explicitly reported ROUTING_UNTWINNABLE_DIFFERENTIAL_PAIR
The proper fix is to explicitly pair both nets at schematic level with 90 Ω differential impedance, delete only their non-protected routing, then reroute them together on Top while preserving the protected connector breakout.
Fix USB pair routing
Review USB geometry
Configure all USB pairs
Add ground reference
Sign up to send

Files

Schematic

Layout

3D View

J1
U2
C2
Capacitance
100nF
C4
Capacitance
47pF
C3
Capacitance
100nF
C6
Capacitance
10nF
C5
Capacitance
47pF
C1
Capacitance
4.7uF
R3
Resistance
27Ω
U1
R4
Resistance
27Ω
FB1
R2
Resistance
5.1kΩ
J2
R1
Resistance
5.1kΩ
USB-C FTDI UART Adapter — Block Diagram
Text
USB-C 16-pin receptacle
  ├─ VBUS (all joined) ───────────────→ +5V USB power ─→ FTDI VCC
  ├─ GND (all joined) ────────────────→ GND
  ├─ CC1 ─→ 5.1 kΩ Rd ─→ GND
  ├─ CC2 ─→ 5.1 kΩ Rd ─→ GND
  └─ D+/D− (A/B duplicates joined) ─→ 2-channel low-C ESD ─→ FTDI USB D+/D−

FTDI USB-UART bridge
  ├─ 3V3OUT support/decoupling ─→ VCCIO (only if datasheet permits)
  ├─ TXD, RXD, RTS#, CTS# ─────────→ 1x6 UART header
  └─ GND, 3V3 ─────────────────────→ 1x6 UART header

Power tree: USB VBUS 5 V → FTDI VCC → internal 3.3 V output → VCCIO and header 3V3. No 5 V is exposed on the header.
Functional blocks and sourcing plan
  1. USB-C device interface and CC configuration — none / from scratch; no matching Flux reference project was found. Use a 16-contact USB 2.0 receptacle, duplicate D+/D− and power pins joined, independent 5.1 kΩ Rd.
  2. USB ESD protection — none / from scratch; no matching Flux reference project was found. Use a low-capacitance two-channel array between connector and FTDI.
  3. FTDI USB-to-UART core and power support — none / from scratch; no matching Flux reference project was found. Prefer a verified FT230X/FT231X family part and follow its datasheet application circuit.
  4. 3.3 V UART header — none / from scratch; no matching Flux reference project was found. Use a 1x6 header carrying GND, 3V3, TXD, RXD, RTS#, CTS#.
The schematic will be arranged left-to-right in this block order, with power and decoupling above/below the FTDI.

  • Functional blocks and sourcing plan