Hi friends and linux lovers,
iam a new geek to xenomai....
can anyone please suggest me the xenomai+linux version+rtnet version to use
with less problems......
Thanks in advance to all of you,
have a lovely day,bye...................
[EMAIL PROTECTED] wrote: Send RTnet-users mailing list submissions to
rtnet-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/rtnet-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of RTnet-users digest..."
Today's Topics:
1. Re: Make RTnet 0.9.9 error (Dennis Nguyen)
2. Re: RTNet in non-TDMA mode? (Roland Tollenaar)
3. Re: RTnet on AT91 (Yeoh Chun Yeow)
4. Re: RTnet on AT91 (Jan Kiszka)
5. Re: RTnet on AT91 (Yeoh Chun Yeow)
6. Re: RTnet on AT91 (Jan Kiszka)
----------------------------------------------------------------------
Message: 1
Date: Fri, 26 Oct 2007 22:46:50 -0800
From: "Dennis Nguyen"
Subject: Re: [RTnet-users] Make RTnet 0.9.9 error
To:
Cc: rtnet-users@lists.sourceforge.net
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Hi Jan,
Thanks for the advice. I rebuild the kernel 2.6.20.10 and Xenomai 2.3.4 but
it has other error with example.
Could you tell me which kernel version can I use with the xenomai 2.4-rc4
and latest RTnet?
For example: kernel-2.6.22.10 with xenomai 2.4-rc and latest RTnet from SVN.
Please be patient with me since I'm a new bee.
Thanks in advance,
Dennis
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 2:14 PM
To: Dennis Nguyen
Cc: rtnet-users@lists.sourceforge.net
Subject: Re: [RTnet-users] Make RTnet 0.9.9 error
Dennis Nguyen wrote:
> I'm a new bee to RTnet. and I'm using linux kernel 2.6.20.10
> and xenomai 2.3.4.
>
> I'm try to compile the RTnet 0.9.9 but I got the errors:
Please try RTnet from SVN (see homepage for details on how to obtain
it). That version should build fine up to 2.6.23.
Jan
------------------------------
Message: 2
Date: Sat, 27 Oct 2007 13:50:33 +0200
From: Roland Tollenaar
Subject: Re: [RTnet-users] RTNet in non-TDMA mode?
To: Jan Kiszka
Cc: rtnet-users
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Please read the Xenomai FAQ on shared IRQs:
> http://www.xenomai.org/index.php/FAQs
>
> If something remains unclear, I could try to improve the explanation.
On every new system its always a black art to untangle the IRQ's. Its
almost impossible to not have shared lines here or there. In most cases
up to now I have managed to get an acceptable compromise using every
single one of the possible tricks (including beating our engineers who
have nothing whatsoever to do with the hardware but it helps relieve the
frustration). I was wondering -and am using this opportunity to post the
question- what the fundamental problem is that makes shared IRQ's
between RTdevices and non-RT devices crash the system? And whether I
understand correctly that later versions (2.4 up?) of xenomai do not
have the problem of the freezing system at least.?
Roland
>
> Jan
>
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> RTnet-users mailing list
> RTnet-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rtnet-users
------------------------------
Message: 3
Date: Mon, 29 Oct 2007 09:23:33 +0800
From: "Yeoh Chun Yeow"
Subject: Re: [RTnet-users] RTnet on AT91
To: "Jan Kiszka"
Cc: rtnet-users
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Dear Jan,
I don't think that I have tested the scenario on "joint TDMA slots or the
Sync frame immediately followed by the
master's payload slot" before. I only tried out the default setup script
with 1 master and 1 slave. Please advice on how to do this.
By the way, how the link state polling timer will affect the real-time
operation?
Regards,
Chun Yeow
On 10/27/07, Jan Kiszka wrote:
>
> Yeoh Chun Yeow wrote:
> > Dear Jan,
> >
> > Please provide me the details on how to do testing.
>
> Just merged your driver with some modifications - hopefully good ones.
>
> My problem is that I don't know the locking requirements of the
> hardware, and that the original Linux driver is no real help here as it
> was built on wrong assumptions about locking. I picked a careful
> approach first and kept what I found, rather extended it. Maybe it would
> be possible to decouple all the PHY handling completely from the
> real-time domain, but that would need deeper analysis of hardware and
> driver.
>
> What I furthermore did is to default-disable the link state polling
> timer. That one is only needed if there is not PHY IRQ and you
> reconfigure your RT network after rtifconfig up. You can re-enable it
> via the module parameter "use_phy_timer".
>
> Another thing I came across is the extremely short TX queue of the
> rt_at91_ether (one slot!). This can be problematic if the TX completion
> interrupt takes longer than a succeeding TX request by the RTnet stack
> (e.g. joint TDMA slots or the Sync frame immediately followed by the
> master's payload slot). Did you already test such scenarios, and did it
> work?
>
> Looking forward to your test results!
>
> Jan
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Mon, 29 Oct 2007 08:55:37 +0100
From: Jan Kiszka
Subject: Re: [RTnet-users] RTnet on AT91
To: Yeoh Chun Yeow
Cc: rtnet-users
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Yeoh Chun Yeow wrote:
> Dear Jan,
>
> I don't think that I have tested the scenario on "joint TDMA slots or the
> Sync frame immediately followed by the
> master's payload slot" before. I only tried out the default setup script
> with 1 master and 1 slave. Please advice on how to do this.
If you ran the default setup for the master on an AT91, you already
generated a scenario like this: The master's Sync frame is then directly
followed by its payload slot (offset 0). If you want to drive this
further, you could add another slot to the master's setup. Use the
advanced setup mode (TDMA_CONFIG=... in rtnet.conf) and modify the
master's slot list like this:
master:
...
slot 0 0
slot 1 0 1/1 1500 1
>
> By the way, how the link state polling timer will affect the real-time
> operation?
Probably not dramatically: It will add periodic non-preemptible hardware
access to your real-time workload. Depending on how tight your schedule
will be and how long those interaction my take (can't tell as I don't
have a target to test), this /can/ be problematic. By disabling it, we
remove one further aspect one has to consider for the real-time design
of the system.
Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
------------------------------
Message: 5
Date: Mon, 29 Oct 2007 19:02:07 +0800
From: "Yeoh Chun Yeow"
Subject: Re: [RTnet-users] RTnet on AT91
To: "Jan Kiszka"
Cc: rtnet-users
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Dear Jan
Can you explain the tdma configuration of "slot 1 0 1/1 1500 1"?
And how should I configure the cycle (previously in the rtnet.conf, I set
the TDMA cycle to 2000 and TDMA offset to 500) and the slave?
Is it ok for me to use the default configuration in tdma config script?
I have ensure that AT91 acts as the master and it is able to ping the slave
using rtping after the completion of TDMA setup. So is this enough?
Please advice. Thanks
Regards,
Chun Yeow
On 10/29/07, Jan Kiszka wrote:
>
> Yeoh Chun Yeow wrote:
> > Dear Jan,
> >
> > I don't think that I have tested the scenario on "joint TDMA slots or
> the
> > Sync frame immediately followed by the
> > master's payload slot" before. I only tried out the default setup script
> > with 1 master and 1 slave. Please advice on how to do this.
>
> If you ran the default setup for the master on an AT91, you already
> generated a scenario like this: The master's Sync frame is then directly
> followed by its payload slot (offset 0). If you want to drive this
> further, you could add another slot to the master's setup. Use the
> advanced setup mode (TDMA_CONFIG=... in rtnet.conf) and modify the
> master's slot list like this:
>
> master:
> ...
> slot 0 0
> slot 1 0 1/1 1500 1
>
> >
> > By the way, how the link state polling timer will affect the real-time
> > operation?
>
> Probably not dramatically: It will add periodic non-preemptible hardware
> access to your real-time workload. Depending on how tight your schedule
> will be and how long those interaction my take (can't tell as I don't
> have a target to test), this /can/ be problematic. By disabling it, we
> remove one further aspect one has to consider for the real-time design
> of the system.
>
> Jan
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 6
Date: Mon, 29 Oct 2007 20:37:38 +0100
From: Jan Kiszka
Subject: Re: [RTnet-users] RTnet on AT91
To: Yeoh Chun Yeow
Cc: rtnet-users
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Yeoh Chun Yeow wrote:
> Dear Jan
>
> Can you explain the tdma configuration of "slot 1 0 1/1 1500 1"?
First of all, this was early-morning nonsense, must rather read:
slot 2 0 1/1 1500 0
Translation: Create a TDMA slot, ID 2 (first arg), offset 0 us relative
to each TDMA Sync (second arg), period 1/1, i.e. use every TDMA cycle
(third arg), 1500 byte payload (fourth arg), and join this slot with the
one of ID 0 (fifth arg). For more details, see README.rtmac (hmm, it's
is failing to mention the fifth argument, too bad...).
>
> And how should I configure the cycle (previously in the rtnet.conf, I set
> the TDMA cycle to 2000 and TDMA offset to 500) and the slave?
Please check the README first, it should explains this.
>
> Is it ok for me to use the default configuration in tdma config script?
As a basis, yes.
>
> I have ensure that AT91 acts as the master and it is able to ping the slave
> using rtping after the completion of TDMA setup. So is this enough?
To be safe, apply the above configuration and run a test with larger
ping frames (ping -s ...). Maybe the time for returning some
transmission buffer from the hardware back to the OS is actually so
short here that a TX queue is not needed. But my feeling is not yet that
optimistic.
Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
------------------------------
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users
End of RTnet-users Digest, Vol 17, Issue 11
*******************************************
Send instant messages to your online friends http://uk.messenger.yahoo.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users
