On 8/28/2019 12:40 AM, [email protected] wrote: > > since CRAMPS.bbio has in the first few lines > > overlay cape-universal > overlay cape-bone-iio > > However there is no cape-bone-io in /lib/firmware, further removing the > reference to it in CRAMPS.hal will again produce > > halcmd loadusr io started > Waiting for /sys/class/uio/uio0
These are all legacy tests from when there were actual device tree overlays that could be dynamically loaded at run-time and it could take a few seconds for the device nodes to show up. If the system is waiting for /sys/class/uio/uio0 it means you don't have the PRUs properly enabled. Make sure you have the PRU UIO device (*NOT* remoteproc) enabled via u-boot. It's the last entry here: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_PRU_Options -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/20e23f82-a7b4-abdf-1a71-cdafc8dea96f%40steinkuehler.net.
