Great, thanks! And not to be a pest but I assume in order to undo that change I simply comment the line that I add to the uEnv.txt and that's it? Should I worry about removing the *.dtbo object from the initrd?
On Friday, November 11, 2016 at 3:22:17 PM UTC-5, RobertCNelson wrote: > > On Fri, Nov 11, 2016 at 2:14 PM, Zach B <[email protected] <javascript:>> > wrote: > > Thanks Robert! That solved the problem I have been having. The overlay > > loaded and everything looks to be working. One follow up question I do > have > > is what is the proper way to load a custom overlay on startup? Is there > a > > way to enable multiple overlays as long as they don't try to use the > same > > pins? > > Add it /boot/uEnv.txt: > > ##Example v4.1.x > #cape_disable=bone_capemgr.disable_partno= > #cape_enable=bone_capemgr.enable_partno= > > ##Example v4.1.x > #cape_disable=bone_capemgr.disable_partno= > cape_enable=bone_capemgr.enable_partno=PRU-GPIO-BLINK > > You'll need to copy PRU-GPIO-BLINK-00A0.dtbo to /lib/firmware/ > > then run: > > sudo /opt/scripts/tools/developers/update_initrd.sh > > To copy the new *.dtbo object into the initrd.. > > Then just reboot, and you should see your overlay loaded.. > > 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/18dbb804-b0c2-495f-bd95-14a933c84022%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
