FW: RTEMS Message Queue Behaviour

Joel Sherrill joel.sherrill at OARcorp.com
Fri Apr 9 12:28:44 UTC 2010

On 04/09/2010 06:51 AM, Aleix Conchillo Flaqué wrote:
> Then, I don't know. Probably Joel or others can help you, but it seems
> to me an application problem.
> About the message order, this can simply be a task priority issue,
> unless you sent all messages from the same task, which I guess is what
> you did to try this out.
Are the messages sent from ISRs?  That introduces
the possibility of a critical section issue which is not
present if all logging is from a task.

Can you quit printing and simply set a boolean array
for sent/received base on the message number?

Just to confirm .. all message queue sends return
successful, right?

Is the LOGMSG a global variable or potentially
shared between multiple senders?


> On Fri, Apr 9, 2010 at 13:32, Jamie Bowman
> <jamie.bowman at steepestascent.com>  wrote:
>> Aleix
>> My apologies!
>> Good call on the rtems_message_queue_receive parameters. However by chance,
>> both RTEMS_WAIT and RTEMS_NO_TIMEOUT are defined as zero, so it wouldn't
>> change the parameters actually sent to rtems_message_queue_receive.
>> Kind regards
>>         Jamie
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users

More information about the users mailing list