skills.rest
51hhh
51hhhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openocd-stm32-debug

Debug STM32 and DW3000 firmware via OpenOCD and ST-Link.

1|Updated Apr 14, 2026
Search Tags:#stm32#gdb#openocd#swd#tcl#st-link#firmware flashing
One-click install
npx skills add https://github.com/51hhh/BU03 --skill openocd-stm32-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openocd-stm32-debug
Source: https://github.com/51hhh/BU03/tree/main/.github/skills/openocd-stm32-debug
Command: npx skills add https://github.com/51hhh/BU03 --skill openocd-stm32-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of debugging STM32 and DW3000 bare-metal firmware by standardizing OpenOCD and ST-Link workflows for flashing, inspection, and automated verification.

Core Features & Use Cases

  • RAM Variable Inspection: Read MCU memory values reliably through OpenOCD TCL using read_memory-based workflows.
  • Firmware Flashing and Validation: Program, verify, reset, and resume STM32 firmware from a repeatable debug flow.
  • Automated Board Testing: Build TCL-driven test scripts that halt execution, check values, and report pass or fail for bare-metal boards.

Quick Start

Ask the Skill to help you create or debug an OpenOCD TCL flow for flashing STM32 firmware, reading RAM variables, and running an automated ST-Link board test.

Frequently Asked Questions about openocd-stm32-debug

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

FAQPage Schema
How do I read STM32 RAM variables using OpenOCD and ST-Link?▼

Read STM32 RAM variables by running OpenOCD TCL scripts through ST-Link. The workflow uses read_memory-based memory inspection commands to reliably halt the MCU and extract variable values during SWD debugging.

What is the best way to automate bare-metal board testing for STM32 firmware?▼

Automate STM32 bare-metal board testing by creating OpenOCD TCL-driven test scripts. These scripts halt execution, check memory values, and report pass or fail, providing a repeatable verification flow for ST-Link.

How do I flash and verify STM32 firmware with OpenOCD?▼

Flash and verify STM32 firmware using a controlled OpenOCD command flow. The process programs the flash, validates the write, and executes a controlled reset, halt, and resume sequence via ST-Link.

Does OpenOCD support SWD debugging for DW3000 boards?▼

OpenOCD supports SWD debugging for DW3000 and STM32 boards via ST-Link. It standardizes the configuration and command flows required to halt, inspect, and resume execution on these bare-metal targets.

Can I use GDB scripting with OpenOCD to debug STM32 firmware?▼

GDB scripting works with OpenOCD to debug STM32 firmware. The Skill standardizes the GDB and TCL scripting integration needed for controlled flash, memory inspection, and automated bare-metal tests.

Why do I need specific OpenOCD TCL scripts for ST-Link configuration?▼

OpenOCD TCL scripts are required for ST-Link configuration to ensure controlled flash, halt, resume, and shutdown command flows. Without these scripts, memory inspection and automated board tests lack the necessary execution control.

Related Skills

Explore More Software Engineering Skills→
mohitmishra786mohitmishra786
159

openocd-jtag

Configure OpenOCD for JTAG and SWD debugging with GDB.

Community
Intermediate
solace-illsolace-ill

test-flakiness

Analyze CI logs and JUnit/XML results to detect flaky tests.

Community
Intermediate
lexlerlexler
225

hexagonal-architecture

Define Domain, Application, and Adapter boundaries with ports and adapters.

Community
Basic
Sonder4Sonder4
27

bfd-stlink-interface

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

Community
Intermediate