Re: RTEMS in AMP mode

2018-10-12 Thread Sebastian Huber
On 12/10/2018 11:57, Thawra Kadeed wrote: On 2018-10-12 07:49, Sebastian Huber wrote: On 11/10/2018 17:32, Thawra Kadeed wrote: Thanks a lot Sebastian for your answer. Actually, we are planning to run a multi-core system using a network-on-chip and network interfaces as a physical

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-12 Thread Sebastian Huber
On 12/10/2018 10:40, Catalin Demergian wrote: Hi, I still think it would be worth to try the latest RTEMS master just to make sure we don't search a bug which is already fixed. Also RTEMS 5 has more assertions in the debug configuration. -> is RTEMS 5 stable branch or development ? It is the

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-12 Thread Catalin Demergian
Hi, I still think it would be worth to try the latest RTEMS master just to make sure we don't search a bug which is already fixed. Also RTEMS 5 has more assertions in the debug configuration. -> is RTEMS 5 stable branch or development ? -> what is the link for RTEMS master (where to do a git clone

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-12 Thread Sebastian Huber
On 11/10/2018 15:37, Catalin Demergian wrote: Hi, Yes, there is a call to rtems_task_wake_after in the code; but in that case state should have been STATES_DELAYING, right ? The state = 0x0 = STATES_READY Wait.flags = 0x02 = THREAD_WAIT_STATE_BLOCKED looks suspicious. It should be state =