rtems_message_queue_receive / rtems_event_receive issues

[Sebastian Huber]

On 25/09/2018 13:37, Catalin Demergian wrote:
> Hi,
> what does it mean exactly to run with the RTEMS master ?

The RTEMS Git master branch.

>
> The problem is like this: I initially had a USB stack for my STM32F7 
> that was working on a bareboard (no OS)
> Starting from that, I integrated that USB code in RTEMS 4.11.2. This 
> was a long duration task, until I got it working
> a spent a lot if time changing the makefiles first to add my new files 
> to the project, then analysing the USB bus with a sniffer
> and various other stuff to see it working.
>
> To try with another RTEMS version would mean redo the USB integration; 
> I can't consider this as a viable option because it
> would take a long time until I would be in the same place, and there 
> are no guarantees it will not fail in the same way.
> I think the only good option would be to debug in my code base and 
> understand what's going on.

The RTEMS APIs didn't change that much between the RTEMS 4.11 release 
and the Git master. Did you add your code to the RTEMS source tree?

There are new fatal errors in the master branch
INTERNAL_ERROR_THREAD_QUEUE_ENQUEUE_STICKY_FROM_BAD_STATE,
INTERNAL_ERROR_BAD_THREAD_DISPATCH_DISABLE_LEVEL, and
INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT
which may help to detect a problem you encountered.

You can also use the --enable-rtems-debug configure option. It is 
available in RTEMS 4.11, however, in the RTEMS master there are more 
internal consistency checks. This would be helpful to track down a 
potential scheduler bug (I don't expect a bug in this area).

-- 
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.