Re: [Xenomai-help] my tick takes a break !!

[Philippe Gerum <rpm@xenomai.org>]

Gilles Chanteperdrix wrote:
> Thomas, Brieuc \(GE Healthcare\) wrote:
>  > 
>  >  > -----Message d'origine-----
>  >  > De : Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.orgt] 
>  >  > Envoyé : dimanche 23 avril 2006 14:54
>  >  > À : Thomas, Brieuc (GE Healthcare)
>  >  > Cc : xenomai@xenomai.org
>  >  > Objet : RE: [Xenomai-help] my tick takes a break !! 
>  >  > 
>  >  > Thomas, Brieuc \(GE Healthcare\) wrote:
>  >  >  > I tried it, but there isn't any change !
>  >  >  > I've got the same behaviour.
>  >  > 
>  >  > I could reproduce your bug here. The uvm-timer thread is blocked in W state, just as if the interrupts were locked.
>  > 
>  > Yes but, I've allowed the interrupts from the compile, and I never used intLock() or something like that!
> 
> Neither your code, nor your setup is wrong, the error come from vxworks
> uvm. Printing uvm_irqlock shows that the interrupts got disabled
> somehow.
> 
>  > Then I tried the trunk version, and I've got an error message during the launch, either:    
>  > 
>  > When I compile a periodic timer mode:
>  > Xenomai: UVM skin init failed, code -16
>  > Xenomai: starting Vxworks services
>  > Or, in aperiodic mode:
>  > Xenomai: starting UVM services
>  > Xenomai: incompatible timer mode(aperiodic found, need periodic).
>  > Xenomai: Vxworks skin init failed, code -16
>  > 
>  > Perhaps my first problem, come from to the timer mode? Normally my configuration is status=oneshot:setup=202:tickval=1... 
> 
> UVM and vxworks are separated skins, that require incompatible timer
> setting. Since you are using UVM (I guess), select only uvm in kernel
> configuration, or select vxworks skin as a module that you do not load
> when running applications using the UVM skin.
> 

If you feel lucky, the 3rd option coming with v2.2 is to get rid of the 
UVM and use the new direct call interface now available from user-space 
for the VxWorks skin. In such a case, you need 1) the development 
trunk/, 2) to load xeno_vxworks, 3) work with the new VxWorks interface 
from user-space exactely the way one would use the existing native or 
POSIX skin.

-- 

Philippe.