TRACE32 Skill - Setup & Debugging Procedures

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.