Page 2
This document is intended only to assist the reader in the use of the product. ARM shall not be liable for any loss or damage arising from the use of any information in this document, or any error or omission in such information, or any incorrect use of the product.
Preface About this book This book is for the Cortex-A53 MPCore processor. This is a cluster device that has between one and four cores. Product revision status The rmpn identifier indicates the revision status of the product described in this book, for example, r1p2, where: Identifies the major revision of the product, for example, r1.
Read this for a description of the technical changes between released issues of this book. Glossary The ARM Glossary is a list of terms used in ARM documentation, together with definitions for ® those terms. The ARM Glossary does not contain terms that are industry standard unless the ®...
Encloses replaceable terms for assembler syntax where they appear in code or code fragments. For example: MRC p15, 0 <Rd>, <CRn>, <CRm>, <Opcode_2> Used in body text for a few terms that have specific technical meanings, that are defined in the ARM Glossary.
This section lists relevant documents published by third parties: • ANSI/IEEE Std 754-2008, IEEE Standard for Binary Floating-Point Arithmetic. Note ARM floating-point terminology is largely based on the earlier ANSI/IEEE Std 754-1985 issue of the standard. See the ARM Architecture Reference Manual ARMv8, for ARMv8-A ®...
The Cortex-A53 processor has one to four cores, each with an L1 memory system and a single shared L2 cache. Figure 1-1 shows an example of a Cortex-A53 MPCore configuration with four cores and either an ACE or a CHI interface. Cortex-A53 processor...
Support for both AArch32 and AArch64 Execution states. • Support for all exception levels, EL0, EL1, EL2, and EL3, in each execution state. • The A32 instruction set, previously called the ARM instruction set. • The T32 instruction set, previously called the Thumb instruction set. •...
Page 15
Introduction 1.2.3 Generic Interrupt Controller architecture The Cortex-A53 processor implements the Generic Interrupt Controller (GIC) v4 architecture. The Cortex-A53 processor includes only the GIC CPU Interface. See the ARM Generic ® Interrupt Controller Architecture Specification. 1.2.4 Generic Timer architecture The Cortex-A53 processor implements the ARM Generic Timer architecture. See the ARM ®...
• The processes to sign off the configured design. The ARM product deliverables include reference scripts and information about using them to implement your design. Reference methodology flows supplied by ARM are example reference implementations. Contact your EDA vendor for EDA tool support.
The Instruction Fetch Unit (IFU) contains the instruction cache controller and its associated linefill buffer. The Cortex-A53 MPCore instruction cache is 2-way set associative and uses Virtually Indexed Physically Tagged (VIPT) cache lines holding up to 16 A32 instructions, 16 32-bit T32 instructions, 16 A64 instructions, or up to 32 16-bit T32 instructions.
Page 26
The optional Advanced SIMD and Floating-point Extension implements: • ARM NEON technology, a media and signal processing architecture that adds instructions targeted at audio, video, 3-D graphics, image, and speech processing. Advanced SIMD instructions are available in AArch64 and AArch32 states.
Page 27
® Reference Manual for more information. 2.1.4 Cryptography Extension The optional Cortex-A53 MPCore Cryptography Extension supports the ARMv8 Cryptography Extensions. The Cryptography Extension adds new A64, A32, and T32 instructions to Advanced SIMD that accelerate: • Advanced Encryption Standard (AES) encryption and decryption.
Page 29
RAMs. 2.1.9 Debug and trace The Cortex-A53 processor supports a range of debug and trace features including: • ARM v8 debug features in each core. • ETMv4 instruction trace unit for each core. • CoreSight Cross Trigger Interface (CTI).
Page 33
• If there are any physical effects that could occur while changing the clock frequency, ARM recommends that the clock ratio is changed only while the STANDBYWFIL2 output of the processor is asserted. • The input signal ACLKENM exists in the Cortex-A53 processor if it is configured to include the ACE interface.
Page 34
• If there are any physical effects that could occur while changing the clock frequency, ARM recommends that the clock ratio is changed only while the STANDBYWFIL2 output of the processor is asserted. • The input signal ACLKENS exists in the Cortex-A53 processor if it is configured to include the ACP interface.
Page 35
Functional Description • If there are any physical effects that could occur while changing the clock frequency, ARM recommends that the clock ratio is changed only while the STANDBYWFIL2 output of the processor is asserted. • The input signal SCLKEN exists in the Cortex-A53 processor if it is configured to include the CHI interface.
Page 43
An APB access to the debug or trace registers residing in the core power domain. Exit from WFE low-power state occurs when the core detects a reset, the assertion of the EVENTI input signal, or one of the WFE wake up events as described in the ARM Architecture ®...
Page 48
Continue a normal cold reset sequence with L2RSTDISABLE held HIGH. The architectural state must be restored, if required. Retention state Contact ARM for information about retention state. 2.4.3 Event communication using WFE or SEV An external agent can use the EVENTI pin to participate in a WFE or SEV event communication with the Cortex-A53 processor.
Page 53
In the trivial Jazelle implementation, the processor does not accelerate the execution of any bytecodes, and the JVM uses software routines to execute all bytecodes. See the ARM ® Architecture Reference Manual ARMv8, for ARMv8-A architecture profile for information.
Page 60
Thumb instruction set state. 3.2.8 AArch32 execution modes ARMv7 and earlier versions of the ARM architecture define a set of named processor modes, including modes that correspond to different exception types. For compatibility, AArch32 state retains these processor modes.
System Control AArch64 register summary This section gives a summary of the system registers in the AArch64 Execution state. For more information on using the system registers, see the ARM Architecture Reference Manual ® ARMv8, for ARMv8-A architecture profile. The following subsections describe the system registers by functional group: •...
Page 71
Architecture Reference Manual ARMv8, for ARMv8-A architecture profile for more information. ® 4.2.9 AArch64 GIC system registers Table 4-9 shows the GIC system registers in AArch64 state. See the ARM Architecture ® Reference Manual ARMv8, for ARMv8-A architecture profile for more information. Table 4-9 GIC system registers...
Page 72
Generic Timer registers. 4.2.11 AArch64 thread registers Table 4-10 shows the thread registers in AArch64 state. See the ARM Architecture Reference ® Manual ARMv8, for ARMv8-A architecture profile for more information about these operations. Table 4-10 AArch64 miscellaneous system control operations...
Function [31:24] Implementer Indicates the implementer code. This value is: ASCII character 'A' - implementer is ARM. 0x41 [23:20] Variant Indicates the variant number of the processor. This is the major revision number x in the rx part of the rxpy description of the product revision status.
Page 81
Support for ARM trace architecture, with memory-mapped access. In the Trace registers, the ETMIDR gives more information about the implementation. [15:12] CopTrc Indicates support for coprocessor-based trace model: Processor does not support ARM trace architecture with CP14 access. [11:8] Reserved, [7:4] CopSDbg Indicates support for coprocessor-based Secure debug model: Processor supports v8 Debug architecture, with CP14 access.
Page 97
Note The optional Advanced SIMD and Floating-point extension is not included in the base product of the processor. ARM requires licensees to have contractual rights to obtain the Advanced SIMD and Floating-point extension. Usage constraints This register is accessible as follows: (NS) (SCR.NS = 1)
Page 98
AArch64. Note The optional Advanced SIMD and Floating-point extension is not included in the base product of the processor. ARM requires licensees to have contractual rights to obtain the Advanced SIMD and Floating-point extension. Usage constraints This register is accessible as follows: (NS) (SCR.NS = 1)
Page 101
Note The optional Cryptography engine is not included in the base product of the processor. ARM requires licensees to have contractual rights to obtain the Cortex-A53 Cryptography engine. Usage constraints This register is accessible as follows: (NS) (SCR.NS = 1)
Page 141
Translation table base address, bits[47:x]. Bits [x-1:0] are x is based on the value of TCR_EL1.T0SZ, the stage of translation, and the memory translation granule size. For instructions on how to calculate it, see the ARM Architecture Reference Manual ARMv8, for ®...
Page 142
Translation table base address, bits[47:x]. Bits [x-1:0] are x is based on the value of TCR_EL1.T0SZ, the stage of translation, and the memory translation granule size. For instructions on how to calculate it, see the ARM Architecture Reference Manual ARMv8, for ®...
Page 155
Translation table base address, bits[47:x]. Bits [x-1:0] are x is based on the value of TCR_EL1.T0SZ, the stage of translation, and the memory translation granule size. For instructions on how to calculate it, see the ARM Architecture Reference Manual ARMv8, for ®...
Page 170
• This register can be written only when the L2 memory system is idle. ARM recommends that you write to this register after a powerup reset before the MMU is enabled and before any ACE, CHI or ACP traffic has begun.
Page 177
Translation aborted because of a stage 2 fault during a stage 1 table walk. Reserved, [6:1] Fault status code, as shown in the Data Abort ESR encoding. See the ARM Architecture Reference Manual ® ARMv8, for ARMv8-A architecture profile for more information.
Page 186
System Control The CPU Auxiliary Control Register can be written only when the system is idle. ARM recommends that you write to this register after a powerup reset, before the MMU is enabled, and before any ACE or ACP traffic begins.
In AArch32 state you access the system registers through a conceptual coprocessor, identified as CP15, the System Control Coprocessor. Within CP15, there is a top-level grouping of system registers by a primary coprocessor register number, c0-c15. See the ARM Architecture ®...
Page 201
Table 4-129 shows the 32-bit wide system registers you can access when the processor is in AArch32 state and the value of CRn is c7. See the ARM Architecture Reference Manual ® ARMv8, for ARMv8-A architecture profile for more information.
Page 202
Table 4-130 shows the 32-bit wide system registers you can access when the processor is in AArch32 state and the value of CRn is c9. See the ARM Architecture Reference Manual ® ARMv8, for ARMv8-A architecture profile for more information.
Page 203
Reset Description VBAR Vector Base Address Register on page 4-263. 0x00000000 MVBAR Monitor Vector Base Address Register. See the ARM ® Architecture Reference Manual ARMv8, for ARMv8-A architecture profile for more information. Reset Management Register on page 4-264. 0x00000000 Interrupt Status Register on page 4-265.
Page 205
4.4.14 c14 registers Table 4-134 shows the CP15 system registers when the processor is in AArch32 state and the value of CRn is c14. See the ARM Architecture Reference Manual ARMv8, for ARMv8-A ® architecture profile for more information. Table 4-134 c14 register summary...
Page 210
Description SCTLR 32 bit System Control Register on page 4-191 0x00C50838 TTBR0 32 bit Translation Table Base Register 0, see the ARM ® Architecture Reference Manual ARMv8, for ARMv8-A 64 bit architecture profile TTBR1 32 bit Translation Table Base Register 1, see the ARM ®...
Page 211
FCSE Process ID Register on page 4-267 0x00000000 4.4.21 AArch32 Address registers Table 4-141 shows the address translation register and operations. See the ARM Architecture ® Reference Manual ARMv8, for ARMv8-A architecture profile for more information. Table 4-141 Address translation operations...
Page 212
EL1 only Thread ID Register HTPIDR Hyp Software Thread ID Register 4.4.23 AArch32 Performance monitor registers Table 4-143 shows the performance monitor registers. See the ARM Architecture Reference ® Manual ARMv8, for ARMv8-A architecture profile for more information. Table 4-143 Performance monitor registers Name...
Page 213
The reset value is if L2 cache is not implemented. 0x623FFFFF 4.4.24 AArch32 Secure registers Table 4-144 shows the Secure registers. See the ARM Architecture Reference Manual ARMv8, ® for ARMv8-A architecture profile for more information. Table 4-144 Security registers Name...
Page 214
System Control 4.4.25 AArch32 Virtualization registers Table 4-145 shows the Virtualization registers. See the ARM Architecture Reference Manual ® ARMv8, for ARMv8-A architecture profile for more information. Table 4-145 Virtualization registers Name Reset Width Description VPIDR 32-bit Virtualization Processor ID Register on page 4-189...
Function [31:24] Implementer Indicates the implementer code. This value is: ASCII character 'A' - implementer is ARM Limited. 0x41 [23:20] Variant Indicates the variant number of the processor. This is the major revision number n in the rn part of the rnpn description of the product revision status.
Page 225
Support for ARM trace architecture, with memory-mapped access. In the Trace registers, the ETMIDR gives more information about the implementation. [15:12] CopTrc Indicates support for coprocessor-based trace model: Processor does not support ARM trace architecture, with CP14 access. [11:8] Reserved, RAZ. [7:4] CopSDbg Indicates support for coprocessor-based Secure debug model: Processor supports v8 Debug architecture, with CP14 access.
Page 282
Trap valid Non-secure performance monitor accesses to Hyp mode. When this bit is set to 1, any valid Non-secure access to the Performance Monitor registers is trapped to Hyp mode. This bit resets to 0. See the ARM Architecture Reference Manual ARMv8, for ARMv8-A architecture ®...
Page 308
Table 4-223 HSR bit assignments Bits Name Function [31:26] Exception class. The exception class for the exception that is taken in Hyp mode. See the ARM Architecture ® Reference Manual ARMv8, for ARMv8-A architecture profile for more information. [25] Instruction length. See the ARM Architecture Reference Manual ARMv8, for ARMv8-A architecture profile for ®...
Page 328
You can write to this register only when the L2 memory system is idle. ARM recommends that you write to this register after a powerup reset before the MMU is enabled and before any ACE, CHI or ACP traffic has begun.
Page 330
(SCR.NS = 0) The CPU Auxiliary Control Register can be written only when the system is idle. ARM recommends that you write to this register after a powerup reset, before the MMU is enabled, and before any ACE or ACP traffic begins.
AArch64 state, the ARMv8 address translation system resembles an extension to the Long Descriptor Format address translation system to support the expanded virtual and physical address spaces. For more information regarding the address translation formats, see the ARM ® Architecture Reference Manual ARMv8, for ARMv8-A architecture profile. Key differences...
XN (Execute Never) attribute bit. To avoid speculative fetches to read-sensitive devices when address translation is disabled, these devices and code that are fetched must be separated in the physical memory map. See the ARM Architecture Reference ®...
However, if the address being accessed by the exclusive code sequence is in cacheable memory, any eviction of the cache line containing that address clears the monitor. ARM therefore recommends that no load or store instructions are placed between the exclusive load and the exclusive store because these additional instructions can cause a cache eviction.
Page 373
0b10 0b11 Note These ID and transaction details are provided for information only. ARM strongly recommends that all interconnects and peripherals are designed to support any type and number of transactions on any ID, to ensure compatibility with future products.
Page 376
This means that the write must be observable to all other masters in the system. ARM expects the majority of peripherals to meet this requirement. For best performance, ARM recommends that barriers are terminated within the cluster.
Page 377
Cortex-A53 processor marks the transaction as privileged, even it if was initiated by an unprivileged process. Table 7-10 shows Cortex-A53 processor exception levels and corresponding ARPROTM[0] and AWPROTM[0] values. Table 7-10 Cortex-A53 MPCore mode and ARPROT and AWPROT values Value of ARPROT[0] Processor exception level Type of access and AWPROT[0]...
Page 385
The master must avoid sending more than one outstanding transaction on the same AXI ID, to prevent the second transaction stalling the interface until the first has completed. If the master requires explicit ordering between two transactions, ARM recommends that it waits for the response to the first transaction before sending the second transaction.
0 to the L2 internal asynchronous error bit of the L2ECTLR register. • ARM recommends that the nINTERRIRQ pin is connected to the interrupt controller so that an interrupt or system error is generated when the pin is asserted.
Page 390
Chapter 9 Generic Interrupt Controller CPU Interface This chapter describes the Cortex-A53 processor implementation of the ARM Generic Interrupt Controller (GIC) CPU interface. It contains the following sections: • About the GIC CPU Interface on page 9-2. • GIC programmers model on page 9-3.
• Determining the highest priority pending interrupt for the processor. • Generating SGIs. For more information on the CPU interface, see the ARM Generic Interrupt Controller Architecture Specification. Table 9-2 on page 9-4 lists the registers for the CPU interface.
Page 393
S = Secure. b. NS = Non-secure. 9.2.3 CPU interface register descriptions This section describes only registers whose implementation is specific to the Cortex-A53 processor. All other registers are described in the ARM Generic Interrupt Controller ® Architecture Specification Table 9-2 provides cross-references to individual registers.
Page 394
Identifies the revision number for the CPU interface: r0p2. [11:0] Implementer Contains the JEP106 code of the company that implements the CPU interface. For an ARM implementation, these values are: Bits[11:8] = The JEP106 continuation code of the implementer. Bit[7] Always 0.
Page 395
List Register 3 0x00000000 9.2.5 Virtual interface control register descriptions This section describes only registers whose implementation is specific to the Cortex-A53 processor. All other registers are described in the ARM Generic Interrupt Controller ® Architecture Specification. Table 9-5 provides cross-references to individual registers.
Page 397
Generic Interrupt Controller CPU Interface 9.2.7 Virtual CPU interface register descriptions This section describes only registers whose implementation is specific to the Cortex-A53 processor. All other registers are described in the ARM Generic Interrupt Controller ® Architecture Specification. Table 9-7 on page 9-7 provides cross-references to individual registers.
Page 398
Chapter 10 Generic Timer This chapter describes the Cortex-A53 processor implementation of the ARM Generic Timer. It contains the following sections: • About the Generic Timer on page 10-2. • Generic Timer functional description on page 10-3. • Generic Timer register summary on page 10-4.
32-bits wide or 64-bits wide and accessible in the AArch32 and AArch64 Execution states. 10.3.1 AArch64 Generic Timer register summary Table 10-2 shows the AArch64 Generic Timer registers. See the ARM Architecture Reference ® Manual ARMv8, for ARMv8-A architecture profile for information about these registers. Table 10-2 AArch64 Generic Timer registers...
Page 402
The reset value for bit[2] is 0 and for bits[1:0] is 10.3.2 AArch32 Generic Timer register summary Table 10-3 shows the AArch32 Generic Timer registers. See the ARM Architecture Reference ® Manual ARMv8, for ARMv8-A architecture profile for information about these registers.
This section gives an overview of debug and describes the debug components. The processor forms one component of a debug system. The following methods of debugging an ARM processor based SoC exist: Conventional JTAG debug (‘external’ debug) This is invasive debug with the core halted using: •...
Page 405
• Application software. • Operating systems. • Hardware systems based on an ARM processor. The debug unit enables you to: • Stop program execution. • Examine and alter process and coprocessor state.
The 64-bit registers cover two addresses on the external memory interface. For those registers not described in this chapter, see the ARM Architecture Reference Manual ARMv8, for ARMv8-A ®...
Page 414
Unlinked data address match. Linked data address match. When this bit is set to 1 the linked BRP number field indicates the BRP that this WRP is linked. See the ARM ® Architecture Reference Manual ARMv8, for ARMv8-A architecture profile for more information.
CRn, op2, CRm, Op1 or instructions in the MCRR MRRC order of CRm, Op1. For those registers not described in this chapter, see the ARM Architecture ® Reference Manual ARMv8, for ARMv8-A architecture profile. See the...
Page 429
0xFC4 11.8.4 Peripheral Identification Registers The Peripheral Identification Registers provide standard information required for all components that conform to the ARM Debug Interface v5 specification. They are a set of eight registers, listed in register number order in Table 11-15.
Page 431
Function [31:8] Reserved, [7:4] DES_0 ARM Limited. This is the least significant nibble of JEP106 ID code. [3:0] Part_1 Most significant nibble of the debug part number. The EDPIDR1 can be accessed through the internal memory-mapped interface and the external...
Page 432
JEDEC RAO. Indicates a JEP106 identity code is used. [2:0] DES_1 ARM Limited. This is the most significant nibble of JEP106 ID code. 0b011 The EDPIDR2 can be accessed through the internal memory-mapped interface and the external debug interface, offset...
Page 433
Size of the component. Log2 the number of 4KB pages from the start of the component to the end of the component ID registers. [3:0] DES_2 ARM Limited. This is the least significant nibble JEP106 continuation code. The EDPIDR4 can be accessed through the internal memory-mapped interface and the external debug interface, offset 0xFD0 Peripheral Identification Register 5-7 No information is held in the Peripheral ID5, Peripheral ID6 and Peripheral ID7 Registers.
Page 434
0xFF4 Component ID2 0x05 0xFF8 Component ID3 0xB1 0xFFC The Component Identification Registers identify Debug as an ARM Debug Interface v5 component. The Component ID registers are: • Component Identification Register • Component Identification Register 1 on page 11-33. •...
The system can access memory-mapped debug registers through the APB interface. The APB interface is compliant with the AMBA 4 APB interface. Figure 11-20 shows the debug interface implemented in the Cortex-A53 processor. For more information on these signals, see the ARM CoreSight Architecture Specification. ®...
Debug 11.11 ROM table The Cortex-A53 processor includes a ROM table that complies with the ARM CoreSight ® ™ Architecture Specification. This table contains a list of components such as processor debug units, processor Cross Trigger Interfaces (CTIs), processor Performance Monitoring Units (PMUs) and processor Embedded Trace Macrocell (ETM) trace units.
Page 447
Debug 11.11.4 Peripheral Identification Registers The Peripheral Identification Registers provide standard information required for all components that conform to the ARM Debug Interface v5 specification. There is a set of eight registers, listed in register number order in Table 11-32.
Page 449
JEDEC RAO. Indicates a JEP106 identity code is used. [2:0] DES_1 Designer, most significant bits of JEP106 ID code. For ARM Limited. 0b011 The ROMPIDR2 can be accessed through the internal memory-mapped interface and the external debug interface, offset 0xFE8...
12.1 About the PMU The Cortex-A53 processor includes performance monitors that implement the ARM PMUv3 architecture. These enable you to gather various statistics on the operation of the processor and its memory system during runtime. These provide useful information about the behavior of the processor that you can use when debugging or profiling code.
Execution state with instructions. Table 12-3 gives a summary of the Cortex-A53 PMU registers in the AArch64 Execution state. For those registers not described in this chapter, see the ARM Architecture Reference Manual ® ARMv8, for ARMv8-A architecture profile. Table 12-3 PMU register summary in the AArch64 Execution state...
Page 462
No action. This is the reset value. Reset PMCCNTR_EL0 to 0. This bit is always RAZ. Note Resetting PMCCNTR does not clear the PMCCNTR_EL0 overflow bit to 0. See the ARM Architecture ® Reference Manual ARMv8, for ARMv8-A architecture profile. for more information.
64-bit registers. MCRR MRRC Table 12-9 gives a summary of the Cortex-A53 PMU registers in the AArch32 Execution state. For those registers not described in this chapter, see the ARM Architecture Reference Manual ® ARMv8, for ARMv8-A architecture profile. See the...
Page 471
No action. This is the reset value. Reset PMCCNTR_EL0 to 0. This bit is always RAZ. Note Resetting PMCCNTR does not clear the PMCCNTR_EL0 overflow bit to 0. See the ARM Architecture ® Reference Manual ARMv8, for ARMv8-A architecture profile for more information.
Page 472
Figure 12-6 PMCEID0 bit assignments Table 12-11 shows the PMCEID0 bit assignments with event implemented or not implemented when the associated bit is set to 1 or 0. See the ARM Architecture Reference Manual ARMv8, ® for ARMv8-A architecture profile for more information about these events.
Page 481
0xE00 12.8.2 Peripheral Identification Registers The Peripheral Identification Registers provide standard information required for all components that conform to the ARM PMUv3 architecture. There is a set of eight registers, listed in register number order in Table 12-17. Table 12-17 Summary of the Peripheral Identification Registers...
Page 483
[31:8] Reserved, [7:4] DES_0 ARM Limited. This is the least significant nibble of JEP106 ID code. [3:0] Part_1 Most significant nibble of the performance monitor part number. The PMPIDR1 can be accessed through the internal memory-mapped interface and the external...
Page 485
Size of the component. Log2 the number of 4KB pages from the start of the component to the end of the component ID registers. [3:0] DES_2 ARM Limited. This is the least significant nibble JEP106 continuation code. The PMPIDR4 can be accessed through the internal memory-mapped interface and the external debug interface, offset 0xFD0 Peripheral Identification Register 5-7 No information is held in the Peripheral ID5, Peripheral ID6 and Peripheral ID7 Registers.
Page 486
Performance Monitor Unit The Component Identification Registers identify Performance Monitor as ARM PMUv3 architecture. The Component ID registers are: • Component Identification Register • Component Identification Register • Component Identification Register 2 on page 12-33. • Component Identification Register 3 on page 12-34.
The ETM trace unit is a module that performs real-time instruction flow tracing based on the Embedded Trace Macrocell (ETM) architecture ETMv4. ETM is a CoreSight component, and is an integral part of the ARM Real-time Debug solution, DS-5 Development Studio. See the CoreSight documentation in Additional reading on page ix for more information.
Page 541
[20] Inverts the selected resources: Resource is not inverted. Resource is inverted. [19] Reserved, [18:16] GROUP Selects a group of resources. See the ARM Architecture Specification, ETMv4 for more information. ® ™ [15:8] Reserved, [7:0] SELECT Selects one or more resources from the required group. One bit is provided for each resource from the group.
Page 565
Function [31:8] Reserved, [7:4] DES_0 ARM Limited. This is bits [3:0] of JEP106 ID code. [3:0] Part_1 Most significant four bits of the ETM trace unit part number. The TRCPIDR1 can be accessed through the internal memory-mapped interface and the...
Page 567
Size of the component. Log2 the number of 4KB pages from the start of the component to the end of the component ID registers. [3:0] DES_2 ARM Limited. This is bits [3:0] of the JEP106 continuation code. The TRCPIDR4 can be accessed through the internal memory-mapped interface and the external debug interface, offset 0xFD0 Peripheral Identification Register 5-7 No information is held in the Peripheral ID5, Peripheral ID6 and Peripheral ID7 Registers.
All trace register accesses through the memory-mapped and external debug interfaces behave as if the processor power domain is powered down when debug double lock is set. For more information on debug double lock, see the ARM Architecture Reference Manual ARMv8, for ®...
Table 14-3 gives a summary of the Cortex-A53 cross trigger registers. For those registers not described in this chapter, see the ARM Architecture Reference Manual ARMv8, for ARMv8-A ®...
Cross Trigger 14.5 Cross trigger register descriptions This section describes the Cortex-A53 MPCore Cross Trigger registers. The Cross trigger register summary on page 14-5 provides cross-references to the individual registers. 14.5.1 CTI Device Identification Register The CTIDEVID characteristics are: Purpose Describes the CTI component to the debugger.
Page 581
Cross Trigger 14.5.3 CTI Peripheral Identification Registers The Peripheral Identification Registers provide standard information required for all components that conform to the ARM CoreSight architecture. There is a set of eight registers, listed in register number order in Table 14-8.
Page 583
JEDEC 1. Indicates a JEP106 identity code is used. [2:0] DES_1 ARM Limited. This is the most significant nibble of JEP106 ID code. 0b011 CTIPIDR2 can be accessed through the internal memory-mapped interface and the external debug interface, offset 0xFE8...
Page 585
Size of the component. Log2 the number of 4KB pages from the start of the component to the end of the component ID registers. [3:0] DES_2 ARM Limited. This is the least significant nibble JEP106 continuation code. CTIPIDR4 can be accessed through the internal memory-mapped interface and the external debug interface, offset 0xFD0 Peripheral Identification Register 5-7 No information is held in the Peripheral ID5, Peripheral ID6, and Peripheral ID7 Registers.
Page 595
Globally disables the CPU interface logic and routes the “External” signals directly to the processor: Enable the GIC CPU interface logic. Disable the GIC CPU interface logic. Required to enable use of non-ARM interrupt controllers. ICDTVALID Input AXI4 Stream Protocol signal. Distributor to GIC CPU Interface messages. TVALID indicates that the master is driving a valid transfer.
Coherency data channel handshake signals on page A-21. • Read and write acknowledge signals on page A-21. For a complete description of the ACE interface signals, see the ARM AMBA AXI and ACE ® ® Protocol Specification AXI3, AXI4, and AXI4-Lite, ACE and ACE-Lite.
Where possible and practical, all ARM implementations adhere to these single preferred behaviors. In some limited instances an ARM implementation might not adhere to these single preferred behaviors, and instead behaves as described by one of the alternate legal behaviors.
ARM Architecture Reference Manual ARMv8, for ARMv8-A ® UNPREDICTABLE architecture profile pseudo-code, or in other places in the ARM Architecture Reference Manual ® ARMv8, for ARMv8-A architecture profile, read 0 unless otherwise stated in section 4.28, or as described in the following paragraph.
Need help?
Do you have a question about the Cortex-A53 MPCore and is the answer not in the manual?
Questions and answers