RTEMS Posix lock failure
joel.sherrill at OARcorp.com
Mon Jan 6 17:23:31 UTC 2014
On 1/6/2014 10:58 AM, John Harwell wrote:
> When RTEMS entries the Internal_error_Occurred() routine, it is within
> the context of an ISR, according to the value of _ISR_Nest_level.
> After reading the documentation on rtems_fire_after() here
> I realized that because my function attempts to acquire a global
> mutex lock within an ISR context, RTEMS will correctly lockup. Now
> that I know the cause, restructuring my code should be
> relatively simple.
You could use the timer server version of the calls but acquiring a lock
potentially negatively impact other timers managed by the server.
> Thanks for your help,
> John Harwell
> High Reliability Software Section
> Communications and Embedded Systems Department
> john.harwell at swri.org
> Office: 210-522-5965
> Southwest Research Institute (SwRI)
> 6220 Culebra Road, San Antonio, TX 78238-5166
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill at OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users