I was able to reproduce the issue, but it only happened if I didn't
have the driver loaded. I would try building it as a loadable module
then load it and confirm it's running using lsmod. Then run your test
application.
-Greg
On Mon, Apr 9, 2018 at 11:13 PM, Greg Gallagher wrote:
> That looks
That looks sane to me, this thread outlines a similar problem:
http://xenomai.org/pipermail/xenomai/2017-December/038078.html
My CFLAGS and LDFLAGS are slightly different:
XENO_CONFIG := $(PATH_TO_STAGE)/usr/xenomai/bin/xeno-config
CFLAGS := $(shell DESTDIR=$(PATH_TO_STAGE) $(XENO_CONFIG) --posi
Am Fri, 6 Apr 2018 17:33:20 +0200
schrieb Leopold Palomo-Avellaneda :
> Hi,
>
> On 06/04/18 10:47, Henning Schild wrote:
>
> [...]
>
> >> >Thanks for sharing this. IIRC, we have some Xeommai user
> >> >in-house as well who looked into cmake, need to check the status
> >> >and scope again (ma
Am Fri, 6 Apr 2018 17:37:06 +0200
schrieb Leopold Palomo-Avellaneda :
> Hi
>
> On 06/04/18 11:36, Lange Norbert wrote:
> [...]
>
> >
> > Google for "FindXenomai" to see that I am hardy the only one with
> > that need. What I would like is to have a proper solution for
> > Xenomai, and my way of
Quoting Greg Gallagher :
Tested on zynq zybo and microzed, the demo works. I built it from
stable using the 4.14 ipipe-arm repo and modprobed the module at
boot. Are you using a module or building it into the kernel?
-Greg
I'm building it into the kernel. Since I'm new to all these I just
>- none (--no-auto-init)
>- bootstrap-pic.o (--auto-init-solib)
>- bootstrap.o (--auto-init or default)
>
>To me the questions then are:
>- The code there could be encapsulated in a header?
I dont see how it could not, it just uses public API
>- or could be put in a lib?
As static lib: Not a