# Webinar Recap: Agentic Debugging of Embedded Systems With CLion and TRACE32® > Source: > Published: 2026-11-12 10:16:24+00:00 [News](https://blog.jetbrains.com/clion/category/news/) # Webinar Recap: Agentic Debugging of Embedded Systems With CLion and TRACE32® CLion can now debug embedded targets through TRACE32 and let AI agents start and control debug sessions. JetBrains and Lauterbach presented the integration in a joint webinar, and this post recaps the session. You can also watch the [demo](#demo-debugging-a-four-core-aurix-board) presented at the webinar and browse the [slides](https://resources.jetbrains.com/storage/products/clion/docs/CLion_Goldcast_Agentic_Debugging_of_Embedded_Systems_with_CLion_and_TRACE32.pdf). ## How CLion and TRACE32 work together Moving from editing source code to investigating behavior on a target usually means switching between tools. The integration brings three capabilities into one workflow: - Develop and debug in a single environment. - Control TRACE32 hardware debugging from CLion. - Give AI agents access to live debugger data to inspect program state and find root causes. [TRACE32](https://www.lauterbach.com/) is Lauterbach’s debug and trace toolset. It supports more than 150 CPU architectures and over 15,000 chips, and the same software covers the product lifecycle from virtual targets to real hardware. For hardware debugging, Lauterbach offers the [PowerDebug System](https://www.lauterbach.com/products/debugger/powerdebug-system). CLion communicates with TRACE32 via the [Debug Adapter Protocol (DAP)](https://www.jetbrains.com/help/clion/dap-support.html). Lauterbach provides a tool called `t32debugadapter` that exposes the DAP interface and connects to TRACE32 through its Remote API. TRACE32 then handles the connection to the target, whether it’s real silicon, an emulator, or a simulator. To use the integration, you need: - [CLion 2026.2.4 or later](https://www.jetbrains.com/clion/download/) - [TRACE32 PowerView 09.2026](https://www.lauterbach.com/products/software/trace32-powerview) - TRACE32 Debug Adapter 0.1.2 or later In CLion, go to *Settings | Debugger | Debug Profiles* and select the dedicated TRACE32 profile. There, enter the path to the debug adapter executable, the PRACTICE script paths, and any auxiliary options. ## Giving AI agents access to the debugger [JetBrains Air](https://www.jetbrains.com/air/ides/) gives you one place to run agents and verify their work in CLion. You can start multiple agent sessions, run them in parallel, follow their progress, and review their changes, whether the agents run locally or in the cloud. Agents get the same IDE context you use, such as symbols, types, and dependencies. CLion exposes its debugger to agents through the built-in Model Context Protocol (MCP) server, which supports SSE, stdio, and Streamable HTTP transports. Because the debugger is connected to TRACE32, an agent can investigate what happens on the actual target. The agent controls the standard CLion debugger, so you can follow the session in the *Debug* tool window and take over at any point. Skills tell agents when and how to use these tools. CLion includes a generic debugger skill, `clion-debugger`, plus skills for hard fault debugging on Arm Cortex-M devices and for RTOS state exploration.  You can install skills for supported agents from the IDE, configure them manually for other agents, or write custom skills for your project or target hardware. In CLion 2026.2 and later, [router mode](https://www.jetbrains.com/help/clion/agentic-debugging.html#router-mode) keeps the debugger tool descriptions out of the agent context until they’re needed, reducing token usage. The choice of agent is yours. CLion supports agents that use the Agent Client Protocol (ACP), including Junie, Claude Code, Codex, and OpenCode, as well as any compatible internal agent your company builds. You can use your existing agent subscriptions or API keys. Junie Lite provides a free AI model through JetBrains infrastructure, and the current offer terms are valid through December 31, 2026. ## Demo: Debugging a four-core AURIX board For the demo, we used a 4-core Infineon AURIX™ TC387QP with HighTec TriCore GCC, a CMake project, and a Lauterbach LA-3504 PowerDebug E50 probe. Claude Code converted the project from an AURIX Development Studio project to CMake. The PRACTICE setup and upload scripts were adapted from the TRACE32 examples with minor adjustments. In the demo, the agent starts a debug session via TRACE32 and inspects registers and memory across all four cores. The agent uses the same debugger you do, so you can follow along, pause the session, or take over. ## Key Q&A ### Licensing The integration adds no cost on the TRACE32 side. You need the same licenses you would use with PowerView directly. Which licenses those are depends on your target and interface, and you get them from Lauterbach. The skills and MCP tools are included in CLion, which is free for non-commercial use. Commercial use requires a trial or a paid license. ### Scope and limits The integration is at an early stage, and a few things are not available yet: - Instruction and data trace. - A trace viewer in CLion. - Real-time variable updates, which we are adding probe by probe. - T32 commands issued directly from CLion. For T32 commands, you can use PowerView in the same debug session as a workaround. PowerView does not need to be visible and can run in the background. HSM cores should work whenever TRACE32 can debug them. The debug adapter is an open interface, while the skills are specific to CLion. ### Documentation and other questions In our experience, an agent such as Claude Code parses PDFs well, so you can point it at a folder with target datasheets without extra tooling. Generating a software bill of materials is up to your build system. ## Try it yourself To set up the integration, follow Lauterbach’s article [*How to Use CLion as Front-End for TRACE32*](https://support.lauterbach.com/kb/articles/how-to-use-clion-as-front-end-for-trace32). To try agents in CLion, download the [2026.3 version](https://www.jetbrains.com/clion/download/) and learn more in the [Air documentation](https://www.jetbrains.com/help/air/air-in-ides-overview.html).  If you want to evaluate CLion for your team, use the CLion trial version or [request a demo](https://www.jetbrains.com/clion/get-in-touch/). #### Subscribe to CLion Blog updates