Schematic Block Reorganization


Assigned all 59 physical components to seven functional groups: USB-C input, battery charging/power path, 3.3 V buck, 5 V boost, ESP32-S3 controller, USB-A interface, and bring-up/mechanical. Connectivity is unchanged, and verification found no open ERC or schematic-legibility errors.
Open item
  • Actual symbol rearrangement and visible block-description text could not be added because schematic canvas placement/annotation editing is unavailable in the current toolset. The functional groups are present, but the visual layout remains unchanged.
Use Schematic Arrange to visually group the blocks, then add the descriptions to a project doc.
I’ll use Schematic Arrange to cluster the seven existing functional groups, then create a concise project document describing each block and verify the resulting schematic legibility.
Created a project doc

Schematic Functional Blocks

View Document

J1 is the external USB-C charge input. Its CC1/CC2 sink configuration uses R1 and R2, and USB_VBUS feeds the charger input; input bulk capac...
Created Schematic Functional Blocks with descriptions of all seven blocks and their inter-block signal/power flow. Connectivity and ERC remain clean, but visual rearrangement is blocked because Schematic Arrange is unavailable in this tool session; no schematic or PCB geometry was changed.
Arrange and verify
Run Schematic Arrange
Check schematic readability
Review power blocks
Update block document

Layout and Review Notes
Work completed
  • Board outline configured as 50mm x 70mm rectangle with 1mm corner radius.
  • Stackup configured as 4-layer with Layer 2 as GND reference and Layer 3 as power plane.
  • Routing defaults added: 0.15mm minimum trace, preferred widths 0.15mm / 0.25mm / 0.5mm, and 0.25mm trace corner radius.
  • All 59 physical components placed on the top layer.
  • USB-C J1 is on the left short edge; USB-A J2 is on the right short edge; J3 battery connector is on the bottom edge.
  • ESP32-S3 module U1 is placed at the top edge with the antenna extending beyond the board boundary.
  • Power sections are grouped: BQ24074 charger near USB-C/battery, TPS62840 buck near its passives, TPS61023 boost near its passives.
  • Test points are placed in an accessible row.
Verification findings
  • Layout is physically configured and placed, but the ESP32 antenna overhang makes the aggregate component bounding box extend beyond the board in Y. This is intentional for antenna performance, but the exact keepout region should be manually reviewed before fabrication.
  • Airwires remain because routing has not been completed. Manufacturing files should not be generated until routing is finished and review is clean.
  • The schematic contains several unresolved functional issues that should be corrected before final PCB routing:
    • TPS61023 feedback/programming network needs cleanup.
    • BQ24074 TS/ITERM/programming network needs datasheet-accurate confirmation.
    • R7 appears to be shared between ILIM and an LED path and should be separated.
    • USB-A 5V host power still lacks a dedicated load switch/current-limit element.
    • Mounting holes were added but three are currently designators U5, U6, U7 instead of H2-H4.
Routing guidance
  • Route power first using 0.5mm or copper pours for USB_VBUS, SYS, VBAT, 3V3, and 5V_HOST.
  • Route USB D+/D- as short, paired, same-layer traces over uninterrupted GND reference; target 90 ohm differential impedance.
  • Keep switching loops around U3/L1/C1/C12 and U4/L2/C14/C15 short and compact.
  • Keep all copper, vias, planes, traces, and components out of the ESP32 antenna keepout zone.
  • Work completed

  • Verification findings

  • Routing guidance