4.7.3. Connections for CoreSight components

The following signals are expected to be connected to local CTIs but the exact connection location to the CTI is not required because it can be establishing using topology detection through full control of source and destination ports.

Note

Where two signals are listed, the second corresponds to an acknowledgement that must be connected to the corresponding ACK signal.

Table 4.29 shows the trigger inputs to the CTI.

Table 4.29. Trigger inputs to the CTI

CoreSight componentComponent signal
HTMHTMEXTOUT[1]
HTMEXTOUT[0]
HTMTRIGGER, HTMTRIGGERACK

Table 4.30 shows the trigger outputs from the CTI.

Table 4.30. Trigger outputs from CTI

CoreSight componentComponent signal
HTM HTMEXTIN[1]
HTMEXTIN[0]
HTMTRACEDISABLE
ETB FLUSHIN, FLUSHINACK
TRIGIN, TRIGINACK
TPIU FLUSHIN, FLUSHINACK
TRIGIN, TRIGINACK

Copyright © 2004-2009 ARM. All rights reserved.ARM DDI 0314H
Non-Confidential