From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Tue, 10 Dec 2013 09:01:52 +0100 From: Wolfgang Grandegger In-Reply-To: <000001cef515$c786ed70$5694c850$@hs-augsburg.de> References: <000001cef515$c786ed70$5694c850$@hs-augsburg.de> Message-ID: Subject: Re: [Xenomai] rtdm can on mpc5121e - no rtcan devices detected List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andreas Gareis Cc: xenomai@xenomai.org On Mon, 9 Dec 2013 20:35:12 +0100, "Andreas Gareis" wrote: > Von: Wolfgang Grandegger > Gesendet: Montag, 9. Dezember 2013 20:10 >> >> On Mon, 9 Dec 2013 19:17:47 +0100, "Andreas Gareis" >> wrote: >> > Von: Tom Evans >> > Gesendet: Sonntag, 8. Dezember 2013 23:07 >> >> >> >> Did the CAN devices work before you installed Xenomai? Get them >> >> working there first. >> >> >> > >> > Yes, the CAN devices worked before Xenomai installation. They were >> > shown in >> > ifconfig and communication with other CAN-devices was possible. >> > >> > When I select normal (non rt) CAN-support and xenomai kernel (without >> > RT-CAN) in the kernelconfig, working CAN devices are also available. >> > >> > Now I want to use RT-CAN with xenomai. So, I activated "RT-Socket-CAN" >> > and "MSCAN driver for MPC52xx and MPC512x" in the kernelconfig. >> > When "normal" CAN support (Networking support => CAN bus >> > subsystem support => CAN Device Drivers Freescale MPC5xxx >> > onboard CAN controller) is disabled, the xenomai module >> > "xeno_can_mscan.ko" isn't able to start. When "normal" CAN support >> >> That's the real problem. What happen's if you want to start the CAN >> device? > > First I call "insmod xeno_can.ko". dmesg shows: > RT-Socket-CAN 0.90.2 - (C) 2006 RT-Socket-CAN Development Team > > Then I call "insmod xeno_can_mscan.ko". > This operation gets stuck (the insmod doesn't return). > In dmesg there are no messages. > lsmod shows that xeno_can is running and xeno_can_mscan is still loading. Add some pr_info/printk to the drivers probe function to see where it hangs. Wolfgang.