All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Le Douarain <marc.le-douarain@laposte.net>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] "illegal instruction", then "rt_task_start()" error -38 (on a 486/no fpu)
Date: Sun, 10 Jun 2012 20:44:51 +0200	[thread overview]
Message-ID: <4FD4EB23.7080203@laposte.net> (raw)
In-Reply-To: <4FCD0C4D.6000004@xenomai.org>

Le 04/06/2012 21:28, Gilles Chanteperdrix a écrit :
> On 06/04/2012 09:26 PM, Marc Le Douarain wrote:
>> Hello,
>>
>> I've some difficulties to run Xenomai with a little 'hello' example
>> (that create/start a task)
>> on a target 486 processor (without fpu).
>>
>> I successfully compiled the Linux kernel 2.6.38.8 with
>> adeos-ipipe-2.6.38.8-x86-2.11-02.patch (Xenomai version is 2.5.6)
>> (modify file xenomai-2.5.6/include/asm-x86/calibration.h
>> "current_cpu_data"->"cpu_info" were required)
>>
>> dmesg extract:
>> [    0.000000] I-pipe 2.11-02: pipeline enabled.
>> ...
>> [    0.140008] CPU: Cyrix Cx486SLC
>> ...
>> [    1.440804] Xenomai: hal/i386 started.
>> [    1.448804] Xenomai: scheduling class idle registered.
>> [    1.452804] Xenomai: scheduling class rt registered.
>> [    1.488806] Xenomai: real-time nucleus v2.5.6 (Wormhole Wizards) loaded.
>> [    1.496807] Xenomai: starting native API services.
>> [    1.500807] Xenomai: starting POSIX services.
>> [    1.504807] Xenomai: starting RTDM services.
> It may be due to the omit-frame-pointer option, please try adding
> -fno-omit-frame-pointer to the CFLAGS
Thanks for the tip,
now it seems to work correctly !
I've used the following command line to configure Xenomai user-part :
"./configure CFLAGS="-march=i486 -fno-omit-frame-pointer" 
LDFLAGS="-march=i486" --disable-x86-sep --disable-x86-tsc"

I've savagely modified latency.c, to avoid libm and double variables in 
the code,
and now when launching a 10millisecs period,
without load I've at worst about 170 microsecs, and best 90 microsecs.
and with load (dd if=/dev/zero of=/dev/null & telnet session while ls;do 
ls;done & ping -f) :
worst 200 microsecs, and best 110 microsecs.
For you, seems to be correct for an embedded equivalent 486 at 300 mhz ?
(Linux bogomips gives : 96.51)

Again, many thanks for the gcc optimize flag to avoid on it ! ;-)

Bye.



  parent reply	other threads:[~2012-06-10 18:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 19:26 [Xenomai] "illegal instruction", then "rt_task_start()" error -38 (on a 486/no fpu) Marc Le Douarain
2012-06-04 19:28 ` Gilles Chanteperdrix
2012-06-04 21:13   ` xenophile
2012-06-10 18:44   ` Marc Le Douarain [this message]
2012-06-10 20:09     ` Gilles Chanteperdrix
2012-06-10 20:19       ` xenophile
     [not found]       ` <4FD61BF8.9090901@laposte.net>
2012-06-11 17:09         ` Gilles Chanteperdrix
2012-06-17 19:05           ` Marc Le Douarain
2012-06-17 19:19             ` Gilles Chanteperdrix
2012-07-14 12:51               ` Marc Le Douarain
2012-06-10 21:00     ` Gilles Chanteperdrix
2012-06-04 19:49 ` Gilles Chanteperdrix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FD4EB23.7080203@laposte.net \
    --to=marc.le-douarain@laposte.net \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.