Upon further investigation, I see this output from dmesg: [ 2.381018] remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
Why is remoteproc looking for a .elf file? How can I update this? On Wednesday, March 8, 2017 at 2:55:42 PM UTC-8, Justyn Bell wrote: > > Hi, > > I'm having trouble getting my BBB to run PRU Cape demos. > > This is what I did: > > 0) cd /opt/source/dtb-4.4-ti && git pull > 1) Add #include "am335x-boneblack-prucape.dtsi" to > am335x-boneblack-wireless.dts > 2) make clean && make && sudo make install > > This should put my device blob in /boot/dtbs/4.4.30-ti-r64, which it does > > 3) cd /opt/source/pru-software-support-package/ && git pull > 4) cd /opt/source/pru-software-support-package/pru_cape/bin/Linux > 5) sudo ./pru_demo.sh > 6) Select LEDs > > I get an error: > > ./pru_demo.sh: line 67: echo: write error: No such device > ./pru_demo.sh: line 68: echo: write error: No such device > > Those lines: > > 67 echo 4a334000.pru0 > /sys/bus/platform/drivers/pru-rproc/bind > 68 echo 4a338000.pru1 > /sys/bus/platform/drivers/pru-rproc/bind > > What should I do here to get these demos to work? Where does the > 4a334000.pru0 come from? How can I find my PRU IDs? > > Thanks, > > -- 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/b9d16c5b-ad46-4d7d-bca3-68dda4a969bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
