bfd-debug-orchestrator

Orchestrate multi-tool STM32 debugging campaigns with flashing, RTT logging, and fault evidence archival.

27|1|Updated Mar 9, 2026

Search Tags:#automation #debug #stm32 #orchestrator #fault-injection #rtt

Ready to run

npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-debug-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bfd-debug-orchestrator
Source: https://github.com/Sonder4/STM32-BFD-Kit/tree/main/skills/claude/bfd-debug-orchestrator
Command: npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-debug-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires JLinkExe, arm-none-eabi-nm, arm-none-eabi-addr2line, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinating multi-step STM32 debugging workflows across flash, RTT, fault injection, and evidence archival is complex; this skill provides an orchestrated, repeatable framework to run end-to-end campaigns.

Core Features & Use Cases

Orchestrates profile-driven flashing, RTT logging, register capture, hardfault snapshots, and evidence archival across multiple tooling scripts.
Enables deterministic fault campaigns by coordinating steps like project init, flashing, RTT collection, and recovery sequences.
Provides artifacts, logs, and structured fault records to feed error-evolution analysis and post-mortem reviews.

Quick Start

Bootstrap the baseline project profile and run the full fault campaign to execute an end-to-end debug sequence.

Frequently Asked Questions about bfd-debug-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate end-to-end STM32 debug campaigns with flashing and RTT collection?▼

Automate STM32 debug campaigns by orchestrating profile-driven flashing, RTT data collection, register capture, and evidence archival into a deterministic sequence. It coordinates multiple tooling scripts to execute repeatable end-to-end validation workflows.

What is the best way to coordinate fault injection and hardfault snapshots on STM32 targets?▼

Coordinate fault injection and hardfault snapshots on STM32 targets by running orchestrated recovery sequences and register capture. This generates structured fault records and artifacts required for deterministic fault campaigns and post-mortem reviews.

Do I need JLinkExe and arm-none-eabi tools to run STM32 fault campaigns?▼

Yes, you need JLinkExe, arm-none-eabi-nm, and arm-none-eabi-addr2line installed. These dependencies handle target flashing, symbol resolution, and address-to-line mapping for generating accurate debug evidence during campaigns.

How does automated fault evidence generation work for STM32 post-mortem analysis?▼

Automated fault evidence generation works by capturing hardfault snapshots, registers, and RTT logs during orchestrated debug sequences. Logs are stored under logs/ and .claude/debug, providing structured artifacts to feed error-evolution analysis.

Can I use this orchestrator to manage debug artifacts across multiple STM32 tooling scripts?▼

Yes, the orchestrator manages debug artifacts across multiple STM32 tooling scripts by applying deterministic sequencing and artifact management. It consolidates logs and structured fault records for cross-tool coordination throughout the campaign.

Why are my STM32 RTT logs and fault records scattered across different tool outputs?▼

RTT logs and fault records scatter without an orchestrator applying deterministic sequencing and artifact management. This skill coordinates cross-tool outputs, storing consolidated evidence under logs/ and .claude/debug for structured archival.