AI Availability Inquiry

I found the GND-related airwires: they are from existing GND stitch vias to C10:P2 and U1:GND. I’m going to try routing those two short connections directly to the nearby stitch vias rather than doing broad re-routing.
I hit a schematic-net artifact while verifying the GND airwires, so I’m rolling back only the subsequent failed RUN-net repair attempts to avoid leaving RUN tied to GND. The GND via/tie work completed before those attempts will be preserved.
I added two GND drop connections into the Mid-Layer 2 plane path: one near C10:P2 and one near U1 exposed GND, reducing airwire count from 29 → 27.
Open items:
  • While verifying, a schematic net artifact caused RUN/reset pins to appear tied to GND; I attempted rollback, but the history revert failed with a platform PersistError.
  • I escalated this internally. Please avoid manufacturing/export until the RUN vs GND net state is reviewed/restored.
Suggested next steps:
  1. Restore to the commit before my RUN-net repair attempts, or contact Flux support: https://docs.flux.ai/Introduction/getting-support
  2. Re-check SW_RESET, U1:RUN, R_RUN:P1, C_RUN:P1, and J7:6.
  3. Re-run ERC/airwires after restoration.
Restore and verify
Fix RUN net
Inspect bad commits
Run ERC airwires
Remove added vias
J5
D_USB
U3
J_USB
U1
C14
Capacitance
10µF
C16
Capacitance
100nF
C19
Capacitance
100nF
C20
Capacitance
100nF
C6
Capacitance
100nF
C12
Capacitance
18pF
C18
Capacitance
100nF
C15
Capacitance
10µF
C10
Capacitance
100nF
C3
Capacitance
100nF
C17
Capacitance
100nF
C4
Capacitance
100nF
C13
Capacitance
10µF
C8
Capacitance
100nF
C_XIN
Capacitance
18pF
C1
Capacitance
100nF
C_RS232_A1
Capacitance
100nF
C_RUN
Capacitance
100nF
C2
Capacitance
100nF
C7
Capacitance
100nF
C9
Capacitance
100nF
C_LDO_IN
Capacitance
10µF
C11
Capacitance
100nF
C21
Capacitance
100nF
C22
Capacitance
100nF
C5
Capacitance
100nF
C_MCU1
Capacitance
100nF
R7
Resistance
1kΩ
J1
U_RS232_B
LED1
R6
Resistance
1kΩ
J_SRC_A
Resistance
U_RS232_A
R_ADC_LO_A
Resistance
10kΩ
R4
Resistance
1kΩ
R11
Resistance
10kΩ
R5
Resistance
1kΩ
R3
Resistance
1kΩ
R_RUN
Resistance
10kΩ
R_MODE_A
Resistance
10kΩ
R2
Resistance
1kΩ
R1
Resistance
1kΩ
R_CC2
Resistance
5.1kΩ
J_SRC_B
Resistance
LED_B_EGM
R_ADC_HI_A
Resistance
33kΩ
R_ADC_LO_B
Resistance
10kΩ
R_FB_HI
Resistance
1MΩ
J2
R8
Resistance
1kΩ
R9
Resistance
1kΩ
LED_A_EGM
R_ADC_HI_B
Resistance
33kΩ
R_FB_LO
Resistance
158kΩ
R_LED1
Resistance
1kΩ
R10
Resistance
1kΩ
LED_CABLE_A
R_CC1
Resistance
5.1kΩ
J7
LED_A_RX
TP2
TP5
U7_BUF
End of Life
U_OPTO_RX_A
LED_A_HOST
LED_HB
SW_SOFTBOOT
D_TVS_TX_B
LED_A_TX
D_TVS_RX_A
D3
TP4
U_OPTO_RX_B
TP1
U_OPTO_TX_B
LED_B_TX
D2
LED_B_HOST
D1
D_BOOST
TP3
SW_RESET
D_TVS_TX_A
D_TVS_RX_B
J6
U_OPTO_TX_A
LED_B_RX
U2
U4
Y1
L1
Inductance
10µH

