USB-C WiFi BLE Sensor Node Design
Thought for 15 sec
I’ll set up placement for a medium-density board: first I’ll verify the current board size/stackup, resize if it is still default or unsuitable, then place by functional block with the ESP32 antenna at the board edge and run a DRC check after placement.
Thought for 9 sec
I’ll pause placement and run the DRC airwire check now, then summarize the remaining unrouted connections by net/component so we can decide what to route next.
Worked for 30 sec
DRC airwire check found 57 unrouted airwires.
Main unrouted groups:
- BUCK_SW / 3.3 V buck area: U2 SW/BST/FB, L1, C4/C5/C6/C7/C8/C10
- 3V3 rail: U2, U3, U4, decoupling caps, I2C pull-ups, boot/strap/fault pull-ups
- VBUS_RAW / VBUS_PROT: J1, D1, U1, C1/C2/C3, U2 VIN/EN
- USB-C / USB data: CC1/CC2, D+/D− through U5 to ESP32-C3
- ESP32 support: EN/reset, BOOT, GPIO2 strap, status LED, eFuse FAULT
- GND stitching/returns: several GND-related airwires remain, including one stitching via connection
Board status:
- Components are already placed on the top layer.
- Board is currently 160 × 100 mm, 4-layer, with very low density (~3.7% component fill), so routing space is generous.
Next step should be routing, but per checkpoint I’ll wait for your approval before running auto-route.
Route buck loop
List airwires
Separate DRC issues
Route USB pair
Add stitching vias
