* [Xenomai-help] rt_task_start returns -38 (ENOSYS)
@ 2010-09-24 19:07 martin mangard
2010-09-24 20:32 ` Gilles Chanteperdrix
0 siblings, 1 reply; 5+ messages in thread
From: martin mangard @ 2010-09-24 19:07 UTC (permalink / raw)
To: xenomai
Hello
I installed Xenomai on a x86 machine (kernel 2.6.30 wih xenomai
2.4.10). In order to verify the installation I ran the
latency-testprogram from the test-suite.
The latency test program aborts with the error ENOSYS :
== Sampling period: 100 us
== Test mode: periodic user-mode task
== All results in microseconds
latency: failed to start display task, code -38
This output ist generated if the call err =
rt_task_start(&display_task, &display, NULL); ---> fails.
As mentioned in the documentation this error occurs, if not all
necesary modules are loaded or configured.
during the startup following messages occur:
.
.
I-pipe: Domain Xenomai registered.
Xenomai: hal/i386 started.
Xenomai: real-time nucleus v2.4.10 (Flavor Crystal 7) loaded.
Xenomai: starting native API services.
Xenomai: starting POSIX services.
Xenomai: starting RTDM services.
Xenomai: starting RTAI emulator.
.
.
This is my configuration of the Kernel subsystem:
.
.
#
# Real-time sub-system
#
CONFIG_XENOMAI=y
CONFIG_XENO_GENERIC_STACKPOOL=y
CONFIG_XENO_OPT_NUCLEUS=y
CONFIG_XENO_OPT_PERVASIVE=y
# CONFIG_XENO_OPT_ISHIELD is not set
CONFIG_XENO_OPT_PRIOCPL=y
CONFIG_XENO_OPT_PIPELINE_HEAD=y
CONFIG_XENO_OPT_PIPE=y
CONFIG_XENO_OPT_PIPE_NRDEV=32
CONFIG_XENO_OPT_REGISTRY=y
CONFIG_XENO_OPT_REGISTRY_NRSLOTS=512
CONFIG_XENO_OPT_SYS_HEAPSZ=128
CONFIG_XENO_OPT_SYS_STACKPOOLSZ=128
CONFIG_XENO_OPT_STATS=y
CONFIG_XENO_OPT_DEBUG=y
CONFIG_XENO_OPT_DEBUG_NUCLEUS=y
CONFIG_XENO_OPT_DEBUG_QUEUES=y
CONFIG_XENO_OPT_DEBUG_REGISTRY=y
# CONFIG_XENO_OPT_DEBUG_TIMERS is not set
# CONFIG_XENO_OPT_WATCHDOG is not set
# CONFIG_XENO_OPT_SHIRQ is not set
#
#
# Interfaces
#
CONFIG_XENO_SKIN_NATIVE=y
CONFIG_XENO_OPT_NATIVE_PERIOD=0
CONFIG_XENO_OPT_NATIVE_PIPE=y
CONFIG_XENO_OPT_NATIVE_PIPE_BUFSZ=4096
CONFIG_XENO_OPT_NATIVE_REGISTRY=y
CONFIG_XENO_OPT_NATIVE_SEM=y
CONFIG_XENO_OPT_NATIVE_EVENT=y
CONFIG_XENO_OPT_NATIVE_MUTEX=y
CONFIG_XENO_OPT_NATIVE_COND=y
CONFIG_XENO_OPT_NATIVE_QUEUE=y
CONFIG_XENO_OPT_NATIVE_HEAP=y
CONFIG_XENO_OPT_NATIVE_ALARM=y
CONFIG_XENO_OPT_NATIVE_MPS=y
# CONFIG_XENO_OPT_NATIVE_INTR is not set
CONFIG_XENO_OPT_DEBUG_NATIVE=y
CONFIG_XENO_SKIN_POSIX=y
CONFIG_XENO_OPT_POSIX_PERIOD=0
CONFIG_XENO_OPT_POSIX_SHM=y
# CONFIG_XENO_OPT_POSIX_INTR is not set
# CONFIG_XENO_OPT_POSIX_SELECT is not set
# CONFIG_XENO_OPT_DEBUG_POSIX is not set
# CONFIG_XENO_SKIN_PSOS is not set
# CONFIG_XENO_SKIN_UITRON is not set
# CONFIG_XENO_SKIN_VRTX is not set
# CONFIG_XENO_SKIN_VXWORKS is not set
CONFIG_XENO_SKIN_RTAI=y
CONFIG_XENO_OPT_RTAI_PERIOD=0
CONFIG_XENO_OPT_RTAI_FIFO=y
CONFIG_XENO_OPT_RTAI_SEM=y
CONFIG_XENO_OPT_RTAI_SHM=y
CONFIG_XENO_SKIN_RTDM=y
CONFIG_XENO_OPT_RTDM_PERIOD=0
CONFIG_XENO_OPT_RTDM_FILDES=128
# CONFIG_XENO_OPT_RTDM_SELECT is not set
CONFIG_XENO_OPT_DEBUG_RTDM=y
Which subsystem do I have to enable in order to be able to start a
rt_task as used in the latency test program ?
Martin
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Xenomai-help] rt_task_start returns -38 (ENOSYS)
2010-09-24 19:07 [Xenomai-help] rt_task_start returns -38 (ENOSYS) martin mangard
@ 2010-09-24 20:32 ` Gilles Chanteperdrix
2010-09-24 20:34 ` Gilles Chanteperdrix
0 siblings, 1 reply; 5+ messages in thread
From: Gilles Chanteperdrix @ 2010-09-24 20:32 UTC (permalink / raw)
To: martin mangard; +Cc: xenomai
martin mangard wrote:
> Hello
>
> I installed Xenomai on a x86 machine (kernel 2.6.30 wih xenomai
> 2.4.10). In order to verify the installation I ran the
> latency-testprogram from the test-suite.
> The latency test program aborts with the error ENOSYS :
>
>
> == Sampling period: 100 us
> == Test mode: periodic user-mode task
> == All results in microseconds
> latency: failed to start display task, code -38
>
> This output ist generated if the call err =
> rt_task_start(&display_task, &display, NULL); ---> fails.
>
> As mentioned in the documentation this error occurs, if not all
> necesary modules are loaded or configured.
>
> during the startup following messages occur:
>
> .
> .
> I-pipe: Domain Xenomai registered.
> Xenomai: hal/i386 started.
> Xenomai: real-time nucleus v2.4.10 (Flavor Crystal 7) loaded.
> Xenomai: starting native API services.
> Xenomai: starting POSIX services.
> Xenomai: starting RTDM services.
> Xenomai: starting RTAI emulator.
> .
> .
>
Please send us the full logs, from the boot up to the point where your
program fails.
--
Gilles.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Xenomai-help] rt_task_start returns -38 (ENOSYS)
2010-09-24 20:32 ` Gilles Chanteperdrix
@ 2010-09-24 20:34 ` Gilles Chanteperdrix
2010-09-27 12:05 ` martin mangard
0 siblings, 1 reply; 5+ messages in thread
From: Gilles Chanteperdrix @ 2010-09-24 20:34 UTC (permalink / raw)
To: martin mangard; +Cc: xenomai
Gilles Chanteperdrix wrote:
> martin mangard wrote:
>> Hello
>>
>> I installed Xenomai on a x86 machine (kernel 2.6.30 wih xenomai
>> 2.4.10). In order to verify the installation I ran the
>> latency-testprogram from the test-suite.
>> The latency test program aborts with the error ENOSYS :
>>
>>
>> == Sampling period: 100 us
>> == Test mode: periodic user-mode task
>> == All results in microseconds
>> latency: failed to start display task, code -38
>>
>> This output ist generated if the call err =
>> rt_task_start(&display_task, &display, NULL); ---> fails.
>>
>> As mentioned in the documentation this error occurs, if not all
>> necesary modules are loaded or configured.
>>
>> during the startup following messages occur:
>>
>> .
>> .
>> I-pipe: Domain Xenomai registered.
>> Xenomai: hal/i386 started.
>> Xenomai: real-time nucleus v2.4.10 (Flavor Crystal 7) loaded.
>> Xenomai: starting native API services.
>> Xenomai: starting POSIX services.
>> Xenomai: starting RTDM services.
>> Xenomai: starting RTAI emulator.
>> .
>> .
>>
>
> Please send us the full logs, from the boot up to the point where your
> program fails.
As well as the "latency" command line which fails.
>
--
Gilles.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Xenomai-help] rt_task_start returns -38 (ENOSYS)
2010-09-24 20:34 ` Gilles Chanteperdrix
@ 2010-09-27 12:05 ` martin mangard
2010-09-27 12:34 ` Gilles Chanteperdrix
0 siblings, 1 reply; 5+ messages in thread
From: martin mangard @ 2010-09-27 12:05 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
Hello
I did some more research.
What I haven't memtioned is, that I'm using openembedded to build
xenomai. It turned out that the reason that caused the ENOSYS error
was the same as descibed in:
https://mail.gna.org/public/xenomai-help/2009-08/msg00047.html
I changed the CFLAGS and the latency test program worked without
errors. It seems to me that some people have made xenomai recipes but
none of them made their way into the
openembedded repository. Maybe I will post my recipe in the
openembedded mailinglist to discuss the possibilities of a xenomai
integration in openembedded.
Thanks for your help
Martin
On Fri, Sep 24, 2010 at 10:34 PM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> Gilles Chanteperdrix wrote:
>> martin mangard wrote:
>>> Hello
>>>
>>> I installed Xenomai on a x86 machine (kernel 2.6.30 wih xenomai
>>> 2.4.10). In order to verify the installation I ran the
>>> latency-testprogram from the test-suite.
>>> The latency test program aborts with the error ENOSYS :
>>>
>>>
>>> == Sampling period: 100 us
>>> == Test mode: periodic user-mode task
>>> == All results in microseconds
>>> latency: failed to start display task, code -38
>>>
>>> This output ist generated if the call err =
>>> rt_task_start(&display_task, &display, NULL); ---> fails.
>>>
>>> As mentioned in the documentation this error occurs, if not all
>>> necesary modules are loaded or configured.
>>>
>>> during the startup following messages occur:
>>>
>>> .
>>> .
>>> I-pipe: Domain Xenomai registered.
>>> Xenomai: hal/i386 started.
>>> Xenomai: real-time nucleus v2.4.10 (Flavor Crystal 7) loaded.
>>> Xenomai: starting native API services.
>>> Xenomai: starting POSIX services.
>>> Xenomai: starting RTDM services.
>>> Xenomai: starting RTAI emulator.
>>> .
>>> .
>>>
>>
>> Please send us the full logs, from the boot up to the point where your
>> program fails.
>
> As well as the "latency" command line which fails.
>
>>
>
>
> --
> Gilles.
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Xenomai-help] rt_task_start returns -38 (ENOSYS)
2010-09-27 12:05 ` martin mangard
@ 2010-09-27 12:34 ` Gilles Chanteperdrix
0 siblings, 0 replies; 5+ messages in thread
From: Gilles Chanteperdrix @ 2010-09-27 12:34 UTC (permalink / raw)
To: martin mangard; +Cc: xenomai
martin mangard wrote:
> Hello
>
> I did some more research.
> What I haven't memtioned is, that I'm using openembedded to build
> xenomai. It turned out that the reason that caused the ENOSYS error
> was the same as descibed in:
>
> https://mail.gna.org/public/xenomai-help/2009-08/msg00047.html
>
> I changed the CFLAGS and the latency test program worked without
> errors. It seems to me that some people have made xenomai recipes but
> none of them made their way into the
> openembedded repository. Maybe I will post my recipe in the
> openembedded mailinglist to discuss the possibilities of a xenomai
> integration in openembedded.
Ok. But maybe we should fix Xenomai too...
--
Gilles.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-09-27 12:34 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-09-24 19:07 [Xenomai-help] rt_task_start returns -38 (ENOSYS) martin mangard
2010-09-24 20:32 ` Gilles Chanteperdrix
2010-09-24 20:34 ` Gilles Chanteperdrix
2010-09-27 12:05 ` martin mangard
2010-09-27 12:34 ` Gilles Chanteperdrix
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.