debug-jlink

Automate J-Link GDB Server debugging sessions for Cortex-M microcontrollers.

810|140|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/LeoKemp223/embed-ai-tool --skill debug-jlink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-jlink
Source: https://github.com/LeoKemp223/embed-ai-tool/tree/main/skills/debug-jlink
Command: npx skills add https://github.com/LeoKemp223/embed-ai-tool --skill debug-jlink

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires SEGGER J-Link GDB Server, GDB, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of debugging Cortex-M microcontrollers using SEGGER J-Link GDB Server, reducing the complexity of firmware development and debugging.

Core Features & Use Cases

  • J-Link GDB Server Integration: Connects to J-Link GDB Server for seamless debugging.
  • Multiple Debug Modes: Supports download-and-halt, attach-only, and crash-context modes.
  • SWO Output Capture: Captures SWO output for detailed debugging.
  • Use Case: When working on a project that requires debugging a Cortex-M microcontroller with J-Link, this Skill simplifies the process by automating the setup and execution of GDB sessions.

Quick Start

Use the debug-jlink skill to start a download-and-halt debug session for your project with the command: debug-jlink --elf path/to/your/elf --device STM32F407VG.

Frequently Asked Questions about debug-jlink

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

FAQPage Schema
How do I automate J-Link GDB Server debugging sessions for Cortex-M microcontrollers?

You can automate J-Link GDB Server debugging sessions for Cortex-M microcontrollers by using this Skill to handle setup and execution. It simplifies connecting GDB to your firmware and manages the debugging process automatically.

What debug modes are supported for Cortex-M firmware development with J-Link?

Supported debug modes for Cortex-M firmware with J-Link include download-and-halt, attach-only, and crash-context. These modes allow you to either flash and pause execution, attach to a running target, or analyze crash states.

Can I capture SWO output while debugging a Cortex-M microcontroller with GDB?

Yes, you can capture SWO output while debugging a Cortex-M microcontroller. The Skill supports SWO output capture directly through the J-Link GDB Server integration to provide detailed debugging insights.

Do I need specific software installed to debug firmware with J-Link and GDB?

Yes, you need the SEGGER J-Link GDB Server and a compatible GDB installed to debug firmware. These dependencies are required to establish the connection and execute the debugging commands for your microcontroller.

How do I start a download-and-halt debug session for an STM32 project?

To start a download-and-halt debug session for an STM32 project, provide your ELF file and device name. This initiates the J-Link GDB Server, flashes the firmware, and halts execution for immediate debugging.