Autoroute Project Setup

flux

I’ll preflight the board for routing readiness, start the autoroute if it passes, then review the routed board for remaining issues.

flux

Preflight passed, with warnings for a few blocked pins and overlapping same-net connector pins. I’m starting autoroute now; the blocked pins may remain unrouted afterward.

flux

Autoroute could not start because there’s already an active auto-layout job on this project with status outOfCredit.
Preflight did pass, but it reported likely routing issues on USER_BUTTON, UWB_SPI_CS, and UWB_SPI_MOSI due to blocked pins. To continue, discard or resolve the existing auto-layout job, then I can start the new autoroute.
P

phukovsky

Retry i've discarded

flux

I’ll retry the autoroute now that the previous job was discarded, then I’ll check the result for remaining routing issues.

flux

Retry still failed: the same auto-layout job is still blocking routing with status outOfCredit.
Board readiness check passes, but the autorouter won’t start until job auto-layout-94801d1c-2912-4886-839c-4ea71b110296 is fully cleared/discarded. Also note: preflight still warns that USER_BUTTON has a blocked pin and may remain unrouted even after autoroute starts.
Fix blocked pin
Run DRC instead
Check job clearing
Manual route key nets

Waiting for input

Sign up to send

Files

Schematic

Layout

3D View

Board Bring-Up Plan — UWB Wearable Tracking Tag
Prerequisites
  • Equipment: multimeter, current-limited bench supply, USB-C 5 V source/current meter, SWD programmer, oscilloscope or logic analyzer.
  • Firmware: see firmware starter once available.
  • Safety: use a protected 1S LiPo only; initial tests should use a current-limited supply instead of a battery.
1. Visual Inspection
  • Verify polarity/orientation for USB-C J1, LiPo connector J2, MCP73831 U3, TLV70033 U4, TPS22916 U5, DWM3000 UWB1, MDBT50Q U1, LIS2DW12 U2, LED1, and TPD4E02B04 D1.
  • Confirm DWM3000 and MDBT50Q antenna keepouts are clear before assembly approval.
  • Inspect fine-pitch module pads and USB-C pins for solder bridges.
2. Power Rail Verification

Table

RailSourceExpected VoltageMeasure AtCurrent LimitPass Criteria
VBUSUSB-C J15.0 VJ1 VBUS / U3 VCC100 mA first power4.75-5.25 V, no heating
VBATcharger BAT / J23.0-4.2 VJ2 P1 / U4 IN100 mA first powerTracks battery/supply input
3V3TLV70033 U4 OUT3.3 VU4 OUT / C4 P1100 mA first power3.2-3.4 V
UWB_3V3TPS22916 U5 VOUT0 V off, 3.3 V onU5 VOUT / UWB1 VDD pins250 mA when enabledOff in sleep, 3.2-3.4 V when enabled
Procedure:
  1. With no battery/USB, measure resistance from VBUS, VBAT, 3V3, and UWB_3V3 to GND.
  2. Apply 3.7 V current-limited supply to J2 and verify 3V3.
  3. Enable UWB_PWR_EN from firmware and verify UWB_3V3.
  4. Connect USB-C and verify charger behavior and VBAT charge voltage.
3. Critical Signals

Table

SignalNetExpected State
ResetNRF_RESETHigh during normal operation; pulled low by debugger reset
UWB power enableUWB_PWR_ENLow in sleep, high when ranging
UWB resetUWB_RSTNFirmware-controlled reset line
I2CI2C_SDA / I2C_SCLIdle high at 3.3 V
SPIUWB_SPI_SCK/MOSI/MISO/CS3.3 V logic during UWB transactions
Accelerometer interruptsACC_INT1 / ACC_INT2Motion-configured interrupt outputs
4. Programming and Debug

Table

InterfaceSignalsConnector
SWDSWDIO, SWDCLK, NRF_RESET, VTref, GNDJ3
USB deviceUSB_DP, USB_DN, VBUSJ1 to U1 module
Procedure:
  1. Connect SWD debugger to J3.
  2. Confirm target voltage is 3.3 V on VTref.
  3. Read nRF52840 device ID.
  4. Flash test firmware.
  5. Verify USB enumeration only after firmware enables USB stack.
5. Functional Validation

Table

TestComponentsExpected Result
I2C scanU1, U2LIS2DW12 responds at 0x18 because SA0 is tied low
Motion wakeU2 to U1ACC_INT1/ACC_INT2 toggles on motion after firmware config
UWB SPIU1 to UWB1Read DWM3000 device ID over SPI
UWB power gateU1, U5, UWB1UWB_3V3 toggles under firmware control
ButtonSW1 to U1USER_BUTTON reads low/high as pressed/released according to firmware pull configuration
LEDU1, R6, LED1STATUS_LED drives visible low-current blink
Battery ADCR7/R8 to U1BAT_ADC is approximately VBAT/2
Charge statusU3 to U1CHG_STAT reflects charge state from MCP73831 STAT output
Pass/Fail Summary

Table

SectionResultNotes
Visual Inspection[ ] Pass / [ ] Fail
Power Rails[ ] Pass / [ ] Fail
Programming[ ] Pass / [ ] Fail
Interfaces[ ] Pass / [ ] Fail
Functional Validation[ ] Pass / [ ] Fail
Board Status: [ ] Ready for deployment / [ ] Requires rework

  • Prerequisites

  • 1. Visual Inspection

  • 2. Power Rail Verification

  • 3. Critical Signals

  • 4. Programming and Debug

  • 5. Functional Validation

  • Pass/Fail Summary