On Tue, Jul 23, 2019 at 12:03 AM debounce <[email protected]> wrote: > > Thanks for the feedback guys. I went ahead and attacked this problem again > tonight. > > This one was really strange. The reason I was using config-pin instead of > overlays was because config-pin seems to be the preferred method on > beaglebone to configure the pins now on the newer kernel and OS. > "/sys/devices/bone_capemgr" no longer exists on my OS. So the two options I > have is to use config-pin (beaglebone-universal-io) or /boot/uEnv.txt > > I tried enabling the overlay in /boot/uboot.txt by adding: > uboot_overlay_addr0=/lib/firmware/BB-CAN1-00A0.dtbo > uboot_overlay_addr0=/lib/firmware/BB-CAN0-00A0.dtbo > > This resulted in the same behavior. > > Then I tried to add the "DCAN" overlay: > uboot_overlay_addr0=/lib/firmware/BB-DCAN1-00A0.dtbo > > This seems to have changed something and both CAN interfaces (can0 and can1) > began to work! After I verified CAN was working with the manually added > overlays in uEnv.txt, I went ahead and removed all the manually added CAN > overlays (BB-CAN0-00A0.dtbo, BB-CAN1-00A0.dtbo, BB-DCAN1-00A0.dtbo) from > /boot/uEnv.txt and left "enable_uboot_cape_universal=1" and attempted to > configure the CAN pins via: > > config-pin P9_19 can > config-pin P9_20 can > config-pin P9_24 can > config-pin P9_26 can > sudo ip link set can0 up type can bitrate 500000 > sudo ip link set can1 up type can bitrate 500000 > sudo ifconfig can0 up > sudo ifconfig can1 up > > The result was the CAN on can0 and can1 continued to work (RX and TX on both > interfaces). How bizarre! Anyone have a clue why adding the > "BB-DCAN1-00A0.dtbo" to /boot/uEnv.txt caused the CAN interfaces to work on > can0 and can1 all of a sudden? > > Anyway, thanks again for the tips. I hope this helps someone in the future!
Interesting, can you please run: sudo /opt/scripts/tools/version.sh When it's working, so i can validate and fix. 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/CAOCHtYjn3m8yMOsnA5%2BRbukj8jyzyDqOL-G%2BFOibWxdscHwFSw%40mail.gmail.com.
