-black/
John
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
Behalf Of Tracy Smith
Sent: November-01-17 9:10 AM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
Hi John,
Both CANS are working on BB
half Of Tracy Smith
> Sent: November-01-17 2:51 AM
> To: beagleboard@googlegroups.com
> Subject: Re: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
>
> Hi John,
>
> Do you see support for both CAN0 and CAN1? Need both and our pins for CAN1
> are E17 and E18
leboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
> Behalf Of Tracy Smith
> Sent: October-31-17 3:42 PM
> To: BeagleBoard
> Subject: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
>
> Hi John,
>
> I'm attempting to enable CAN support for a
problems using latest debian image
Hi John,
I'm attempting to enable CAN support for a USB/CAN from a Lawicel. We have a
custom board and need to use pin D17/D18 and E17/E18 for CAN1 and CAN2.
The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h for the
BBB includes i2c0_sda (pin
Hi John,
I'm attempting to enable CAN support for a USB/CAN from a Lawicel. We have
a custom board and need to use pin D17/D18 and E17/E18 for CAN1 and CAN2.
The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h for
the BBB includes i2c0_sda (pin C17) and i2c0_scl (pin C16),
@John D
Which kernel version are you running on the black ? kernel version 3.14.x
is supposed to bring some USB, and ethernet improvements over kernel
version 3.8.x. However, I'm not sure what exactly these improvement are.
Anyhow, it was a thought while reading your post. I do know that early on
I'm a little late on this discussion but since I have lots of CAN
experience and I'm also working on getting CAN working on my Beagle so I
thought I'd jump in.
I bought the Logic Supply CBB_Serial with the on board CAN driver.
I followed the instructions on page 14 of their Serial Cape Manual
Hi William,
uname -r returns 3.8.13-bone47 from the revC board that arrived a couple of
weeks ago.
I'm running with a 2A supply since I as using a WiFi USB module. At the
moment I'm hardwired again.
Following the instructions in Derek Malloy's Exploring Beaglebone I
created a user and a group.
Hi Mark,
On my system I have dtb=am335x-boneblack.dtb, I don't think you should
comment it out.
Are you using *both *can0 and can1? You should enable just the one you need.
If you are using can0 you must comment out i2c2: cape eeprom because it
uses the same pins.
Regards,
Rui
On Wednesday,
Hi Rui,
I have reverted the changes to uEmv to comment out the #dtb line
I then modified am335x-boneblack.dts to uncomment so that it looks like the
following:
/*can0: P9.19, P9.20: disable: i2c2: cape eeprom */
/* can0: peripheral */
#include am335x-can0.dtsi
/* can0: pinmux */
#include
Hi Mark,
That kernel version has no cape manager support. You have to rebuild the
device tree.
First revert the changes to uEnv.
Then, download Robert Nelson's dtb-rebuilder (
https://github.com/RobertCNelson/dtb-rebuilder) and checkout 3.14-ti.
Edit am335x-boneblack.dts to include can0.
To
Hi Mark,
I would rebuild the device tree to make sure can0 is included.
- Revert the changes to uEnv.
- download Robert Nelson's dtb-rebuilder (
https://github.com/RobertCNelson/dtb-rebuilder) and checkout 3.14-ti.
- edit am335x-boneblack.dts to include can0.
- make
12 matches
Mail list logo
