On 2017-12-18 15:49, Lange Norbert wrote:
> Same issue with latest ipipe. Threads look like this (when the instance is
> halted in the debugger).
> Somehow, atleast the RT Tasks will block waiting on a timerfd when one task
> is in state XT (whatever that means)
>
> # cat
You'll have to be more specific then "it didn't work", is it possible
to post some code so we can see what you are trying to do?
-Greg
On Mon, Dec 18, 2017 at 7:12 PM, rajae rajae wrote:
> Hello everyone please I have a question about rt-fprontf it didn't work
>
Hello everyone please I have a question about rt-fprontf it didn't work
,should I call a specific function like rt_print_auto_init(1) or what
exactly
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
Sorry I should say that "a team at Johnson Space Center" not the whole center
itself. :)
Steven
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
I don't really want to congratulate Jan, because I think the progression of
the project is very sad for all of us. (And I am sure he doesn't want to be
congratulated for having more work to do -- haha.) I can't imagine things
would have ever needed to change if Gilles was still with us.
Like
On 18/12/17 07:33, Jan Kiszka wrote:
> On 2017-12-15 21:42, Philippe Gerum wrote:
>> On 12/15/2017 02:48 PM, Philippe Gerum wrote:
>>> On 12/15/2017 02:40 PM, Jan Kiszka wrote:
On 2017-12-15 14:29, Philippe Gerum wrote:
> On 12/15/2017 02:20 PM, Jan Kiszka wrote:
>> On 2017-12-15
Same issue with latest ipipe. Threads look like this (when the instance is
halted in the debugger).
Somehow, atleast the RT Tasks will block waiting on a timerfd when one task is
in state XT (whatever that means)
# cat /proc/xenomai/sched/threads
CPU PIDCLASS TYPE PRI TIMEOUT
Hi,
I looked into why this driver isn't compiling, basically it needs to
be brought up to match the newer imx serial driver. It's relying on
files and structures that existed in earlier versions of the kernel
before a reorganization happened (around 3.18 I think). I have access
to a i.mx6
On 2017-12-17 20:16, Philippe Gerum wrote:
>
> Sixteen years after Gilles and I founded the Xenomai project, time has
> come for me to hand over the leadership to a contributor recognized for
> his skills, bringing fresh ideas, and a creative roadmap.
>
> Jan Kiszka has agreed to take over the
Hello,
I tried debugging a cobalt application, and when I hit a breakpoint most of the
system freezes.
If I run for example top over Serial or SSH, then the display won`t be
refreshed anymore,
A separate program running as RT Task, waiting for an timer-event (occurring 10
times a second) will
Passing the options returned by `xeno-config --skin=posix --ldflags` to the
linker will automatically "wrap" the calls to most `posix_` functions (full
list at /usr/xenomai/lib/posix.wrappers). When a function (e.g.:
pthread_create() ) is "wrapped", then all the calls to `pthread_create()` will
Hello,
I am programming an application that runs in the secondary zone,
communicating with a primary zone application.
(Briefly , in the primary zone , i do data acquisition that I write in a
shared memory. When i'm done writing data, i send a signal to my
seondary zone program through a pipe
Le 18/12/2017 à 09:13, Stéphane Ancelot a écrit :
Hi,
I have got a program that uses some xeno heap api functions for shared
memory access, but I would like to be able to run my program on the
secondary space for pthreads. This is not a hard realtime task.
Is there a flag in xenomai that
Hi,
I have got a program that uses some xeno heap api functions for shared
memory access, but I would like to be able to run my program on the
secondary space for pthreads. This is not a hard realtime task.
Is there a flag in xenomai that permits specifying which pthread_ func
we use
14 matches
Mail list logo