so did an ls on /lib/firmware, I am showing part of the ls, but it should show the 2 files you are interested in (bold and underlined):
root@beaglebone:/lib/firmware# ls -l -rw-r--r-- 1 root root 1102 Dec 9 21:09 ADAFRUIT-SPI0-00A0.dtbo -rw-r--r-- 1 root root 1105 Dec 9 21:09 ADAFRUIT-SPI1-00A0.dtbo -rw-r--r-- 1 root root 867 Dec 9 21:09 ADAFRUIT-UART1-00A0.dtbo -rw-r--r-- 1 root root 867 Dec 9 21:09 ADAFRUIT-UART2-00A0.dtbo -rw-r--r-- 1 root root 867 Dec 9 21:09 ADAFRUIT-UART4-00A0.dtbo -rw-r--r-- 1 root root 867 Dec 9 21:09 ADAFRUIT-UART5-00A0.dtbo *-rw-r--r-- 1 root root 36256 Jan 30 04:53 am335x-pru0-fw-rw-r--r-- 1 root root 96272 Jan 30 04:53 am335x-pru1-fw*-rw-r--r-- 1 root root 1205 Nov 22 15:28 am33xx_pwm-00A0.dtbo drwxr-xr-x 2 root root 4096 Dec 9 20:49 ar3k -rw-r--r-- 1 root root 153416 Dec 4 22:43 ar5523.bin Although when I ls /dev I get rpmsg_pru31 not rpmsg_pru30 (again I don't want to show everything, I am going to show the snippet that you are interested in: root@beaglebone:/dev# ls -ltr crw-rw---- 1 root spi 153, 1 Jan 30 04:49 spidev1.0 crw-rw---- 1 root spi 153, 3 Jan 30 04:49 spidev2.0 crw-rw---- 1 root spi 153, 2 Jan 30 04:49 spidev2.1 crw-rw---- 1 root spi 153, 0 Jan 30 04:49 spidev1.1 *crw------- 1 root root 245, 0 Jan 30 04:50 rpmsg_pru31*drwxr-xr-x 2 root root 2740 Jan 30 04:50 char prw-r----- 1 root adm 0 Jan 31 05:31 xconsole crw-rw-rw- 1 root tty 5, 2 Jan 31 05:36 ptmx In your pdf you look for rpmsg_pru31 instead of rpmsg_pru30, is there a reason you are looking for that one? Even after doing that I am still getting the following error: root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# prumodin /usr/bin/prumodin: line 9: echo: write error: No such device /usr/bin/prumodin: line 10: echo: write error: No such device root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# ls /usr/bin/prum* /usr/bin/prumodin /usr/bin/prumodout /usr/bin/prumsg I got through part of your tutorial and I am bit a confused. Why are you copying the .out file to a different file name and then moving it to /lib/firmware? What does that file do? By the way, thanks again for all your help, this is really helpful. On Monday, January 30, 2017 at 4:41:41 AM UTC-8, Greg wrote: > > I think you are making progress, but I'm having a little trouble following > the grep pru. > > You should end up with 2 firmwares in /lib/firmware with very specific > names: > > am335x-pru0-fw > am335x-pru1-fw > > Just do > > ls /lib/firmware > > and see if they are there. > Also: > > ls /dev > > If you got through the example from the support package, there should be a > character device file there: > > rpmsg_pru30 > > If you get the above, that is a very good sign that everything is > configured and working. > Note that you will probably have to reboot for the character device to > appear after successfully compiling the firmwares and moving them > /lib/firmware. > > Toggling a GPIO is easy. You will need to use the __R30 special register > variable. > Look in the am335x examples directory of the PRU support package: > > PRU_gpioToggle > > Yes you are correct I didn't use the CCS. In the case of the PRUs, simple > projects are not creating libraries of code. > And the C code files for the PRUs are no problem for the BeagleBone itself > to compile. > If you have used a cross-compiler set-up before, there is a lot of > configuration required, and probably debugging of problems. > I did see a note that the CCS no longer requires any sort of license. I > might go back and look at it in the future, > but for now the command line via SSH is more than adequate for what I want > to achieve with the PRUs. > > Greg > > -- 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/a9b58a40-cf79-40a4-9cec-ad0a30f85a90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
