Raspberry Pi
Enable an AI agent to recognise a Raspberry Pi computer, assess its configuration and operating condition, and determine compatible, safe actions for its intended workload.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an AI agent to recognise a Raspberry Pi computer, assess its configuration and operating condition, and determine compatible, safe actions for its intended workload.
Raspberry Pi is a family of compact, Arm-based single-board computers and related compute modules designed for general-purpose computing, programming education and embedded applications, with specifications that vary by model.
It can be Identify the variant and select matching documentation, operating-system images and accessories.; Prepare or replace boot media and configure supported boot paths while preserving required data.; Connect compatible HATs, cameras, displays and GPIO circuits after checking electrical and software requirements.; Measure supply and thermal behaviour under the intended workload and adjust cooling or load.; Provision, update, diagnose and recover a deployed Raspberry Pi using methods supported by its variant.; Integrate a board or Compute Module into a larger assembly with documented power, carrier and service dependencies..
Distinguishing features
Establish Raspberry Pi product identity through consistent board markings, hardware identifiers and official product documentation; a similar connector layout or compatible operating system alone is insufficient.
Distinguish the computer variants covered here from Pico-class microcontroller boards by the identified product family and its documented boot and software architecture.
Distinguish a Compute Module from a standalone board by its documented carrier interface and dependence on a suitable carrier for exposed connections.
Distinguish a Raspberry Pi component from a finished appliance by identifying the physical computer and the functions supplied by the surrounding system.
Treat generation, memory option and board revision as variant attributes, and serial number and observed condition as attributes of an individual unit.
Scope
+ Identification of the board or module, product generation, hardware revision and installed memory
+ Power, cooling, enclosure and carrier-board requirements for the identified variant
+ Boot firmware, boot media, operating-system compatibility and recovery state
+ Available ports, GPIO capabilities and attached peripheral compatibility
+ Workload suitability, operating health and deployment readiness
- Raspberry Pi companies, charitable organisations and their governance
- Raspberry Pi Pico microcontroller boards and standalone microcontroller chips, provisionally treated as neighbouring kinds
- Operating systems and application software as independently maintained information products
- HATs, cameras, displays, power supplies and carrier boards as independently modelled accessories
- Complete robots, appliances or industrial installations that contain a Raspberry Pi
Characteristics
- Product variant and board revision
- Documented product designation, hardware revision and identification confidence Controls which specifications, firmware, accessories and recovery procedures apply.
- Physical implementation
- Single-board computer | keyboard-integrated computer | Compute Module; carrier required or integrated Determines installation boundaries, connector availability and enclosure requirements.
- Processor and software architecture
- SoC designation, supported instruction sets and installed operating-system architecture Determines whether an image or executable can run on the identified hardware.
- Installed memory
- MiB or GiB, distinguishing nominal capacity from operating-system-usable memory Constrains concurrent services, memory-intensive applications and image selection.
- Power-path capability
- Required and available V, A and W at the documented input, with cable and peripheral load identified Helps explain unstable operation and determines whether the complete setup has an adequate supply.
- Boot configuration
- Firmware version where applicable, supported and selected boot source, boot order and observed boot stage Separates unsupported boot choices from media, firmware and operating-system failures.
- Storage configuration and condition
- Media type, capacity in GB or GiB, free space, read/write status and observed errors Determines persistence, recovery options and risk when changing or interrupting the system.
- Exposed interfaces
- Variant-specific connector types, counts, supported protocols and occupied functions Prevents assumptions that every Raspberry Pi has the same ports or expansion capabilities.
- Attached hardware
- Links to carrier, HAT, GPIO circuit, camera, display, storage, cooling and power-supply records Makes compatibility and electrical dependencies inspectable.
- Thermal and supply health
- Temperature in °C, available undervoltage or throttling indicators, observation time and workload Distinguishes satisfactory operation from performance constrained by cooling or power.
- Physical fit
- Board or assembly dimensions and mounting positions in mm, including connector and cooling clearance Determines whether a case, carrier or mounting arrangement fits the actual assembly.
- Deployment trust state
- Image provenance, update status, enabled remote services, credential provisioning and recovery readiness Determines whether the configured computer is ready for its intended network and maintenance conditions.
Also called
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 11 layers · 19 findings · 29 questions.
Product identity and variant Establish which Raspberry Pi computer is present and where its physical boundary lies.
Family resemblance conceals differences that change nearly every compatibility and maintenance decision.
Hardware identification
Reconcile physical markings with reported hardware identity.
Variant evidence
Record evidence for the product designation, board revision and memory option without assuming that an installed image identifies the board.
- Which Raspberry Pi product and revision do board markings and available hardware identifiers indicate? definition
- Which official identification reference was used, and do physical and software-reported identifiers agree? provenance
Assembly boundary
Separate the computer variant from carriers, accessories and the host appliance.
Computer and carrier
Record whether usable interfaces belong to the Raspberry Pi itself, an integrated assembly or a separate Compute Module carrier.
- Is this a standalone board, keyboard-integrated computer or Compute Module requiring a carrier? boundary
- Which installed carrier or enclosure determines connector access, mounting and replacement compatibility? boundary
Power, cooling and installation Assess the power path and thermal environment of the complete Raspberry Pi assembly.
Supply limitations, peripheral demand and enclosure cooling can make a correctly configured Pi unreliable.
Power path
Relate documented input requirements to the actual supply, cable and connected loads.
Supply and load budget
Establish an evidence-based power budget that includes board demand, peripherals and the chosen input method.
- What input voltage, supply capability and connection or negotiation requirements are documented for this exact variant? measurement
- Under peak intended load, what evidence shows that the supply and cable support the board and attached peripherals? measurement
Thermal and mechanical fit
Check cooling performance and physical installation against the intended workload.
Sustained operation envelope
Record temperature and performance observations together with cooling hardware, case geometry and ambient conditions.
- What temperatures and available throttling indicators are observed during a representative sustained workload? measurement
- What changes to the documented cooling or mounting arrangement are needed to maintain acceptable operation and connector clearance? action
Boot, storage and recovery Trace the supported path from power-on through firmware and storage to a working operating system.
Raspberry Pi variants differ in boot facilities, and replaceable or embedded media creates distinct recovery constraints.
Boot-chain compatibility
Match firmware, boot source and operating-system image to the identified board.
Supported startup path
Record the selected boot path and its prerequisites without assuming that all variants support identical media or firmware configuration.
- Which boot sources and firmware configuration mechanisms are supported by this variant, and which are currently selected? definition
- What source establishes that the installed operating-system image supports this board and processor architecture? provenance
Media integrity and restoration
Assess persistence, failure evidence and practical restoration routes.
Recoverable storage state
Identify the actual system and data media, their observed condition and the steps needed to restore service.
- Which media hold boot files, the operating system and persistent data, and what errors or capacity constraints are observed? measurement
- How can this board or module be restored from verified media or backups, and what data must be preserved before that action? action
GPIO and peripheral integration Model the electrical, connector and software dependencies of Raspberry Pi expansion.
Physical connection alone does not establish compatibility, and pin assignments can conflict across attached hardware.
GPIO electrical contract
Make pin numbering, signal levels and shared functions explicit before connecting circuits.
Pin use and protection
Record each connected circuit against the variant's documented header and electrical limits.
- Which physical pins and GPIO identifiers does the circuit use, and what signal levels and current limits apply? measurement
- What level conversion, external driver, isolation or wiring change is required before this circuit may be connected or energised? action
Accessory and interface compatibility
Check connector variants, occupied resources and software enablement for expansion hardware.
Complete peripheral path
Trace each HAT, camera, display or other peripheral through its connector, adapter, interface resources and required software.
- Which documented board and accessory revisions, cables and adapters establish compatibility for each attached device? provenance
- Which pin functions, bus addresses, drivers or device-tree settings must be enabled or reconciled for these devices to operate together? action
Deployment health and service Determine whether a configured Raspberry Pi can deliver its assigned workload and remain maintainable.
A board that boots successfully may still lack adequate resources, trustworthy configuration or an accessible recovery route.
Workload and fault evidence
Evaluate the deployed configuration using workload observations and variant-specific diagnostics.
Service fitness
Connect observed failures or degraded performance to memory, storage, connectivity, power and thermal evidence.
- Under the intended workload, what memory use, storage latency, network performance and service interruptions are measured? measurement
- Which available logs, diagnostic indicators or controlled checks distinguish media failure, supply problems, overheating and software faults? action
Provisioning and deployment constraints
Record software provenance, remote maintenance access and evidence relevant to the intended installation.
Maintainable deployment
Establish an update and recovery route and identify which compliance evidence applies to the board versus the assembled product.
- What image source, update process, credentials and remote-access configuration are recorded, and how will access be recovered after an unsuccessful change? action
- Which official conformity documents, certification marks and installation restrictions apply to this variant and jurisdiction, and what remains the responsibility of the host assembly? boundary
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- This describes the computer family, not a particular model or physical unit, and excludes Pico microcontroller boards.
- Dimensions, power requirements, memory, connectors, cooling needs and boot media must be checked against the specific model; Compute Modules have different integration requirements.
- These are recalled facts, not researched findings; model-specific conformity declarations and certification marks require verification.
- Which of these check these first hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Model A and A+ boards
- Model B and B+ boards
- Raspberry Pi Zero boards
- Raspberry Pi Compute Modules
- Keyboard-integrated Raspberry Pi computers
- Which of these kinds and varieties hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- Raspberry Pi product naming - Raspberry Pi plus generation, form-factor designation and, where applicable, memory capacity - Identifies a product variant rather than an individual physical unit.
- Raspberry Pi board revision codes - Hexadecimal revision code - Identifies hardware revision information; decoding depends on whether the code uses the older or newer scheme.
- Which of these identifiers and schemes hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- USB specifications - USB Implementers Forum; supported versions and connector roles depend on the model.
- IEEE 802.3 Ethernet standards - IEEE; applicable to models with Ethernet interfaces.
- IEEE 802.11 wireless LAN standards - IEEE; applicable to wireless-equipped models.
- Which of these standards and regulation hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Teaching programming, computing and electronics
- Prototyping embedded systems and sensor interfaces through GPIO
- Running small servers and network services
- Media playback and digital signage
- Industrial integration using Compute Modules and carrier boards
- Which of these real-world use hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Nominal external supply voltage for common standalone boards - 5 - V DC
- GPIO logic voltage - 3.3 - V
- Common Model B board footprint, excluding connector protrusions - Approximately 85 × 56 - mm
- Zero-family board footprint - Approximately 65 × 30 - mm
- Which of these typical measurements hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Insufficient supply voltage or excessive cable voltage drop can cause instability, resets and peripheral failures.
- Interrupting power during storage writes can corrupt filesystems; flash storage can also wear out.
- Inadequate cooling under sustained load can cause thermal throttling.
- Applying 5 V to ordinary 3.3 V GPIO pins, shorting pins or drawing excessive current can damage hardware.
- Motors, relays and other substantial or inductive loads require suitable drivers and protection rather than direct GPIO connection.
- Which of these failure modes and hazards hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Wireless channel availability and permitted operation depend on the configured country and local radio rules.
- Power adapters vary by mains plug and regional electrical approvals.
- Which of these regional variation hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Single-board computer - The broader hardware category; Raspberry Pi identifies a particular product family within it.
- Raspberry Pi Pico - A related microcontroller-board family intended primarily for firmware execution rather than the Linux-capable computer sense described here.
- Raspberry Pi OS - An operating-system distribution used on Raspberry Pi computers, rather than the hardware.
- Raspberry Pi Foundation - An educational organisation rather than a computer product family.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Raspberry Pi this model covers, and on what evidence? provenance
What the second pass must settle
- Does the registry intend Raspberry Pi to cover the computer family only, or also Pico-class microcontroller boards and other branded hardware?
- Does an existing Vercy world model already cover this concept or a parent computer kind that this entry should reference?
- Which official variant and revision references should anchor processor, memory, dimensions, power, thermal and boot-support records?
- Which peripheral compatibility claims require assembly-level testing beyond the published board and accessory documentation?
- Which jurisdiction-specific conformity records and environmental limits apply to each variant and to finished products incorporating it?