What problem does it solve? Bringing up an OS or writing bare-metal code on the Raspberry Pi 5 requires accurate knowledge of the BCM2712 SoC and RP1 southbridge — memory maps, boot chain hand-off, interrupts, clocks — but there is no public BCM2712 peripherals datasheet, and reading GPL driver source directly can contaminate clean-room reimplementation efforts. ## Core Features & Use Cases - Board-specific knowledge base: Provides memory map and MMIO addresses, device tree structure, boot chain and EL2 hand-off contract, PSCI/SMP, GIC-400 interrupts, timers, clocks, UART/GPIO, and PCIe/RP1 topology for the Pi 5 and CM5. - Curated source cache: Clones and maintains the Raspberry Pi Linux tree, ARM Trusted Firmware-A, firmware blobs, and official datasheets under a local resource directory for grounded answers. - Clean-room subagent isolation: Runs as a delegated subagent so the main agent never reads GPL source, returning hardware facts and mechanism descriptions without any source code. - Use Case: While porting an OS to the Pi 5, ask where the debug UART lives and how secondary cores start; the expert returns the PL011 address 0x10_7D00_1000 and the PSCI CPU_ON mechanism with citations, not code. ## Quick Start Ask the agent to spawn the rpi-expert subagent and answer a specific Raspberry Pi 5 bring-up question, such as where the debug UART is mapped and how the boot chain hands off to your kernel.
