From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Sender: had2006@gmail.com In-Reply-To: References: <55072D34.1070405@xenomai.org> <550837E2.9050701@xenomai.org> <55083DA4.3080201@xenomai.org> <550850D5.9060207@xenomai.org> <5508600D.4020500@xenomai.org> <550B0626.5090801@xenomai.org> <550B1584.8040309@xenomai.org> <550FF5FB.3090603@xenomai.org> <55101373.7010008@xenomai.org> Date: Mon, 30 Mar 2015 17:51:18 +0100 Message-ID: From: Helder Daniel Content-Type: text/plain; charset=UTF-8 Subject: Re: [Xenomai] Xenomai/cobalt: low_init(): binding failed: Function not implemented error issued when trting to run latency app on xeno 3.x-rc3 List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum Cc: "Xenomai@xenomai.org" Hi, I installed ipipe patched linux 3.16.7 and Xenomai 3.0-rc4 from the scratch and all the compiling errors that I was experiencing were gone. So It should have been a local installation issue as you pointed out. Probably due to many reinstalls of successive Xenomai new versions, without proper clean up of the oldest. I am just cleaning the oldest one removing folder /usr/xenomai. May be there is a better way? Sorry to mess up things. thanks On 23 March 2015 at 13:55, Helder Daniel wrote: > On 23 March 2015 at 13:21, Philippe Gerum wrote: > >> On 03/23/2015 12:47 PM, Helder Daniel wrote: >> > PS: I can run also /usr/xenomai/bin/latency >> > >> >> Sorry, you lost me. You are trying way too many things in parallel, >> reporting apparently inconsistent results. >> > > I am sorry. > I am porting several demos that I developed in 2.5 to version 3. > Kernel space and userspace. And yes I am trying too many things at once. > I tried to filter the issues when asking for your help but it seems I > don't. > > If you can run latency, then the Cobalt inits certainly went well. > > > Yes. After reboot: dmesg | grep -i xeno reported that Cobalt inits well. > > >> Or >> maybe you are running a Mercury version of latency, in which case you >> might have two Xenomai installations somehow conflicting. >> > > I thought also that this might be an installation issue so I deleted > /usr/xenoami before reinstalling Xenomay (Cobalt) again. > > >> The last time you reported ENODEV when booting Cobalt, you also >> mentioned that using the latest patch including this change did fix the >> issue: >> >> http://git.xenomai.org/ipipe.git/commit/?h=ipipe-3.14&id=02416ccdfe926cc1434dc8e0b1fb03693718c45d > > > Yes. But now I noticed that sometimes Cobalt does not initialize returning > ENODEV. > > >> >> At this point, it looks like this is a local installation issue, not a >> Xenomai one. > > > It might. I am gonna reinstall everything from scratch (kernel too), > before I get back to you again. > > Thanks > > > > -- Helder Daniel UALG - FCT DEEI http://w3.ualg.pt/~hdaniel