So I think I have it mostly working, I can see rpmsg_pru31 and rpmsg_pru30 in the /dev folder and I saw that prumodin was already enabled, I had to do prumodout first and then prumodin then the script didn't error out. I see P9_42 toggle for a second and then the pin stays high. Is that what is supposed to happen? If that is what is supposed to happen then great! But I do have some questions about why you did certain things during the installation. Let me know how far off I am. Thanks, Ashwini Bhat
On Tuesday, January 31, 2017 at 5:18:08 AM UTC-8, Greg wrote: > > There are two examples, one for PRU0 and another for PRU1. So you will > get rpmsg_pru30 for PRU0, and rpmsg_pru31 for the other. > So if you are seeing rpmsg_pru31, this is a major step forward and you > have it working!!! > Also note the "c" at the first column of the ls; this indicates a > character device. It's good news. > > So I think the scripts prumodin and prumodout must be looking for the > wrong file names. It is probable they are not consistent as kernel changes > are rolled out. > So: > > ls /sys/bus/platform/devices > > Do you see PRU related entries as shown in the set-up documentation? > There are probably small differences which are breaking the scripts. > -- 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/8f5f2eb4-7bfe-41bd-b913-8291afa3a523%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
