Tethered Mini Drone Design


Routing preflight found C2 and D1 inside the bottom-left mounting-hole keepout. Routing cannot preserve both the approved placement and the required Ø8 mm mechanical clearance; moving those two parts is the recommended fix.
The autorouter connected 125 of 134 initial airwires, and surgical routing reduced the remainder to six. The remaining pins are physically blocked by the approved placement/existing copper, so further retries without changing placement or deleting working routes would not converge; I’m running the final DRC summary now.
Routing is substantially complete: 753 trace segments and 154 vias were added, with no overlapping-copper, via-in-pad, dangling-trace, or redundant-trace errors.
Open items
  • 6 airwires remain:
    • EFUSE_OVP: U2 OVP → R5
    • 3V3: U4 VOS → existing 3V3 via
    • Four ground-plane connections around U6, C13, and R3
  • These remained blocked after two targeted attempts; finishing them requires local copper rip-up and likely small placement adjustments.
  • Non-blocking placement advisories remain for five decoupling loops and the U3→L1 switch-path detour.
Suggested next steps
  1. Authorize surgical movement around U2/U4/U6 and local trace rip-up to clear the six airwires.
  2. Re-run full DRC and power-integrity checks.
  3. Reconcile the routed PCB against the frame and USB-C cable clearance.

Waiting for input


Board Bring-Up Plan
Safety Setup
  • No propellers fitted for electrical bring-up.
  • Use a current-limited dedicated USB-C PD source or bench setup that preserves correct USB-C negotiation.
  • Keep PA12 / motor-rail enable low until the protected input and 3.3 V rail are verified.
Test Points

Table


Test pointNet
TP1VBUS_RAW
TP29V_PROTECTED
TP34V_MOTOR
TP43V3
TP5GND
TP6MCU_NRST
TP7SWDIO
TP8SWCLK
TP9IMU_SCK
TP10MOTOR_RAIL_ENABLE
Staged Procedure
  1. Inspect polarity, solder bridges, exposed-pad joints, and USB-C shield/ground continuity.
  2. With power removed, measure resistance from VBUS_RAW, 9V_PROTECTED, 4V_MOTOR, and 3V3 to GND; investigate any low resistance.
  3. Apply USB default power with the motor rail disabled. Verify 3V3 regulation and stable NRST.
  4. Attach SWD and load firmware that leaves all motor PWM pins low and PA12 low.
  5. Verify HUSB238A communication, request 9 V, and confirm TP1 rises to the negotiated voltage.
  6. Confirm TP2 follows through the TPS25940, fault is inactive, and PA0 current telemetry is plausible.
  7. Verify IMU identity, SPI traffic at TP9, stationary acceleration magnitude, and gyro bias stability.
  8. Assert PA12 with no motors connected. Confirm TP3 is approximately 3.97 V and PB5 indicates power good.
  9. Connect one motor at a time without a propeller. Run a low-duty PWM sweep and inspect gate, drain, rail ripple, and fault behavior.
  10. Repeat for all four channels, then test controlled simultaneous loading while monitoring input current, converter temperature, cable droop, and PD stability.
  11. Fit propellers only on a guarded thrust stand. Characterize each motor/prop pair before any flight attempt.
Acceptance Gates
  • No unexpected motor twitch during reset, flashing, or PD renegotiation.
  • 3.3 V remains within tolerance during motor switching.
  • 9 V contract remains stable under the planned aggregate command ceiling.
  • Motor rail and protection parts pass a supervised two-minute thermal test.
  • Firmware disarms within one control cycle on each injected fault.
  • Safety Setup

  • Test Points

  • Staged Procedure

  • Acceptance Gates