BCM2712 quad-core Arm SBC with VideoCore VII graphics, LPDDR4X memory, RP1 I/O, MIPI camera/display, PCIe and 40-pin expansion header
Compute & Control · Single-board computer family
Raspberry Pi 5
The family-level product identity used by LeKiwi, TrotBot and optional AlohaMini configurations. It is deliberately separate from the OpenAMR-specific Rev 1.1 record and does not infer a board revision from a RAM label.
Raspberry Pi 5 · Also: Raspberry Pi 5 4 GB, Raspberry Pi 5 8 GB, Raspberry Pi 5 (≥ 2GB RAM)
What this record can support today.
Coverage is computed from published, non-unknown fields. It measures the record—not product quality—and makes missing procurement evidence explicit.
Engineering field coverage60%
6 of 10 selected fields published
- Official product sourcepublished
- Lifecycle statepublished
- Mechanical dimensions / mass / mountingmissing
- Environmental operating limitsmissing
- Compute performance boundarypublished
- Memory and storagepublished
- Power mode / inputpublished
- I/O and expansionpublished
- Software / OS supportmissing
- Thermal design boundarymissing
Procurement field coverage15%
2 of 13 selected fields published
- Official product / sales routepublished
- Lifecycle statepublished
- Exact orderable SKU / part numbermissing
- Price with region, currency and quantitymissing
- Lead time with check datemissing
- Commercial availability / stock statemissing
- Minimum order quantitymissing
- Authorized distributor / sales channelmissing
- CAD / STEP / interface drawingmissing
- Certification with identifiermissing
- MTBF / failure / reliability datamissing
- Warranty termsmissing
- PCN / EOL / replacement noticemissing
Coverage measures whether a selected public field is present with non-U evidence. It is not a product score, compatibility result, certification, availability confirmation or procurement recommendation. Download the complete readiness coverage JSON →
Exact-model responsibility-party BOM crosswalk.
This edge requires a pinned robot BOM identity and an exact RCI component record. It remains separate from as-built inspection, compatibility and performance evidence.
Robot BOM → exact component
AlohaMini1 mobile manipulator
The pinned AlohaMini1 table names one Raspberry Pi 5 with at least 2 GB RAM inside Standalone Mode (Optional). The relation preserves that optional configuration and does not treat it as simultaneously installed base hardware.
Published quantity: 1. One unit is published only within the optional standalone-mode boundary; PCB revision and selected RAM capacity above the minimum are not published.
Boundary: This family-level identity relation does not establish a PCB revision, default installation, power/cooling sufficiency, software compatibility, endorsement or physical validation.
Robot BOM → exact component
AlohaMini2 mobile manipulator
The pinned AlohaMini2 Mobile Base table publishes one Raspberry Pi 5 with 2 GB RAM. RCI maps the exact family name and preserves the memory configuration without inferring a PCB revision.
Published quantity: 1. One board is published for the selected AlohaMini2 mobile-base configuration. No serial, receipt, PCB revision, image or unit-level as-built manifest is available.
Boundary: This family-level crosswalk does not prove power or cooling sufficiency, peripheral or software compatibility, current availability, endorsement or an RCI robot test.
Robot BOM → exact component
LeKiwi 12 V mobile manipulator
The pinned LeKiwi 12 V Sensors and Compute table publishes one Raspberry Pi 5 with 4 GB RAM. RCI maps the family identity while keeping this 12 V configuration separate from the LeKiwi 5 V and wired alternatives.
Published quantity: 1. One board is published for the selected LeKiwi 12 V configuration. No serial, receipt, PCB revision or as-built inspection is available.
Boundary: This relation does not prove battery-path sufficiency, cooling, software/peripheral compatibility, current availability, endorsement or an RCI robot test.
Robot BOM → exact component
DYNAMIXEL LeKiwi mobile manipulator
The pinned DYNAMIXEL LeKiwi Sensors and Compute table publishes one Raspberry Pi 5 with 4 GB RAM. RCI maps the family identity and keeps it attached only to the DYNAMIXEL configuration represented by this BOM.
Published quantity: 1. One board is published for the selected DYNAMIXEL LeKiwi configuration. No serial, receipt, PCB revision or unit-level as-built manifest is available.
Boundary: This relation does not prove U2D2, camera or actuator-chain compatibility, power or cooling sufficiency, current availability, endorsement or an RCI robot test.
Robot BOM → exact component
LeKiwi 5 V mobile manipulator
The pinned LeKiwi 5 V configuration publishes one Raspberry Pi 5 with 4 GB RAM. RCI maps it to the family record without inferring a PCB revision.
Published quantity: 1. One board is published for the selected 5 V configuration. No serial, receipt, lot, PCB revision or as-built inspection is available.
Boundary: The relation does not prove power or cooling sufficiency, software/peripheral compatibility, current availability, endorsement or an RCI robot test.
Robot BOM → exact component
TrotBot ROS 2 quadruped hardware boundary
The pinned TrotBot hardware requirements name one Raspberry Pi 5 with 8 GB RAM as the main compute board. RCI maps the family identity while leaving the PCB revision unknown.
Published quantity: 1. One main compute board is implied by the singular requirement; no serial, PCB revision, image or unit-level as-built manifest is published.
Boundary: The relation does not prove installation in a physical TrotBot, power/cooling sufficiency, software compatibility, endorsement or RCI validation.
1 bounded physical-evidence record.
Publisher independence, identity precision and measurement scope vary by row. Results remain bounded by the disclosed specimen, setup, workload and metric; an inconclusive mapping is evidence associated with the catalog model, not verification of a manufacturer claim.
| Measured result | Conditions | Claim mapping | Source |
|---|---|---|---|
| Independent direct-component measurementindependent_physical_evidence | Independent CPU, storage and power benchmark results published for physical Raspberry Pi 5 boardsFamily-level review hardware; board revision and memory SKU vary by test. | inconclusiveThe record establishes bounded physical evidence for the named model, but the experiment does not reproduce the catalogued claim metric and conditions; the claim remains inconclusive. | Raspberry Pi 5 Review ↗Benchmark, thermal and power sections Checked 2026-08-26 |
Reported values, conditions attached.
Evidence state describes the claim—not the prestige of the company or document.
| Claim | Reported value | Condition / boundary | State | Source |
|---|---|---|---|---|
| CPUcpu | Broadcom BCM2712; 2.4 GHz quad-core 64-bit Arm Cortex-A76 | Raspberry Pi 5 family specification. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| GPUgpu | VideoCore VII; OpenGL ES 3.1; Vulkan 1.3 | Raspberry Pi 5 family specification. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| Memory configurationsmemory | LPDDR4X-4267: 1, 2, 4, 8 or 16 GB | Each robot relation preserves its source-declared RAM option. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| Wirelesswireless | Dual-band 802.11ac Wi-Fi; Bluetooth 5.0 / BLE | Family specification. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| Storagestorage | microSD with SDR104 support | Card and software image are separate build inputs. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| USBusb | 2 × USB 3.0 at simultaneous 5 Gbps; 2 × USB 2.0 | Family specification. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| Ethernetethernet | Gigabit Ethernet; PoE+ with separate HAT | PoE+ requires an accessory. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| MIPI camera/displaymipi | 2 × 4-lane transceivers | Cable, sensor and software compatibility remain separate. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| PCI Expresspcie | PCIe 2.0 ×1 | Requires a separate adapter for common M.2 devices. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| Recommended DC inputpower | 5 V / 5 A USB-C with Power Delivery support | Manufacturer warns about under-powered supplies. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| Production lifetimeproduction_lifetime | At least January 2036 | Manufacturer obsolescence statement observed on verification date. | M · Manufacturer claimed | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| Board revision in family-level robot rowsrobot_board_revision | Not published in cited public evidence | RCI checked the cited official public evidence on the verification date.LeKiwi, TrotBot and AlohaMini identify family and RAM boundaries but do not publish exact PCB revisions. | U · Unknown | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
| Independent robot integration validationindependent_robot_validation | Not published in cited public evidence | RCI checked the cited official public evidence on the verification date.RCI has not inspected board revision, power, cooling, image, peripherals or operating robot for these rows. | U · Unknown | Raspberry Pi 5 product page ↗Specification, operating-system, power, cooling and obsolescence sections · Live product page observed 2026-08-13 Checked 2026-08-13 |
Known limits
What this record does not prove.
- This family record must not be used to infer Rev 1.1 or any other board revision.
- RAM option alone does not identify PCB revision, serial, software image, cooling configuration or power margin.
- The robot relations are responsibility-party identity links, not compatibility or physical validation.