From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <45DD8303.8060605@domain.hid> Date: Thu, 22 Feb 2007 12:48:19 +0100 From: Wolfgang Grandegger MIME-Version: 1.0 Subject: Re: [Xenomai-help] CAN driver References: <45DC1D05.1000206@domain.hid> <45DC2478.2020602@domain.hid> <45DC39DE.8050802@domain.hid> <45DC3E6C.8040905@domain.hid> <45DD5DC0.6040402@domain.hid> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: roland Tollenaar Cc: Xenomai-help@domain.hid, Jan Kiszka roland Tollenaar wrote: > Hi, > > The first thing I notice is that I do not seem to find the devices > rtcan0, rtcan1 etc. The devices will be available when after the driver have properly loaded. You can find corresponding messages in the system log (type dmesg to list them. Here is the output from my Laptop: RT-Socket-CAN 0.20.2 - (C) 2006 RT-Socket-CAN Development Team rtcan: registered rtcan0 rtcan0: VIRT driver loaded rtcan: registered rtcan1 rtcan1: VIRT driver loaded RTCAN SJA1000 driver initialized rtcan: registered rtcan2 > They are mentioned in the documentation and I presume they must be nodes in > /dev or so. But I cannot find them. rt-can is statically built into my No, see above. > kernel so I don;t need to load any modules. I have selected the SJA > chip and the PEAK CAN Dongle. You must build the driver for the PEAK CAN Dongle as module and specify the port type, I/O port and IRQ number when you load it. But as Jan already pointed out, you can use the virtual CAN driver for getting started. > I am reading the README in /src/can and the one in ksrc/drivers/can. > > /proc/rtcan is present but no devices rtcan0, rtcan1 etc under it. > > What have I missed? What have you selected? Check your boot log! Wolfgang. > On 2/22/07, Wolfgang Grandegger wrote: >> Jan Kiszka wrote: >> > Wolfgang Grandegger wrote: >> [...] >> >> I have attached a patch for a nice program to measure >> >> the round trip time of CAN messages. It contrast to the other CAN >> >> utility programs, it uses the POSIX-API and works as-is for Socket-CAN >> >> as well. Jan, any objections to include it? If yes, I'm going to >> provide >> >> a README. >> > >> > On first glance, nope, looks nice and clean. >> >> I have just commited the example program "rtcan_rtt" to the trunk. >> >> Wolfgang. >> > >