I did the Echo Lab 5 and everything seemed to go fine. I ran prumsg and all I saw was a quick squarewave and then the pin would stay high. Ok, I played with it some more and I am trying to get /home/debian/pru-software-support-package/examples/am335x/PRU_gpioToggle example to work. And as you guessed I am not seeing anything toggle for P8_11 under PRU0. I see that P8_11 is on pruout (when doing config-pin P8_11) as is defined by https://www.cs.sfu.ca/CourseCentral/433/bfraser/other/2016-student-howtos/PRU_GPIO_guide.pdf I am not using P8_27 due to having to load in a new overlay and I don't know if its going to load cape-universala is going to boot of the SD card or not, so I didn't want to risk it. Anyways, everything goes and I hit no errors. I copied the out file into am335x-pru0-fw. So I am confused here. I don't know where the issue is coming from, why I can't see the GPIO pin being toggled on the scope. I was also going through your directions and had some questions, Why include am33xx-pruss-rproc.dtsi? Does this mean I have to include some other files for the Why did you have blacklist certain files? Do I have to blacklist certain files too? As I am reading through you previous emails maybe I will give my hand at Lab 6 and see if I can see anything toggle in the meantime. Let me know your thoughts. This is really helpful, but there is so much going on I am having a hard time wrapping my head around everything that is happening, I don't know if its just me thats having such a hard time... Thanks again for you time and your patience. -Ashwini
On Thursday, February 2, 2017 at 1:51:51 AM UTC-8, Ashwini Bhat wrote: > > Sweet! Thanks a lot man! Let me play with this for a day or 2. I am > definitely going to have questions but just need to get my thoughts in > order! > > On Wednesday, February 1, 2017 at 4:23:22 AM UTC-8, Greg wrote: >> >> OK, great! >> >> So exactly which firmware are you using? In my docs, for set-up purposes >> I suggest the PRUmsg Echo Lab 5. >> >> So this example does not intentionally toggle any GPIO. The idea is that >> if you can get this lab to work, the PRU RemoteProc kernel drivers are >> completely functional. >> >> The final thing to do with this example is to compile the user-space C >> program and run it. >> I think the Makefile handles this, but compiling any C program for >> user-space is easy: >> >> gcc main.c -o pru_msg_test >> >> or something like that. >> Running the user-space test program does a simple exercise of the >> RemoteProc messaging character devices. >> Lab 6 toggles an LED using the PRU and uses the same character device >> mechanism to control the PRU. >> Let me know if you have any more questions. I think you have gained a >> lot of capability to experiment 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/7d500eb3-b203-426a-a87c-692d08777bcc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
