thank you so much for clarifiation m8! been trying to get my BB Green to communicate CAN for too long now, actually ERROR- passive vs. active led me to right track here!
Den torsdag 8 augusti 2013 kl. 21:10:04 UTC+2 skrev [email protected]: > > While I can't help solve the problem, maybe I can provide some more > information to help debug it, as it appears I'm seeing a similar problem. > > I am merely trying to get DCAN1 up and running, and have followed numerous > tutorials, etc (including the one Scott points out) to get the DCAN1 > running, and I can't get it to send data. I've not tried receiving, > because if I can't send then I don't care if I can't receive at this point. > > > The interesting thing I notice is when I do cansend, I get data spewing > back and forth on the wire. I've tried this with a CANBus controller as > well as just tying DCAN1_TX and DCAN1_RX together. If I disconnect one of > the Tx/Rx lines, then the spewing stops. > > Here is what I do: > > *reboot* > > canconfig can0 ctrlmode bitrate 125000 triple-sampling on > canconfig can0 start > cansend can0 051#11.22.33.44.55.66.77.88 > > > > This results in no Tx bytes as reported by ifconfig or ip -details > -statistics link show can0. The ip link shows that the can state is > ERROR-PASSIVE which from my exhaustive research says that there is an > active error, and it will listen, but not transmit. Previous to this, the > state as ERROR-ACTIVE (which is supposedly OK). > > I'd love to figure out what the problem we're running into is. > > My system details: > Angstrom base image with 3.8.13 kernel image > I've also built an image from the Ubuntu directions and tried that with no > difference (I've not built the whole image as I don't have a 4GB SD card > yet). > > Thanks in advance for any help that can be provided, > Drew Hintz > > On Wednesday, August 7, 2013 9:42:05 PM UTC-4, Scott Heighway wrote: >> >> >> I've been following the examples provided here ( >> http://www.aero-box.co.uk/beaglebone-black#TOC-CANbus ) and have managed >> to get both CAN modules to show up, but I can only get CAN0 to transmit and >> receive. Nothing untoward shows up in dmesg, and I can bring up the >> devices; its only CAN1 that doesn't work. Does anyone have any suggestions >> to figure out what could be wrong? >> >> I'm running Ubuntu 13.04 (07-22), and have the following modifications to >> my am335x-bone-common.dtsi file: >> >> *snip* >> dcan0_pins: pinmux_dcan0_pins { >> pinctrl-single,pins = < >> 0x178 0x12 /* ic2c.sda_dcan0_rx, >> SLEWCTRL_FAST | INPUT_PULLUP | MODE2 */ >> 0x17C 0x32 /* ic2c_scl.dcan0_rx, >> SLEWCTRL_FAST | RECV_ENABLE | INPUT_PULLUP | MODE2 */ >> >; >> }; >> >> dcan1_pins: pinmux_dcan1_pins { >> pinctrl-single,pins = < >> 0x180 0x12 /* uart1_rxd.d_can1_tx, >> SLEWCTRL_FAST | INPUT_PULLUP | MODE2 */ >> 0x184 0x32 /* uart1_txd.d_can1_rx, >> SLEWCTRL_FAST | RECV_ENABLE | INPUT_PULLUP | MODE2 */ >> >; >> }; >> *snip >> >> *snip* >> uart2: serial@48022000 { >> status = "disabled"; >> }; >> >> dcan0: d_can@481cc000 { >> status = "okay"; // Switch on DCAN0 >> pinctrl-names = "default"; // Apply default >> pinmuxing >> pinctrl-0 = <&dcan0_pins>; >> }; >> >> dcan1: d_can@481d0000 { >> status = "okay"; // Switch on DCAN1 >> pinctrl-names = "default"; // Apply default >> pinmuxing >> pinctrl-0 = <&dcan1_pins>; >> }; >> *snip* >> >> *snip* >> &i2c2 { >> status = "disabled"; >> pinctrl-names = "default"; >> pinctrl-0 = <&i2c2_pins>; >> *snip* >> >> >> And my /proc/net/dev file: >> >> Inter-| Receive | >> Transmit >> face |bytes packets errs drop fifo frame compressed multicast|bytes >> packets errs drop fifo colls carrier compressed >> lo: 0 0 0 0 0 0 0 0 >> 0 0 0 0 0 0 0 0 >> eth0: 2351960 13013 0 0 0 0 0 0 >> 32410 388 0 0 0 0 0 0 >> usb0: 474271 9333 0 0 0 0 0 0 >> 4156896 15720 0 0 0 0 0 0 >> can0: 0 0 0 0 0 0 0 0 >> 0 0 0 0 0 0 0 0 >> can1: 0 0 0 0 0 0 0 0 >> 0 0 0 0 0 0 0 0 >> >> >> And my /sys/kernel/debug/pinctrl/44e10800.pinmux/pins >> >> *snip* >> pin 94 (44e10978) 00000012 pinctrl-single >> pin 95 (44e1097c) 00000032 pinctrl-single >> pin 96 (44e10980) 00000032 pinctrl-single >> pin 97 (44e10984) 00000012 pinctrl-single >> *snip* >> >> Thanks in advance. >> > -- 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.
