rtems_message_queue_receive / rtems_event_receive issues

[Joel Sherrill]

Also the subject says message queue and event receive but the scenario
described is just about events. Events do not queue. They are one deep. If
the receiving task ever misses an event send (2 sends before.one receive),
then the described scenario.is expected.

--joel

On Thu, Sep 20, 2018, 7:44 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> Hello Catalin,
>
> could you please check if you have the same behaviour on the RTEMS master.
>
> On ARMv-7M and RTEMS exceptions and interrupts with a priority value of
> less than 0x80 are non-maskable with respect to the operating system and
> therefore must not use operating system services. If you use operating
> system services in non-maskable interrupts, then the system behaviour is
> quite undefined.
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20180920/7fb8427e/attachment.html>