On 02/10/2018 08:48, Catalin Demergian wrote:
Hi,
This assert may not be directly related to my issue because I
reproduced it a few times (with RTEMS_DEBUG enabled in the build)
without seeing the assert being hit. What I discovered is that after a
while _Scheduler_priotity_Unblock is not calle
Hi,
This assert may not be directly related to my issue because I reproduced it
a few times (with RTEMS_DEBUG enabled in the build)
without seeing the assert being hit. What I discovered is that after a
while _Scheduler_priotity_Unblock is not called for my task anymore.
And since _Scheduler_prioti
I'm using 4.11.2
Catalin
On Mon, Oct 1, 2018 at 10:16 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 01/10/2018 08:55, Catalin Demergian wrote:
> > Hello,
> > After enabling RTEMS_DEBUG like you told me, I found the test I left
> > running over the weekend like this
> >
> >
On 01/10/2018 08:55, Catalin Demergian wrote:
Hello,
After enabling RTEMS_DEBUG like you told me, I found the test I left
running over the weekend like this
[/] #
[/] #
[/] # assertion "first != _Chain_Tail( &ready_queues[ index ] )"
failed: file
"../../cpukit/../../../stm32f7/lib/include/
