Hello Ravindra,
thanks for the update.
On 11/06/2019 08:18, Ravindra Kumar Meena wrote:
Plan for the week:
1. Update the event recording documentation(sent the patches)
2. Build a custom converter that can transform TCP streams and files
with record items into CTF.
For 2nd point of the plan, we have to write the decoder(source plugin).
This would involve understanding the current rtems trace format
With "rtems trace format" I guess you mean the format used by the Event
Recording. Could you please elaborate this a bit more what you mean with
understanding. The format is very simple. It is just a timestamp, an
event number and some event specific data.
Getting timestamps in CLOCK_MONOTONIC nanosecond values is a bit tricky,
however, this is already handled by the client:
https://github.com/rmeena840/rtems-tools/commit/0a279786b73197973dc8a5a5f7818a7669714216
Did you already work on a TSDL description of the format?
and
codebase. I will also try out the decoder(source plugin) example shared
by the babeltrace community.
Ok.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
