skills.rest
ormastes
ormastesCOMMUNITY
Explore all skills by this author →
GitHub

TRACE32 Skill - Setup & Debugging Procedures

Connect TRACE32 debugging workflows via Simple RCL APIs and MCP tools.

Updated May 27, 2026
Search Tags:#mcp#jtag#trace32#trace capture#embedded debugging#gdb bridge#remote protocol
One-click install
npx skills add https://github.com/ormastes/Spipe --skill trace32-skill-setup-debugging-procedures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: TRACE32 Skill - Setup & Debugging Procedures
Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/skill_command/skills/claude/lib/t32
Command: npx skills add https://github.com/ormastes/Spipe --skill trace32-skill-setup-debugging-procedures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrating TRACE32-based debugging with a portable LLM process is hard because developers need a consistent way to start PowerView, control target execution, bridge to GDB, and run T32-specific trace/coverage workflows.

Core Features & Use Cases

  • TRACE32 session control via Simple RCL API: Connect to a running TRACE32 endpoint to halt/resume/step, read registers, and execute PRACTICE/CMM sequences.
  • T32-aware MCP debug tools: Use MCP tools for trace capture, coverage collection, flash programming, system reset, and PRACTICE script execution with correct target session types.
  • GDB bridge and DAP adapter support: Enable a GDB server inside TRACE32, then connect with a GDB client, or use the provided DAP adapter interface for IDE-style workflows.
  • Repeatable host/container lifecycle: Use the t32q container wrapper and semihost smoke tests to launch, verify ports, and validate output signals.

Quick Start

Run the T32 container flow to bring up TRACE32, then enable the MCP/T32 debugging tools and verify port 20000 responds before starting your debug session.

Frequently Asked Questions about TRACE32 Skill - Setup & Debugging Procedures

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

FAQPage Schema
How do I connect TRACE32 to an LLM for embedded debugging?▼

To connect TRACE32 to an LLM for embedded debugging, you use Simple RCL APIs and MCP debug tooling to establish a reliable session. This enables you to control target execution, read registers, and execute PRACTICE scripts seamlessly.

Can I use a GDB bridge with TRACE32 for target debugging?▼

Yes, you can use a GDB bridge with TRACE32 by enabling a GDB server inside TRACE32 and connecting via a GDB client on TCP 30000. A DAP adapter interface is also available for IDE-style workflows.

What is the best way to capture trace and coverage data using TRACE32?▼

The best way to capture trace and coverage data using TRACE32 is through T32-aware MCP debug tools. These tools manage trace capture and coverage collection directly within your active target session.

Do I need specific network ports open for TRACE32 debugging sessions?▼

Yes, TRACE32 debugging requires UDP port 20000 for TRACE32 services and optionally TCP 30000 for GDB server bridging. Verifying port 20000 responds ensures your debug session starts reliably.

How do I automate flash programming and system resets in TRACE32?▼

You automate flash programming and system resets in TRACE32 by executing PRACTICE scripts via the MCP debug tools. This method supports repeatable host and container lifecycle management for embedded targets.

Related Skills

Explore More Software Engineering Skills→
ormastesormastes
1

t32q

Manage TRACE32 container lifecycle with GUI and headless modes.

Community
Intermediate
zhinkgitzhinkgit
551

workflow

Automate Keil or GCC builds, flashing, debugging, and runtime observation workflows.

Community
Intermediate
lexlerlexler
225

hexagonal-architecture

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

Community
Basic
LeoKemp223LeoKemp223
810

debug-gdb-openocd

Automate OpenOCD and GDB setup for embedded firmware debugging.

Community
Intermediate