|Re: [embed-cdt-dev] Remove CDT features|
sorry for the late response. I don't have any good suggestions for an open source solution of getting the trace data from the target. Maybe GDB and GDB Tracepoints?.
Once the trace has been retrieved from the target, Trace Compass is definitely a solution to read and visualize the traces. If the format of the trace is one of the built-in formats, then it can be opened in Trace Compass right away. If not, then a parser extension could be created to open the trace in Trace Compass.
Not sure if the following blog about using bare-ctf with the Adapteva chip can give you some pointers.
From: embed-cdt-dev-bounces@xxxxxxxxxxx <embed-cdt-dev-bounces@xxxxxxxxxxx> on behalf of Liviu Ionescu <ilg@xxxxxxxxxx>
Sent: September 23, 2020 2:27 AM
To: embed-cdt developer discussions <embed-cdt-dev@xxxxxxxxxxx>
Subject: Re: [embed-cdt-dev] Remove CDT features
BTW, I forgot to mention, I do have some experience with SEGGER J-Link tracing.
With their proprietary technology (very nice otherwise), the application must be extended with instrumentation code, actually some macros, which were generally called in pairs, like INTERRUPT_ENTER/INTERRUPT_EXIT.
These macros called some functions in a library SEGGER provided, which stored the data into a butter.
>From this buffer, the J-Link continuously downloaded the data to the debugger, which stored it on disk, for later inspection with a dedicated graphical application.
But in this case everything is proprietary, and requires the J-Link probe.
If you know of an open source solution, that can be visualised in Eclipse, that would be useful.
> On 23 Sep 2020, at 08:42, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:
>> On 22 Sep 2020, at 23:47, Bernd Hufmann <bernd.hufmann@xxxxxxxxxxxx> wrote:
>> about bare-metal traces, there is a project that is called bare-ctf  which can be used to create tracers for bare-metal systems. It will output traces in CTF (Common Trace Format) format . Any trace in CTF format can be parsed by default by Trace Compass. Not sure if this what you're looking for.
> There's a lot of interesting stuff there, but the bare-ctf project is a python script doing conversion work.
> That's fine, but the question is what do I convert? Where is the original trace data coming from? How do I configure the compiler & run-time to generate the trace data and how do I get it out of a bare-metal device, which is like an isolated island?
embed-cdt-dev mailing list
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/embed-cdt-dev
Back to the top