t32q

Manage TRACE32 container lifecycle with GUI and headless modes.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ormastes/simple --skill t32q
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t32q
Source: https://github.com/ormastes/simple/tree/main/.codex/skills/t32q
Command: npx skills add https://github.com/ormastes/simple --skill t32q

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TRACE32 container control for embedded development workflows, enabling reliable start, stop, restart, and GUI lifecycle management without manual container fiddling.

Core Features & Use Cases

  • Lifecycle control for TRACE32 containers (on, off, reopen, wait, ping, status)
  • GUI and headless operation support (gui-on, gui-reopen, status, logs)
  • Diagnostics through logs inspection and a readiness-check script
  • Recovery and retry pathways for repo-managed TRACE32 container flows

Quick Start

Start the TRACE32 container in the desired mode and verify readiness using status and logs.

Frequently Asked Questions about t32q

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

FAQPage Schema
How do I manage the TRACE32 container lifecycle for embedded development?

To manage the TRACE32 container lifecycle, this Skill orchestrates turning TRACE32 on or off, reopening it, and launching GUI or headless containers. It provides reliable lifecycle control without manual container fiddling.

How do I start a TRACE32 container in headless or GUI mode?

You can launch the TRACE32 container in either mode using the gui-on or headless commands. After starting, verify readiness using the status and logs commands to ensure the container is fully operational.

Do I need specific scripts to run TRACE32 container readiness checks?

Yes, this Skill requires container scripts and runtime notes to orchestrate headless and GUI modes, including a readiness check script. These scripts enable the ping and wait options to verify TRACE32 readiness.

How do I inspect TRACE32 container logs and status for diagnostics?

You can check TRACE32 container logs and status through this Skill's diagnostic commands. It provides logs inspection and a readiness-check script to monitor container health and diagnose issues during repo-managed deployments.

What is the best way to restart or reopen a TRACE32 GUI container?

The gui-reopen command provides the best way to restart a TRACE32 GUI container. This Skill manages the recovery and retry pathways for repo-managed TRACE32 container flows, ensuring reliable GUI lifecycle management.

Why does my TRACE32 container deployment fail to verify readiness?

TRACE32 container readiness checks may fail if prerequisite container scripts and GUI prerequisites are missing. This Skill uses a readiness check script and runtime notes to orchestrate headless and GUI modes, providing ping and wait options to resolve readiness issues.