On 8/20/2014 3:06 PM, Hesham Moustafa wrote: > Hi, > > On Wed, Aug 20, 2014 at 9:54 PM, Joel Sherrill > <joel.sherr...@oarcorp.com> wrote: >> Hi >> >> Thanks. >> >> I just pushed this. I did not compile it. Make sure it builds all tests > What about the nop instruction? Should I add a conditional macros in > the init.c file, or create a new macro to mirror l.nop to nop for or1k > targets? Temporarily add to the test. I think the idea of always having nop as a pseudo-mnemonic in gas is still open. Christian for sure hasn't weighed in yet. >> for >> you just like it did before. >> > Thanks for pushing the code. No problem. Hopefully it is ok. Easier to fix after getting the bulk in IMO. >> How is the test pass/fail rate? >> > How can I get this? Is there a script for running all tests or > something similar? rtems-tools/tester/rtems-test is a nice Python tool for running a set of .exe's. It has to be taught how to run the simulator for a particular BSP.
rtems-testing/sim-scripts the older framework which supports more simulators at the moment but does not parallelize the runs. If you want to add it to this, I can help. You should teach rtems-test about running the or1ksim. Chris can give some advice on that. Ideally both frameworks would support the or1ksim BSP but rtems-tester is the new way and preferred. >> Did you get ticker running? >> > Ticker is running but there are still two issues. The first is with > the very long delay of context switches. The second is about the > printf and the possibility of broken context switch (which I debug > currently). To get around the printf problem, I was adding an entry in > buffer_test_io.h for or1k target to force tests to use printk. Gedare > suggested not to push such a solution. :) Hopefully I can take a few minutes and read the assembly for the ISR code next to the SPARC. I need to reproduce what you have first though. -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherr...@oarcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel