On Thu, Jun 15, 2017 at 5:14 PM, Piotr C <[email protected]> wrote: > Yes, it popped accidentally due to copying command from one of the tutorials > that I have linked. > > I have added: > uboot_overlay_addr4=/lib/firmware/BB-CAN1-00A0.dtbo > as you suggested. > > It changed the output of cat > /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins > > > pin 96 (44e10980.0): 481d0000.can (GPIO UNCLAIMED) function > pinmux_dcan1_pins group pinmux_dcan1_pins > pin 97 (44e10984.0): 481d0000.can (GPIO UNCLAIMED) function > pinmux_dcan1_pins group pinmux_dcan1_pins > > However, after typing: > root@beaglebone:/home/debian# cat /sys/devices/platform/bone_capemgr/slots > 0: ---l-- -1 > 1: ------ -1 > 2: ---l-- -1 > 3: ---l-- -1 > 4: --Ol-- -1 > 5: --O--- -1 > > In line 5: I was expecting some text like: "Override Board > Name,00A0,Override (...)" > // taken from here: > > Should I expect a change in slots configuration after adding the lines that > you have mentioned in /boot/uEnv.txt? > Is there any other to check whether the CAN Device Tree overlay was properly > loaded?
With u-boot overlays, the "/sys/devices/platform/bone_capemgr/slots" is not updated.. you should see the can interface showing up under: sudo ifconfig -a 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/CAOCHtYjn4kNGoOoqyEq%3DkBtSe_vD1mT_u2uGP4OAPr4M0yofMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
