Thanks for your reply Charles. My question was not well formulated. I have an understanding of the theory of mutual exclusion. However, applying the theory using starterware on the beaglebone black is where I am making slow progress. ANY examples would be useful of any method. One simple method I have used in the past is spinlocks and shared memory. But I haven't been able to get that working yet on the BBB with Starterware. I posted a more detailed question on the TI E2E Starterware forum but haven't received any replies as yet (perhaps it was also a badly formulated question!). https://e2e.ti.com/support/embedded/starterware/f/790/t/410442 Thanks again.
On Friday, 27 March 2015 00:15:39 UTC+11, Charles Steinkuehler wrote: > > On 3/26/2015 2:38 AM, BryanB wrote: > > > > Hi Satz, > > Did you ever make any progress with your questions? > > > > I have successfully used Starterware on the BBB and a TI PRU-Cape with > its > > supporting software to load and run PRU program examples. > > However, I haven't found any examples on communicating between the ARM > and > > the PRUs via shared memory. Have you? > > I did get a simple transfer to work but am not sure about ensuring > mutual > > exclusion or the best way to set up the shared memory. > > There is no single correct or "best" way to implement communications > between the ARM core and the two PRUs. This is a standard problem in > all multiple core machines, and you will find a lot of material with a > quick Google search. Depending on your application you may want to use > things like mailbox registers, lockless queues, interrupt signaling, > req/ack handshakes, etc. > > -- > Charles Steinkuehler > [email protected] <javascript:> > -- 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]. For more options, visit https://groups.google.com/d/optout.
