It was my mistake.but remotproce1 also gives the same error. In fact, all remotproce 0-3 state is suspended with and 4-7 state is offline. debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc5/state offline debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc0/state suspended debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc0/firmware dra7-ipu1-fw.xem4 debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc1/state suspended debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc1/firmware dra7-ipu2-fw.xem4 debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc2/state suspended debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc2/firmware dra7-dsp1-fw.xe66 debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc3/state suspended debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc3/firmware dra7-dsp2-fw.xe66 debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc4/state offline debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc4/firmware am57xx-pru1_0-fw debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc5/state offline debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc5/firmware am57xx-pru1_1-fw debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc6/state offline debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc6/firmware am57xx-pru2_0-fw debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc7/state offline debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc7/firmware am57xx-pru2_1-fw
Why remotproce0-3/firmware have changed by remotproce4-7/firmware that are in the first boot?? Best regards, Farzad On Friday, April 10, 2020 at 9:29:36 PM UTC+4:30, RobertCNelson wrote: > > On Fri, Apr 10, 2020 at 11:49 AM Farzad <[email protected] <javascript:>> > wrote: > > > > hi. I use the Debian 9.12 2020-04-06 on BeagleBone AI. > > for the first boot, I go to /var/lib/cloud9/BeagleBone/AI/pru directory > and run > > root@beaglebone:/var/lib/cloud9/BeagleBone/AI/pru# source setup.sh > > TARGET=blinkInternalLED.pru1_1 > > > > and run make command > > > PRU_DIR = /sys/class/remoteproc/remoteproc1 > > rm /tmp/cloud9-examples/blinkInternalLED.pru1_1.o > > root@beaglebone:/var/lib/cloud9/BeagleBone/AI/pru# cat > /sys/class/remoteproc/remoteproc0/state > > suspended > > root@beaglebone:/var/lib/cloud9/BeagleBone/AI/pru# cat > /sys/class/remoteproc/remoteproc0/firmware > > dra7-ipu1-fw.xem4 > > On the am57xx family there are many more "remoteproc" devices, the > script used "remoteproc1" but you referenced "remoteproc0".. We are > working on symlinks to fix this confusion, but it hasn't shipped yet. > > https://elinux.org/Beagleboard:BeagleBone_cape_interface_spec#PRU > > 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/8c343540-86f2-416e-bd0c-b50494720e7e%40googlegroups.com.
