From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Grandegger Subject: Re: [Socketcan-users] [socketcan]problem to using CAN with BeagleBone Black A5A Date: Mon, 10 Jun 2013 19:37:32 +0200 Message-ID: <51B60EDC.5000402@grandegger.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from ngcobalt02.manitu.net ([217.11.48.102]:48071 "EHLO ngcobalt02.manitu.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754286Ab3FJRhh (ORCPT ); Mon, 10 Jun 2013 13:37:37 -0400 In-Reply-To: Sender: linux-can-owner@vger.kernel.org List-ID: To: Michael Luxen Cc: Oliver Hartkopp , "linux-can@vger.kernel.org" On 06/10/2013 06:24 PM, Michael Luxen wrote: =2E.. >>> I'm not sure about the cpu-load, latency and messages lost problems= =2E My=20 >> experience on the RasperryPi is that 2x MCP2515 on one SPI-Channel d= oesn't work=20 >> with busload above 10% at 500kbit/s. >> >> That's not that much. But it's an interesting information to get an = estimation >> what one might get with this setup. > But keep in mind that the Raspi has only one SPI channel where I've c= onnected two MCP2515 (only independetn ChipSelect and Interrupt lines).= Therefore I'm interested in to sees how the BeagleBone Black can handl= e two MCP2515 on idenpendent SPI channels (SPI1/SPI2). The problem is not (only) SPI hardware but software. The CAN messages are not read-out quickly enough due to latencies resulting in message losses. May user do report that problem with the MPC251x. The following link does have some nice figures: http://clientes.netvisao.pt/anbadeol/mcp2515.html I think the software can do better but still latency is critical for th= e MPC251x, especialy MPC2510. Wolfgang. > Regards > Mike > =20 >>> -----Urspr=FCngliche Nachricht----- >>> Von: Oliver Hartkopp >>> Gesendet: Sa 08.06.2013 13:46 >>> Betreff: Re: AW: [Socketcan-users] [socketcan]problem to using CAN = with=20 >> BeagleBone Black A5A >>> An: Michael Luxen ;=20 >>> CC: linux-can@vger.kernel.org;=20 >>>> Hello Mike, >>>> >>>> thanks for pointing to that comprehensive documentation. >>>> >>>> I was asked by a colleague how to get both internal CAN controller= s working >>>> instead of adding SPI-based MCP2515 interfaces. >>>> >>>> Good job! >>>> >>>> Best regards, >>>> Oliver >>>> >>>> On 07.06.2013 21:46, Michael Luxen wrote: >>>>> Hello Mohamed, >>>>> >>>>> is you question still open or answered already? >>>>> >>>>> If still open, please have a look on this page where you can find= how to=20 >>>> enable the CAN-Devices on BeagleBone Black. >>>>> http://www.aero-box.co.uk/beaglebone-black#TOC-Enable-CANbus-devi= ce >>>>> >>>>> The only thing you have to do is to edit the am335x-bone-common.d= tsi file=20 >> for=20 >>>> enabling dcan0 and/or dcan1. >>>>> Please have in mind that dcan0 is normaly used for the optional C= apes, as=20 >>>> they use the I2C2 pins which are muxed on the same pins than dcan0= =2E >>>>> Nevertheless I've edited am335x-bone-common.dtsi successfully to = enable=20 >> dcan0=20 >>>> and dcan1. On my BeagleBone Black (Hardware A5A) eveything is runn= ing fine=20 >> on=20 >>>> both internal CAN-Interfaces with latest Angstrom and latest Debia= n as well. >>>>> Keep in mind that you have to put a CAN-transceiver on the Pins 2= 0/19=20 >> (DCAN0)=20 >>>> an 24/26 (DCAN1) on your BeagleBone Black. >>>>> >>>>> Regards >>>>> Mike >>>>> >>>>> -----Urspr=FCngliche Nachricht----- >>>>> Von: Martin Gysel >>>>> Gesendet: Di 04.06.2013 13:32 >>>>> Betreff: Re: [Socketcan-users] [socketcan]problem to using CAN wi= th=20 >>>> BeagleBone Black A5A >>>>> An: linux-can@vger.kernel.org;=20 >>>>> CC: socketcan-users@lists.berlios.de;=20 >>>>>> Am 25.05.2013 00:49, schrieb Mohamed HAMZAOUI: >>>>>>> Hi, >>>>>>> >>>>>>> I started with beaglebone black A5A, i installed on it the late= st >>>>>>> Angstrom image with : Linux beaglebone 3.8.13 #1 SMP Mon May 20 >>>>>>> 17:07:58 CEST 2013 armv7l GNU/Linux >>>>>>> >>>>>>> I have a problem when I try to add a can device, i load with mo= dprobe >>>>>>> all necessary kernel module (can, ti_hecc, c_can, c_can_platfor= m, >>>>>>> can-raw, can-bcm) but when i execute >>>>>>>> ip link add can0 type can >>>>>>> I have : RTNETLINK answers: Operation not supported >>>>>>> I used a recent version of iproute2. >>>>>> >>>>>> did you initialize the can module? do you use a can cape? if yes= , does >>>>>> your kernel already include the needed dts to enable the can mod= ule? >>>>>> >>>>>> /martin >>>>>> >>>>>> -- >>>>>> To unsubscribe from this list: send the line "unsubscribe linux-= can" in >>>>>> the body of a message to majordomo@vger.kernel.org >>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.ht= ml >>>>>> >>>>> -- >>>>> To unsubscribe from this list: send the line "unsubscribe linux-c= an" in >>>>> the body of a message to majordomo@vger.kernel.org >>>>> More majordomo info at http://vger.kernel.org/majordomo-info.htm= l >>>>> >>>> >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe linux-ca= n" in >>>> the body of a message to majordomo@vger.kernel.org >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-can= " in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-can"= in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-can" = in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >=20 >=20