From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Lyons, Brendon N" <lyonsb@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai, Beagleboard and RTAI
Date: Fri, 04 Nov 2011 20:06:34 +0100 [thread overview]
Message-ID: <4EB437BA.5070104@domain.hid> (raw)
In-Reply-To: <768BACF5E8359A48BAF0059F2E3E1A430A86C3C7@domain.hid>
On 11/04/2011 07:15 PM, Lyons, Brendon N wrote:
> I am sorry for the previous message with no subject. I am resending
> this so that it can be properly tagged.
>
> ______________________________________
>
> Hello,
>
> I am currently working on a project which requires realtime use of a
> beagleboard. I know that Xenomai is a realtime kernel however, our
> setup calls for the use of Mathworks' Simulink support for RTAI. I
> have been doing some research and have found that Xenomai
> incorporates RTAI as a skin? I am not entirely sure what that means
> but it sounds like I can simply copy and paste RTAI headers in the
> designated ../rtai folder within Xenomai and have my rtai programs
> compile and run on Xenomai.
>
> Here is an outline of the goals I would like to achieve:
>
>
> * Have Xenomai running on a beagleboard with an RTAI skin *
> Generate realtime programs with the Simulink support for RTAI *
> Upload the program and run it on the beagleboard
>
> I have a few questions regarding this approach:
>
> First of all is this even feasible?
I do not think so. Xenomai RTAI skin was a kernel-only skin, and chances
are that the code generated by simulink is for LXRT, that is, RTAI
user-space support.
However, there exist equivalent solutions to RTAI-lab for Xenomai. We
have seen a post recently about such a solution:
https://mail.gna.org/public/xenomai-core/2011-10/msg00019.html
A user of Xenomai, "Michel He" seems also to have worked on that too.
Secondly if it is, what would be
> the consequences of running an RTAI executable built on say <ubuntu
> 9.04 kernel 2.6.28.7 with gcc 4.3.3> on <Xenomai 2.5.2 Kernel
> 2.6.28.10 (adeos-ipipe-2.6.28.10-arm-1.12-07) patch with gcc 4.3.3>
> (this is the closest kernel match I could find)
>
> Or if I wanted to run a later Xenomai such as <Xenomai 2.5.6 Kernel
> 2.6.33 (adeos-ipipe-2.6.33-arm-1.18-02) patch with gcc 4.3.3>
>
> Which leads me to my next question, what is the earliest kernel +
> Xenomai combination supported on the beagleboard?
Note that it does not make sense to pick a release in a branch which is
not the latest, for instance, if you pick a release in the 2.5 branch,
it should be the latest, that is 2.5.6, previous adeos patches work with
latest releases anyway.
What is the reason for picking an old version of the Adeos patch? When
starting a new project people usually pick the latest kernel. Anyway,
the oldest version of the Adeos patch supporting omap3 should be 2.6.31.
--
Gilles.
prev parent reply other threads:[~2011-11-04 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 18:15 [Xenomai-help] Xenomai, Beagleboard and RTAI Lyons, Brendon N
2011-11-04 19:06 ` Gilles Chanteperdrix [this message]
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=4EB437BA.5070104@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lyonsb@domain.hid \
--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.