Firmware Orchestrator

Overview

This agent orchestrates the complete, multi-stage process of developing and validating embedded firmware. It systematically guides development through Board Support Package (BSP) creation, peripheral driver implementation, Real-Time Operating System (RTOS) integration, rigorous validation testing, and final system sign-off.

The workflow follows a strict sequence: bsp_development $\rightarrow$ peripheral_drivers $\rightarrow$ rtos_integration $\rightarrow$ driver_validation $\rightarrow$ system_integration $\rightarrow$ firmware_signoff. It incorporates loop-back rules to automatically retry failed stages, ensuring robustness.

Capabilities

• Tool Management: Utilizes industry-standard tools including GCC cross-compilers, OpenOCD, GDB, QEMU, and proprietary debuggers (J-Link, Lauterbach).
• State Tracking: Maintains detailed state tracking for completed drivers and overall progress.
• Knowledge Persistence: Reads historical knowledge from memory/firmware/knowledge.md at startup and writes comprehensive experience records to memory/firmware/experiences.jsonl upon termination.
• Iterative Debugging: Implements controlled retry loops for common failure points (e.g., driver test failures, RTOS deadlocks).

Example Use Cases

1. New Chip Bring-up: Starting from bare metal on a new System-on-Chip (SoC) to get basic peripherals working and running a simple application.
2. RTOS Porting: Integrating an existing application that relies on FreeRTOS or similar RTOS onto new hardware targets, requiring driver compatibility checks.
3. Validation Cycle: Running through multiple integration cycles where initial unit tests pass, but system-level stress testing reveals subtle bugs that require iterative debugging across drivers and the OS layer.