Files
zeroclaw/src/hardware/registry.rs
T
ehu shubham shaw de3ec87d16 Ehu shubham shaw contribution --> Hardware support (#306)
* feat: add ZeroClaw firmware for ESP32 and Nucleo

* Introduced new firmware for ZeroClaw on ESP32 and Nucleo-F401RE, enabling JSON-over-serial communication for GPIO control.
* Added `zeroclaw-esp32` with support for commands like `gpio_read` and `gpio_write`, along with capabilities reporting.
* Implemented `zeroclaw-nucleo` firmware with similar functionality for STM32, ensuring compatibility with existing ZeroClaw protocols.
* Updated `.gitignore` to include new firmware targets and added necessary dependencies in `Cargo.toml` for both platforms.
* Created README files for both firmware projects detailing setup, build, and usage instructions.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

* feat: enhance hardware peripheral support and documentation

- Added `Peripheral` trait implementation in `src/peripherals/` to manage hardware boards (STM32, RPi GPIO).
- Updated `AGENTS.md` to include new extension points for peripherals and their configuration.
- Introduced comprehensive documentation for adding boards and tools, including a quick start guide and supported boards.
- Enhanced `Cargo.toml` to include optional dependencies for PDF extraction and peripheral support.
- Created new datasheets for Arduino Uno, ESP32, and Nucleo-F401RE, detailing pin aliases and GPIO usage.
- Implemented new tools for hardware memory reading and board information retrieval in the agent loop.

This update significantly improves the integration and usability of hardware peripherals within the ZeroClaw framework.

* feat: add ZeroClaw firmware for ESP32 and Nucleo

* Introduced new firmware for ZeroClaw on ESP32 and Nucleo-F401RE, enabling JSON-over-serial communication for GPIO control.
* Added `zeroclaw-esp32` with support for commands like `gpio_read` and `gpio_write`, along with capabilities reporting.
* Implemented `zeroclaw-nucleo` firmware with similar functionality for STM32, ensuring compatibility with existing ZeroClaw protocols.
* Updated `.gitignore` to include new firmware targets and added necessary dependencies in `Cargo.toml` for both platforms.
* Created README files for both firmware projects detailing setup, build, and usage instructions.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

* feat: enhance hardware peripheral support and documentation

- Added `Peripheral` trait implementation in `src/peripherals/` to manage hardware boards (STM32, RPi GPIO).
- Updated `AGENTS.md` to include new extension points for peripherals and their configuration.
- Introduced comprehensive documentation for adding boards and tools, including a quick start guide and supported boards.
- Enhanced `Cargo.toml` to include optional dependencies for PDF extraction and peripheral support.
- Created new datasheets for Arduino Uno, ESP32, and Nucleo-F401RE, detailing pin aliases and GPIO usage.
- Implemented new tools for hardware memory reading and board information retrieval in the agent loop.

This update significantly improves the integration and usability of hardware peripherals within the ZeroClaw framework.

* feat: Introduce hardware auto-discovery and expanded configuration options for agents, hardware, and security.

* chore: update dependencies and improve probe-rs integration

- Updated `Cargo.lock` to remove specific version constraints for several dependencies, including `zerocopy`, `syn`, and `strsim`, allowing for more flexibility in version resolution.
- Upgraded `bincode` and `bitfield` to their latest versions, enhancing serialization and memory management capabilities.
- Updated `Cargo.toml` to reflect the new version of `probe-rs` from `0.24` to `0.30`, improving hardware probing functionality.
- Refactored code in `src/hardware` and `src/tools` to utilize the new `SessionConfig` for session management in `probe-rs`, ensuring better compatibility and performance.
- Cleaned up documentation in `docs/datasheets/nucleo-f401re.md` by removing unnecessary lines.

* fix: apply cargo fmt

* docs: add hardware architecture diagram.

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-16 11:40:10 -05:00

103 lines
2.4 KiB
Rust

//! Board registry — maps USB VID/PID to known board names and architectures.
/// Information about a known board.
#[derive(Debug, Clone)]
pub struct BoardInfo {
pub vid: u16,
pub pid: u16,
pub name: &'static str,
pub architecture: Option<&'static str>,
}
/// Known USB VID/PID to board mappings.
/// VID 0x0483 = STMicroelectronics, 0x2341 = Arduino, 0x10c4 = Silicon Labs.
const KNOWN_BOARDS: &[BoardInfo] = &[
BoardInfo {
vid: 0x0483,
pid: 0x374b,
name: "nucleo-f401re",
architecture: Some("ARM Cortex-M4"),
},
BoardInfo {
vid: 0x0483,
pid: 0x3748,
name: "nucleo-f411re",
architecture: Some("ARM Cortex-M4"),
},
BoardInfo {
vid: 0x2341,
pid: 0x0043,
name: "arduino-uno",
architecture: Some("AVR ATmega328P"),
},
BoardInfo {
vid: 0x2341,
pid: 0x0078,
name: "arduino-uno",
architecture: Some("Arduino Uno Q / ATmega328P"),
},
BoardInfo {
vid: 0x2341,
pid: 0x0042,
name: "arduino-mega",
architecture: Some("AVR ATmega2560"),
},
BoardInfo {
vid: 0x10c4,
pid: 0xea60,
name: "cp2102",
architecture: Some("USB-UART bridge"),
},
BoardInfo {
vid: 0x10c4,
pid: 0xea70,
name: "cp2102n",
architecture: Some("USB-UART bridge"),
},
// ESP32 dev boards often use CH340 USB-UART
BoardInfo {
vid: 0x1a86,
pid: 0x7523,
name: "esp32",
architecture: Some("ESP32 (CH340)"),
},
BoardInfo {
vid: 0x1a86,
pid: 0x55d4,
name: "esp32",
architecture: Some("ESP32 (CH340)"),
},
];
/// Look up a board by VID and PID.
pub fn lookup_board(vid: u16, pid: u16) -> Option<&'static BoardInfo> {
KNOWN_BOARDS.iter().find(|b| b.vid == vid && b.pid == pid)
}
/// Return all known board entries.
pub fn known_boards() -> &'static [BoardInfo] {
KNOWN_BOARDS
}
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn lookup_nucleo_f401re() {
let b = lookup_board(0x0483, 0x374b).unwrap();
assert_eq!(b.name, "nucleo-f401re");
assert_eq!(b.architecture, Some("ARM Cortex-M4"));
}
#[test]
fn lookup_unknown_returns_none() {
assert!(lookup_board(0x0000, 0x0000).is_none());
}
#[test]
fn known_boards_not_empty() {
assert!(!known_boards().is_empty());
}
}