bfd-stlink-interface

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ST-Link-based flashing, memory access, and debugging for STM32 targets, when J-Link paths are not suitable or available.

Core Features & Use Cases

  • ST-Link-specific probe control for flashing, reading memory, and writing memory
  • Independent from J-Link/HSS workflows and guidance
  • Guidance for using STM32CubeProgrammer CLI or ST-LINK_gdbserver to manage targets

Quick Start

Connect the ST-Link, flash firmware, and start a debug session using the documented CLI commands.

Frequently Asked Questions about bfd-stlink-interface

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

FAQPage Schema
How do I flash firmware to an STM32 target using ST-Link?

To flash STM32 firmware using ST-Link, this Skill provides deterministic command usage for STM32_Programmer_CLI to write binaries directly to the target while safely managing the debug probe.

Can I start a GDB debug session for STM32 with ST-LINK_gdbserver?

Yes, you can start an STM32 debug session using ST-LINK_gdbserver. This Skill guides you through initiating debug connections independently from J-Link or HSS workflows.

Does this ST-Link workflow support reading and writing memory on STM32 targets?

Yes, ST-Link workflows support reading and writing memory on STM32 targets. You can inspect memory and perform read or write operations using ST-Link-specific probe control commands.

What is the best way to debug STM32 without a J-Link probe?

The best way to debug STM32 without a J-Link probe is using ST-Link tools. This approach provides independent flashing and debugging guidance specifically tailored for ST-Link hardware connections.

When should I avoid using J-Link workflows for STM32 debugging?

You should avoid J-Link workflows for STM32 debugging when J-Link paths are not suitable or available, switching to ST-Link tools to manage flashing, memory access, and debug sessions independently.