The most likely cause of this test failing is because the timer is not getting configured correctly and the 'wait_for_interrupt' in 'preempt_count_func' to never return. sel4test here will use whatever the default hardware timer for the platform is. For the am335x this looks like the 'DM timer'. Possible problems are * Timer not being configured correctly and not counting * Interrupt for timer not being handled or being lost. Interrupt would be 'lost' if you are listening for the wrong IRQ number * Using a simulator that does not actually emulate the particular timer hardware My advice would first to be confident that the timer is counting accurately and giving you interrupts (i.e. wait_for_interrupt returns at the timers periodic rate).
Adrian
On 16/02/15 10:08, Tim Newsham wrote:
while running the am335x port through the sel4 test suite I'm getting a hang in the PREEMPT_REVOKE test. It appears the revoke_thread is getting created but it is never getting executed and hence the wait_for_helper on the revoke thread is hanging indefinitely.. Any idea what would cause this behavior?
Tim
Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
________________________________
The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.