|Help non-Linux/non-Java embedded C developer make use of Trace Compass [message #1794462]
||Thu, 30 August 2018 21:27
| Buck Fobb
Registered: August 2018
I'm developing C on bare metal ARM Cortex (M3) with a very basic custom OS (no Linux) and am attempting to make use of Trace Compass to trace thread states (very very basic threading), specific finite state machines in the code, call stacks (well, instrumented call enter/exit sequence - not full stack - for short sections of executing code to look for optimizations), etc. TC seems like it could be a great boon to us bare metal developers, if I could figure it out. I'm not a Linux or Java developer, so I'm trying to figure out how to bend TC to my will.
I'm successfully putting basic trace info (event timestamp + test events like ThreadRun, ThreadStop, etc.) into CTF and getting Eclipse to import it. I can see the list/table of events and event contents. However the trace views (call graph analysis, critical path, etc.) don't populate like hope. I'm guessing this is because these are tailored for Linux/LTTng and I'm not presenting info in a format it understands. I've also tried to implement custom xml per the "Data driven analysis" http://archive.eclipse.org/tracecompass/doc/stable/org.eclipse.tracecompass.doc.user/Data-driven-analysis.html#Data_driven_analysis in the Trace Compass User's Guide using xml but not having a ton of success. Not knowing what's going on inside Trace Compass it is difficult to know what the elements and attributes do.
Are there any tutorials geared toward me: bare metal embedded guy (non-Linux/Java) who wants to make use of Trace Compass?
Thanks for any help.
Powered by FUDForum
. Page generated in 0.01679 seconds