Tried it with bone-debian-10.3-iot-armhf-2020-03-16-4gb.img. Same thing: copying over firmware fixed it.
On Thursday, March 19, 2020 at 11:36:45 AM UTC-4, Jacob Kunnappally wrote: > > I swear I tried all of this, but in lieu of good notes (which I rarely > take unfortunately), I decided to redo everything from scratch today to > make sure I didn't hallucinate through all the different iterations I tried. > > Ok, so first I downloaded the IoT image at > https://debian.beagleboard.org/images/bone-debian-9.9-iot-armhf-2019-08-03-4gb.img.xz > > and flashed it onto a card. > > Looking at Exploring BB, Derek's using kernel 4.14.67-ti-rt-r73. Mine > shows as 4.14.108-ti-r113. I disabled video in uEnv.txt and rebooted. After > re-checking that PRU related messages showed up in dmesg, Here's a > transcript of me trying to turn PRU0 on, both as root and debian > > root@beaglebone:~# cd /sys/class/remoteproc/remoteproc1 > root@beaglebone:/sys/class/remoteproc/remoteproc1# ls > device firmware power state subsystem uevent > root@beaglebone:/sys/class/remoteproc/remoteproc1# cat state > offline > root@beaglebone:/sys/class/remoteproc/remoteproc1# echo 'stop' > state > -bash: echo: write error: Invalid argument > root@beaglebone:/sys/class/remoteproc/remoteproc1# echo 'start' > state > -bash: echo: write error: Invalid argument > root@beaglebone:/sys/class/remoteproc/remoteproc1# exit > logout > debian@beaglebone:~$ cd /sys/class/remoteproc/remoteproc1 > debian@beaglebone:/sys/class/remoteproc/remoteproc1$ echo 'stop' > state > -bash: echo: write error: Invalid argument > debian@beaglebone:/sys/class/remoteproc/remoteproc1$ echo 'start' > state > -bash: echo: write error: Invalid argument > > I got the same firmware load failure messages in dmesg that I first > reported. After copying over the firmware in /opt/scripts: > > debian@beaglebone:/opt/scripts/device/bone/pru-rpmsg_client_sample$ sudo > cp * /lib/firmware > debian@beaglebone:/opt/scripts/device/bone/pru-rpmsg_client_sample$ cd / > sys/class/remoteproc/remoteproc1 > debian@beaglebone:/sys/class/remoteproc/remoteproc1$ echo start > state > debian@beaglebone:/sys/class/remoteproc/remoteproc1$ cat state > running > > I'm going to try to load up a recent image from your site and see if I get > the same thing. I'll report back. This epidemic's given me a chance for a > lot of play time while I'm on the clock :) > > On Thursday, March 19, 2020 at 10:03:10 AM UTC-4, RobertCNelson wrote: >> >> On Thu, Mar 19, 2020 at 7:12 AM <[email protected]> wrote: >> > >> > git:/opt/scripts/:[109f74fb87e6034ae1a8971a244064a8d5e090a5] >> > eeprom:[A335BNLT00C02516BBBK1ED1] >> > model:[TI_AM335x_BeagleBone_Black] >> > dogtag:[BeagleBoard.org Debian Image 2019-08-03] >> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot >> 2019.04-00002-gbb4af0f50f]:[location: dd MBR] >> > kernel:[4.14.108-ti-r113] >> > >> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo] >> >> >> >> Okay you are fine.. >> >> (my version of that book was at work) >> >> Look closer at Derek's examples, he's doing it as root, as debian you >> can't just "echo > something" without proper permissions... >> >> His examples also relied on v4.9.x-ti (so hopefully TI didn't break >> something with regards the v4.14.x-ti we ship..) >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- 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/b0d0a8a5-82a4-4846-b01e-4bb70332eb58%40googlegroups.com.
