According to the Logic Supply serial cape manual . . . *Important:* > > *You cannot just test the CAN Bus software without connecting the > CBB-Serial hardware to another CAN device. You need to be connected to a > receiving CAN device so that ACK (acknowledge) packets get sent and the CAN > sender can mark it as sent (i.e. stop buffering it), otherwise the buffer > gets full after a short period of time and all future writes to the CAN Bus > will fail.* >
We've pretty much duplicated the exact steps you've done with the exception of connecting the beaglebone + serial cape to an external CAN device. We've also tested kernels 3.8.x, 3.14.x, and 4.1.x( most recently ). They all work. Most curious though . . *I am working with a BeagleBone Black rev C for a project using CAN. I am using the CBB-Serial-r02 cape because we need the UART features too* We're using . . . [email protected] password: Last login: Mon May 11 20:23:49 2015 from 192.168.7.1 debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots 0: 54:P---L *cape-CBB-Serial,r01,Logic Supply,cape-CBB-Serial* 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- Curious because you say you're using an r2, where we're using and r1. Is this a Logic Supply board ? On Mon, Jun 1, 2015 at 12:10 PM, Robert Nelson <[email protected]> wrote: > On Mon, Jun 1, 2015 at 1:16 PM, <[email protected]> wrote: > > I am working with a BeagleBone Black rev C for a project using CAN. I am > > using the CBB-Serial-r02 cape because we need the UART features too. The > > problem is that CAN is not working. I did a lot of things to test it on a > > 3.8-rt kernel from RobertCNelson (which is only PREEMPT), but it didn't > > worked at all. Some things that I did: > > > > 1) Always modprobe the can modules (can, can-dev, can-raw) > > 2) Compiled and installed canutils, always using the "cangen can0" to > test > > the can output > > 3) Always run "ip link set can0 up type can bitrate 125000; ifconfig can0 > > up" to activate can0 > > 4) Installed the CBB-Serial-r02 dtbs from the official repository, even > that > > the debian image that I used already includes it > > 5) Test the output with an osciloscope. I did the same test with an EzDSP > > 28335 and it worked, so it is not a problem with this part of the method > > 6) I tried to do a candump can0 with the DSP generating random data, but > the > > candump didn't show any data > > > > I recompiled 3.14 kernel using the dtb-rebuilder (instructions on this > > tutorial: > > https://groups.google.com/d/msg/beagleboard/_9u1B6ZkgCU/K2ARgwfC490J) > and > > enabling the DCAN1 (because DCAN0 disables the I2C used for capemgr) and > it > > didn't worked too. > > > > Well, I ran out of options here. Some one is having problems with the > rev C > > and CAN too or that is some problem with my method? > > No reason to double post to the group. ;) > > can0/can1 works on 3.14/4.1.x > > Right now i'd recommend you use v4.1.x and utilze cape overlays.. > > Step 1: update kernel: > > sudo apt-get update > sudo apt-get install linux-image-4.1.0-rc6-bone5 > sudo reboot > > Step 2: clone overlay repo: > > git clone https://github.com/beagleboard/bb.org-overlays > cd ./bb.org-overlays > > Update dtc: > ./dtc-overlay.sh > > Install overlays: > ./install.sh > > reboot.. > > the CBB-Serial-r02 cape should be auto-detected.. if not, please reply > with: > > dmesg | grep cape > > So i can add it.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
