RE: [ECOS] Scheduler problems, thread delay

["James Yates" <j.yates@quartzuk.com>]

I have looked further into this problem and can see the RTC isr be installed. I turned on Asserts & Tracing to see what was going on and see the following as the scheduler is started:

TRACE: sched.cxx           [ 318] static void Cyg_Scheduler::start()  {{enter
TRACE: sched.cxx           [ 344] static void Cyg_Scheduler::start_cpu()  {{enter
TRACE: mlqueue.cxx         [ 119] Cyg_Thread* Cyg_Scheduler_Implementation::schedule()  {{enter
TRACE: mlqueue.cxx         [ 192] Cyg_Thread* Cyg_Scheduler_Implementation::schedule()  }}returning thread 00815650
TRACE: except.cxx          [ 247] void cyg_hal_deliver_exception() {{enter
TRACE: except.cxx          [ 207] void Cyg_Exception_Control::deliver_exception() {{enter
TRACE: except.cxx          [ 207] void Cyg_Exception_Control::deliver_exception() ((exception number=4, exception info=00815558))
TRACE: except.cxx          [  83] void cyg_null_exception_handler() {{enter
TRACE: except.cxx          [  83] void cyg_null_exception_handler() ((data=00000000, exception=4, info=00815558))
TRACE: except.cxx          [  86] void cyg_null_exception_handler() 'Uncaught exception: 4'

Would I be right in thinking that what is probably happen is that I am getting an RTC isr but due to an error with the VSR table, an exception is being raised which isn't handled? Does this then imply that my VSR table is wrong which is why cyg_thread_delay never returns.

		James Yates



--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss