ooooh that's my problem. I was only using pasm -b blink2.asm which doesn't link against anything. I had missed that because most of the other examples that I had read where using the UIO pru loader, which doesn't require any linking of the remoteproc. I had planned on switching to C in the future but I was using my simple assembly program to start. I guess I will just try modifying the example pru code gpio_toggle to toggle the pin I want as a first attempt. What is the proper way to link those files in during the assembly compilation process?
Sorry if some of these questions are pretty basic I'm learning as I go through all of this. On Friday, November 18, 2016 at 10:12:08 AM UTC-5, Greg wrote: > > How did you compile the assembly code? The compilation has to be done > with the Remoteproc and linker files. > Remoteproc will look for certain code in the firmwares, and if it is not > there, nothing will happen. > > On Friday, November 18, 2016 at 10:06:07 AM UTC-5, Zach B wrote: >> >> In trying to test my code for the PRUs is there a good way to check and >> see if binary is being loaded into the PRU properly and check whether or >> not it is executing. I have a simple LED circuit running some basic blink >> code but nothing seems to be occurring. Also with everything activated, the >> pru_rproc running and the devices showing up as they should I still >> sometimes get "no such device" when I try to bind pru0, have you ever run >> into this issue? >> >> >> -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/81ffcf78-63c9-4dd3-ae70-e0805722db65%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
