On Tuesday, May 16, 2017 at 3:27:07 AM UTC+2, William Hermans wrote: > > > > On Wed, Apr 26, 2017 at 1:02 AM, Joseph Heller <[email protected] > <javascript:>> wrote: > >> Updated link: http://catch22.eu/beaglebone/beaglebone-pru-c/ >> > > I may have mentioned this before, but I think blinking a USR LED would be > far more useful. Nothing to hook up, and worry about blowing the pins on > the processor, etc. However, then we're talking about involving the L3 > interconnect, which might be what you did not want to do ? > > A point of contention that I have with the article however, is: How does > the GPIO bank + DATA_OUT register get into the PRU's _R30 register ? This > also has to be dynamic somehow. I can't imagine all registers r0-r31 are > each dedicated to a single control register of *something*. Then yes, I do > know that some PRU registers are reserved, I just do not know which anymore. >
I don't know yet either at the moment. The way I use it in the example seems to work magically per default. Risk is that is breaks though. An explanation would be helpful. > In another part of the article: > >> The issue faced here is that one has to deep-dive into the workings of >> the header files, and make the relation to the defined variables in those >> header files and the PRU registers defined in the Reference Manual. >> Fortunately the header files and the reference manual closely match each >> other. *Unfortunately, you have to do the footwork to figure it out for >> each common or less common usage of the registers. For instance, here’s a >> relevant section of the pru_iep.h header file for the IEP example above:* > > > Then you go on to show some "pictures" from various sources, most notably > the applicable registers from the TRM. My point here is, I'm not sure what > your point is. This is pretty much standard procedure when working with any > hardware on this level. That is, *IF* you really need to know for sure, > what you're doing. > So, do not get me wrong, I'm not bashing what you've done there at all. > It's a lot more than I've done in demonstrating the PRU's to the public. > Mostly due to the fact that I do not know how to use the PRU's very well at > all. > Okay, I've rephrased that part a bit. Thanks for the feedback. -- 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/a0b82fcb-923f-4223-a839-87a3578cbee1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
