Re: [Xenomai-help] Adeos/Xenomai Arm Port

["Schlägl Manfred jun." <manfred.schlaegl@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 3793 bytes --]

Here some test-cases:


-sh-3.00# cat /proc/xenomai/rtdm/rttest0/information 
driver:         xeno_timerbench
version:        0.2.0
peripheral:     Timer Latency Benchmark
provider:       Jan Kiszka
class:          6
sub-class:      0
flags:          NAMED_DEVICE  
lock count:     0
-sh-3.00# cat /proc/xenomai/rtdm/rttest1/information 
driver:         xeno_irqbench
version:        0.1.0
peripheral:     IRQ Latency Benchmark
provider:       Jan Kiszka
class:          6
sub-class:      1
flags:          NAMED_DEVICE  
lock count:     0
-sh-3.00# cat /proc/xenomai/rtdm/rttest2/information 
driver:         xeno_switchtest
version:        0.1.1
peripheral:     Context Switch Test
provider:       Gilles Chanteperdrix
class:          6
sub-class:      2
flags:          NAMED_DEVICE  
lock count:     0
-sh-3.00# cat /proc/xenomai/rtdm/named_devices       
Hash    Name                            /proc
D6      rttest0                         rttest0
D7      rttest1                         rttest1
D8      rttest2                         rttest2


-sh-3.00# ./latency -D0 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to start in-kernel timer benchmark, code -25
---|------------|------------|------------|--------|-------------------------
RTS|-1091011.128|       0.001|      93.252|   93340|
00:00:00/00:00:10

-sh-3.00# ./latency -D1 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to start in-kernel timer benchmark, code -25
---|------------|------------|------------|--------|-------------------------
RTS|-1098113.592|       0.001|      93.252|   93340|
00:00:-01/00:00:10

-sh-3.00# ./latency -D2 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to start in-kernel timer benchmark, code -25
---|------------|------------|------------|--------|-------------------------
RTS|-1093665.336|       0.001|      93.252|   93340|
00:00:00/00:00:10

-sh-3.00# ./latency -D3 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)
-sh-3.00# ./latency -D4 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)
-sh-3.00# ./latency -D4 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)
-sh-3.00# ./latency -D5 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)
-sh-3.00# ./latency -D6 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)
-sh-3.00# ./latency -D7 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)
-sh-3.00# ./latency -D8 -t 1 -T 10 -p 10000
== Sampling period: 10000 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)



... no success




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]