From: Wolfgang Grandegger <wg@grandegger.com>
To: Mohamed HAMZAOUI <requinham@gmail.com>
Cc: linux-can Mailing List <linux-can@vger.kernel.org>,
Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
Subject: Re: Fwd: problem to using CAN on beaglebone black A5A
Date: Mon, 03 Jun 2013 13:21:45 +0200 [thread overview]
Message-ID: <51AC7C49.7070700@grandegger.com> (raw)
In-Reply-To: <CABMxt4gBjFZnWCx-dY=PpnbQ7P96ZhXAeJQ71c34J3jtTKV_1A@mail.gmail.com>
On 06/03/2013 01:09 PM, Mohamed HAMZAOUI wrote:
> Hi,
>
> Hardware : BeagleBone Black version A5A
> (http://beagleboard.org/Products/BeagleBone%20Black )
> Linux distribution : Angstrom
> Linux kernel : 3.8.13
> the driver for the can is C_CAN
>
> I can solve this issue by loading the correct cape firmware for my
> BeagleBone Black with :
> echo BB-BONE-SERL-01 > /sys/devices/bone_capemgr.9/slots
> we need to have the related firmware in /lib/firmware and
> bone_capemgr.9 have not always the same name (example bone_capemgr.7,
> ...)
>
> The problem actually is that is not possible to load the second CAN
> channel like mentionned by Olivier :
> "A Problem of this board
>
> http://circuitco.com/support/index.php?title=TT3201_CAN_Cape#EEPROM
>
> is, that the pins for the second D_CAN are assigned to the I2C to read the
> EEPROM. I have no idea how to solve this right now."
OK, I see.
> Any idea ?
Maybe it could be done by just modifying the DTS file. Could you show
that DTS file?
Wolfgang.
next prev parent reply other threads:[~2013-06-03 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 22:56 problem to using CAN on beaglebone black A5A Mohamed HAMZAOUI
2013-05-25 11:37 ` Oliver Hartkopp
2013-05-25 11:55 ` Mohamed HAMZAOUI
2013-05-26 10:35 ` Oliver Hartkopp
[not found] ` <CABMxt4h-0zYYBvjUqBdf=eChKXxJv77OPhQmh_y7rkwj18mdcQ@mail.gmail.com>
[not found] ` <CABMxt4jMmBeMqFeyRMQ=5PtQtt6SHDGNGXUGm-WzPsW6Er9+SQ@mail.gmail.com>
2013-05-28 17:02 ` Oliver Hartkopp
2013-05-28 18:00 ` Wolfgang Grandegger
[not found] ` <CABMxt4gO+mQR3JshUDUztKC7oPt3zXcyZ-1Hp4dn7Wy7=CEhAQ@mail.gmail.com>
[not found] ` <CABMxt4gBjFZnWCx-dY=PpnbQ7P96ZhXAeJQ71c34J3jtTKV_1A@mail.gmail.com>
2013-06-03 11:21 ` Wolfgang Grandegger [this message]
2013-06-03 18:03 ` Fwd: " Mohamed HAMZAOUI
2013-06-03 18:41 ` Wolfgang Grandegger
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=51AC7C49.7070700@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-can@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=requinham@gmail.com \
/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).