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/e31269c3-803c-4d9b-b177-1cc953ad06b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
