Same issue with brand new beaglebone black wireless -- just flashed with latest version of stretch.
debian@beaglebone:~$ ls /sys/class/remoteproc/ remoteproc0 On Tuesday, May 7, 2019 at 8:17:31 AM UTC-7, hugh....@gmail.com wrote: > > I have the exact same issue, except my output from version.sh indicates > the board id eeprom is programmed correctly? Any other ideas Robert?... I'm > playing around with migrating our device from 8.7 with 4.4 kernel up to > something more recent and am coming up against this PRU issue... > > On Wednesday, 10 April 2019 03:06:45 UTC+1, eth...@uw.edu wrote: >> >> >> I've just set up a new Debian 9.5 (kernel 14.4.71-ti-r80) image >> <https://debian.beagleboard.org/images/bone-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz> >> >> and made the following changes to /boot/uEnv.txt: >> >> disable_uboot_overlay_video=1 >> uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo >> >> I've also disabled loading of the uio modules. ( >> /etc/modprobe.d/pruss-blacklist.conf) >> blacklist uio >> blacklist uio_pdrv_genirq >> >> However, I don't see any evidence that the rproc module has loaded the >> PRU: >> "uio\|pru" >> >> Specifically, there is no module for the PRU in /sys/class/remoteproc/. >> remoteproc0 appears, but this is for the M3 power management unit. >> >> Am I doing anything wrong? or is there an additional step to allow use of >> the PRUs? What should I look at to debug this issue? >> > -- 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/f417b17c-bf84-436b-8916-5a9a4435b7df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
