GSOC2016: Improvements in RTEMS Tracing Framework

[Isaac Gutekunst]

Hi Vivek,

This is looking good!

I somewhat sketchy solution for getting binary files off a target is to print them as intel hex, and copy them from the terminal. If the Zynq bsp supports networking, you could setup a TFTP server. My ugly trace implementation implements the lttng-live protocol for getting the CTF stream off the target.

See https://github.com/lttng/lttng-tools/blob/master/doc/live-reading-protocol.txt

Chris, do you think it's worth going down this path yet? I think this is the best long term solution, as it makes RTEMS targets with networking support remotely traceable with babeltrace and Trace Compass.

I'm a little confused how the BSD, old style, and lwip networking stacks differ, and whether it would be possible to target all three easily. My understanding is that the existing stack, and the BSD stack both integrate into the RTEMS filesystem (have file descriptors), while LWIP has some super ugly macros that redefine read/write/etc.

Isaac




On 05/16/2016 02:41 PM, vivek kukreja wrote:
> Hello all,
>
> Thanks for the prompt answer regarding libBSD drivers Chris. I found a few links and have setup Qemu for Xilinx Zynq A9.  I will try to build drivers for USB and Ethernet and run a few examples on qemu by next week.
>
> I have made some rudimentary changes in rtems-tld and rtrace shell utiltiy to print traces in CTF. I tested these changes on fileio.exe example for both sparc/erc32 and arm/xilinx_zynq_a9_qemu(tested on qemu). I am working on producing metadata in TSDL format as required by CTF 1.9. I will send patches for review this week.
>
> Once we have trace in CTF we can write Babeltrace scripts for testing the output. However, CTF bitstream is produced on target and pulling it on host is tricky. Is there any solution apart from copy-pasting from terminal?
>
> Also, I'm trying to trace user-extensions by running multiple applications on Qemu for better understanding. These traces will be converted to CTF next.
> Any comments regarding my project plan or progress are welcome.
>
> Regards,
> Vivek
>
> On Tue, May 10, 2016 at 2:40 PM, vivek kukreja <vivekkukreja5 at gmail.com <mailto:vivekkukreja5 at gmail.com>> wrote:
>
>     Hello Chris, Joel, Isaac,
>
>     Sorry for the delay in getting back. I was ill for the last couple days.
>
>     Here is a quick status update,
>
>     * Setup my work environment. Earlier I was using RTEMS version 4.11 because I could not download the source code for 4.12 from GIT in my university network. I have not moved to the new version.
>
>     * Compiled the Xilinx Qemu BSP. I am unable to find help on how to run the BSP on Qemu however. I will send another mail to ask for help on the list.
>
>     * Prepared some documents to plan the project and track progress. Please take a look at these documents, and recommend any changes.
>     https://drive.google.com/open?id=0B2FBdgOy1yWXWE44RnhNLXUwLVU
>
>     * Started studying Babeltrace to understand its capabilities.
>
>     In the rest of the week, I will
>
>     * Study the source code for scheduler events tracing in User Extensions.
>
>     * Ensure that I have the BSP running on Qemu.
>
>     * Port my experimental changes in RTEMS TLD to the version 4.12 and share patches with you, to get some feedback.
>
>     On Wed, Apr 27, 2016 at 6:45 PM, vivek kukreja <vivekkukreja5 at gmail.com <mailto:vivekkukreja5 at gmail.com>> wrote:
>
>         Hello all
>
>         Thank you for your help and support. My proposal for Tracing tool
>         improvements has been accepted in GSOC 2016.
>
>         I will be occupied with university exams for the rest of this week. I
>         will update the RTEMS page over the weekend. I will be able to commit
>         full-time to the project in the coming weeks during my vacations.
>
>         I am thrilled to start working on this project!
>
>         Regards,
>         Vivek
>
>
>