> -----Message d'origine-----
> De : Gilles Chanteperdrix [mailto:[EMAIL PROTECTED]
> Envoyé : dimanche 23 avril 2006 14:54
> À : Thomas, Brieuc (GE Healthcare)
> Cc : [email protected]
> 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.
>
> --
>
>
> Gilles Chanteperdrix.
>
Yes but, I've allowed the interrupts from the compile, and I never used
intLock() or something like that!
By the way, I made some test: and if I add a taskLock() before the heavy
while() and a taskUnlock() just after this while, my tick number is updated.
But the task behaviour is the same; the task doesn't give the priority to the
other task.
The second test is: I've added a takdelay() before the heavy while(). The tick
counter work's, the task behaviour is fine, but evidently the workout takes a
long time!
In fact, I think than I never seen working the schedule without delay() (like
taskdelay() or msqReceive(WAIT)...) I've got probably a bad configuration
somewhere!
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...
Any idea?
Brieuc THOMAS.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
