From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <496CAD93.9010206@domain.hid> Date: Tue, 13 Jan 2009 16:04:51 +0100 From: Wolfgang Grandegger MIME-Version: 1.0 References: <496B6B66.7070905@domain.hid> <200901121810.42126.Sebastian.Smolorz@domain.hid> <496BA87C.2020306@domain.hid> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] [Socketcan-users] rtcanconfig rtcansend rtcanrecv List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Charlton, John" Cc: "xenomai@xenomai.org" , "socketcan-users@domain.hid" Charlton, John wrote: > Wolfgang, > > You are right. I am just learning the sja1000 registers and modes and I was looking at the 'BasicCAN' register configuration and the sja1000 can driver is using the 'PeliCAN' mode. So it does look like everything is configured correctly and it also looks like the data are tranferred from rtcan1 to rtcan0 registers except that the interrupts do not occur to notify the socket that the data is sent and received. There does not appear to be any error messages but only debug messages in the dmesg output below (all of those Wrote/Read messages are generated by the rtcan_tscan1.c printk which I am removing to reduce the spew): OK. > - What do your read at offset 0x6 (JMP)? > For idx 0: 0x30, 1: 0x22 Looks good for the IRQ selection, but I can't tell what the bit 0x02 is good for. > - What does /proc/interrupts return? > cat /proc/interrupts > CPU0 > 0: 12314 XT-PIC-XT timer > 1: 146 XT-PIC-XT i8042 > 2: 0 XT-PIC-XT cascade > 6: 0 XT-PIC-XT uhci_hcd:usb1, uhci_hcd:usb2 > 12: 13 XT-PIC-XT eth0 > 14: 0 XT-PIC-XT ide0 > 15: 2151 XT-PIC-XT ide1 > NMI: 0 Non-maskable interrupts > TRM: 0 Thermal event interrupts > ERR: 0 I just wanted to check if IRQ 3 and 5 is already used by Linux. You also can set the Xenomai IRQ flags in your driver to chip->irq_flags = 0; because IRQ sharing is not required. Maybe there are x86-related problems with the IRQs. I'm not really an expert, but sometimes there is trouble due to improper BIOS settings, interrupt routing, etc. Wolfgang.