His relentless dedication was a true source of inspiration.
I believe he made a valuable and long-lasting contribution, which is I’m
sure all any of us hope to be true at the end of our lives.
His legacy will live on through all that will ever stem from his passionate
and meaningful work.
Mes pl
Hi Mathieu,
Thank your for your much appreciated contribution.
I have been playing around with your patch for a couple of hours now, and I
appear to be experiencing the same stability issue as the one I had with
the patch your proposed back in November.
I was able to run /usr/xenomai/bin/latency
au :
> On 16-03-14 12:47 AM, Nicolas SCHURANDO wrote:
> > Hi Mosta,
> >
> > I have written a quick guide to get Xenomai 3.0 on the Raspberry Pi 2
> > working at
> https://www.raspberrypi.org/forums/viewtopic.php?p=926466#p926466
> > .
> >
> > It relies
Hi Mosta,
I have written a quick guide to get Xenomai 3.0 on the Raspberry Pi 2
working at https://www.raspberrypi.org/forums/viewtopic.php?p=926466#p926466
.
It relies on a post patch written by a member of the mailing list a few
month ago.
I however find the system to be very unstable so I wou
implement interrupt-based or
dma-based transfer, your contribution is welcome!
https://github.com/nicolas-schurando/spi-bcm283x-rtdm
Regards,
Nicolas
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
Hi guys,
So I have been playing around with the Raspberry Pi 2 for a couple of days
now. And I keep noticing that at random times, but usually in a matter of
seconds / minutes when there is a couple of hundreds of ko/s ethernet
traffic, the device will freeze entirely.
I have tried a few things,
; wrote:
> On 01/18/2016 07:15 PM, Nicolas SCHURANDO wrote:
> > Hi Philippe,
> >
> > I switched to branch stable-3.0.x, retrieved your commit b411e4c
> > "lib/cobalt: add init trace points", and rebuilt everything.
> >
> > Below is what
Hi Elmar,
The version of the linux kernel you should use is determined by the version
of the i-pipe patch that is available for the hardware you are targeting.
Here, as it is probably the case for most embedded boards, it turns out
that the i-pipe patch alone is not enough.
If you are using a ras
est-bug-wa] vxworks_init: failed to
> initialize VxWorks clock (res=100 ns)
>0"022.093| WARNING: [main] setup call vxworks failed
>0"024.535| BUG in xenomai_init(): [main] initialization failed, EINVAL
Regards
2016-01-18 16:19 GMT+01:00 Philippe Gerum :
> On
:00 Philippe Gerum :
> On 01/15/2016 10:57 AM, Nicolas SCHURANDO wrote:
> > Hi Philippe,
> >
> > Thank your for your answer. I have read the manual page entitled
> > "Application setup and init", and in particular the part about manual vs
> > automati
gt; implicit call)
What could I be missing ?
Cheers,
Nicolas
2016-01-14 18:24 GMT+01:00 Philippe Gerum :
> On 01/14/2016 10:22 AM, Nicolas SCHURANDO wrote:
> > Hello everyone,
> >
> > In an attempt to migrate from Xenomai 2.6.4 on a Raspberry Pi 1 to
> Xenoma
Hello everyone,
In an attempt to migrate from Xenomai 2.6.4 on a Raspberry Pi 1 to Xenomai
3.0.1 on a Raspberry Pi 2, I get an error when trying to spawn a VxWorks
task in a fairly simple test program. Here is the output :
0"000.064| WARNING: [main] Xenomai compiled with full debug enabled,
>
en steps 1 and 5.
Have you cross-compiled for the correct arch ? Providing us with the
content of your dmesg would be a starting point.
Regards,
Nicolas Schurando
2015-08-19 13:58 GMT+02:00 :
> i followed documentation to get xenomai up and running on a udoo board
> but when i run the latenc
Hello everybody,
I am running a real-time application using the VxWorks skin, on a Raspberry
Pi 1, with Xenomai 2.6.4. The application also makes use of the native API
to spawn an additional and periodic task. I have witnessed that, at random,
the product will stop working. Taking a look at the sy
14 matches
Mail list logo
