Re: Error in Trace-buffering example

On 19/03/2018 03:44, Joel Sherrill wrote: > On Mar 18, 2018 6:48 AM, "Vidushi Vashishth" > wrote: > > Hello! > > I am hoping to apply to Gsoc'18 for the runtime tracing project. I am > following the RTEMS tracing documentation [1] and have been trying to r

Re: autotools build fail from rsb

On 19/03/2018 03:23, Vijay Kumar Banerjee wrote: > I have tried  > perl-5.24.3 On FreeBSD I have: ruru rtems $ type perl perl is a tracked alias for /usr/local/bin/perl ruru rtems $ perl --version This is perl 5, version 24, subversion 3 (v5.24.3) built for amd64-freebsd-thread-multi I do not h

Re: RTEMS monitor commands and the shell

Thomas, Paul and Sebastian, thank you for the feedback. It seems like it would be nice to have this command controlled somehow and it is something that should be fixed. I will take a look and see what I can do and will report back with any issues or a patch. Again thanks Chris On 16/03/2018 18:4

Re: Error in Trace-buffering example

On Mar 18, 2018 6:48 AM, "Vidushi Vashishth" wrote: Hello! I am hoping to apply to Gsoc'18 for the runtime tracing project. I am following the RTEMS tracing documentation [1] and have been trying to run the fileio trace sample to familiarise with how traces are generated. I have set the rtems-pa

Re: autotools build fail from rsb

On Mar 18, 2018 11:23 AM, "Vijay Kumar Banerjee" wrote: I have tried perl-5.24.3 perl-5.22.4 perl-5.20.3 still getting the same error, it be coming from something else By any chance can this be worked around by disabling documentation for what is being built? -- vijay On 18 March 2018 at 16

Re: autotools build fail from rsb

I have tried perl-5.24.3 perl-5.22.4 perl-5.20.3 still getting the same error, it be coming from something else -- vijay On 18 March 2018 at 16:15, Vijay Kumar Banerjee wrote: > > > -- vijay > > On 18 March 2018 at 16:13, Gedare Bloom wrote: > >> On Sun, Mar 18, 2018 at 6:41 AM, Gedare Bloom

Re: x86_64 port and BSP (GSoC 2018)

On Mar 18, 2018 5:37 AM, "Gedare Bloom" wrote: On Sat, Mar 17, 2018 at 2:32 PM, Joel Sherrill wrote: > > > On Sat, Mar 17, 2018 at 1:09 PM, Gedare Bloom wrote: >> >> On Sat, Mar 17, 2018 at 11:58 AM, Amaan Cheval >> wrote: >> > First off, thank you so much for the prompt and detailed response!

Re: GSoC'18 proposal - Porting SDIO driver and benchmarking

Am 18.03.2018 um 14:22 schrieb Udit agarwal: > Hi all, > Here's the link to my proposal: > https://docs.google.com/document/d/15Ut9FLAV3Y0Up1Qn02ys6KAb2QhtReF_P-wNR861NMo/edit?usp=sharing > > Please have a look, and comment where ever needed. > I tried my best to make time-line as realistic as pos

GSoC'18 proposal - Porting SDIO driver and benchmarking

Hi all, Here's the link to my proposal: https://docs.google.com/document/d/15Ut9FLAV3Y0Up1Qn02ys6KAb2QhtReF_P-wNR861NMo/edit?usp=sharing Please have a look, and comment where ever needed. I tried my best to make time-line as realistic as possible. Please feel free to comment in case of any unbalan

Error in Trace-buffering example

Hello! I am hoping to apply to Gsoc'18 for the runtime tracing project. I am following the RTEMS tracing documentation [1] and have been trying to run the fileio trace sample to familiarise with how traces are generated. I have set the rtems-path to the installed BSP erc32 in the fileio-trace.ini.

Re: autotools build fail from rsb

-- vijay On 18 March 2018 at 16:13, Gedare Bloom wrote: > On Sun, Mar 18, 2018 at 6:41 AM, Gedare Bloom wrote: > > Vijay, > > > > On Sun, Mar 18, 2018 at 6:36 AM, Vijay Kumar Banerjee > > wrote: > >> > >> I have set the PATH like this > >> /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/hom

Re: autotools build fail from rsb

On Sun, Mar 18, 2018 at 6:41 AM, Gedare Bloom wrote: > Vijay, > > On Sun, Mar 18, 2018 at 6:36 AM, Vijay Kumar Banerjee > wrote: >> >> I have set the PATH like this >> /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/lunatic/.local/bin:/home/lunatic/bin >> >> I'm still getting the same err

Re: autotools build fail from rsb

Vijay, On Sun, Mar 18, 2018 at 6:36 AM, Vijay Kumar Banerjee wrote: > > I have set the PATH like this > /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/lunatic/.local/bin:/home/lunatic/bin > > I'm still getting the same error > > > -- vijay > > On 18 March 2018 at 16:01, Gedare Bloom wro

Re: autotools build fail from rsb

I have set the PATH like this /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/luna tic/.local/bin:/home/lunatic/bin I'm still getting the same error -- vijay On 18 March 2018 at 16:01, Gedare Bloom wrote: > On Sat, Mar 17, 2018 at 12:37 PM, Joel Sherrill wrote: > > I answered what I

Re: x86_64 port and BSP (GSoC 2018)

On Sat, Mar 17, 2018 at 2:32 PM, Joel Sherrill wrote: > > > On Sat, Mar 17, 2018 at 1:09 PM, Gedare Bloom wrote: >> >> On Sat, Mar 17, 2018 at 11:58 AM, Amaan Cheval >> wrote: >> > First off, thank you so much for the prompt and detailed response! I >> > really >> > appreciate the help! >> > >>

Re: Improve coverage analysis toolset

Thanks Cillian :) It's great to see it running , I'll do some background reading about RSB, and RTEMS-Tools along with the covoar code . And also work on my python skills. to try rtems-test on a bsp that runs gdb , I tried it on erc32 and that also worked. I'm also waiting for Joel and other me

Re: autotools build fail from rsb

On Sat, Mar 17, 2018 at 12:37 PM, Joel Sherrill wrote: > I answered what I think the cause is on another thread. > > Take the ancient RTEMS autotools out of your PATH while building qemu. Use a > PATH without RTEMS tools in it. I think the ancient automake version we use > must have --help which h

Re: Improve coverage analysis toolset

On 18 March 2018 at 06:51, Vijay Kumar Banerjee wrote: > I guess I couldn't understand properly what you're suggesting , > on the basis of what I understood , > I have set the PATH like this > /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/luna > tic/.local/bin:/home/lunatic/bin > I thi

Re: Improve coverage analysis toolset

On 18 March 2018 at 06:47, Vijay Kumar Banerjee wrote: > It worked ! > That's great! That's the good news then. I was using an old leon3 build and maybe some older Qemu too and I think that's why I didn't see any issues initially. I was hoping you could see the coverage running and the reports