From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4FEC8A85.4050506@epfl.ch> Date: Thu, 28 Jun 2012 18:47:01 +0200 From: Klas Kronander MIME-Version: 1.0 References: , <4FE60190.5000108@xenomai.org> <4FEC3FF0.1050307@grandegger.com>, <4FEC4245.9090804@grandegger.com> <4FEC46B5.7060700@grandegger.com> <4FEC5381.9040804@epfl.ch> <4FEC570A.8040406@grandegger.com> <4FEC5BD9.4060105@grandegger.com> <4FEC819D.2080804@epfl.ch> <4FEC8259.2090300@xenomai.org> In-Reply-To: <4FEC8259.2090300@xenomai.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Peak PCI CAN card RTCAN problem List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix , "xenomai@xenomai.org" On 2012-06-28 18:12, Gilles Chanteperdrix wrote: > On 06/28/2012 06:09 PM, Klas Kronander wrote: >> >> On 2012-06-28 15:27, Wolfgang Grandegger wrote: >>> On 06/28/2012 03:07 PM, Wolfgang Grandegger wrote: >>>> On 06/28/2012 02:52 PM, Klas Kronander wrote: >>>>> Hi, >>>>> >>>>> ok did that. The return value from rt_dev_socket is -14. I could not >>>>> find the definition of EPROTONOSUPPORT anywhere, so I don't know if this >>>>> was the expected value? >>>> ~$ errno 14 >>>> #define EFAULT 14 /* Bad address */ >>>> >>>> Hm, strange. I have to look that up. >>> To better understand what you are doing... are you using a Xenomai >>> enabled kernel? Does the latency test work? >>> >>> Wolfgang. >> Yes, I am using a Xenomai enabled kernel. None of the tests seem to work >> though. >> >> clocktest just gives me zeros. latency does not show anything. I have >> tried to recompile the kernel, still the same result. How find out >> what's wrong? I followed the guidlines on the xenomai website for the >> kernel configuration. > http://www.xenomai.org/index.php/Configuring_x86_kernels#Does_Xenomai_work.3F > In the syslog it seems as xenomai was initialized properly. The mesages correspond to those on the faq. I also looked through the troubleshooting file, nothing there seems to help my case. I will try to redo everything again with a different kernel version to see if that helps. Any other ideas? Thanks, Klas