3.2.72. c13, Context ID Register

The purpose of the Context ID Register is to provide information on the current ASID and process ID, for example for the ETM and debug logic.

Debug logic uses the ASID information to enable process-dependent breakpoints and watchpoints. The ASID field of the Context ID Register and FCSE PID Register cannot be used simultaneously. The FCSE PID Register remapping of VA to MVA has priority over setting the ASID field to designate non-global pages. Therefore, non-global pages cannot be used if the FCSE PID Register is set to a non-zero value.

The Context ID Register is:

Figure 3.66 shows the bit arrangement of the Context ID Register.

Figure 3.66. Context ID Register format

Table 3.144 shows how the bit values correspond with the Context ID Register functions.

Table 3.144. Context ID Register bit functions


Extends the ASID to form the process ID and identifies the current process. The reset value is 0.


Holds the ASID of the current process to identify the current ASID. The reset value is 0.

Table 3.145 shows the results of attempted access for each mode.

Table 3.145. Results of access to the Context ID Register[61]

Secure privilegedNonsecure privilegedSecure UserNonsecure User
Secure dataSecure dataNonsecure dataNonsecure dataUndefinedUndefinedUndefinedUndefined

[61] An entry of Undefined in the table means that the access gives an Undefined Instruction exception when the coprocessor instruction is executed.

The current ASID value in the Context ID Register is exported to the MMU.

To access the Context ID Register, read or write CP15 with:

MRC p15, 0, <Rd>, c13, c0, 1 ; Read Context ID Register
MCR p15, 0, <Rd>, c13, c0, 1 ; Write Context ID Register

You must ensure that software executes a Data Synchronization Barrier operation before changes to this register. This ensures that all accesses are related to the correct context ID.

You must execute an IMB instruction immediately after changes to the Context ID Register. You must not attempt to execute any instructions that are from an ASID-dependent memory region between the change to the register and the IMB instruction. Code that updates the ASID must execute from a global memory region.

You must program each process with a unique number to ensure that the ETM and debug logic can correctly distinguish between processes.

Copyright © 2006-2009 ARM Limited. All rights reserved.ARM DDI 0344I