On 4/29/2019 3:32 PM, Jon Elson wrote: > OK, so now I think I'm back to you, Charles. So, if I have the original > overlay > uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > > loaded, the system boots up just fine. So, now I want to add my PRU pin > assignments, but adding that file locks up the Bone.
What do you mean "locks up the Bone"? What's printed out on the serial console when booting? > Here's what I have in my .dts file : <snip> > Does any of this conflict with what is in the PRU-UIO file? Or, is some of > it out of date and needs to be updated? Well, you're enabling the PRU, which is almost certainly also happening in the PRU-UIO overlay as well, so that's at least one conflict. Honestly, I haven't worked at all with U-Boot overlays (other than letting U-Boot load the universal and pru overlays I need), so I'm not really familiar with what happens if you have errors. I also suspect some names have changed with the newer kernels, so it's reasonably likely something like your fragment@2 doesn't have a valid reference for &pruss in the newer 4.x kernels. You may find this blog post helpful: https://beagleboard.org/blog/2018-01-17-building-a-device-tree-overlay-for-your-new-pocketcape-design And you can always dig through the live device-tree via: /proc/device-tree/ ...to see if your overlays got loaded the way you expect. -- Charles Steinkuehler [email protected] -- 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.
