Sounds a tad more intricate, but seems powerful. Thanks for letting us know, Steinkuehler.
On Wed, Jul 3, 2019, 9:05 PM Charles Steinkuehler <[email protected]> wrote: > As has been discussed, the PRUs have no direct "interrupt" like > functionality that interrupts and redirects program execution. > > In addition to the various methods already discussed, if you are > trying to tightly couple program execution between the two PRU cores, > I suggest using the transfer instructions (XIN/XOUT). While these > instructions are typically used to access the scratchpad and hardware > multiplier, you can also specify a direct connection between the two > PRU cores. In this case, one PRU core executes an XIN instruction and > the other core executes an XOUT. The core that executes the > instruction first will stall until the other PRU executes it's > transfer instruction, at which point the two PRU cores will continue > executing code, synchronized by the transfer instruction. The > transfer is terminated if either PRU core stalls for more than 1024 > cycles. > > Details are in the TRM, but you have to have one of the versions with > full details on the PRU cores (eg: spruh73c or similar). > > On 7/2/2019 7:49 AM, Venkatesh Vadde wrote: > > We are a group working with a Beaglebone and trying to get more time > > determinism between the PRUs. We are trying to get one PRU to respond to > a > > trigger from the other PRU. The INTC framework seems quite complex, and > we > > are finding it quite difficult to decipher or understand (but an example > > might help us build on it). Does the PRU allow for a timed response like > an > > interrupt based mechanism? Can someone suggest something for our > > requirement of communication between the PRUs? > > > > Thank you, > > -Vadde > > > > > -- > Charles Steinkuehler > [email protected] > > -- > 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/30cf3e82-eae4-07cb-7be8-0bf34137de0d%40steinkuehler.net > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAHW0bcxPVtppGTkVd51nkYWgg3J3hvZuJtV1yV%2BhC9TaVhSzWA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
