Resolving Copper DRC Errors

I can’t cancel that server-side auto-layout job from the chat tools. You’ll need to discard it manually in the Flux UI job/auto-layout panel.
Once it is cleared, send:
rerun focused route
Then I’ll run exactly:
  1. one routing attempt
  2. one DRC count check
  3. stop immediately.
rerun focused route
I’ll run exactly one routing attempt, then one DRC count check, and stop.
Routing attempt failed: the same stuck outOfCredit job is still active.
Final DRC count check: 130 items remain.
Inspect stuck job
Manual USB routing
Check USB placement
Generate Rev A docs
Review export readiness
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

34
New Comment

1
New Comment

34
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

34
New Comment

34
New Comment

1
New Comment

34
New Comment

1
New Comment

1
New Comment

1
New Comment

34
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

1
New Comment

34
New Comment

1
New Comment

1
New Comment

34
New Comment

1
New Comment

1
New Comment

34
New Comment

1
New Comment

34
New Comment

34
New Comment

34
New Comment

1
New Comment

1

Refine this doc
Ask about this doc
Project Specification — HyperPulse Blade 2
Overview
HyperPulse Blade 2 is an ultra-compact athletic performance wearable worn on the body during sport. The target PCB is 30 mm × 22 mm on a 4-layer stackup, but the layout goal is to reduce below 30 mm × 22 mm if legal DFM clearances allow.
Core Architecture
  • Primary processor: Nordic nRF5340 QFN-94 / 7 mm × 7 mm dual-core BLE SoC.
  • BLE RF path: external stub antenna through U.FL connector.
  • Sensors: ICM-42688-P IMU over SPI, MMC5983MA magnetometer over I2C, BMP390 pressure/temperature over I2C, MAX30102 heart-rate/SpO2 over I2C, u-blox MAX-M10S GPS over UART.
  • GPS RF path: external ceramic patch antenna through U.FL connector.
  • Power: 250 mAh single-cell LiPo, Qi wireless charging receiver, BQ25180 1S LiPo charger/power-path, 3.3 V LDO rail for MCU IO and sensors.
  • User interface: BQ25180 push-button wake/ship-mode control, BLE/status LED, and charge-status LED.
Requirements

Table


IDRequirementValue / Target
MECH-001Initial board size30 mm × 22 mm target ceiling
MECH-002Minimum size goalShrink below 30 mm × 22 mm if component fit and DFM clearances allow
MECH-003Component sidesPopulate both top and bottom layers to minimize area
PCB-001Layer count4 layers
PCB-002Board thicknessTarget 0.8 mm total PCB thickness
PCB-003Package strategySmallest available package for every component; QFN/LGA/CSP/BGA preferred; 0402/0201 passives preferred
PWR-001Battery1S LiPo, 250 mAh, 3.7 V nominal
PWR-002ChargingWireless Qi only, no USB port
PWR-003Power controlPhysical momentary button to BQ25180 PB/TS-MR function; firmware soft power control; no extra power IC
PWR-004Sleep current10 s hold enters ship mode
UI-002BLE/status LEDBlue indicator controlled by nRF5340 GPIO with ~2 mA resistor target
UI-003Charge LEDRed or red/green charge indicator driven by BQ25180 STAT/~INT-class output with ~2 mA resistor target
RF-001BLE antennaU.FL to external stub antenna
RF-002GPS antennaU.FL to external ceramic patch antenna
RF-003RF layoutMaintain BLE/GPS antenna separation, short 50 Ω RF launches, solid return path, and no noisy power routing under RF sections
OPT-001MAX30102 placementRequires optical window, skin-facing placement, light isolation from ambient and LEDs
DEC-001DecouplingRobust local decoupling on MCU, GPS, PMIC, and every sensor power rail
AREA-001Board-area goalMaximize sensor density per cubic millimeter
Placement Constraints to Carry into Layout
  • MAX30102 must be placed on the skin-facing side, aligned to the optical window, with mechanical light isolation/gasket around the LEDs/photodiode.
  • Power button must sit on a board edge, aligned to a pinhole or flexure in the enclosure.
  • Indicator LEDs must sit on the top-side board edge and align to small optical windows/light pipes.
  • GPS U.FL and antenna feed should be separated from the BLE U.FL/feed; avoid routing the two RF feeds in parallel and preserve 50 Ω controlled-impedance geometry.
  • GPS antenna should be kept away from the Qi receiver coil, high-current charging paths, and noisy digital clocks.
  • BLE antenna U.FL should be edge-accessible with a short RF path and keepout around the connector/launch.
  • IMU should be mechanically near the board/body reference center where possible, away from flexing edges and high-vibration connectors.
  • Magnetometer should be kept away from the Qi coil, battery current paths, inductors, magnets, and ferrous hardware.
  • Qi coil and BQ51013B receiver section need their own keepout/noise-control region away from GPS and magnetometer.
