Hi
I've been trying to get an Intel PCIE network card working under Xenomai on
the phyflex i.mx6 platform (phyflex i.mx6 SOM in the phyflex eval board).
The network card works well with the Linux e1000e driver (legacy
interrupts) on this hardware. However, when I switch to the rt_e1000e
driver
>
> I applied the most recent 4.1.y x86 ipipe patch to the following kernel:
It seems this error was caused by the patching tool using the
downloaded x86 patch. Today I merged in the latest git ipipe tree into
my custom 4.1.42 kernel, and this doesn't cause the issues reported
below. So it seems
Hi
I applied the most recent 4.1.y x86 ipipe patch to the following kernel:
vrc:~# cat /proc/version
Linux version 4.1.42-yocto-standard (andreas@x) (gcc version 5.2.0
(GCC) ) #2 SMP PREEMPT Thu Dec 28 15:16:20 GMT 2017
vrc:~# cat /proc/ipipe/version
9
It boots, however, I get WARN_ON()
>>> I have pulled wip/rtnet-fixes branch with the last commit of Philippe from
>>> Sun
>>> Dec 17 15:27:04 2017 +0100: net/udp: ioctl: fix temp arg buffer type
>>>
>>> I have created the packages and new kernel with the same configuration that
>>> I had.
>>>
>>> I run my application, that it's a
>>>
>>> I have pulled wip/rtnet-fixes branch with the last commit of Philippe from
>>> Sun
>>> Dec 17 15:27:04 2017 +0100: net/udp: ioctl: fix temp arg buffer type
>>>
>>> I have created the packages and new kernel with the same configuration that
>>> I had.
>>>
>>> I run my application, that
On Sun, Dec 17, 2017 at 2:25 PM, Philippe Gerum <r...@xenomai.org> wrote:
> On 12/17/2017 12:01 AM, Andreas Glatz wrote:
>>>
>>> I pushed a pile of RTnet fixes in a WIP branch of the official repo
>>> (wip/rtnet-fixes). Most of them address invalid direct refer
>
> I pushed a pile of RTnet fixes in a WIP branch of the official repo
> (wip/rtnet-fixes). Most of them address invalid direct references to
> user memory from kernel space (instead of properly copying back and
> forth via the copy_from/to_user interface), which are badly wrong at any
> rate,
>>
>> We're testing our application now by running it continuously over
>> weeks. I randomly reports the following mode switches in the log:
>>
>> > 0x2b03a420 0x93980 >
>>
>> With the process memory map from /proc//maps:
>>
>> ...
>> 2af68000-2b084000 r-xp 00:0d 22235 /lib/libc-2.14.1.so
>>
>> ? My Xenomai version is 3.0.3 and I use the POSIX API with the
>> following build options.
>>
>>
>> XENO_CONFIG := /usr/xenomai/bin/xeno-config
>> CFLAGS := $(shell $(XENO_CONFIG) --vxworks --cflags)
>> LDFLAGS := $(shell $(XENO_CONFIG) --vxworks --ldflags)
>> CC := $(shell $(XENO_CONFIG)
Hi
We're testing our application now by running it continuously over
weeks. I randomly reports the following mode switches in the log:
With the process memory map from /proc//maps:
...
2af68000-2b084000 r-xp 00:0d 22235 /lib/libc-2.14.1.so
...
and output from -objdump -d
> Message: 4
> Date: Thu, 7 Dec 2017 10:35:59 +0800
> From: JackLee
> To: xenomai@xenomai.org
> Subject: [Xenomai] xenomai 3.0.3 POSIX rtnet API
> Message-ID:
> <830662c3-0cbc-78ab-b7ab-456861679...@foxmail.com>+45245C193B26E5A4
> Content-Type: text/plain;
>
> I pushed a pile of RTnet fixes in a WIP branch of the official repo
> (wip/rtnet-fixes). Most of them address invalid direct references to
> user memory from kernel space (instead of properly copying back and
> forth via the copy_from/to_user interface), which are badly wrong at any
> rate,
> Le 04/10/2017 ? 10:54, Philippe Gerum a ?crit?:
>> On 10/03/2017 01:49 PM, Andreas Glatz wrote:
>>> Hi
>>>
>>> I implemented the debug signal handle SIGXCPU as described in the
>>> Xenomai documentation. The glibc function backtrace() returns
Hi
I implemented the debug signal handle SIGXCPU as described in the
Xenomai documentation. The glibc function backtrace() returns
backtraces, but they often are very short (they typically end at the
signal (restore) handler, and don't show the function which caused the
SIGXCPU in the first
> I've got two versions of the same piece of code, the only difference
> is that lines are reordered:
>
> #if 1
>u32Tmp= ntohl(*reinterpret_cast(pDat+4));
>sPhasor.angle = interpretU32AsFloat(u32Tmp);
>u32Tmp= ntohl(*reinterpret_cast(pDat));
>sPhasor.mag
Hi
I've got two versions of the same piece of code, the only difference
is that lines are reordered:
#if 1
u32Tmp= ntohl(*reinterpret_cast(pDat+4));
sPhasor.angle = interpretU32AsFloat(u32Tmp);
u32Tmp= ntohl(*reinterpret_cast(pDat));
sPhasor.mag =
>
> HW/SW:
> - phyflex i.MX6 dual core SOM
> - Linux version 3.0.43-tpcom_run2-PD13.2.4
> - Xenomai/Ipipe: 2.6.4/1.18-3
> - RTnet: 0.9.13
> - custom RTnet driver
>
> Problem:
> Recently, we came across a case where the rx/tx through RTnet works
> for several hours and then stops with the following
>
> Thank you Andreas and Christophe for helping resolve the rtroute issue.
No problem. Just a remark: I believe this mailing list doesn't like
top-posting...
>
> The messed up routing table was likely as a result of my various attempts
> to get it working.
>
> Unfortunately, now that I've
>
> # ./rtping 10.0.0.1
> Real-time PING 10.0.0.1 56(84) bytes of data.
> ioctl: No route to host
You should populate your RTnet routing table with some meaningful
combinations of IP address and MAC address after bringing it up.
The other non-persistent option is to ping your RTnet device from a
>>
>> I managed to compile and bring-up Xenomai v3.0.5, Ipipe v2, Linux
>> v4.9.35 on a Wandboard Quad C1 [1]. I ran all unit-tests sucessfully
>> [2] and was able to get RTnet ping to an external PC working. RT ping
>> stops working after about 1000 pings... but that's a different story,
>> I
Hi
I managed to compile and bring-up Xenomai v3.0.5, Ipipe v2, Linux
v4.9.35 on a Wandboard Quad C1 [1]. I ran all unit-tests sucessfully
[2] and was able to get RTnet ping to an external PC working. RT ping
stops working after about 1000 pings... but that's a different story,
I guess.
So when I
Hi
HW/SW:
- phyflex i.MX6 dual core SOM
- Linux version 3.0.43-tpcom_run2-PD13.2.4
- Xenomai/Ipipe: 2.6.4/1.18-3
- RTnet: 0.9.13
- custom RTnet driver
Problem:
Recently, we came across a case where the rx/tx through RTnet works
for several hours and then stops with the following errors:
[
On Tue, Jan 31, 2017 at 9:27 AM, Philippe Gerum <r...@xenomai.org> wrote:
> On 01/30/2017 01:27 PM, Andreas Glatz wrote:
>> Hi
>>
>> During optimisation I found out that I have a POSIX socket() call for
>> opening a TCP connection that tends to switch to secondary
Hi
During optimisation I found out that I have a POSIX socket() call for
opening a TCP connection that tends to switch to secondary mode, which
I expected to stay in primary mode. However, then I found a post [1],
which says that it is in fact considered normal behaviour:
"rt_dev_socket may
Hello,
My probleme is that i can't launch any latency tests , they always hang .
I work with a Imx6 quad core board ( arm architecture ) , my kernel
version is :
# cat /proc/version
Linux version 3.0.43 (root@modx6sdk) (gcc version 4.7.1 20120402
(prerelease) (crosstool-NG
Hi,
I recently installed the recent xenomai on an i.MX6 Quad SOC from
PHYTEC (for details see end of this Email). The base system was
created with the instructions in [1]. Then I pulled in the changes
from the ipipe 3.14 tree and installed the new kernel. It boots and I
can start the basic
Gilles,
On Wed, Nov 26, 2014 at 12:49 PM, Gilles Chanteperdrix
gilles.chanteperd...@xenomai.org wrote:
On Wed, Nov 26, 2014 at 12:38:37PM +, Andreas Glatz wrote:
However, starting switchtest and latency separately on the console
doesn't produce this error. Do you have any clues what
Message: 5
Date: Thu, 24 Jul 2014 11:16:23 +0200
From: Philippe Gerum r...@xenomai.org
To: Botev, Roumen roumen.bo...@brooks.com, xenomai@xenomai.org
xenomai@xenomai.org
Subject: Re: [Xenomai] Latency Test Results (xeno-test) on Xilinx Zynq
XC702 Board with Xenomai 2.6.3
On 9 May 2014, at 11:00, xenomai-requ...@xenomai.org wrote:
Message: 2
Date: Thu, 08 May 2014 22:00:30 +0200
From: Wojciech Domski wojciech.dom...@gmail.com
To: xenomai@xenomai.org
Subject: Re: [Xenomai] Configuring analog subdevice via analogy
interface
Message-ID:
A couple of corrections:
git remote add ipipe git://http://git.xenomai.org/ipipe.git
git pull ipipe raw raw/ipipe-3.14.0 # requires a commit to the
local git tree
git remote add ipipe git://git.xenomai.org/ipipe.git
git pull ipipe raw/ipipe-3.14.0 # requires a commit to the local git
On 14 Apr 2014, at 08:13, Gilles Chanteperdrix wrote:
On 01/06/2014 04:30 PM, Andreas Glatz wrote:
Hi,
I managed to produce a kernel (v3.8.13) with xenomai 2.6.3 ipipe
patch and
rootfs (debian wheezy) with xenomai 2.6.3 libraries for my
Pandaboard ES
(omap4460). The simple regression
On 14 Apr 2014, at 08:35, Gilles Chanteperdrix wrote:
On 04/14/2014 09:24 AM, Andreas Glatz wrote:
On 14 Apr 2014, at 08:13, Gilles Chanteperdrix wrote:
On 01/06/2014 04:30 PM, Andreas Glatz wrote:
Hi,
I managed to produce a kernel (v3.8.13) with xenomai 2.6.3 ipipe
patch and
rootfs
Hi,
I think a4l_snd_insnlist() would be the best option for my use-case,
where I basically want to turn GPIOs on and off, occasionally change
DAC values and at the end acquire a certain amount of ADC samples. So
basically it's a linear sequence of synchronous (well, partly
asynchronous -
Currently my analogy driver for a new DAQ board doesn't need the
private data struct of the driver, so I set the size to 0:
/* Analogy driver structure */
static a4l_drv_t a4l_drv_pandadaq = {
.owner = THIS_MODULE,
.board_name = analogy_pandadaq,
.attach = dev_pandadaq_attach,
On 6 Apr 2014, at 22:04, Gilles Chanteperdrix wrote:
On 04/06/2014 10:57 PM, Andreas Glatz wrote:
On 6 Apr 2014, at 16:28, Gilles Chanteperdrix wrote:
On 04/06/2014 05:22 PM, Andreas Glatz wrote:
On 6 Apr 2014, at 15:44, Gilles Chanteperdrix wrote:
On 04/06/2014 01:21 PM, Andreas Glatz
On 7 Apr 2014, at 11:52, Gilles Chanteperdrix wrote:
On 04/07/2014 12:18 PM, Andreas Glatz wrote:
On 6 Apr 2014, at 22:04, Gilles Chanteperdrix wrote:
On 04/06/2014 10:57 PM, Andreas Glatz wrote:
On 6 Apr 2014, at 16:28, Gilles Chanteperdrix wrote:
On 04/06/2014 05:22 PM, Andreas Glatz
On 4 Apr 2014, at 11:44, Gilles Chanteperdrix wrote:
On 04/04/2014 12:27 PM, Andreas Glatz wrote:
Hi Gilles,
I'm finally back to my original problem below:
On 6 Jan 2014, at 17:39, Gilles Chanteperdrix wrote:
On 01/06/2014 04:30 PM, Andreas Glatz wrote:
Hi,
I managed to produce a kernel
On 6 Apr 2014, at 15:44, Gilles Chanteperdrix wrote:
On 04/06/2014 01:21 PM, Andreas Glatz wrote:
On 4 Apr 2014, at 11:44, Gilles Chanteperdrix wrote:
On 04/04/2014 12:27 PM, Andreas Glatz wrote:
Hi Gilles,
I'm finally back to my original problem below:
On 6 Jan 2014, at 17:39, Gilles
On 6 Apr 2014, at 16:28, Gilles Chanteperdrix wrote:
On 04/06/2014 05:22 PM, Andreas Glatz wrote:
On 6 Apr 2014, at 15:44, Gilles Chanteperdrix wrote:
On 04/06/2014 01:21 PM, Andreas Glatz wrote:
On 4 Apr 2014, at 11:44, Gilles Chanteperdrix wrote:
On 04/04/2014 12:27 PM, Andreas Glatz
On 6 Apr 2014, at 21:54, Gilles Chanteperdrix wrote:
On 04/06/2014 06:02 PM, Andreas Glatz wrote:
On 6 Apr 2014, at 16:54, Gilles Chanteperdrix wrote:
On 04/06/2014 01:21 PM, Andreas Glatz wrote:
First i mounted tmpfs on /tmp so I don't wear out the SD card too
much:
mount -t tmpfs -osize
On 4 Apr 2014, at 11:44, Gilles Chanteperdrix wrote:
On 04/04/2014 12:27 PM, Andreas Glatz wrote:
Hi Gilles,
I'm finally back to my original problem below:
On 6 Jan 2014, at 17:39, Gilles Chanteperdrix wrote:
On 01/06/2014 04:30 PM, Andreas Glatz wrote:
Hi,
I managed to produce a kernel
On 4 Apr 2014, at 12:00, Gilles Chanteperdrix wrote:
On 04/04/2014 12:27 PM, Andreas Glatz wrote:
Hi Gilles,
I'm finally back to my original problem below:
On 6 Jan 2014, at 17:39, Gilles Chanteperdrix wrote:
On 01/06/2014 04:30 PM, Andreas Glatz wrote:
Hi,
I managed to produce a kernel
Message: 7
Date: Tue, 1 Apr 2014 17:45:39 -0400
From: Lennart Sorensen lsore...@csclub.uwaterloo.ca
To: Gilles Chanteperdrix gilles.chanteperd...@xenomai.org
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Porting xenomai 2.6.3 and ipipe to 3.12 kernel
Message-ID:
+0xb4/0xe8) from
[c000e340] (ret_fast_syscall+0x0/0x34)
[4.498962] ---[ end trace 14db3df94de50363 ]---
[4.503936] omap2_raw_probe: device registered with ret=0
---
Andreas Glatz
Phone: +44 (0) 793 996 9950
Skype: g_andy
___
Xenomai
Message: 4
Date: Mon, 24 Mar 2014 11:01:58 -0400
From: Adam Vaughan vaugh...@umich.edu
To: xenomai@xenomai.org xenomai@xenomai.org
Subject: Re: [Xenomai] Raspberry Pi SD Card Issue
Message-ID:
cak4ezfrdafwbsz0fopzmqiddc2jzwnn-9scbx9k8l8wtb-r...@mail.gmail.com
Content-Type:
Message: 2
Date: Fri, 21 Mar 2014 10:47:20 -0400
From: Adam Vaughan vaugh...@umich.edu
To: Paul pau...@tuxcnc.org, xenomai@xenomai.org
xenomai@xenomai.org
Subject: Re: [Xenomai] Raspberry Pi SD Card Issue
Message-ID:
CAK4EZFQecV3B0uq+d3KKWX7HJB0=
Hi Gilles,
On Tue, Jan 7, 2014 at 7:23 AM, Andreas Glatz andi.gl...@gmail.com wrote:
Hi Gilles,
At first /tmp was tmpfs since I didn't want to wear out my flash with the
testing. Now I connected an external usb harddrive to the panda and mounted
one of the harddrive partions as /tmp
Hi,
I managed to produce a kernel (v3.8.13) with xenomai 2.6.3 ipipe patch and
rootfs (debian wheezy) with xenomai 2.6.3 libraries for my Pandaboard ES
(omap4460). The simple regression test, which only calls dd during the
switchtest, works fine. However the regression test with the linux test
the
problem.
I still have all three consoles open, where just one is still repsonsive.
Any further suggestions?
Thanks for any help,
A.
On Mon, Jan 6, 2014 at 5:39 PM, Gilles Chanteperdrix
gilles.chanteperd...@xenomai.org wrote:
On 01/06/2014 04:30 PM, Andreas Glatz wrote:
Hi,
I
Hi,
I was wondering if anyone is aware of an RTDM SPI driver (McSPI1) for
the OMAP4460 Soc (Pandaboard). Experimental open-source code is
welcome... any code snippets to get started would be fine, in fact.
Thanks and regards,
Andreas
___
50 matches
Mail list logo