Re: assertion "first != _Chain_Tail( &ready_queues[ index ] )"

2019-05-21 Thread Sebastian Huber
On 22/05/2019 04:34, Jython wrote: finally i find it's usleep call causes that while(retry && ((RCC_BDCR & 0x02) == 0))  // External low-speed oscillator ready { retry--;             usleep(5000);             #if 0             volatile int k = 0;             (voi

Re: assertion "first != _Chain_Tail( &ready_queues[ index ] )"

2019-05-21 Thread Jython
finally i find it's usleep call causes that while(retry && ((RCC_BDCR & 0x02) == 0)) // External low-speed oscillator > ready > { > retry--; > > usleep(5000); > #if 0 > volatile int k = 0; > (void)k; > int j; > for(j = 0; j <

Undefined reference using Gaisler's rcc-1.3-rc6-gcc GR712RC SMP BSP library

2019-05-21 Thread Pete Cunningham
Folks, I'm using Gaisler's pre-compiled rcc-1.3-rc6-gcc GR712RC SMP BSP library (rtemsbsp.a in the gr712rc_smp/lib directory). I'm trying to integrate the SMP compatible version of the greth ethernet driver that is built into the gr712rc BSP library. When I use the code listed in rtems_net.c and

Re: assertion "first != _Chain_Tail( &ready_queues[ index ] )"

2019-05-21 Thread Gedare Bloom
This just covers up some bug. When the system overhead increased to check the stack contents, it might modify the timing enough to obscure a race condition. Since the stack checker didn't report anything, you probably don't have a blown task stack. (But you could still have a function stack overflo