Hi Robert, Thanks for looking at this. Below is the output of the version.sh script. I took this with can0 and can1 working. Please let me know if there is anything else I can help with.
git:/opt/scripts/:[1d3eb3a15fafc1463e0a86dcef15857aa2a827be] eeprom:[A335BNLTSE0A2019BBE81671] model:[SanCloud_BeagleBone_Enhanced]:WiFi AP Enabled:[https://github.com/lwfinger/rtl8723bu] dogtag:[rcn-ee.net console Ubuntu Image 2019-04-10] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-gbb4af0f50f]:[location: dd MBR] kernel:[4.19.31-ti-r19] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[disable_uboot_overlay_video=1] uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo] uboot_overlay_options:[enable_uboot_cape_universal=1] pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>] pkg:[bb-cape-overlays]:[4.4.20190610.0-0rcnee0~bionic+20190610] pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~bionic+20190227] pkg:[kmod]:[24-1ubuntu3.2rcnee0~bionic+20190208] WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED] cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable] dmesg | grep remote dmesg | grep pru dmesg | grep pinctrl-single dmesg | grep gpio-of-helper lsusb Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub END On Tuesday, July 23, 2019 at 9:55:11 AM UTC-5, RobertCNelson wrote: > > On Tue, Jul 23, 2019 at 12:03 AM debounce <[email protected] > <javascript:>> 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/e1cbd852-591c-40aa-80bb-5903f2a8ea5b%40googlegroups.com.
