On 08/08/2019 14:03, Ravindra Meena wrote:
+Step 4: After successfully connected to the target, we can get event records
+item from QEMU target text format by using the following commands:
+
+.. code-block:: none
+
+ cd rtems-tools
+ ./build/misc/rtems-record -H 169.254.XXX.XXX -p 1234 | head
---
images/user/event-recording-trace.png | Bin 0 -> 9573 bytes
images/user/event-recording-trace.puml | 12 +++
user/tracing/eventrecording.rst| 117 -
3 files changed, 128 insertions(+), 1 deletion(-)
create mode 100644 images/user/event-recording-trace.png
c
> > These patches are not the production side. Is it good to talk about
> > patches here?
>
> Just use your GSoC branches as a reference. In the end it should work
> with the upstream master branches as is without external patches.
>
> Okay
I have added the event recording example and made a push
On 11/06/2019 10:22, Ravindra Kumar Meena wrote:
Yes, it would be good to have a worked out example, however, the
general
description should be independent of this.
The trace stream received on the host was only possible after applying
the two patches in the root directory of rtem
>
> Yes, it would be good to have a worked out example, however, the general
> description should be independent of this.
>
The trace stream received on the host was only possible after applying the
two patches in the root directory of rtems-libbsd and rtems-tools. I mean
it is not from the master
On 11/06/2019 08:28, Ravindra Kumar Meena wrote:
A worked out Qemu example should move to another section.
Are you talking about the current trace stream which is generated by
QEMU target?
Yes, it would be good to have a worked out example, however, the general
description should be in
>
> you can highlight that this is the second version of a patch with the
> "git format-patch -v2" command line option.
>
Okay. Thanks
>
> > +++ b/images/user/event-recording-trace.puml
> > @@ -0,0 +1,12 @@
> > +@startuml
> > +
> > +rectangle Host
> > +rectangle "Target/QEMU Target" as target
>
>
Hello Ravindra,
you can highlight that this is the second version of a patch with the
"git format-patch -v2" command line option.
On 10/06/2019 07:46, Ravindra Meena wrote:
---
images/user/event-recording-trace.png | Bin 0 -> 9573 bytes
images/user/event-recording-trace.puml | 12 ++
I have sent the new patch with the changes pointed out.
Thanks
On Sat, Jun 8, 2019 at 6:48 AM Chris Johns wrote:
> On 8/6/19 3:05 am, Gedare Bloom wrote:> We require that our GSoC Students
> keep
> their contributions visible on
> > their personal GitHub. I recommend that Ravindra stage the wor
---
images/user/event-recording-trace.png | Bin 0 -> 9573 bytes
images/user/event-recording-trace.puml | 12 +
user/tracing/eventrecording.rst| 47 -
3 files changed, 58 insertions(+), 1 deletion(-)
create mode 100644 images/user/event-recording
On 8/6/19 3:05 am, Gedare Bloom wrote:> We require that our GSoC Students keep
their contributions visible on
> their personal GitHub. I recommend that Ravindra stage the work on
> personal GitHub, and post here for review by the community. Merge from
> personal GitHub to git.rtems.org when suffici
On Fri, Jun 7, 2019 at 12:11 AM Chris Johns wrote:
>
> On 7/6/19 3:51 pm, Sebastian Huber wrote:
> > On 07/06/2019 07:21, Chris Johns wrote:
> Should we have something working before we make any additions to the user
> manual?
> >>> It was actually my idea to add this section right now.
On 7/6/19 3:51 pm, Sebastian Huber wrote:
> On 07/06/2019 07:21, Chris Johns wrote:
Should we have something working before we make any additions to the user
manual?
>>> It was actually my idea to add this section right now. My experience is that
>>> documentation which is planned at the
On 07/06/2019 07:21, Chris Johns wrote:
Should we have something working before we make any additions to the user
manual?
It was actually my idea to add this section right now. My experience is that
documentation which is planned at the end of the project is never written.
Great and I also enc
On 7/6/19 3:11 pm, Sebastian Huber wrote:
> On 07/06/2019 05:40, Chris Johns wrote:
>>> +Eclipse to analyse and display trace data graphically. Trace data can be
>>> gathered from
>>> +RTEMS applications via various means, for example:
>>> +
>>> +- :ref:`RTEMS Trace Linker `
>>> +- :ref:`RTEMS Capt
On 07/06/2019 05:40, Chris Johns wrote:
+Eclipse to analyse and display trace data graphically. Trace data can be
gathered from
+RTEMS applications via various means, for example:
+
+- :ref:`RTEMS Trace Linker `
+- :ref:`RTEMS Capture Engine `
+- :ref:`RTEMS Event Recording `
+
+Event Recording
Thank you for switching to PlantUML.
On 7/6/19 2:45 am, Ravindra Meena wrote:
> ---
> images/user/event-recording-trace.png | Bin 0 -> 7784 bytes
> images/user/event-recording-trace.puml | 12 ++
> user/tracing/eventrecording.rst| 39
> -
> 3 f
---
images/user/event-recording-trace.png | Bin 0 -> 7784 bytes
images/user/event-recording-trace.puml | 12 ++
user/tracing/eventrecording.rst| 39 -
3 files changed, 50 insertions(+), 1 deletion(-)
create mode 100644 images/user/event-recordin
18 matches
Mail list logo
