I may be misreading P2 documentation, but, in a paired Cog situation (LUT-sharing), and provided enough cycles are allowed for the first Cog-to-Hub write-transfers to take place (Streamer-conducted), the paired Cog (Streamer-conducted too) would be able to begin doing its job of Hub-to-(paired-LUT) transfers.
In a scenario like the one above depicted, after the first 16 longs (the actual number of longs may depend on the architecture; i.e., the number of implemented Cogs) have been written to the Hub by the first Cog/Streamer, the second (paired) Cog/Streamer could begin transfering from Hub to its paired Lut, at a one-long-per-cycle rate.
I believe that would be the faster way to accomplish the task. Resource-consuming, but very expedite, anyway.
In the mean time, both Cogs would be freed to do any processing/task that would not depend on their individual Fifos resources.
Sorry, my fault! evanh got it explainned right, at the next post!
Comments
In a scenario like the one above depicted, after the first 16 longs (the actual number of longs may depend on the architecture; i.e., the number of implemented Cogs) have been written to the Hub by the first Cog/Streamer, the second (paired) Cog/Streamer could begin transfering from Hub to its paired Lut, at a one-long-per-cycle rate.
I believe that would be the faster way to accomplish the task. Resource-consuming, but very expedite, anyway.
In the mean time, both Cogs would be freed to do any processing/task that would not depend on their individual Fifos resources.
Sorry, my fault! evanh got it explainned right, at the next post!
A streamer can't modify lutRAM nor cogRAM. In fact the only operation a streamer can do within cog memories is read lutRAM for purpose of pin output.
You're right. Post striked-thru...