ZHCSBT2G November 2012 – October 2017 66AK2H06 , 66AK2H12 , 66AK2H14
PRODUCTION DATA.
The cross-trigger lines are shared by all the subsystems implementing cross-triggering. An MPU subsystem trigger event can therefore be propagated to any application subsystem or system trace component. The remote subsystem or system trace component can be programmed to be sensitive to the global SOC trigger lines to either:
Table 11-61 describes the cross-triggering connection.
NAME | SOURCE TRIGGERS | SINK TRIGGERS | COMMENTS |
---|---|---|---|
Inside DEBUGSS | |||
Device-to-device trigger via EMU0/1 pins | YES | YES | This is fixed (not affected by configuration) |
MIPI-STM | NO | YES | Trigger input only for MIPI-STM in DebugSS |
CT-TBR | YES | YES | DEBUGSS CT-TBR |
CS-TPIU | NO | YES | DEBUGSS CS-TPIU |
Outside DEBUGSS | |||
DSPSS | YES | YES | |
CP_Tracers | YES | YES | |
ARM | YES | YES | ARM Cores, ARM CS-STM and ARM CT-TBR |
Table 11-62 describes the crosstrigger connection between various cross trigger sources and TI XTRIG module.
NAME | ASSIGNED XTRIG CHANNEL NUMBER |
---|---|
C66x CorePac0-3 (66AK2H06 only) | XTRIG 0-3 (66AK2H06 only) |
C66x CorePac0-7 (66AK2H12/14 only) | XTRIG 0-7 (66AK2H12/14 only) |
CPTracer 0..31 (The CPTracer number refers to the SID[4:0] as shown in Table 11-59 | XTRIG 8 .. 39 |