Re: RTAI 3.9 lock on

Peter Soetens <[email protected]>
Newsgroups gmane.science.robotics.orocos.devel
Message-ID <CAMYDobVjOEX6eEzUJ0jZr1imNMi-tpx3NQKYda-8NTg3Unx5FQ@mail.gmail.com>
On Thu, May 2, 2013 at 11:51 AM, <[email protected]> wrote:

> I  tried to compile with the option  cmake . -DOROBLD_OS_AGNOSTIC=OFF
> -DOROSEM_OS_LXRT_CHECK=ON but it didn't change anythings.
>
> I changed by hands the file lxrt/fosi.h according to the patch but there
> are
> many error of type :
>
> [ 12%] Building C object
> rtt/CMakeFiles/orocos-rtt-lxrt_dynamic.dir/os/lxrt/fosi.c.o
> /home/laboratorio/rock/tools/rtt/rtt/os/lxrt/fosi.c: In function
> ‘rtos_sem_init’:
> /home/laboratorio/rock/tools/rtt/rtt/os/lxrt/fosi.c:94: error: ‘rt_sem_t’
> has no member named ‘sem’
> /home/laboratorio/rock/tools/rtt/rtt/os/lxrt/fosi.c:95: error: ‘rt_sem_t’
> has no member named ‘sem’
> /home/laboratorio/rock/tools/rtt/rtt/os/lxrt/fosi.c: In function
> ‘rtos_sem_destroy’:
> /home/laboratorio/rock/tools/rtt/rtt/os/lxrt/fosi.c:101: error:
> ‘rt_sem_t’ has no member named ‘sem’
>
> If I change the functions in this way
>      int rtos_sem_init(rt_sem_t* m, int value )
>      {
>          CHK_LXRT_CALL();
>
> //        m->sem = rt_sem_init( rt_get_name(0) , value);
> //       return m->sem == 0 ? -1 : 0;
>         m= rt_sem_init( rt_get_name(0) , value);
>          return m == 0 ? -1 : 0;
>      }
>

You can keep this fix for now...


>
> it compiles but the system hangs during the core-test.
> Just one time I read on the screen before the system hangs :
> CANNOT INIT LXRT Tread gloabalEngine....
>

The I probably know what went wrong... could you check that the "Number of
LXRT slots" in the RTAI kernel configuration is at least 1000 ?

See the installation manual:
http://www.orocos.org/stable/documentation/rtt/v2.x/doc-xml/orocos-installation.html#general_setup_rtai

Peter

-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.