Gilles Chanteperdrix wrote:
> Sherk Chung wrote:
>> We are using Xenomai on an AT91 ARM board. We wrote a program that
>> creates multiple Xenomai tasks, which use rt_mutexes to when accessing
>> some shared global variables. The rt_mutexes used are declared
>> globally, as in the example below. Since the objects sharedVar1,
>> shredVar2, etc. are declared on the global stack, the rt_mutexes are
>> created prior to main() getting executed. The problem we are having is
>> that our program is causing our HW to freeze up on program load, it
>> never gets to the first line of main(), and our HW supplier pointed out
>> that we must call mlockall() and the set up the signal handlers before
>> creating the mutexes.
>>
>>
>>
>> Is there a problem with creating rt_mutexes the way we are doing, and
>> should that cause the ARM board to freeze? (the same program loads fine
>> on an x86)
>
> No, there should not be any problem. Creating a mutex does not require a
> particular context, only locking it does.
>
> Which version of Xenomai do you sue, with which version of the I-pipe patch?
Is not there any output on the kernel (serial) console?
--
Gilles.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
