CM5 Handheld Voice Assistant Project
Thought for 5 sec
I’ll organize the PCB for a compact handheld layout: set/confirm board constraints, place the CM5 centrally, group power/input parts, cluster UI/audio/display parts, then route and run layout checks.
Worked for 50 mins 56 sec
Organized the PCB into a compact 70 × 120 mm, 4-layer handheld layout: CM5 centered, USB-C/power at the bottom, microphones at the top, buttons on the right edge, display FPC near the CM5, and audio/power passives grouped near their ICs. Auto-routing completed and added 762 routing nodes.
Estimated time saved vs. manual EDA workflow: ~6–10 hours.
Open items:
- Final checks still show unresolved routing issues: mainly USB D+/D−, MIPI DSI pairs, some GND/audio connections, dangling traces, and overlapping copper.
- The charger footprint has a pad conflict that likely needs footprint/symbol cleanup.
- The high-current boost converter and battery connector are still placeholders/not finalized, so the power layout is not production-ready.
Suggested next steps:
- Fix the U3 charger footprint pad conflict.
- Manually route/clean USB and MIPI differential pairs.
- Delete/repair dangling and overlapping autoroute traces.
- Add the real boost converter and battery connector, then reroute the power section.
Fix routing and power
Fix U3 conflict
Clean routing errors
Route USB and DSI
Select power parts
Review manufacturability
Refine this doc
Ask about this doc
Project Specification: CM5 Handheld Voice Assistant
1. Purpose
Build a phone-sized handheld voice assistant device around a Raspberry Pi Compute Module 5 (CM5). The custom carrier PCB provides battery power, USB-C charging, microphones, speaker output, a small display interface, wireless connectivity support, and user buttons so the CM5 can run local voice-assistant and edge-AI workloads on-device.
2. Current Project State
Existing parts in the project include:
- Raspberry Pi Compute Module 5
- Raspberry Pi CM4-style module/component currently present and should be reviewed for whether it is needed or redundant
- Same Sky CMS-18138A-SP speaker
- Infineon S80KS5123GABHI020 memory component
- Fuse
- Google G313-06329-00 component
No schematic nets are currently connected.
3. Target Functional Blocks
- Compute: Raspberry Pi CM5 carrier interface and required power sequencing/support
- Power: Li-ion/LiPo battery input, USB-C charging, protection, fuel gauging, and regulated rails for CM5 and peripherals
- Audio input: microphone subsystem for voice capture, preferably digital MEMS microphones unless analog front-end requirements are specified
- Audio output: speaker amplifier sized for the selected speaker and enclosure volume
- Display: compact low-power display interface suitable for handheld UI/status feedback
- Controls: user buttons for wake, volume, mute, and/or action input
- Connectivity: CM5-supported Wi-Fi/Bluetooth antenna/RF considerations or external wireless subsystem if required by the selected CM5 variant
- Storage/memory: verify whether the listed memory component is required by the selected CM5 configuration
4. Initial Electrical Requirements
- Form factor: phone-sized handheld PCB/carrier, final dimensions TBD
- Main compute module: Raspberry Pi Compute Module 5
- Power source: rechargeable single-cell battery assumed until confirmed
- Charging input: USB-C
- User interface: display, speaker, microphones, buttons
- Workload: local voice assistant and edge AI
5. Key Open Decisions
- Exact CM5 variant: RAM size, eMMC/no-eMMC, wireless/no-wireless
- Battery capacity, chemistry, max charge current, and expected runtime
- Display type, size, resolution, and interface
- Microphone count and array geometry
- Speaker power target and amplifier class
- USB-C behavior: charge-only, USB 2.0 device/host, USB 3.x, DisplayPort, or debug-only
- Whether the existing Raspberry Pi CM4 module component should be removed
- Mechanical constraints: board outline, enclosure, button placement, speaker location, display window, antenna keepout
6. Validation Goals
- Power budget confirms regulator, charger, fuse, and battery sizing
- CM5 rails meet Raspberry Pi power requirements and sequencing guidance
- USB-C CC, protection, and current-limit behavior are correct
- Audio input/output subsystem meets intended voice capture and playback needs
- RF/antenna keepouts are respected
- ERC/DRC pass before layout/routing completion
7. Next Engineering Steps
- Confirm the open decisions above.
- Create a power budget for CM5, display, audio, wireless, and peripherals.
- Select charger, power-path, regulator, audio codec/amplifier, microphones, display connector, and buttons.
- Wire the schematic by functional block.
- Run ERC and create a board bring-up plan before layout.
1. Purpose
2. Current Project State
3. Target Functional Blocks
4. Initial Electrical Requirements
5. Key Open Decisions
6. Validation Goals
7. Next Engineering Steps
