BLE Wearable PCB Design

flux

Routing is blocked by a preflight error I can’t safely fix automatically: the router reports five P1 “components” still set to position:auto, but layout inspection shows P1 only as normal pads inside already-placed parts, not standalone components.
What I did:
  • Confirmed placement is still single-sided and clean.
  • Re-ran placement cleanup; it found no movable standalone P1 objects.
  • Re-ran router preflight; the same blocker remains.
  • Reported the likely router/preflight misclassification internally.
Open item:
  • Routing was not started, so no new DRC/JLCPCB counts are available yet. The blocker needs manual/platform resolution or a deeper cleanup of the affected library pad rules before auto-routing can run.
X

xhenium

J1 (the pogo connector) was rotated and no longer points to the top edge. Fix it:
rotate J1 so its cable/contact opening points in the +Y direction, i.e. toward
the TOP board edge (exits off the top edge, not into the board), and keep J1 on
the top edge.
Verify the other three connectors too:
  • J2 opening faces the BOTTOM edge
  • J3 opening faces the LEFT edge (270 deg)
  • J4 opening faces the RIGHT edge (90 deg)
    Report the final rotation (degrees) of J1, J2, J3, J4.

flux

Fixed the connector orientations and kept them on their assigned edges; no routing was performed.
Final rotations:
  • J1: 180° — opening toward top / +Y
  • J2: 0° — opening toward bottom / −Y
  • J3: 270° — opening toward left / −X
  • J4: 90° — opening toward right / +X
Fix routing blocker
Spread U1 area
Run connector DRC
Update placement notes
Try routing again
Sign up to send

Files

Schematic

Layout

3D View

Firmware Starter Notes
Target
  • Product: Luminous Cap BLE Wearable
  • MCU/module: Raytac MDBT42Q-512KV2, Nordic nRF52832-based BLE module
  • Supply net: 3V3
  • Ground: GND
  • Programming/debug: SWD only; USB intentionally not included
Initial hardware present
  • U1: MDBT42Q-512KV2
  • C1: 100 nF decoupling from 3V3 to GND
  • C2: 1 uF decoupling from 3V3 to GND
Firmware bring-up assumptions
  • Use Nordic nRF5 SDK or Zephyr/NCS depending on application needs.
  • Reserve SWDIO and SWDCLK for programming/debug header or pogo access.
  • P0.21/RESET is available as reset if configured and should be considered during SWD fixture design.
Open firmware-facing decisions
  • LED/driver pin allocation not assigned yet.
  • Rail-contact detection / onboard-energy measurement pins not assigned yet.
  • BLE advertising/service profile not defined yet.
  • Low-power sleep/wake behavior not defined yet.

  • Target

  • Initial hardware present

  • Firmware bring-up assumptions

  • Open firmware-facing decisions