DOCS/TRACE DOMAINS/TRACE DOMAIN CATALOG
BKPT DEBUG & VIEWALYZER RS
Trace Domain catalog
Choose a domain by subsystem, inspect its engineering reference, and download the JSON that defines its fields, cards and checks.
Needs: These references describe the current development definitions. Use a BKPT Debug or ViewAlyzer RS build with Trace Domains v1 support. The P2P command additionally needs typed-actions-v1. Each file uses domain API 1; firmware and device prerequisites still apply.
The canonical files live in ViewAlyzer-Examples on GitHub. Each reference links its source and a byte-identical website download. Contribute a domain or correction through a pull request.
Domain catalog · Authoring examples
Domain catalog
Definitions for the listed firmware or recorded channels, with their required inputs and compatibility. Canonical JSON: domains/catalog/.
USB
| DOMAIN / JSON | PURPOSE | REQUIRES |
|---|---|---|
| STM32U575 USBX / ThreadX · JSON | USB controller, CDC transfers, ThreadX waits, error reports, control queue and allocator pressure. | STM32U575 SVD and matching USBX CDC ACM / ThreadX Debug ELF |
Ethernet
| DOMAIN / JSON | PURPOSE | REQUIRES |
|---|---|---|
| STM32N6 Ethernet / lwIP · JSON | Follow frames from the MAC through DMA descriptors and lwIP; distinguish receive pressure, wire errors and stack drops. | STM32N657 ETH_S / RCC_S SVD and exact N6 demo ELF / lwIP layout |
Motion
| DOMAIN / JSON | PURPOSE | REQUIRES |
|---|---|---|
| STM32WB six-axis IMU · JSON | Sensor samples, configuration and consumption rate reveal a stalled reader, bus errors or a reader falling behind the sensor. | STM32WB5MM-DK ISM330DHCX firmware mirrors, matching ELF and STM32WB55_CM4 SVD |
Recorded channels
| DOMAIN / JSON | PURPOSE | REQUIRES |
|---|---|---|
| Joulescope power channels · JSON | Group imported MCU current and power traces under Power. | Existing external MCU current / MCU power channels; recorder or import pipeline supplied separately |
BLE
STM32WB55 BLE suite engineering reference · Download all nine JSON files
These nine files belong to the same STM32WB5MM-DK application. The single reference covers Overview, four GATT slot files, two activity journal files, the ST P2P profile and shared transport, with individual downloads and GitHub sources. Begin with Overview and GATT slots 0–1 for the ST P2P demo. Firmware observation hooks and the matching Debug ELF are required; other STM32WB variants or BLE stacks are not established by these definitions.
Authoring examples
Templates for building your own domain. Adapt the placeholder symbols, registers or recorder before use. The IMU styling example has no supplied firmware producer; use the STM32WB six-axis IMU entry above for the sensor demo. Canonical JSON: domains/authoring-examples/. See the authoring guide.
| EXAMPLE / JSON | PURPOSE | REQUIRES |
|---|---|---|
| IMU channel styling example · JSON | A presentation-only template for user_trace channels; no matching firmware producer is supplied. | Adapt to actual recorder channel names and units; not STM32WB sensor support |
| Packet counter example · JSON | Wrapping counters, a derived rate and an error-count finding. | Firmware must supply packets_completed and packet_errors |
| Ethernet authoring example · JSON | Guarded registers, descriptor ownership and backlog checks for a placeholder MAC. | Replace ExampleMCU registers and ring layout with verified target definitions |
| Middleware queue example · JSON | Structured pointers, occupancy/capacity cards and consumer-progress checks. | Implement or map active_queue, queue_slots, queue_enqueued and queue_drained |
| Typed actions example · JSON | RAM writes, an application mailbox and a register-field action. | Implement matching firmware/mailbox/SVD; actions require explicit debugger Send |
| Instrument sidecar example · JSON | External current samples and a high-current threshold. | Supply sensor-recorder executable and synchronization channel; no sidecar included |
Read the evidence
Probe samples can miss transitions and can span different firmware updates. A configured rate is a request, not proof of achieved throughput. Unavailable, stale or disabled inputs do not mean zero. A finding is evidence of its stated condition, not a unique root-cause diagnosis.
Styling domains annotate recorded channels and do not acquire sensor data. Sampled domains observe firmware/registers; BLE requires an observation adapter. Consuming Ethernet counters can change what a firmware reader subsequently sees. Each reference explains these distinctions.
For setup, use the Trace Domains overview, U575 walkthrough, or desktop guide. For new definitions, use Creating custom Trace Domains.