debug-gdb-openocd

Automate OpenOCD and GDB setup for embedded firmware debugging.

810|140|Updated Apr 17, 2026

Search Tags:#debugging #GDB #firmware development #embedded firmware #OpenOCD

Ready to run

npx skills add https://github.com/LeoKemp223/embed-ai-tool --skill debug-gdb-openocd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-gdb-openocd
Source: https://github.com/LeoKemp223/embed-ai-tool/tree/main/skills/debug-gdb-openocd
Command: npx skills add https://github.com/LeoKemp223/embed-ai-tool --skill debug-gdb-openocd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openocd, gdb, arm-none-eabi-gdb, gdb-multiarch, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of debugging embedded firmware by automating the setup and control of OpenOCD and GDB, reducing the time and complexity of the debugging process.

Core Features & Use Cases

Automated Debugging Setup: Automatically configure and launch OpenOCD and GDB.
GDB Mode Selection: Choose from 'download-and-halt', 'attach-only', or 'crash-context' GDB modes.
Data Extraction: Extract and view registers, backtrace, and crash context information.
Use Case: Ideal for embedded system developers who need to debug their firmware using OpenOCD and GDB, without manually configuring the debugging environment.

Quick Start

Run the debug-gdb-openocd skill with the command 'debug-gdb-openocd --detect' to ensure the environment is ready for debugging.

Frequently Asked Questions about debug-gdb-openocd

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

FAQPage Schema

How do I automate embedded firmware debugging with OpenOCD and GDB?▼

Automating embedded firmware debugging with OpenOCD and GDB involves using a skill that configures and launches both tools, streamlining the process to connect to a target device and load a program without manual environment setup.

What is the difference between attach-only and download-and-halt GDB modes?▼

Attach-only connects GDB to a running target without stopping it, while download-and-halt loads a new program into the target device and suspends execution immediately for inspection.

Can I extract crash context and backtrace information from an embedded device using GDB?▼

Yes, you can extract crash context and backtrace information by using the crash-context GDB mode, which automates data extraction to retrieve registers and stack traces for debugging firmware crashes.

Do I need arm-none-eabi-gdb to debug embedded firmware with OpenOCD?▼

You need either arm-none-eabi-gdb or gdb-multiarch installed to interface with OpenOCD, as these specific GDB versions provide the necessary cross-compilation architecture support for embedded target devices.

How do I verify my environment is ready for OpenOCD and GDB debugging?▼

You can verify your environment readiness by running the detection command, which checks if OpenOCD, GDB, and necessary cross-architecture dependencies are properly installed and configured before debugging.

What are the limitations of using OpenOCD and GDB for embedded firmware debugging?▼

Limitations of using OpenOCD and GDB include the strict dependency on specific GDB versions like arm-none-eabi-gdb or gdb-multiarch, and the need for manual configuration if the automated setup fails to detect your target device.