From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Florian Feldbauer <florian@ep1.ruhr-uni-bochum.de>,
linux-can@vger.kernel.org
Subject: Re: Enable both CAN interfaces of BeagleBone Black
Date: Mon, 24 Nov 2014 19:13:00 +0100 [thread overview]
Message-ID: <5473752C.8090505@hartkopp.net> (raw)
In-Reply-To: <54735986.2090603@ep1.ruhr-uni-bochum.de>
Hello Florian,
the problem is that the pins for DCAN0 are usually used by the I2C for the
EEPROM that contains device-tree informations for the beagle-cape.
So you need to disable the I2C device-tree automatism (if enabled) and then
assign the two pins to be DCAN0.
The best tutorial I've seen so far is here:
http://www.embedded-things.com/bbb/enable-canbus-on-the-beaglebone-black/
Regards,
Oliver
On 24.11.2014 17:15, Florian Feldbauer wrote:
> Hey all,
>
> I've a BeagleBone Black here, and I would like to use
> _both_ CAN interfaces of the SoC.
> Does anybody know how to enable them?
>
> I'm using the debian sd-card image from
> http://beagleboard.org/latest-images
>
> Best regards,
> Florian
>
prev parent reply other threads:[~2014-11-24 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 16:15 Enable both CAN interfaces of BeagleBone Black Florian Feldbauer
2014-11-24 18:13 ` Oliver Hartkopp [this message]
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=5473752C.8090505@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=florian@ep1.ruhr-uni-bochum.de \
--cc=linux-can@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).