SPRUI30H November 2015 – May 2024 DRA745 , DRA746 , DRA750 , DRA756
In this usage model, task is partitioned between the EVEs.
Figure 8-15 shows the task partitioning usage model.
In this case EVE1 is consumer for VIPx, EVE2 is the consumer for EVE1, and VIPx+1 is the consumer for EVE2.
The CME issues producer start to VIPx, and VIPx returns done when it is done. The CME then indicates a consumer start to EVE1 and receives the consumer done EVE1.
EVEs can use the following methods to communicate the START and DONE signaling between them:
1. Mailbox: Each EVE indicates START and DONE to the respective EVE using the Send Remote and Receive Local method. This method gives the most flexible time relationship for the task partitioning, but also adds most load on ARP32
2. GPIOs: In this case, each EVE uses GPIOs to communicate Start and Done to each EVE. This method adds the complexity of determining change of state of GPIOs to make sure a change of state is correctly determined.
3. EDMA events: Each EVE can trigger an EDMA and indicate DONE directly by using EDMA events and GPOuts for DONE functionality. The event trigger is completely hardware-based handshaking that does not include the ARP32 in the scheme. The DONE generation involves ARP32 as GPOut is used for this functionality. This scheme can only be used where there is deterministic timing relationship between each event and the processing needs in each EVE. In this case, the EVE triggering the EDMA uses its GPOUT signal connected to the INTC1 of the corresponding EVE to trigger the EDMA.
The last EVE in the usage model communicates with VIPx using the standard CME protocol.