RTEMS scheduler bug ?

[Catalin Demergian]

Yes, I made a test, _ISR_Get_level() can be used on my CPU.

About --enable-rtems-debug .. it doesn't seem to enable the RTEMS_DEBUG
flag in the code, I tried --enable-rtems-debug=yes as well ..
is there maybe a combination of options to enable RTEMS_DEBUG in the code ?
I'm afraid I will run for nothing without it, it seems the
Assert is defined to nothing if this is not set right.

regards,
Catalin



On Fri, Mar 29, 2019 at 3:36 PM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> On 29/03/2019 14:31, Catalin Demergian wrote:
> > Sure, I will build and try.
> > Is _ISR_Get_level() something CPU-specific ? I mean we use it to
> > figure out if interrupts are enabled or not, right ?
> > forgot to say, I use a STM32H7. Does _ISR_Get_level work on it ?
>
> I would run test
>
> testsuites/sptests/sp37
>
> to figure out if it works.
>
> >
> > Also, I thought the scheduler code runs with interrupts enabled, I
> > mean doesn't it use the tick interrupt itself ?
> > How does that work on RTEMS ?
>
> Some critical sections of the scheduler are protected by disabled
> interrupts.
>
> --
> 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20190401/b0ad213f/attachment.html>