Hi Sebastian, I followed https://diamon.org/ctf/ and tried to code. I forked the rtems-tools and made a commit. https://github.com/rmeena840/rtems-tools/commit/e1917f5afeba051e4e87285eed9e36b2591dc643
Please have a look and let me know if I am going in the right direction. I would like to ask one thing that at 5.1 of https://diamon.org/ctf/ it is mentioned that "trace.packet.header" is required. Since, It was not there I was getting error at: trace { /* ... */ packet.header := struct event_packet_header; }; Is there any need requirement of file or library? On Mon, May 20, 2019 at 11:23 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 20/05/2019 07:46, Ravindra Kumar Meena wrote: > > On Thu, May 16, 2019 at 2:54 PM Sebastian Huber > > <sebastian.hu...@embedded-brains.de > > <mailto:sebastian.hu...@embedded-brains.de>> wrote: > > > > On 16/05/2019 11:05, Ravindra Kumar Meena wrote: > > > > The record data format is described in > > cpukit/include/rtems/recorddata.h. If you think this documentation is > > insufficient, unclear and needs to be improved, then please do > > this as > > part of the project. > > > > > > I can see there is a fixed set of 512 system reserved and 512 > > user-defined events. The total size of the record i item is 32 bits > > out of which 10 bits are allocated to the event and 22 bits are > > allocated to timestamps. The record item is defined in two formats 32 > > and 64 bits. > > Yes, the target depends if the data member is 32-bits or 64-bits. The > reason for this is that we need enough space to store pointers. > > > > > With the Qemu simulation you set up during the project proposal, > > you are > > able to get a TCP stream of record items from the Qemu target to your > > host. You also have an example client which sorts this stream, > > determines the timestamps and prints the items. > > > > > > The stream print function is defined at > > rtems-tools/misc/record/record-main.c inside function "static void > > print_item( FILE *f, const client_item *item )". This function prints > > the TCP stram. > > Yes. > > > > > Your job is now to convert the record item stream into a CTF stream. > > > > > > In order to convert to CTF, we need to know the structure of it. I > > followed this page https://diamon.org/ctf/. The CTF stream packet has > > three major parts header, context, concatenated events(header, > > stream-specific context, event-specific context, payload). > > Yes. > > > > > *I would like to point out one thing that I recently pulled the > > rtems-libbsd and tried to build it again. The build fails due to > > recent commits made in the master branch(after the commits "Update due > > to API changes").* > > If you update rtems-libbsd, then also update rtems and build the BSP > again, then build the libbsd. > > > * > > * > > Thanks > > > > > > > > -- > > 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 > > <mailto:sebastian.hu...@embedded-brains.de> > > PGP : Public key available on request. > > > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > > > > > > > > -- > > *Ravindra Kumar Meena*, > > B. Tech. Computer Science and Engineering, > > Indian Institute of Technology (Indian School of Mines) > > <https://www.iitism.ac.in/>, Dhanbad > > -- > 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. > > -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School of Mines) <https://www.iitism.ac.in/>, Dhanbad
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