Refine this doc
Ask about this doc
Board Bring-Up Plan — RP2350 Dual-Port SAS USB Interface
Prerequisites
  • Equipment: current-limited USB-C 5V source, multimeter, oscilloscope/logic analyzer, SWD debugger, SAS test fixture or loopback cable.
  • Initial current limit: 300mA from USB during first power-up.
  • Do not connect casino/EGM field wiring until +3V3, +5V, VCC10, USB enumeration, and GPIO idle states are verified.
1. Visual Inspection
  • Check RP2350A QFN orientation and solder bridges.
  • Verify USB-C connector tabs and shield soldering.
  • Verify Schottky diode orientations for D1/D2/D3 and D_BOOST.
  • Verify optocoupler and MAX3232 populate-option policy per port.
2. Power Rail Verification

Table


RailSourceExpectedMeasure AtPass Criteria
+5VUSB VBUS5.0VTP24.75–5.25V
+3V3AP2112K-3.33.3VTP13.23–3.37V
VCC10Cable VCC or boost OR~9–10VTP38.5–10.5V bench mode, cable VCC dominates when present
BOOST_SWTPS61040 switch nodeswitching waveformTP4No DC short; expected switching when boost active
GNDcommon return0VTP5Continuity to USB and port pin 1
3. Critical Signal Verification

Table


SignalNetExpected
RP2350 RUNRUNPulled high to +3V3; button pulls low
CrystalXIN/XOUT12MHz oscillation after boot
USBUSB_DP/USB_DMEnumerates as RP2350 USB device
QSPIQSPI_CS/SCK/SD0-3Flash activity during boot
4. Connector and Interface Tests
  • J1/J2 pinout: 1 GND, 2 RX board-listens, 3 TX board-transmits, 4 cable VCC.
  • Verify cable VCC dividers produce about 2.33V at ADC input for 10V cable VCC.
  • Verify cable-live LEDs light from cable VCC without USB power.
  • Verify source-mode jumpers J_SRC_A/J_SRC_B are DNP by default.
5. Programming and Debug
  • Connect SWD to J7: SWDIO, SWCLK, RUN/reset, +3V3 sense, and GND.
  • Confirm target detect, flash test firmware, then verify USB enumeration.
6. Functional Validation

Table


TestExpected Result
Heartbeat GPIO251Hz blink on LED_HB
Port A TX/RX PIO9-bit SAS waveform on logic analyzer header J6
Port B TX/RX PIOIndependent 9-bit SAS waveform on J6
Mode strapsOpen = host default; grounded = EGM default
Monitor mode indicationBoth HOST and EGM LEDs lit
Open Items
  • ERC currently reports unresolved floating pins from support passives, unused MAX3232 channels, headers, and incomplete indicator/charge-pump wiring; resolve before fabrication.
  • Confirm exact Phoenix terminal block MPN or approve the 4-position 3.5mm TE-compatible substitute footprint.
  • Prerequisites

  • 1. Visual Inspection

  • 2. Power Rail Verification

  • 3. Critical Signal Verification

  • 4. Connector and Interface Tests

  • 5. Programming and Debug

  • 6. Functional Validation

  • Open Items

Documents

  • Board Bring-Up Plan — RP2350 Dual-Port SAS USB Interface

  • Project Specification — RP2350 Dual-Port SAS USB Interface

Assets

Assets are files uploaded to this project which can be used in various ways.

RP2350 Dual-Port SAS USB Interface thumbnail
USB-C powered RP2350 dual-port SAS interface board with opto-isolated current-loop and RS-232 populate-option front-ends.

Properties

Properties describe core aspects of the project.

Pricing & Availability

Distributor

Qty 1

Arrow

$5.86–$13.80

Digi-Key

$4.30–$5.26

HQonline

$4.28–$4.75

LCSC

$16.70–$18.38

Mouser

$16.41–$17.93

TME

$9.32

Verical

$9.50–$14.99

Controls