Fixing ERC/DRC Errors and Routing


Replacement/placement completed, but validation found two remaining blocker types: stale traces from the old footprints and U7 still has duplicate exposed-pad footprint geometry. I’m correcting U7 with a different clean same-function BQ24074 package entry, then deleting stale traces before rechecking.
Pre-routing check is now clean, so I’m spending the routing ACUs now. I also removed the last stale trace first to avoid wasting a routing pass.
Blocked: the project ran out of ACUs during the auto-route job, so I can’t continue tool work in this run.
Completed so far:
  • Replaced the problematic footprint components:
    • U1 ESP32-S3 module
    • U3 MAX-M10S GNSS
    • U7 BQ24074 charger/power path
    • U8 TPS63070 buck-boost regulator
  • Restored their original functional connections: USB, GPS UART, I2C, I2S mic, battery charger, SYS/3V3 power, boot/reset.
  • Re-placed the replacements on the PCB.
  • Removed stale/dangling traces from the old footprints.
  • Fixed the SYS rail reconnection for C12/R15.
  • Reduced small-pin routing width for U8 BB_L1 and BB_VAUX.
  • Got the board to pass the pre-routing feasibility check before routing was attempted.
Remaining:
  • Add ACUs, then re-run routing.
  • The paused route reported USB differential pair routing stalled, so after ACUs are available the next step is to adjust/route USB_DP/USB_DN specifically, then run final ERC/DRC/airwire checks.
  • U3:VIO_SEL may still appear as a false ERC issue; per MAX-M10S datasheet it should be left open for 3.3 V V_IO operation.
Route USB first
Verify VIO_SEL
Run final checks
Inspect footprints

Waiting for input


Board Bring-Up Plan
Preconditions
  • Use a current-limited bench supply, DMM, oscilloscope, USB data cable, known-good single-cell LiPo or battery simulator, U.FL GNSS antenna, BLE phone, and ESD controls.
  • Inspect polarity/orientation and soldering at J1 USB-C, J2 LiPo, J3 U.FL, U7 BQ24074, U8 TPS63070, U9 TPS71518, U1 and sensors.
  • Prototype status: the live layout now has zero airwires and zero dangling traces, with no reported missing-footprint, invalid-layer, overlapping different-net copper, or unintended outside-board blockers. This is manufacturing-data readiness only; physical first-spin validation still requires every test below.
Power-off checks

Table


CheckMethodPass
GND shortsResistance from USB_VBUS_RAW, VBUS, BAT, SYS, 3V3, 1V8_U2 to GNDNo hard short; investigate any stable reading below 10 Ω before power
J2 polarityVerify J2 pin 1=BAT, pin 2=GND against actual battery harnessCorrect; never assume JST cable color/polarity
ButtonsContinuity while pressedSW1 pulls ESP_EN to GND; SW2 pulls ESP_BOOT/GPIO0 to GND
RF connectorMicroscope/continuityJ3 center only to GPS_RF_50OHM; shell to GND; no center-shell short
Staged power bring-up
  1. USB input only, battery disconnected. Set 5.0 V source, 100 mA limit initially; connect at J1.
    • USB_VBUS_RAW: 4.75–5.25 V.
    • VBUS after F1: within 0.25 V of raw at light load.
    • No rapid heating; raise limit gradually only if current behavior is understood.
  2. Charger/power path. Measure U7 input and SYS.
    • SYS: expected roughly battery/system power-path range, normally about 3.5–4.4 V with USB present; must remain below 4.5 V.
    • Verify U7 CE is low/enabled. EN1 is high and EN2 is low, selecting the BQ24074 USB500 500 mA input-current limit. R8 is populated for optional external-limit mode but is inactive in this strap state. Do not test full charge current until battery suitability and thermal setup are approved.
  3. Main regulator. Measure 3V3 at U8 output and at U1/sensors.
    • Pass: 3.20–3.40 V steady at idle; no sustained oscillation; ripple target 70 °C during bench testing.
Reset, boot and firmware flashing
  1. Confirm ESP_EN is high near 3.3 V. Press SW1: it must go low and the MCU must reset.
  2. Confirm ESP_BOOT is high normally. Hold SW2, tap SW1, release SW1 then SW2 to enter ROM download mode.
  3. Connect J1 to a USB host; verify native USB D-/D+ enumeration on GPIO19/20.
  4. Flash the released PlatformIO image, record binary hash, board serial and result. Firmware flashing is mandatory post-assembly.
  5. Pass: USB CDC shows the boot log at 115200 baud and repeated resets are clean.
Documented ERC exception
U3 MAX-M10S VIO_SEL is intentionally left open because V_IO is 3.3 V. The u-blox datasheet requires open for 3.3 V and GND only for 1.8 V. Do not connect this pin merely to clear the ERC warning.
Digital interfaces

Table


InterfaceActual nets/endpointsTestPass
I2CGPIO8 I2C_SDA, GPIO9 I2C_SCL; U2/U4/U5Scan at 100 kHz first, then 400 kHzACK at 0x57 MAX30102, 0x48 TMP117, 0x68 BMI270; high ≈3.3 V; no stuck-low line
MAX30102HR_INT GPIO10; VDD=1V8_U2, VLED+=3V3Read ID/FIFO; exercise LED at conservative currentSamples change with optical target; INT toggles; no overheating
TMP117Shared I2CCompare to calibrated reference after thermal settlingWithin project acceptance limit; draft target ±0.5 °C near room temperature
BMI270Shared I2C; IMU_INT GPIO11Read chip ID 0x24; load released Bosch config; move boardPlausible accel/gyro response and INT1 activity
GNSSU3 TXD→GPIO18, GPIO17→U3 RXD; J3 RFCheck 9600 8N1, attach correct active/passive antenna, test outdoorsValid NMEA/UBX stream and position fix; record TTFF and satellites
I2S micGPIO4 BCLK, GPIO5 WS, GPIO6 DATA; SEL=GND/leftScope clocks, capture 16 kHz/32-bit slots, apply soundBCLK/WS valid; nonzero level rises with sound, no clipping at normal level
BLEU1 ESP32-S3 moduleScan/connect/subscribe from phonePetCollar advertises and JSON telemetry notification updates at 1 Hz
Charging validation
  • Use only an approved protected 1S LiPo with known capacity, maximum charge rate, polarity, and preferably a pack NTC.
  • Measure charge current at low state of charge; it must not exceed the lower of battery rating, USB/source capability, and configured limit.
  • Verify transition to taper/termination near 4.2 V and safety timer behavior using a battery simulator where practical.
  • The present U7 TS network uses a fixed 10 kΩ valid-temperature resistor; it does not measure cell temperature. This is not acceptable as the sole thermal safeguard for unattended production charging without a documented battery/enclosure safety justification or an NTC-capable revision.
Final pass/fail record
A board passes bring-up only when all rails, current limits, USB flashing, buttons, I2C IDs, GNSS, microphone, BLE, and battery transitions pass; no unexplained heating occurs; firmware ID/hash is recorded; and final PCB DRC/footprint signoff is attached. Log measured values, instrument IDs, operator, date, board serial and failures. Failed units must be quarantined and dispositioned, not reworked without traceability.
  • Preconditions

  • Power-off checks

  • Staged power bring-up

  • Reset, boot and firmware flashing

  • Documented ERC exception

  • Digital interfaces

  • Charging validation

  • Final pass/fail record