RTEMS scheduler bug ?
sebastian.huber at embedded-brains.de
Fri Apr 5 04:36:43 UTC 2019
On 04/04/2019 15:23, Joel Sherrill wrote:
> On Thu, Apr 4, 2019 at 7:28 AM Sebastian Huber
> <sebastian.huber at embedded-brains.de
> <mailto:sebastian.huber at embedded-brains.de>> wrote:
> On 04/04/2019 14:09, Catalin Demergian wrote:
> > Hi Andrei,
> > thank you for the elaborated answer !
> > I checked my STM32 Cube settings, I have 3 enabled interrupts
> and they
> > all have the preemption priority/sub priority set to zero !
> > it seems I ran into the same issue you had in 2015 :)
> > I will take your advice - change the priorities, regenerate the
> > and see what happens.
> I mentioned this possible problem some months ago:
> Andrei's answer is definitely a bit more elaborate.
> Thanks Andrei! I am glad you are past this but let's do a post-game
> analysis of what
> could be better next time so no one else suffers as much. These are
> random ideas
> and I am open to more.
> + Could this be detected at run-time during setup with a debug option?
This is difficult. Something from the outside destroys your operating
system data structures. This is similar normal memory corruption.
> + Could this be written up in the BSP Guide so at least there is a
> place to reference?
> Perhaps in a generic section on dealing with interrupt controllers
At least for ARM it is documented in the CPU Supplement:
However, who knows that this manual exists and reads it? I would place
this information in the user manual, but this was rejected.
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.
More information about the users