gpiocore.dev
Official ecosystem site — Work in Progress
Open platform • Rust • XML/XSD-driven

Deterministic hardware systems for Rust.

gpiocore is an open ecosystem for defining, running, recording, and replaying hardware-driven applications across real hardware, simulation, and remote execution.

Explore the platform Current status
Open core Core crates, XML model, and published protocols are intended as the public foundation.
Spec-first Architecture and schemas are being locked before implementation.
Replay-ready Recording and deterministic replay are part of the ecosystem design from the start.
Ecosystem overview Open foundation with optional commercial companion tools XML / XSD System Definition Devices, wiring, recording, MQTT extension, canvas Runtime gpiocore Devices, factories, events, MQTT, recording hooks Targets Real / Sim / Remote rppal, cdev, esp32, Mock, SimPin, Remote Open crate gpiocore-mqtt Declarative MQTT layer Commercial tool Recording System Agent + Collector Commercial tool SimPin Visual simulation

What this site is about

This site is the future public entry point for the gpiocore ecosystem: the place for specifications, architecture, crate links, examples, and implementation notes. It is intentionally early while the specification set is being validated.

Define

Describe hardware projects declaratively using XML and XSD: devices, factories, wiring, recording intent, MQTT integration, and visual overrides.

Run

Execute the same application logic on Raspberry Pi, Linux SBCs, ESP32 targets, visual simulation, or remote-controlled setups.

Replay

Record what happened on real systems, then replay it later for debugging, teaching, deterministic testing, and algorithm work.

Core architecture

The ecosystem is being shaped around a spec-first model: a structured XML definition, a runtime layer that executes it, and optional tool layers that record, visualize, and replay the system lifecycle.

Layer 1 XML / XSD system definition devices • factories • recording flags • source connections • MQTT extension Layer 2 gpiocore runtime engine device abstractions • per-device factories • event flow • MQTT layer • recording hooks Layer 3 Observation and replay tools Recording Agent • Collector • SimPin visual host • deterministic replay loop

Ecosystem Architecture

The gpiocore ecosystem is built around a modular factory pattern, supporting multiple backends, runtime hosts, and optional commercial tools for simulation and recording.

Page-1 Sheet.1 Sheet.2 Sheet.3 Sheet.4 gpiocore-mqtt gpiocore-mqtt Sheet.5 FACTORY MODE FACTORY MODE Sheet.6 BACKEND BACKEND Sheet.7 RUNTIME HOST RUNTIME HOST Sheet.8 APPLICATIONS APPLICATIONS Sheet.9 Sheet.10 gpiocore gpiocore Sheet.11 Sheet.12 RemoteFactory RemoteFactory Sheet.13 Sheet.14 RemoteClient RemoteClient Sheet.15 Sheet.16 Mock Mock Sheet.17 Sheet.18 SimPinFactory SimPinFactory Sheet.19 Sheet.20 Recording Agent Recording Agent Sheet.22 Sheet.23 rppal rppal Sheet.24 Sheet.25 cdev cdev Sheet.26 Sheet.27 esp32 esp32 Sheet.28 Sheet.29 Redox Redox Sheet.30 Bus Protocols Bus Protocols Sheet.31 Sheet.32 I2C I2C Sheet.33 Sheet.34 SPI SPI Sheet.35 Sheet.36 UART UART Sheet.37 Sheet.38 PC PC Sheet.39 Sheet.40 Wafer Wafer Sheet.41 Sheet.42 SimPin App SimPin App Sheet.43 Sheet.44 PC or Wafer PC or Wafer Sheet.45 Might be absent Might be absent Sheet.46 Published API Published API Sheet.47 Sheet.48 Collector App Collector App Sheet.49 Sheet.50 PC only PC only Sheet.51 Might be absent Might be absent Sheet.52 Published API Published API Sheet.53 Sheet.54 Sheet.55 Sheet.56 Sheet.57 Sheet.58 Sheet.59 Sheet.61 Sheet.62 Sheet.63 Sheet.64 Sheet.65 Core / Primary Core / Primary Sheet.66 Sheet.67 Simulation / Replay Simulation / Replay Sheet.68 Sheet.69 Optional / Remote Optional / Remote Sheet.70 Sheet.71 Backend Driver Backend Driver

Status

The architecture is being stabilized before implementation begins. This page exists now so the project has a real public presence while the ecosystem moves from specification to code.

Now
Specification validation
Core specifications, tool boundaries, protocols, file formats, XML schemas, and visual simulation workflows are being reviewed and locked down.
Next
Core implementation
The first implementation work will focus on the runtime foundation, pin factories, XML loading, and test infrastructure.
Later
Public crates and docs
This site will expand into the main documentation and download hub once the core crates and initial examples are ready to publish.

Stay Updated

This project is under active development. If you want to know when it becomes available:

Contact / Join the waitlist

No spam. Only major updates and release announcements. You can also email directly at Info@gpiocode.dev.