3.3.1. Control Override Register

The Control Override Register characteristics are:

Purpose

Additional control register that provides a fail-safe override for some CCI-400 functions, if these cause problems that you cannot otherwise work around.

Usage constraints

If you cannot avoid using them, only set them using non-bufferable transactions, and before barriers, shareable transactions, or DVM messages are issued into the CCI-400. This could be, for example, very early in the boot sequence, prior to the installation of any secure OS. You can access the Control Override Register using secure transactions only, irrespective of the programming of the Secure Access Register.

Configurations

Available in all CCI-400 configurations.

Attributes

Table 3.2 shows the bit assignments.

Table 3.2. Control Override Register

BitsReset valueAccessFunction
[31:4]-RAZ/WIReserved
[3]0x0R/W

Terminate all barrier transactions. The options are as follows:

0b0

Master interfaces terminate barriers according to the BARRIERTERMINATE inputs.

0b1

All master interfaces terminate barriers.

[2]0x0R/W

Disable speculative fetches. The options are as follows:

0b0

Send speculative fetches according to the Speculation Control Register. See Speculation Control Register.

0b1

Disable speculative fetches from all master interfaces.

[1]0x0R/W

DVM message disable. The options are as follows:

0b0

Send DVM messages according to the Snoop Control Registers. See Snoop Control Registers.

0b1

Disable propagation of all DVM messages.

[0]0x0R/W

Snoop disable. The options are as follows:

0b0

Snoop masters according to the Snoop Control Registers. See Snoop Control Registers.

0b1

Disable all snoops, but not DVM messages.


Copyright © 2011-2012 ARM. All rights reserved.ARM DDI 0470D
Non-ConfidentialID040512