SPRUIE9D May 2017 – May 2024 DRA74P , DRA75P , DRA76P , DRA77P
The SIMCOP subsystem is connected to the rest of the system through the ISS local interconnect. Figure 9-175 shows the integration of the SIMCOP subsystem in the ISS.
Figure 9-175 SIMCOP IntegrationFor more information about the IDLE hardware handshake and the wake-up request, see Clock Management in Power, Reset, and Clock Management.
This section gives an overview of typical uses of the module. See Power, Reset, and Clock Management for more information and settings of the PRCM relationship to ISS clocks and resets.
Table 9-2576 lists the Integration Attributes.
| Module Instance | Attributes | |
| Power Domain | Interconnect | |
| SIMCOP | PD_EVE3 | L3_MAIN via ISS interconnect |
Table 9-2577 lists the clocks and resets values.
| Clocks | ||||
| Module Instance | Destination Signal Name | Source Signal Name | Source | Description |
| SIMCOP | SIMCOP_FCLK | ISS_MAIN_FCLK | ISS | Functional clock. It is used by all ISS submodules and ISS top-level resources. |
| Resets | ||||
| Module Instance | Destination Signal Name | Source Signal Name | Source | Description |
| SIMCOP | SIMCOP_RST | ISS_RST | ISS | ISS and SIMCOP global reset. |
Table 9-2578 lists the hardware resets.
| Interrupt Requests | ||||
| Module Instance | Source Signal Name | Destination Signal Name | Destination | Description |
| SIMCOP | SIMCOP_STEP0_IRQ | SIMCOP_IRQ0 | SIMCOP IRQ merger | Event triggered when a SIMCOP context is activated by the hardware sequencer |
| SIMCOP | SIMCOP_STEP1_IRQ | SIMCOP_IRQ1 | SIMCOP IRQ merger | Event triggered when a SIMCOP context is activated by the hardware sequencer |
| SIMCOP | SIMCOP_STEP2_IRQ | SIMCOP_IRQ2 | SIMCOP IRQ merger | Event triggered when a SIMCOP context is activated by the hardware sequencer |
| SIMCOP | SIMCOP_STEP3_IRQ | SIMCOP_IRQ3 | SIMCOP IRQ merger | Event triggered when a SIMCOP context is activated by the hardware sequencer |
For more information about interrupt requests, see Section 9.1.2.1.1Interrupt Merger.