bfd-fault-logger

Record and classify STM32 hardware faults into structured reports.

27|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-fault-logger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bfd-fault-logger
Source: https://github.com/Sonder4/STM32-BFD-Kit/tree/main/skills/claude/bfd-fault-logger
Command: npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-fault-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill helps teams automatically record and organize hardware fault data from STM32 devices into structured, searchable reports for debugging and post-mortem analysis.

Core Features & Use Cases

  • Record and classify HardFault, BusFault, and UsageFault with registers, fault status, and stack traces.
  • Export fault data to JSON/CSV/HTML/Markdown formats for archival and analysis.
  • Generate readable fault reports and summaries to facilitate faster root-cause investigation.

Quick Start

Capture fault context by triggering the fault logger and view the generated report in the logs/hw_error directory.

Frequently Asked Questions about bfd-fault-logger

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

FAQPage Schema
How do I capture STM32 HardFault registers and stack traces for post-mortem analysis?

Capturing STM32 HardFault data involves recording registers, fault status, and stack traces into structured reports, enabling deterministic fault capture for post-mortem debugging sessions.

Can I export STM32 fault reports to JSON or CSV formats?

You can export STM32 fault reports to JSON, CSV, HTML, and Markdown formats, generating readable summaries and structured data files for local storage and post-mortem analysis.

What is the best way to classify and record UsageFault and BusFault data on STM32 devices?

Recording and classifying UsageFault and BusFault data requires capturing contextual state and fault status deterministically, organizing the hardware fault evidence into searchable local fault reports.

Does this STM32 fault logger require any specific dependencies to generate Markdown reports?

No external dependencies are required to generate Markdown reports; the logger independently captures fault context and exports structured fault data directly to the local logs directory.

Where are the generated STM32 fault logs stored after a debugging session?

Generated STM32 fault logs are stored in the logs/hw_error directory, providing local storage for structured fault reports and contextual state captured during debugging sessions.