I broke my installation (screwed up node.js and bonescript versions, stuff went bad) so re-flashed my test hardware with the latest Stretch IoT image... I'm now figuring out how U-Boot overlays work, which seem pretty straightforward, just a few changes in uEnv.txt...
How the heck do I get pru_rproc to work again? I'm guessing I need to blacklist uio_pruss modules before I'll start to see the results of a modprobe pru_rproc in a dmesg output? During bootup I don't see much in the way of output from the pru_rproc subsystem in dmesg, the only stuff there is related to what I assume is a power management peripheral: [ 2.519084] remoteproc0: powering up wkup_m3 [ 2.519481] remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148 [ 2.521735] remoteproc0: remote processor wkup_m3 is now up [ 2.521759] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x192 [ 2.521955] PM: bootloader does not support rtc-only! I have copied my binary over and symlinked it against /lib/firmware/am335x-pru1-fw as before. -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/44e31ad0-d029-40c1-809f-f4e5957866e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
