I’ll tighten the placement around the ESP32-P4, flash, DSI connector, and SD socket to shorten the unrouted flash/DSI/SD nets, then rerun the relevant DRC/airwire check.
The first placement pass shortened the flash/DSI/SD paths, but it introduced a visible overlap around the SD socket and a Wi‑Fi edge warning. I’m correcting those before reporting the final check results.
Placement pass completed around the ESP32-P4: flash was pulled closer to U1, the DSI connector was moved closer to the ESP32-P4, display power stayed near it, and the SD socket was moved closer to reduce SD/DSI/flash airwire length.
Open items:
I’m blocked now because there are no available ACUs.
The placement pass introduced issues that still need cleanup: SD socket overlap, Wi‑Fi module edge/outside-board warning, and new overlapping-copper warnings.
DRC/airwire checks still need to be rerun after that cleanup.
Suggested next steps:
Add ACUs, then ask me to fix the SD/Wi‑Fi placement issues.
Backlight brightness can be controlled by I2C write 0x00–0xFF to device 0x45, register 0x96.
Connector notes
Wiki mentions Raspberry Pi 22-pin and 15-pin DSI cable variants depending host board.
The scraped wiki content does not expose a signal-by-signal connector pinout table.
Before final PCB layout, use Waveshare’s 2D/3D mechanical files and/or schematic for exact FFC connector pinout, orientation, and mating height.
Design implications
Keep the 5 V display rail budget at ≥0.3 A plus margin; the existing TPS54302 3 A buck is sufficient for display + controller overhead if thermals/layout are good.
Keep MIPI DSI as controlled-impedance differential routing from ESP32-P4 to display connector.
Add I2C connection for display/touch/backlight control once the exact connector pinout is confirmed.