Re: Rtems-test cortex-m3

are waiting for revision. -Disable-priority_mask: this patch does not apply directly and rtems is running without it. So I run the rtems-test script: ./rtems-test --log=lm3s6965_qemu --timeout=60 --rtems-bsp=lm3s6965_qemu --rtems-tools=/home/aurelio-remonda/rtems/install /home/aurelio-remonda

Re: Rtems-test cortex-m3

On Mon, Jan 11, 2016 at 3:47 AM, Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: > > > On 08/01/16 17:41, Aurelio Remonda wrote: >> >> Thanks for your answers! I am running the tests for >> realview_pbx_a9_qemu for the moment. >> I

Re: Rtems-test cortex-m3

Thanks for your answers! I am running the tests for realview_pbx_a9_qemu for the moment. I have a few questions if you don't mind With the git repository version of rtems ./rtems-test --log=realview_pbx_a9_qemu --rtems-bsp=realview_pbx_a9_qemu --rtems-tools=/home/aurelio-remonda/rtems_a9/install

Rtems-test cortex-m3

-bsps. For example it shows armcortexa9, armcortexa9-run and realview_pbx_a9_qemu board wich, from what i understand, has a cortex a9. So this does not support what im trying to test? If it doesn't can you give me a hint of how to add it? Thank you. -- Aurelio Remonda Software Engineer San

Rtems-testing bsp add

to modify rtems-testing code or rtems code as well? If im wrong with this approach please let me know, or if someone can give me some hints i will be glad to add this bsp. Thank you in advance. -- Aurelio Remonda Software Engineer San Lorenzo 47, 3rd Floor, Office 5 Córdoba, Argentina Phone: +54

[PATCH] Add pre global constructors hook

Having an optional function that could be called prior to the construction of any global objects would be very useful. This is being discussed in the C++Embedded mailing list, in this thread: http://www.open-std.org/pipermail/embedded/2014-November/000226.html For example, we would like to use

[PATCH] [rtems-testing] Enable Rtems tests samples

This patch enables rtems tests samples on the do_one script. When setting up the environment for testing stdlibc++ you need this test samples to check everything it's ok before running the gcc test suite. This check consists on running a sample (i.e ticker.exe) making sure it behaves as it

[PATCH] [rtems-testing] Update environment README

This patch update the README file on /rtems-testing: *Added comments about bootstrap and RTEMS building steps. *Added comments about RTEMS test samples. *Updated binutils, newlib and gcc repositories using git now. *Updated gdb, autoconf and automake repositories using ftp sites now. --- README

Re: [PATCH] [RTEMS] Update RTEMS thread model

mple but multiple ways to solve. Just need to figure out the best way. > > -- Aurelio Remonda Software Engineer San Lorenzo 47, 3rd Floor, Office 5 Córdoba, Argentina *Phone:* +54-351-4217888 / 4218211 <http://www.tallertechnologies.com> <http://www.tallertechnologies.com> __

Re: [PATCH] [RTEMS] Update RTEMS thread model

< sebastian.hu...@embedded-brains.de> wrote: > > > On 17/09/15 16:36, Aurelio Remonda wrote: > >> It is printing the "real time" but the time is set to a date early >>> >in the RTEMS development history. Look at the year. That's about the >>> >ti

Re:[PATCH] [RTEMS] Update RTEMS thread model

mind: where i can find the realview_pbx_a9_qemu.exp file? I can't find it in dejagnu/boards. I did try making one (basically a copy of rtems-i386-qemu.exp with modifications), though. However, when I try: make check 'RUNTESTFLAGS= SIM=realview_pbx_a9_qemu RTEMS_MAKEFILE_PATH=/home

Re: [PATCH] [RTEMS] Update RTEMS thread model

On Fri, Sep 11, 2015 at 11:34 AM, Joel Sherrill <joel.sherr...@oarcorp.com> wrote: > > > On 9/11/2015 9:21 AM, Aurelio Remonda wrote: > >> The test runners are in "sim-scripts" make sure a "realview_pbx_a9_qemu >>> -i ticker.exe" produces t

Re:[PATCH] [RTEMS] Update RTEMS thread model

> The test runners are in "sim-scripts" make sure a "realview_pbx_a9_qemu > -i ticker.exe" produces the expected output. Hi, silly question here, running ticker gave me the elapsed times but not in 'real time'. It prints 09:00:00, 09:00:04,..., 09:00:34 immediately. Is this a normal behaviour