On Thu, Dec 15, 2016 at 12:36 PM, Phil <[email protected]> wrote: > On Thursday, December 15, 2016 at 11:20:13 AM UTC-6, Phil wrote: > I have written a device tree overlay that incorporates SPI0, SPI1 and the > PRUSS, and where SPI1 uses a GPIO for a 2nd chip select. Can I load this in > the same manner via the kernel parameter in /boot/uEnv.txt? If this isn't > the right way, then what is? >
So whatever way that works for you, is the right way. But yes, in my own opinion loading from uEnv.txt is the proper way. As the pin configurations take place the quickest possible after a boot. 1. So you need the overlay in /lib/firmware of course. 2. Then you need to add the overlay to the cape_enable=bone_capemgr.enable_partno= line in uEnv.txt 3. Finally you'll need to update the initramfs To update the initramfs You need to: william@beaglebone:~$ cd /opt/scripts/ william@beaglebone:/opt/scripts$ git pull /* So you need to sudo apt-get install git - If not already installed */ william@beaglebone:/opt/scripts$ cd tools/developers/ william@beaglebone:/opt/scripts/tools/developers$ sudo ./update_initrd.sh william@beaglebone:/opt/scripts/tools/developers$ sudo reboot Then your custom overlay will be "injected" into the initramfs, and properly load at boot. -- 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/CALHSORqYzrWkMi_K3Lyjj%2B44bVALvaUbS%3Dm8nDxu86pyRRXFfw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
