>
>
> >>>>> Hi,all
> >>>>> i am a newer to xenomai.Now i want to build xenomai for my
> target
> >>>>> platform with AT91SAM9263 ARM and linux kernel vision 2.6.25.I use
> >>>>> arm-linux-gcc 3.4.1 for compiler,
> >>>>> is it suitable for build
> >>>>> xenomai？which xenomai vision is better for me?
> >>>
> >>>> Xenomai 2.5.6 is the latest stable release, it should work. But I-pipe
> >>>> patches for later linux kernel releases have support for FCSE, which
> >>>> greatly improves latencies. As for the version of gcc, I have only
> been
> >>>>using gcc 4 for a long time.
> >>>
> >>> --
> >>>
> >>
> >>
> >>
> >>> Gilles.
> >>>
> >> Hi Gilles
> >> thank you for your kindly replying.I have used linux-2.6.25
> >> and Xenomai 2.4.4 today.I compiled both linux kernel and Xenomai
>
> >If you have no special reason for using such old versions, you should
> >probably use the latest releases.
Actually,I want to use RTnet-0.9.12 for my target platform.The network
card driver contained in RTnet-0.9.12 comes from linux kernel vision2.6.25.I
prepare to use the same kernel vision as the author who ported standard
linux network card driver to RTnet.
> >Really. Even if you are stuck with linux 2.6.25 (which probably means
> that the I-pipe patch you use does not have the FCSE
FCSE is a completely new concept for me，I will get more information about
it.
> >option), you can use Xenomai 2.5.6
I have already compiled Xenomai 2.4.4 and linux kernel 2.6.25
> successfully on my target platform.
> >>how can i check out that Xenomai can run smoothly with my
> target platform.look forward to your reply.
>
> >Just run the latency test. But without FCSE, you will not get
> good latencies.
>
I run latency test,and I got the following result:
[@NewMsg9263: bin]# pwd
/usr/xenomai/bin
[@NewMsg9263: bin]# ./latency -t0 -T60 -p200 -h
== Sampling period: 200 us
== Test mode: periodic user-mode task
== All results in microseconds
warming up...
RTT| 00:00:01 (periodic user-mode task, 200 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat
worst
RTD| 33.730| 50.453| 84.750| 0| 33.730|
84.750
RTD| 23.242| 50.736| 85.034| 0| 23.242|
85.034
RTD| 20.975| 50.453| 85.034| 0| 20.975|
85.034
RTD| 24.659| 50.453| 85.884| 0| 20.975|
85.884
RTD| 24.376| 50.453| 85.600| 0| 20.975|
85.884
RTD| 24.092| 50.453| 84.750| 0| 20.975|
85.884
RTD| 23.242| 50.453| 85.034| 0| 20.975|
85.884
RTD| 24.376| 50.453| 86.167| 0| 20.975|
86.167
RTD| 22.675| 50.453| 85.600| 0| 20.975|
86.167
RTD| 23.809| 50.453| 85.317| 0| 20.975|
86.167
^C---|--param|----range-|--samples
HSD| min| 20 - 21 | 1
HSD| min| 22 - 23 | 1
HSD| min| 23 - 24 | 3
HSD| min| 24 - 25 | 4
HSD| min| 33 - 34 | 1
---|--param|----range-|--samples
HSD| avg| 20 - 21 | 1
HSD| avg| 22 - 23 | 1
HSD| avg| 23 - 24 | 7
HSD| avg| 24 - 25 | 16
HSD| avg| 25 - 26 | 18
HSD| avg| 26 - 27 | 18
HSD| avg| 27 - 28 | 6
HSD| avg| 28 - 29 | 11
HSD| avg| 29 - 30 | 4
HSD| avg| 30 - 31 | 2
HSD| avg| 32 - 33 | 6
HSD| avg| 33 - 34 | 13
HSD| avg| 34 - 35 | 13
HSD| avg| 35 - 36 | 3
HSD| avg| 36 - 37 | 1
HSD| avg| 37 - 38 | 11
HSD| avg| 38 - 39 | 15
HSD| avg| 41 - 42 | 29
HSD| avg| 42 - 43 | 109
HSD| avg| 43 - 44 | 104
HSD| avg| 44 - 45 | 6
HSD| avg| 45 - 46 | 14
HSD| avg| 46 - 47 | 17
HSD| avg| 47 - 48 | 15
HSD| avg| 48 - 49 | 38
HSD| avg| 49 - 50 | 2084
HSD| avg| 50 - 51 | 38208
HSD| avg| 51 - 52 | 11706
HSD| avg| 52 - 53 | 283
HSD| avg| 53 - 54 | 96
HSD| avg| 54 - 55 | 18
latency: failed to pend on semaphore, code -3
HSD| avg| 55 - 56 | 12
HSD| avg| 56 - 57 | 31
HSD| avg| 57 - 58 | 13
HSD| avg| 58 - 59 | 4
HSD| avg| 59 - 60 | 7
HSD| avg| 60 - 61 | 75
HSD| avg| 61 - 62 | 103
HSD| avg| 62 - 63 | 38
HSD| avg| 63 - 64 | 11
HSD| avg| 64 - 65 | 11
HSD| avg| 65 - 66 | 2
HSD| avg| 66 - 67 | 4
HSD| avg| 67 - 68 | 3
HSD| avg| 73 - 74 | 19
HSD| avg| 74 - 75 | 4
HSD| avg| 82 - 83 | 1
HSD| avg| 83 - 84 | 32
HSD| avg| 84 - 85 | 36
HSD| avg| 85 - 86 | 19
HSD| avg| 86 - 87 | 2
---|--param|----range-|--samples
HSD| max| 84 - 85 | 2
HSD| max| 85 - 86 | 7
HSD| max| 86 - 87 | 1
HSH|--param|--samples-|--average--|---stddev--
HSS| min| 10| 24.000| 3.399
HSS| avg| 53300| 50.229| 2.137
HSS| max| 10| 84.900| 0.568
---|------------|------------|------------|--------|-------------------------
RTS| 20.975| 50.453| 86.167| 0| 00:00:11/00:01:00
I think my Xenomai environment built successfully.And I want to do more
performance test on Xenomai,is there any other existing test program i can
use?
With above-mentioned linux and Xenomai I compiled RTnet0.9.12.There seems
something wrong with RTnet.
[@NewMsg9263: modules]# insmod rt_macb.ko
RTnet: registered rteth0
MACB_mii_bus: probed
rteth0: Atmel MACB at 0xfffbc000 irq 21 (12:34:56:78:90:12)
rteth0: attached PHY driver [Davicom DM9161A] (mii_bus:phy_addr=ffffffff:00,
irq=-1)
[@NewMsg9263: modules]# lsmod
rt_macb 8164 0 - Live 0xbf014000
rt_loopback 2404 0 - Live 0xbf012000
rtipv4 25484 0 - Live 0xbf00a000
rtnet 33360 3 rt_macb,rt_loopback,rtipv4, Live 0xbf000000
[@NewMsg9263: sbin]# ./rtifconfig rteth0 up
[@NewMsg9263: sbin]# rteth0: link up (100/Full)
RTnet: host 192.168.0.255 unreachable
RTnet: unable to forward packet from 192.168.0.8
RTnet: host 255.255.255.255 unreachable
RTnet: unable to forward packet from 192.168.0.100
RTnet: host 192.168.0.255 unreachable
RTnet: unable to forward packet from 192.168.0.122
RTnet: host 255.255.255.255 unreachable
RTnet: unable to forward packet from 192.168.0.100
I know this is Xenomai maillist，but if you know where is my problem.Please
tell me.
> >--
> > Gilles.
>
thank you for your kindly help.
regards
yizheng
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
