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

bfd-debug-executor

Execute J-Link command sequences for STM32 debugging workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill enables direct, non-interactive J-Link command sequences to drive STM32 debugging workflows, including breakpoints, stepping, and registers reads, without a full GDB session.

Core Features & Use Cases

  • Direct J-Link scripting for breakpoint control, stepping, and register reads on STM32 devices.
  • Deterministic sessions by using prepared command files and a bootstrap profile to initialize the environment.
  • Automation-friendly workflows that integrate with CI or scripted debugging tasks in embedded firmware projects.

Quick Start

Bootstrap the profile and then run the provided debug script to execute J-Link commands for the target STM32.

Frequently Asked Questions about bfd-debug-executor

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

FAQPage Schema
How do I run J-Link debugging commands on STM32 without an interactive GDB session?▼

You can automate STM32 debugging by executing prepared J-Link command script files non-interactively. This directly drives breakpoint control, stepping, and register reads without requiring a full interactive GDB session.

Can I automate STM32 breakpoint and register workflows in a CI pipeline?▼

Yes, you can automate STM32 debugging in CI pipelines by executing prepared J-Link command files. This provides deterministic, automation-friendly sessions for scripted debugging tasks in embedded firmware projects.

Do I need the Segger J-Link toolchain to script STM32 debugging sessions?▼

Yes, the Segger J-Link toolchain is required to script STM32 debugging sessions. The workflow relies on J-Link command scripting to execute non-interactive sessions for breakpoints, registers, and memory.

What is the best way to ensure deterministic J-Link debugging sessions for STM32?▼

The best way to ensure deterministic J-Link debugging sessions is to use prepared command files and a bootstrap profile. This initializes the environment consistently before running the target STM32 debug script.

Does non-interactive J-Link scripting support memory reads and stepping on STM32 targets?▼

Yes, non-interactive J-Link scripting supports memory reads, stepping, and breakpoint control on STM32 targets. These operations are executed directly through prepared command sequences.

Related Skills

Explore More Software Engineering Skills→
LeoKemp223LeoKemp223
810

flash-jlink

Flash ELF, HEX, and BIN firmware to microcontrollers via SEGGER J-Link.

Community
Intermediate
zhinkgitzhinkgit
551

jlink

Automate J-Link probe operations for ARM Cortex-M device flashing and debugging.

Community
Advanced
Sonder4Sonder4
27

bfd-flash-programmer

Automate STM32 flash programming and verification via J-Link or ST-Link.

Community
Intermediate
MarbleSodasMarbleSodas

node-inspect-debugger

Control the V8 inspector to debug Node.js runtime state with breakpoints and expression evaluation.

Community
Intermediate