Hello Michele,
On 25/03/2020 16:13, Michele Dekleva wrote:
My customer request me to use RTEMS 4.11.3 so i need to use this version.
this makes little sense given that we are about to release RTEMS 5 soon.
Also consider that the FPGA based CortexM3 use a 133 MHz clock so I’m
quite surprise
synchronization between tasks, avoidable with minimal modifications on task’s
source code.
Best Regards.
Dr. Michele Dekleva
Da: Joel Sherrill
Inviato: mercoledì 25 marzo 2020 14:20
A: Sebastian Huber
Cc: Michele Dekleva ; rtems-us...@rtems.org
Oggetto: Re: R: sptest SP06 strange
On Wed, Mar 25, 2020, 8:06 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Michele,
>
> I am not sure if the RTEMS 4.11 test suite works with an interrupt
> driven console driver. I would use the RTEMS master for new BSPs anyway.
>
You should use polled or the buffered tes
Hello Michele,
I am not sure if the RTEMS 4.11 test suite works with an interrupt
driven console driver. I would use the RTEMS master for new BSPs anyway.
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
r a test problem ?
If you consider this a BSP porting problem could suggest me how to try to
solve it ?
Best Regards
Dr. Michele Dekleva
-Messaggio originale-
Da: Sebastian Huber
Inviato: mercoledì 25 marzo 2020 11:01
A: Michele Dekleva ; users@rtems.org
Oggetto: Re: sptest SP06 strange behavio
Hello Michele,
both tests should run without errors. Which RTEMS version do you use?
A frequent error in Cortex-M BSPs are improper interrupt priorities.
Make sure all interrupt priorities are set up correctly:
https://docs.rtems.org/branches/master/cpu-supplement/arm.html#interrupt-processin
I'm porting RTEMS to a new ARM target (Microsemi M2Sxxx FPGA based Cortex
M3).
I'm executing the SPTEST tests to validate the BSP.
There are strange behavior on some tests; for example:
. Test SP02 fails when the third task is trying to be created:
the return code say TOO_MANY; i
