All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Michael Luxen <mluxen@gmx.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: AW: [Socketcan-users] [socketcan]problem to using CAN with BeagleBone Black A5A
Date: Sat, 08 Jun 2013 13:35:08 +0200	[thread overview]
Message-ID: <51B316EC.3090300@hartkopp.net> (raw)
In-Reply-To: <zarafa.51b23885.159b.07db93856850360d@v14647.1blu.de>

Hello Mike,

thanks for pointing to that comprehensive documentation.

I was asked by a colleague how to get both internal CAN controllers 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 enable the CAN-Devices on BeagleBone Black.
> http://www.aero-box.co.uk/beaglebone-black#TOC-Enable-CANbus-device
> 
> The only thing you have to do is to edit the am335x-bone-common.dtsi file for enabling dcan0 and/or dcan1.
> Please have in mind that dcan0 is normaly used for the optional Capes, as they use the I2C2 pins which are muxed on the same pins than dcan0.
> Nevertheless I've edited am335x-bone-common.dtsi successfully to enable dcan0 and dcan1. On my BeagleBone Black (Hardware A5A) eveything is running fine on both internal CAN-Interfaces with latest Angstrom and latest Debian as well.
> Keep in mind that you have to put a CAN-transceiver on the Pins 20/19 (DCAN0) an 24/26 (DCAN1) on your BeagleBone Black.
> 
> Regards
> Mike
> 
> -----Ursprüngliche Nachricht-----
> Von:	Martin Gysel <m.gysel@gmail.com>
> Gesendet:	Di 04.06.2013 13:32
> Betreff:	Re: [Socketcan-users] [socketcan]problem to using CAN with BeagleBone Black A5A
> An:	linux-can@vger.kernel.org; 
> CC:	socketcan-users@lists.berlios.de; 
>> Am 25.05.2013 00:49, schrieb Mohamed HAMZAOUI:
>>> Hi,
>>>
>>> I started with beaglebone black A5A, i installed on it the latest
>>> 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 modprobe
>>> all necessary kernel module (can, ti_hecc, c_can, c_can_platform,
>>> 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 module?
>>
>> /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.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
> 


  reply	other threads:[~2013-06-08 11:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 19:46 AW: [Socketcan-users] [socketcan]problem to using CAN with BeagleBone Black A5A Michael Luxen
2013-06-08 11:35 ` Oliver Hartkopp [this message]
2013-07-31  9:23 ` Jeffrey Lin
  -- strict thread matches above, loose matches on Subject: below --
2013-06-08 21:45 Michael Luxen
2013-06-09  7:11 ` Oliver Hartkopp
2013-06-10  9:49   ` Mohamed HAMZAOUI
2013-06-10 16:24 Michael Luxen
2013-06-10 19:54 Michael Luxen
2013-06-16 19:35 Michael Luxen
2013-07-31 22:45 Michael Luxen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51B316EC.3090300@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-can@vger.kernel.org \
    --cc=mluxen@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.