skills.rest
Sonder4
Sonder4COMMUNITY
Explore all skills by this author →
GitHub

bfd-debug-interface

Provides a unified interface for STM32 debugging with J-Link or ST-Link.

27|1|Updated Mar 9, 2026
Search Tags:#debugging#stm32#gdb#st-link#fault-analysis#j-link
One-click install
npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-debug-interface
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bfd-debug-interface
Source: https://github.com/Sonder4/STM32-BFD-Kit/tree/main/skills/claude/bfd-debug-interface
Command: npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-debug-interface

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Streamline STM32 debugging workflows by providing a unified interface for breakpoints, watchpoints, register/memory inspection, HardFault analysis, and automated fault-context capture using J-Link or ST-Link.

Core Features & Use Cases

  • Standardized debug sessions: Run repeatable STM32 debug flows with consistent CLI commands and GDB integration.
  • Fault context automation: Capture fault data and logs automatically to support rapid triage and evidence collection.
  • Workflow integration: Seamlessly tie debugging activities into BFD-Kit assets and learnings for continuous improvement.

Quick Start

Bootstrap the BFD-Kit project and start a debugging session against a target using the configured J-Link or ST-Link tools.

Frequently Asked Questions about bfd-debug-interface

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

FAQPage Schema
How do I debug STM32 HardFaults using J-Link or ST-Link?▼

You can debug STM32 HardFaults by running standardized debug sessions that automatically capture fault context and logs, providing centralized evidence for rapid triage using J-Link or ST-Link.

Can I run repeatable STM32 debugging sessions with consistent CLI commands?▼

Yes, you can run repeatable STM32 debugging sessions using consistent CLI commands and GDB integration, ensuring reproducible steps for breakpoints, watchpoints, and memory inspection across builds.

What's the best way to capture fault evidence during STM32 debugging?▼

The best way to capture fault evidence during STM32 debugging is using automated fault-context capture, which automatically logs fault data and centralizes evidence for rapid triage and continuous improvement.

Does this STM32 debugging interface support both J-Link and ST-Link?▼

Yes, this STM32 debugging interface fully supports both J-Link and ST-Link, providing a unified environment for setting breakpoints, inspecting registers, and performing fault analysis.

How do I inspect memory and registers on an STM32 target with GDB?▼

You inspect memory and registers on an STM32 target by initiating a debug session through the unified GDB interface, which standardizes memory inspection and watchpoint configuration.

Related Skills

Explore More Software Engineering Skills→
Sonder4Sonder4
27

bfd-stlink-interface

Flash, read, and write STM32 memory via ST-Link CLI tools.

Community
Intermediate
linfordWulinfordWu
1

offline-GPU-fault-diagnosis

Analyze offline GPU fault logs from iBMC, OS messages, and InfoCollect to identify root causes.

Community
Advanced
Sonder4Sonder4
27

bfd-debug-orchestrator

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

Community
Advanced
zhinkgitzhinkgit
551

openocd

Flash firmware and control debugging on embedded devices using OpenOCD.

Community
Advanced