AI Availability Inquiry


An old out-of-credit routing job is blocking a new route run, so I’m discarding that stale job and starting a fresh route.
Auto-route reduced airwires from 53 to 9, but DRC still reports 9 airwires plus copper/trace issues. I’m running one more routing pass to try to finish the remaining connections.
Routing improved, but RUN/GND verification found RUN split and some reset pins still on GND. I’m correcting that now before wrapping up.
I re-routed using the active 6-layer stackup: fixed the auto-positioned TP pad blockers, reduced trace width for U1 fine-pitch routing, cancelled the stale out-of-credit route job, and ran two routing passes. Airwires improved from 53 → 9, but the router left 9 airwires, 3 overlapping-copper errors, and 22 dangling-trace warnings.
Open items:
  • RUN/GND connectivity is not clean: verification shows the RUN-side reset pins are still in a separate 12-pin net labeled GND despite repeated attempts to move them to RUN. I escalated this as a platform/data-repair issue.
  • Remaining DRC: 9 airwires, 3 overlapping-copper errors, 22 dangling-trace warnings.
  • Auto-route preflight still reports a duplicate-via cleanup warning.
Suggested next steps:
  1. Repair the RUN net manually or via project history/data repair before manufacturing.
  2. Re-run ERC on SW_RESET, U1:RUN, R_RUN:P1, C_RUN:P1, and J7:6.
  3. Manually clean the 3 overlapping-copper errors, then route the final 9 airwires.
Fix RUN, copper, DRC
Fix RUN net
Inspect commit diff
Clean DRC errors
Manual final routing

Schematic of RP2350 Dual-Port SAS USB Interface
R13
Resistance
330Ω

RP2350 Dual-Port SAS USB Interface

RP2350 Dual-Port SAS USB Interface thumbnail