Hi Onur, everything works now. It was a problem with the transceiver. They were not soldered properly... If you still have some problems just write me a mail or ask in detail here. Regards, benjamin
On Tue, Sep 1, 2015 at 11:04 AM, Onur Duran <[email protected]> wrote: > Hi Benjamin > > I work on CAN Bus with BBB. Did you find your problem's solution ? > I could send data to use CAN bus with BBB but i didn't see anything do you > have idea? > > 6 Nisan 2015 Pazartesi 23:24:42 UTC+3 tarihinde Ben F. yazdı: > >> Hi Guys, >> >> I have a similar Problem. I am trying to activate the CAN1 Bus. (P9_24 & >> P9_26). >> >> With Kernel 3.8.13 I am using the bone_capemgr.9 according to >> http://www.embedded-things.com/bbb/enable-canbus-on-the-beaglebone-black/ >> It works! >> >> But with 3.19.0 I have some problems. I just can get any signal with >> candump! >> I used the dtb-rebuilder and commented out the two CAN1 lines: >> ... >> #include "am335x-peripheral-can1.dtsi" >> #include "am335x-bone-pinmux-can1.dtsi" >> ... >> >> After make install, modeprobe etc... the ifconfig of debian 3.19 and >> 3.13 (bone_capemgr.9) *looks the same.* >> >> can0 Link encap:UNSPEC HWaddr >> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> UP RUNNING NOARP MTU:16 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:10 >> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >> Interrupt:159 >> >> But with 3.19 I can't get any signal. Anyone a Idea? >> Thanks in advance for your help! >> >> Benjamin >> >> Am Montag, 30. März 2015 17:44:21 UTC+2 schrieb [email protected]: >>> >>> Hi there! >>> >>> I don't know how to get BBB's DCAN1 working, though I've been striving >>> for quite a long time. >>> >>> I installed the OS from a Debian image available at >>> http://beagleboard.org/ and followed the guide >>> http://dev.ardupilot.com/wiki/building-the-code/building-for-beaglebone-black-on-linux/ >>> to make the kernel RT-Preempt: >>> >>> root@beaglebone:~# uname -a >>> Linux beaglebone 3.8.13-rt9-00899-g3d8f2b1 #1 SMP PREEMPT Sat Jan 31 >>> 12:22:12 CET 2015 armv7l GNU/Linux >>> >>> To work with DCAN1, I also followed the guide >>> http://www.embedded-things.com/bbb/enable-canbus-on-the-beaglebone-black/ >>> using the suggested device tree overlay: >>> >>> root@beaglebone:~# modprobe can >>> root@beaglebone:~# modprobe can-dev >>> root@beaglebone:~# modprobe can-raw >>> root@beaglebone:~# echo BB-DCAN1 > $SLOTS >>> root@beaglebone:~# cat $SLOTS >>> 0: 54:PF--- >>> 1: 55:PF--- >>> 2: 56:PF--- >>> 3: 57:PF--- >>> 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G >>> 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI >>> 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN >>> 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-DCAN1 >>> >>> root@beaglebone:~# /sbin/ip link set can0 up type can bitrate 500000 >>> root@beaglebone:~# ifconfig can0 up >>> root@beaglebone:~# ifconfig can0 >>> can0 Link encap:UNSPEC HWaddr >>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >>> UP NOARP MTU:16 Metric:1 >>> RX packets:3 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:10 >>> RX bytes:24 (24.0 B) TX bytes:0 (0.0 B) >>> Interrupt:71 >>> >>> Pins seem to be muxed correctly: >>> >>> root@beaglebone:~# cat $PINS | grep 984 >>> pin 97 (44e10984) 00000032 pinctrl-single >>> root@beaglebone:~# cat $PINS | grep 980 >>> pin 96 (44e10980) 00000012 pinctrl-single >>> >>> Now, as I run a simple cansend-candump test on can0, candump doesn't get >>> anything. Is there anyone who can help me out? >>> >>> Thank you >>> >>> Frudak >>> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/1T_m9uXJ8Kc/unsubscribe. > To unsubscribe from this group and all its topics, 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.
