Trice — Trace IDs for Embedded C

Hi, I am Trice.⁰

Log and trace in as few as 6 CPU clocks per call.¹
Printf-like calls.² Compact records.³ Even from interrupt handlers.⁴
Compiler-independent.⁵ ID-free user code.⁶ Aliases for legacy code.⁷

Explore Trice in the Guide

See the moments that matter: a fleeting interrupt, a changing sensor value, or the response to a command.⁸ Trice brings them into view while your firmware runs. Read events as text,⁹ work with structured values,¹⁰ or watch measurements come alive in a plot.¹¹

The Guide helps you choose your first experiment, discover the features, and find the details for your own project. Start on your PC, then explore what Trice can do on your hardware.

Small demo animation

If Trice helps your work, support the project.

---

Footnotes:

0. The name combines TRace IDs, C and Embedded systems.
1. Record creation in an optimized configuration; transmission is handled separately. See the measurement and configuration.
2. Printf-like syntax and supported formats.
3. Compact binary records and transfer size.
4. Trice calls can be used directly inside interrupt handlers. The example output shows interrupt-originated ISR: messages mixed with events from normal application code.
5. Target-code portability and modularity.
6. Bind keeps numeric IDs out of user log calls; see its supported constructs and compiler requirements.
7. Aliases for existing logging and assert macros.
8. Asynchronous Broadcast Commands and responses.
9. Text output and event boundaries.
10. Structured Logging with named values.
11. Live visualization with the LabPlot demo.