USB-C Power Hub Design


Worked for 7 mins 5 sec
Referenced guidance.
1/3 Inspect current PCB placement, connectivity, and board constraints

Inspect current PCB placement, connectivity, and board constraints

Re-place components into three logical USB-C functional clusters

Reroute affected nets and verify DRC/airwires

Thought for 22 sec — Clarifying delegation needs
Thought for 3 sec — Planning execution steps
Referenced guidance.
Thought for 9 sec
Checking routing progress.
Getting a layout overview.
Looking at the board.
Reading schematic details.
Thought for 4 sec — Clarifying functional group details
Reading schematic details.
Reading schematic details.
Reading schematic details.
Reading schematic details.
Reading schematic details.
Thought for 27 sec
Moving footprints.
Moving footprints.
Moving footprints.
Moving footprints.
Thought for 4 sec
Moving footprints.
Moving footprints.
Thought for 4 sec
Moving footprints.
Thought for 3 sec — Planning inspection of stats
Moving footprints.
Thought for 9 sec — Figuring out connections and positions
Moving footprints.
Thought for 5 sec — Evaluating constraints and layout
Moving footprints.
Thought for 14 sec — Evaluating connector design
Moving footprints.
Thought for 35 sec
Moving footprints.
Moving footprints.
Thought for 3 sec
Moving footprints.
Thought for 11 sec — Determining movement summary
Moving footprints.
Thought for 1 min 5 sec — Rearranging layout elements
Moving footprints.
Thought for a moment — Evaluating coordinates and constraints
Moving footprints.
Moving footprints.
Thought for 5 sec — Fixing overlaps
Moving footprints.
Thought for 41 sec — Adjusting placement and constraints
Moving footprints.
Moving footprints.
Thought for 26 sec
Moving footprints.
Moving footprints.
Thought for 25 sec
Moving footprints.
Moving footprints.
Thought for 14 sec
Moving footprints.
Moving footprints.
Thought for 14 sec
Moving footprints.
Moving footprints.
Thought for a moment

Flux stopped


Project Specification
Project Overview
First-pass schematic for a USB-C PD power-distribution hub. Status: Draft / engineering review required.
Intended Use
One upstream USB-C PD supply powers a Raspberry Pi 5 and a USB-C display through two independently negotiated downstream source ports.
What the Device Should Do
  • Negotiate an upstream target of 20 V/5 A (100 W), requiring an e-marked 5 A cable.
  • Port A advertises 5.1 V at up to 5 A (27 W class) for Raspberry Pi 5; require a 5 A e-marked cable for >3 A.
  • Port B advertises SPR fixed PDOs 5, 9, 12, 15, and 20 V, capped at 3 A and 60 W.
  • Dynamically allocate and shed load so output power plus losses and controls remain within the active upstream contract.
  • Never claim both outputs can exceed the negotiated upstream budget.
Main Features
Independent downstream PD negotiation; input/output protection; current sensing; programmable display rail; dedicated high-current Pi buck; firmware-controlled policy and fault handling.
System Architecture
See the Block Diagram project file.
Hardware Subsystems
  1. Upstream Type-C receptacle, ESD/TVS, fuse/eFuse, sink PD controller and protected 20 V bus.
  2. Port A 20 V-to-5.1 V >=5 A buck, source switch, current sense, discharge, Type-C source controller and receptacle.
  3. Port B programmable buck/buck-boost, source switch, current sense, discharge, Type-C source/DRP controller and receptacle.
  4. MCU/policy controller with controller buses, telemetry, enables, interrupts and fault inputs.
  5. Auxiliary logic supply and decoupling.
Interfaces and Connections
USB-C CC1/CC2 and VBUS on all ports; controller-to-MCU I2C/SPI/GPIO as supported by selected parts; analog/current telemetry; firmware-controlled converter setpoint and source-enable signals.
Power and Runtime Expectations
Externally powered; no battery. Full-load operation assumes a valid 100 W upstream contract and 5 A cable.
Power Tree and Power Budget
At 90% conservative conversion efficiency: Pi input allocation 25.5/0.90 = 28.33 W; display input allocation 60/0.90 = 66.67 W; controls = 2 W; total = 97.0 W. Margin at 100 W is only 3.0 W. Firmware must reserve margin and reduce/deny Port B allocation when the upstream contract is lower or measured input approaches limits.
Manufacturing and Assembly Expectations
Production-intent SMD architecture. High-current/thermal layout, connector current rating, eFuse SOA, converter thermals, and USB PD compliance require later PCB and qualified review. PCB layout is explicitly out of scope for this pass.
Firmware-Relevant Hardware Requirements
Firmware reads active upstream contract and telemetry, programs downstream PDO availability, sequences converters and source switches, enforces cable-current limits, handles faults/discharge, and performs deterministic load shedding with Pi priority.
Physical Design Expectations
Connectors accessible at board edges; high-current paths short; separate noisy converter regions; thermal copper and airflow to be determined during layout.
Important Design Decisions
Port A has priority and is dedicated to Pi 5. Port B allocation is dynamic. A controller-plus-MCU architecture is acceptable if an autonomous multi-port power-sharing controller is unavailable.
Assumptions
Upstream source supports 20 V/5 A; cables claiming 5 A are electronically marked; display accepts at least one advertised fixed PDO; no USB data routing is required.
Change Notes
Initial requirements and conservative power budget captured. First-pass schematic instantiated with three real GCT USB4105-GF-A 5 A receptacles, STUSB4500 sink control, dual STUSB4710 source controllers, STM32G071 policy MCU, protected VBUS paths, Pi buck, provisional display converter, 3.3 V housekeeping buck, and SWD.
Provisional / Validation Required
  • STUSB4710 library entries lack attached datasheets; source-controller pin usage and PDO-selection wiring require validation against the official ST document.
  • Display conversion is provisionally represented by ST1S14PHR. It cannot produce a regulated 20 V output from a nominal 20 V bus and is not a complete digitally programmable multi-PDO implementation. A buck-boost or direct 20 V bypass plus selectable lower-voltage converter is required in revision 2.
  • TCPP03-M20 devices are instantiated for each connector but their detailed pass-FET/current-sense support network is not yet wired; official reference design extraction is required.
  • USB data and SBU pins are intentionally unused for this power-only hub.
  • Project Overview

  • Intended Use

  • What the Device Should Do

  • Main Features

  • System Architecture

  • Hardware Subsystems

  • Interfaces and Connections

  • Power and Runtime Expectations

  • Power Tree and Power Budget

  • Manufacturing and Assembly Expectations

  • Firmware-Relevant Hardware Requirements

  • Physical Design Expectations

  • Important Design Decisions

  • Assumptions

  • Change Notes

  • Provisional / Validation Required