From: Wolfgang Grandegger <wg@grandegger.com>
To: Mohamed HAMZAOUI <requinham@gmail.com>
Cc: linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: Fwd: problem to using CAN on beaglebone black A5A
Date: Mon, 03 Jun 2013 20:41:58 +0200 [thread overview]
Message-ID: <51ACE376.1040807@grandegger.com> (raw)
In-Reply-To: <CABMxt4jcBXyJDs6D7N5SM7iBLvZGxk0geougX3u=Kf4_=74E2g@mail.gmail.com>
On 06/03/2013 08:03 PM, Mohamed HAMZAOUI wrote:
> I can't find DTS file, so can you give me more information about this file ?
DTS stands for "Device Tree Source"...
> there is the kernel output when I change the device tree to get can channels :
... so how do you change the device tree?
> [ 113.083038] bone-capemgr bone_capemgr.9: part_number
> 'BB-BONE-SERL-01', version 'N/A'
> [ 113.093905] bone-capemgr bone_capemgr.9: slot #7: generic override
> [ 113.101776] bone-capemgr bone_capemgr.9: bone: Using override
> eeprom data at slot 7
> [ 113.110931] bone-capemgr bone_capemgr.9: slot #7: 'Override Board
> Name,00A0,Override Manuf,BB-BONE-SERL-01'
> [ 113.122488] bone-capemgr bone_capemgr.9: slot #7: Requesting part
> number/version based 'BB-BONE-SERL-01-00A0.dtbo
> [ 113.134366] bone-capemgr bone_capemgr.9: slot #7: Requesting
> firmware 'BB-BONE-SERL-01-00A0.dtbo' for board-name 'Override Board
> Name', version '00A0'
> [ 113.150154] bone-capemgr bone_capemgr.9: slot #7: dtbo
> 'BB-BONE-SERL-01-00A0.dtbo' loaded; converting to live tree
> [ 113.162739] bone-capemgr bone_capemgr.9: slot #7: #2 overlays
> [ 113.171190] platform 481d0000.d_can: alias fck already exists
You seem to use the alias twice.
> [ 113.184668] c_can_platform 481d0000.d_can: invalid resource
> [ 113.201248] c_can_platform 481d0000.d_can: control memory is not
> used for raminit
> [ 113.218966] c_can_platform 481d0000.d_can: c_can_platform device
> registered (regs=fa1d0000, irq=71)
> [ 113.243172] bone-capemgr bone_capemgr.9: slot #7: Applied #2 overlays.
>
> I can't get the second CAN channel !
Some doc of the CAN device tree bindings can be found here:
-
http://lxr.linux.no/#linux+v3.8.6/Documentation/devicetree/bindings/net/can/c_can.txt
In a recent kernel tree, there seem to be support for two D_CAN devices
on the AM33xx SOCs:
-
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am33xx.dtsi
I can not tell you more details because I'm not familiar with that CPU.
Hope it helps anyway.
Wolfgang.
Wolfgang.
prev parent reply other threads:[~2013-06-03 18:42 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 ` Fwd: " Wolfgang Grandegger
2013-06-03 18:03 ` Mohamed HAMZAOUI
2013-06-03 18:41 ` Wolfgang Grandegger [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=51ACE376.1040807@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-can@vger.kernel.org \
--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 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.