Re: [Xenomai-help] version of __ipipe_restore_pipeline_head

Re: [Xenomai-help] version of __ipipe_restore_pipeline_head

[Jean-Luc Pamart]

Jean-Luc Pamart a écrit :
> Gilles Chanteperdrix a écrit :
>> Jean-Luc Pamart wrote:
>>  
>>> (...)
>>> realtimedriver: disagrees about version of symbol 
>>> __ipipe_restore_pipeline_head
>>> realtimedriver: Unknown symbol __ipipe_restore_pipeline_head
>>>
>>> My configuration :
>>> xeno 2.3
>>> hal 1.6-03
>>>     
>>
>> I hope you mean Adeos I-pipe 1.7-03, right ?
>>
>>   
>
> Well, not :-(   !
> I use the Adeos I-pipe 1.6-03 which is embedded with the xeno 
> distribution ...
> So, I decided to pass to linux 2.6.20 and Adeos I-pipe 1.7-03
> but after problems of compilation (My linux box is a 2.4 kernel one 
> apparently there is a binutils issue with the 2.4 kernel) I have tried 
> 2.6.19 and  Adeos I-pipe 1.7-03.
>
>  
>>> My linux version is 2.6.19
>>>
>>>
>>> We have __ipipe_restore_pipeline_head symbol in
>>> the kernel :
>>>
>>> c013f7b0 T __ipipe_restore_pipeline_head
>>> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_native]
>>> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_nucleus]
>>> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_rtdm]
>>> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_posix]
>>>
>>> but the module realtimedriver I want to insmod has
>>> been builded with the same sources.
>>>
>>>
>>> So what may I do ?
>>>     
>>
>> You likely changed a kernel option and recompiled the kernel without
>> recompiling the "realtimedriver" module. Try recompiling the module.
>>   
>
> Ok, I have change to 2.6.19 - Adeos I-pipe 1.7-03. After 2 days of
> building my emdedded distribution : all right !
> The realtimedriver can be load and user can be run.
>
> Nevertheless I have a slight but strange problem :
> When trying the user program with Timer int (#0)
> it says "cannot open demodev0"
> But when I change only inc.h like this :
> #define TIMER_INT       14 // for the hard disk
> or
> #define TIMER_INT       11 // for the net board
> it's ok : I have WRITE, READ etc. accordingly with
> the amount of work of the devices.
>
> I have a 100 Hz timer int.
> Perhaps too fast for the realtimedriver ???
> A idea ?
>
>
>
>
>

[Xenomai-help] version of __ipipe_restore_pipeline_head

[Jean-Luc Pamart]

Hello

The rtdm heartbeat example is working fine.
I try now to run a more complete example :
"Hard Real Time Driver Example Tutorial with MMAP using the RTDM (Real 
Time Driver Model)"
(http://www.captain.at/xenomai-real-time-driver-example.php)

After building, it give a dmesg when loading :
realtimedriver: disagrees about version of symbol 
__ipipe_restore_pipeline_head
realtimedriver: Unknown symbol __ipipe_restore_pipeline_head

My configuration :
xeno 2.3
hal 1.6-03
My linux version is 2.6.19


We have __ipipe_restore_pipeline_head symbol in
the kernel :

c013f7b0 T __ipipe_restore_pipeline_head
c013f7b0 U __ipipe_restore_pipeline_head    [xeno_native]
c013f7b0 U __ipipe_restore_pipeline_head    [xeno_nucleus]
c013f7b0 U __ipipe_restore_pipeline_head    [xeno_rtdm]
c013f7b0 U __ipipe_restore_pipeline_head    [xeno_posix]

but the module realtimedriver I want to insmod has
been builded with the same sources.


So what may I do ?

Re: [Xenomai-help] version of __ipipe_restore_pipeline_head

[Gilles Chanteperdrix]

Jean-Luc Pamart wrote:
> (...)
> realtimedriver: disagrees about version of symbol 
> __ipipe_restore_pipeline_head
> realtimedriver: Unknown symbol __ipipe_restore_pipeline_head
> 
> My configuration :
> xeno 2.3
> hal 1.6-03

I hope you mean Adeos I-pipe 1.7-03, right ?

> My linux version is 2.6.19
> 
> 
> We have __ipipe_restore_pipeline_head symbol in
> the kernel :
> 
> c013f7b0 T __ipipe_restore_pipeline_head
> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_native]
> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_nucleus]
> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_rtdm]
> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_posix]
> 
> but the module realtimedriver I want to insmod has
> been builded with the same sources.
> 
> 
> So what may I do ?

You likely changed a kernel option and recompiled the kernel without
recompiling the "realtimedriver" module. Try recompiling the module.

-- 
                                                 Gilles Chanteperdrix