Thanks for quoting the TRM for me (I didn't download the 'c' version yet). Am Donnerstag, 4. Juli 2019 15:10:38 UTC+2 schrieb Charles Steinkuehler: > > On 7/4/2019 2:57 AM, TJF wrote: > > Interesting, thanks Charles! > > > > Am Mittwoch, 3. Juli 2019 17:35:41 UTC+2 schrieb Charles Steinkuehler: > >> > >> The > >> transfer is terminated if either PRU core stalls for more than 1024 > >> cycles. > > > > How to distinguish between a terminated or regular transfer? > > From the TRM: > "In direct connect mode (device ID 14), any PRU transaction will be > terminated if the stall is greater than 1024 cycles. This will > generate the event pr<1/0>_xfr_timeout that is connected to INTC." >
So we have to check the event bit and clear it in a second cycle. My method to HALT one PRU and resume it by the other is less expensive and more flexible. It isn't limited to a 1024 cycle window. And by specifying any program counter, the halted PRU can continue anywhere, not just at the next position in IRAM. Regards -- 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/a547441e-e653-4000-8885-5c3a936dd1d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
