4.7.2. Connections for ARM11 systems

Table 4.27 shows the recommended input connections for use with ARM11 systems.

Table 4.27. Recommended input connections for use with ARM11 systems

Trigger input bitSource signalSource deviceComments
[7]!INTL2CC Event Monitor

Compulsory if L2CC Event Monitor present. INT must be negated. This is to ensure the same programming (active LOW) whether it is connected directly to nIRQ or through the ECT.

Any L2CC event can be passed to the ECT by configuring a counter to select the event and generate an interrupt on increment. Set the interrupt type as edge-sensitive, 1-cycle pulse duration and active LOW.

[6]TRIGGERETMRecommended if ETM present.
[5]EXTOUT[1]ETMRecommended if ETM present.
[4]EXTOUT[0]ETMCompulsory if ETM present.
[3]ACQCOMPETBSee FULL.
[2]FULLETBRecommended if an ETB is present. If a single ETB is shared between multiple cores, only connect to the CTI of one of the cores.
[1]!nPMUIRQCoreCompulsory. nPMUIRQ must be negated.
[0]DBGACKCoreCompulsory.

Inputs not connected as shown in Table 4.27 can be used for user-defined functions.

Table 4.28 shows the recommended output connections for use with ARM11 systems.

Table 4.28. Recommended output connections for use with ARM11 systems

Trigger output bitDestination signalDestination deviceComments
[7]User defined--
[6]User defined--
[5]EXTIN[1]ETMRecommended if ETM present.
[4]EXTIN[0]ETMCompulsory if ETM present.
[3]VICINTSOURCE[y]VICRecommended if the VIC is present. Any interrupt can be used.
[2]VICINTSOURCE[x]VICCompulsory if the VIC is present. Any interrupt can be used.
!nIRQCoreCompulsory if the VIC is not present. The output must be negated and connected to the core nIRQ input, ANDed with other signals using this input.
[1]User-defined--
[0]EDBGRQCoreCompulsory.

Outputs not connected as shown in Table 4.28 can be used for user-defined functions.

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