Traxcope 2.0.0 — TraxAI assistant, Comm Map, Linux applications, ST-LINK

Bundles TraxProbe SDK 2.0.0 (wire protocol 3.x, unchanged). Firmware built with the 1.x SDK keeps working. Update the SDK in your firmware to get the items marked (SDK).

Added

• TraxAI assistant (Standard and Professional). Ask about your traces in plain language: CPU load and task timing, who blocks whom, lost signals, gaps, spectra, logs. TraxAI answers from the real data through Traxcope's own tools, and shows the evidence in the Trace View and the Scope. With your approval each time, it can also design filters and put them into your firmware, edit source files, build, flash and connect the probe. It runs on a model you choose: a local model server, one inside your own network, or your own cloud provider account. Embedya is not in the data path. You can attach files and pictures, pick the model from the chat panel, and let TraxAI read and place cursors. Set it up in Preferences → TraxAI (Manual chapter 23).
• Use TraxAI's tools from your own AI app (MCP). Claude Code, Claude Desktop, VS Code (Copilot), Codex, Cursor, Gemini CLI and Windsurf can read and drive Traxcope. Set it up in Preferences → AI apps (MCP). Tools that change something ask you first, in the Traxcope window.
• Comm Map. A new view that shows which tasks and ISRs talk through which kernel object (queues, semaphores, mutexes, event groups, stream and message buffers, timers, task notifications), how often and how fast. Beside the map, a problem list says what went wrong and why: lost signals, dropped data, lock waits and timeouts, each with its usual cause ("Control was waiting for flashLock, held by Logger"). It works the same on a one-minute capture and on a recording weeks long. The map is open to every tier; the problem list needs Standard or Professional (Manual chapter 24).
• Trigger Studio: kernel object conditions (Professional). Fire a trigger on a lost signal, dropped data, a lock wait or a timeout on any object. These are the same rules as the Comm Map's problem list.
• Linux applications (SDK). TraxProbe now runs inside a Linux program, on a PC, embedded Linux, PetaLinux or Yocto. It traces threads, logs, variables and markers, plus pthread mutexes, semaphores, condition variables and read-write locks. Link it in, or attach it to a program without rebuilding it (LD_PRELOAD). With perf permission (root, CAP_PERFMON or perf_event_paranoid <= 0) you also get CPU lanes for every task on the machine and interrupt lanes. In the Trace View each process's threads fold under one lane (Manual chapter 07).
• VxWorks 7 support (SDK), with one ring buffer per core.
• ST-LINK. Traxcope reads RTT through an ST-LINK/V2 or V3 with its own driver, on Windows and Linux. No J-Link is needed.
• Build identity. When the stream starts, Traxcope says whether the device runs the build in the configured ELF, using the GNU build-id where there is one.
• Trace View: CPU load per core; hide lanes.
• Choose what the probe traces while it streams, and mute individual VAR streams.
• Floating License Server kit for Linux and Windows. It covers air-gapped activation by file exchange, running as a service, and a status command. There is a new administrator guide (Manual chapter 05).
• Manual: new chapters for ESP32 (ESP-IDF), Linux applications, the license server and the Comm Map.

Changed

• A Node-Locked license is for one person. It can still be activated on two machines, but only one person uses it at a time. While someone else holds the key, Traxcope runs read-only: recordings open, but nothing new is captured. This lasts until the key is free or you take it over. Taking a key over is limited per day. Releasing an activation from a lost machine is possible once every 30 days. A shared computer (terminal server, remote desktop) needs a license per person. Teams that share licenses use a Floating license.
• End User License Agreement 2.1. It adds the one-person rule, what TraxAI can do on your computer and connected devices, and the seat check a Node-Locked license sends every few minutes. The seat check sends a hash of the key and a pseudonymous person identifier, not a readable user name. Traxcope shows the agreement at startup whenever its version changes, and asks you to accept it.

Fixed

• TraxFault froze Cortex-M3/M4F/M7 boards (SDK). With FreeRTOS and configASSERT enabled, the fault handler hung in the kernel's assert loop. No record was written and the board did not reset. Rebuild your firmware with SDK 2.0.0.
• Multi-core timestamps. On probes with a ring per thread, timestamps were counted per core. That could put cores tens of seconds apart in one recording. They now come from the merged timeline.
• 64-bit targets (SDK): metadata records are now laid out as their count assumes. On 64-bit targets the record count could come out wildly wrong.
• TCP (SDK): a host that disconnects no longer kills the traced process with SIGPIPE.
• Event View: a mutex wait no longer reads as a queue receive. The Delta column measures against the row above it when filtered. A live view that skips events now says so.
• VxWorks (SDK): mutex hold times and ownership are now correct under contention, and timed-out waits are recorded.

Known issues

• Losing a floating license lease mid-stream shows "hourly streaming quota was reached" and disconnects the probe. It should say the license was lost and keep the connection.
• Estimator Studio or Trigger Studio tabs opened before a license downgrade stay open until Traxcope restarts.
• Linux: without perf permission the CPU lanes stay empty, and each session starts with the warning "scheduler not visible: perf denied". The planned fallback that would trace the program's own threads without root does not work yet.

Downloads

File	For
Traxcope-2.0.0-Setup.exe	Windows 10/11, 64-bit (signed by Embedya)
traxcope_2.0.0_amd64.deb	Ubuntu 22.04+ / Debian 12+
Traxcope-2.0.0-linux-x86_64.run	Any x86_64 Linux with glibc 2.35 or newer (self-extracting installer)
Traxcope-2.0.0-linux-x86_64.tar.gz	Portable Linux build

SHA-256 checksums are in SHA256SUMS-2.0.0.txt. To verify, run sha256sum -c SHA256SUMS-2.0.0.txt on Linux, or Get-FileHash <file> in PowerShell.