Hello Robert, thank you for your response!
Unfortunately I don't get it work :-( What I did: 1) Downloaded the new changed dtb-rebuilder with the new files to the beaglebone 2) Un-commented everything (can0/1, spi and adc) in am335x-boneblack-custom.dts 3) Went to the dtb-builder directory (cd dtb-rebuilder-4.4-ti/) 4) ./dtc-overlay.sh 5) make 6) make install 7) Downloaded and installed canutils (git clone https://github.com/linux-can/can-utils.git) 8) shutdown -r now After the reboot, i tried to send a can message to my can test laptop: cansend can0 100#deadbeef But BBB told me: "write: Network is down" So I started: ip link set can0 up type can bitrate 500000 cansend can0 100#deadbeef But nothing happens. I checked all can-pins with the scope, there was no output signal. dmesg output looks good for me: root@beaglebone:/sfb/devicetree# dmesg | grep can [ 32.566162] c_can_platform 481cc000.can: c_can_platform device registered (regs=fa1cc000, irq=208) [ 32.623212] c_can_platform 481d0000.can: c_can_platform device registered (regs=fa1d0000, irq=209) [ 60.805589] can: controller area network core (rev 20120528 abi 9) [ 60.819806] can: raw protocol (rev 20120528) [ 194.863977] c_can_platform 481cc000.can can0: setting BTR=1c02 BRPE=0000 [ 194.864175] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready After that I tried the adc, but the expected folder /sys/bus/iio/devices/iio:device0 wasn't there, so I think the adc doesn't work too. Can you tell me, what I did wrong? Regards, Andre Am Donnerstag, 26. Mai 2016 18:26:42 UTC+2 schrieb RobertCNelson: > > > > On Thu, May 26, 2016 at 7:47 AM, wippich1981 via BeagleBoard < > [email protected] <javascript:>> wrote: > >> Hello, >> >> I've problems to change the device tree on debian jessie on my beaglebone >> black. >> >> After boot, I need the following interfaces working: >> - can0 >> - can1 >> - spi0 >> - adc >> - i2c2 disabled (to use both can interfaces, I need no cape eeprom >> support) >> >> I've installed this image (and executed apt-get update && apt-get >> upgrade): bone-debian-8.4-iot-armhf-2016-05-13-4gb.img >> >Distributor ID: Debian >> >Description: Debian GNU/Linux 8.4 (jessie) >> >Release: 8.4 >> >Codename: jessie >> >> The Kernel Version is: >> >uname -a >> >Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l >> GNU/Linux >> >> >> Previously I used a debian "wheezy" image with 3.8.13 kernel. But since >> that the device tree seems to changed a lot and now I'm stuck :-( >> >> On wheezy I changed the am335x-bone-common.dtsi (get the source from >> https://github.com/derekmolloy/boneDeviceTree.git), for disabling i2c2 >> and enabling can0/can1/spi/adc. Then I rebuilded the am335x-boneblack.dtb >> and copied it in the >> <https://github.com/derekmolloy/boneDeviceTree.git>/boot/dtbs/3.8.13-bone71 >> folder. To use the can-bus, I had to add the interfaces to >> */etc/network/interfaces*: >> >> auto can0 >> iface can0 can static >> bitrate 500000 >> >> auto can1 >> iface can1 can static >> bitrate 500000 >> >> >> After a reboot everything works fine. This was the result of many >> different tutorials about enabling periphery on beaglebone black. Propably >> it was not the right way, but I was glad that it finally worked :-) >> >> For jessie I found the dtb-rebuilder, but everything I tried to change >> did not work. New debian, no function - it's very frustrating... >> >> Can someone explain me, how to work with the dtb-rebuilder, so I can >> enable at least both can interfaces? >> > > > https://github.com/RobertCNelson/dtb-rebuilder/commit/d664d9d5411d2242355cd777b0211a2a3268cfbe > > Just un-comment what you want: > > > https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-custom.dts#L47-L65 > > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f2fbb7b2-fd58-4f61-8b24-bde1dc6c9f0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