Size Bottlenecks / Alternatives to Evaluate

Table


ComponentBottleneckSmaller Alternative Path
nRF5340 QFN-94Unavoidable 7 mm × 7 mm primary ICNone per requirement
MAX-M10S~9.7 mm × 10.1 mm GNSS module dominates board areaEvaluate smaller GNSS modules or chipset-only design if schedule/RF validation allows
U.FL connectorsTwo coax connectors consume edge length/heightMHF4 connectors are smaller if antenna cable ecosystem can change
SKRPACE010 library footprintAvailable library footprint is ~4.2 mm × 3.2 mm, larger than requested 3.2 mm × 2.3 mmImport/create verified smaller tactile switch footprint if exact alternate is selected
Qi receiver coilCoil/mechanical stack dominates thickness and areaCustom thin flexible receiver coil may be required
0603 LEDs in current libraryExact 0402 color LED matches not foundImport/create verified 0402 LEDs from selected MPNs
Power Budget — Initial Sizing
Estimated active peaks are BLE/nRF5340 ~20 mA, GPS acquisition/tracking ~25–30 mA, MAX30102 LED pulses up to tens of mA depending LED current, IMU/magnetometer/barometer <5 mA combined, plus LDO/PMIC overhead. Size the 3.3 V LDO for at least 150 mA peak with low IQ suitable for <50 µA sleep.
Design Notes / Open Decisions
  • Final pin mapping should prioritize SPI for ICM-42688-P, shared I2C for MMC5983MA/BMP390/MAX30102, UART for MAX-M10S, and GPIO for BLE status LED.
  • Add SWD pads/test points despite no USB port, otherwise firmware bring-up is high risk.
  • Qi receiver coil geometry and placement will need mechanical integration and shielding review during layout.
  • Actual minimum board dimensions require placement feasibility after schematic wiring and footprint placement; preliminary bottleneck is MAX-M10S + nRF5340 + two U.FL connectors + Qi coil area.
  • Overview

  • Core Architecture

  • Requirements

  • Placement Constraints to Carry into Layout

  • Size Bottlenecks / Alternatives to Evaluate

  • Power Budget — Initial Sizing

  • Design Notes / Open Decisions

Documents

  • Project Specification — HyperPulse Blade 2

  • Firmware Starter — HyperPulse Blade 2

  • Board Bring-Up Plan — HyperPulse Blade 2

  • Regulatory and Risk Notes — HyperPulse Blade 2

  • BOM Update — RGB LED and Battery NTC Safety Add

  • Complete BOM — HyperPulse Blade 2

  • MacroFab Polarity and Orientation Review — HyperPulse Blade 2

Assets

No assets added.

HyperPulse Blade 2

HyperPulse Blade 2 thumbnail
Ultra-compact 30 mm × 22 mm, 4-layer wearable sports tracker using Nordic nRF5340 BLE 5.4, motion/environment/optical/GPS sensing, external U.FL antennas, 250 mAh LiPo battery, Qi wireless charging only, and sub-50 µA target sleep current.

Properties

30mm x 22mm 4-layer board; wireless Qi charging only; no USB; soft power control; target sleep current <50uA.

Battery

3.3

V

Wearable

Bluetooth LE

Pricing & Availability

Distributor

Qty 1

Arrow

$25.21–$35.39

Digi-Key

$35.73

HQonline

$13.71

LCSC

$65.07

Mouser

$52.64

TME

$9.29

Verical

$26.87–$68.21

Controls