Conversation

It's cool to see things like interrupt.memfault.com/blog/trice (and zephyr's version) becoming common for C folks as well. As far as I can tell, the "deferred logging revolution" seems to have all started with

@FerrousSystems

' #knurling defmt tool, but there's always SOME prior art :)

interrupt.memfault.com

Tracing & Logging with the TRICE Library (Interrupts too!)

Best practices on embedded logging and tracing and an introduction to the open-source library Trice

Replying to

and

Cool! I went through a similar process. Eventually decided that adding complexity of an extra build step was not worth it so I started converting the performance sensitive statements to binary logs.

Replying to

and

I do wonder though. Is this an actual parser, or a regexp hack?

Replying to

and

No idea how the TRACE library works. defmt works by placing the interned strings into an unused linker section, and decodes it automatically when you give it an ELF file and a stream of logs.

Replying to

and

Oh nice. I tried something like that for C but couldn't figure it out how to do it for const strings.

Replying to

and

At least in Rust, with the benefit of macros, defmt is pretty well documented, even in impl details: defmt.ferrous-systems.com/interning.html

Replying to

and

Thanks. The issue I had is how to annotate a const string without first binding it to a variable like answer here:

stackoverflow.com

How to put c-style strings (function arguments) in the specific section?

I want to put some functions in a specific section named ".xip.text", but the read only data cannot put in that section. The following is my test code: #include void foo(void)

Replying to

and

But it might be possible to wrap it with a C expression statement in a macro, do a variable binding in that expression statement and add the annotation.

Replying to

and

Yeah, something like that might work. I think defmt relies on the linker to gc all the strings out, after creating it as a static string in the specific section. I think the defmt section is expressly excluded from the final binary.

Replying to

and

(Rust procedural macros are also much more powerful, basically compiler plugins, so doing shenanigans like generating random identifiers for each string and encoding as JSON is much easier)