On Wed, May 1, 2019 at 5:03 PM Charles Steinkuehler <[email protected]> wrote: > > On 5/1/2019 4:21 PM, Robert Nelson wrote: > > On Wed, May 1, 2019 at 4:12 PM Jon Elson <[email protected]> wrote: > >> > >> OK, now I seem to have (maybe) got it! So, I put in : > >> ###Custom Cape > >> dtb_overlay=/lib/firmware/cape-universalh-00A0.dtbo > >> > >> And I seem to have both the uio_pruss module loaded, AND all the P8 pins > >> available! > > > > So, you shouldn't have to force that overlay, as out of the box, we > > have cape-universal auto-loading.. > > Does U-Boot automatically change the universal overlay loaded when you > disable on-board "capes" like the eMMC and HDMI?
That is correct, u-boot will pick the correct path based on the enable/disables of the onboard devices set in /boot/uEnv.txt https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices Now even more crazy then that, in v4.14.x-ti and v4.19.x-(all)+, we merged in the cape-universal rewrite, that even when other random overlays are loaded, the config-pin pinmux's will still show up.. This why all overlays now have a Px_yz_pinmux { status = "disabled";}; section at the start: https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAN0-00A0.dts#L31-L40 PS, a dynamic generated config-pin vs the classic static config-pin then makes this work very well.. https://github.com/beagleboard/bb.org-overlays/tree/master/tools/pmunts_muntsos ( i have it set as default for buster, as it's not 100% compatible with the classic config-pin output..) Regards, -- Robert Nelson https://rcn-ee.com/ -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
