Page 2
Use of the word “partner” in reference to Arm’s customers is not intended to create or refer to any partnership relationship with any other company.
Page 3
This document is Non-Confidential. The right to use, copy and disclose this document may be subject to license restrictions in accordance with the terms of the agreement entered into by Arm and the party that Arm delivered this document to.
Page 22
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 Arm meaning differs from the generally accepted meaning. See the Glossary for more information.
Page 24
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 architecture ®...
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 Reference Manual ®...
L2ECTLR register. • Arm recommends that the nINTERRIRQ signal is connected to the interrupt controller so that an interrupt or system error is generated when the signal is asserted. When a dirty cache line with an error on the data RAMs is evicted from the processor, the write on the master interface still takes place, however if the error is uncorrectable then: •...
However, if the exclusive code sequence is accessing an address in cacheable memory, any cache line eviction that contains 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.
You must ensure that your interconnect and any peripherals connected to it do not return a write response for a transaction until that transaction would be considered complete by a later barrier. 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.
Page 111
0b1xxxnn 1 Core nn read 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.
You must ensure that your interconnect and any peripherals connected to it do not return a write response for a transaction until that transaction would be considered complete by a later barrier. 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.
This section describes the ACE configurations. Note If you want to connect the processor to an AXI interconnect, Arm recommends that you use the AXI processor configuration option. Using the ACE processor configuration option in AXI mode is less area- efficient than the AXI configuration option.
Page 121
0b1xxxnn 1 Core nn read 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.
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.
The processor can access different 32-bit wide system registers. Registers where CRn has the value nine are called c9 registers. The following table 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 ®...
The following table shows the 32-bit wide system registers you can access when the processor is in AArch32 state and the value of CRn is c13. For information on all registers but FCSE Process ID, see the Arm Architecture Reference Manual ®...
(SCR.NS = 0) RW RW RW 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 master interface or ACP traffic begins.
Page 249
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, ®...
26 25 24 Figure B1-24 HSR bit assignments EC, [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. IL, [25] Instruction length.
(SCR.NS = 0) RW RW RW 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 AXI, ACE, CHI, or ACP traffic has begun.
B2.1 AArch64 register summary B2.1 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.
(SCR.NS = 0) RW RW RW 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 master interface or ACP traffic begins.
Page 426
B2 AArch64 system registers B2.42 Exception Syndrome Register, EL2 Table B2-34 ISS field contents for the Cortex-A35 processor (continued) ISS[23:22] ISS[1:0] Description 0b01 0b00 nSEI , or nVSEI in a guest OS, asserted 0b01 0b01 nREI asserted To access the ESR_EL2: MRS <Xt>, ESR_EL2 ;...
Provides information about the optional cryptographic instructions that the processor can support. The optional Cryptographic engine is not included in the base product of the processor. Arm requires licensees to have contractual rights to obtain the Cortex‑A35 Cryptographic engine. Usage constraints...
Provides additional information about implemented processor features in AArch64. The optional Advanced SIMD and floating-point support 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 support.
Provides information about the instruction sets that the processor implements. The optional Advanced SIMD and floating-point support 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 support.
The L2ACTLR_EL1: • 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 516
Translation aborted because of a stage 2 fault during a stage 1 table walk. Reserved, RES0 FST, [6:1] Fault status code, as the Data Abort ESR encoding shows it. See the Arm Architecture ® Reference Manual Armv8, for Armv8-A architecture profile for more information.
C3.1 About the ETM The ETM trace unit is a build-time configuration option. This module performs real-time instruction flow tracing that complies with the ETM architecture. As a CoreSight component, it is part of the Arm real-time debug solution. CLKIN...
Page 634
C8.1 Memory-mapped debug register summary on page C8-644 for a complete list of registers accessible from the external debug interface. 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 ®...
Memory-mapped debug register summary The following table shows the offset address for the registers that are accessible from the external debug interface. For those registers not described in this chapter, see the Arm Architecture Reference Manual Armv8, for ® Armv8-A architecture profile.
C9.1 About the ROM table The 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.
ROM Table Peripheral Identification Registers The ROM Table Peripheral Identification Registers provide standard information required for all components that conform to the Arm Debug Interface Architecture Specification, ADIv5.0 to ADIv5.2. There are eight registers listed in register number order in the following table.
64-bit registers. MCRR MRRC The following table gives a summary of the Cortex‑A35 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.
Page 693
No action. This is the reset value. Reset PMCCNTR_EL0 to 0. This bit is always RAZ. Resetting PMCCNTR does not clear the PMCCNTR overflow bit to 0. See the Arm ® Architecture Reference Manual Armv8, for Armv8-A architecture profile for more information.
Common architectural and microarchitectural feature events that can be counted by the PMU event counters. The following table 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 ®...
The PMU counters and their associated control registers are accessible in the AArch64 Execution state with instructions. The following table gives a summary of the Cortex‑A35 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.
Page 705
No action. This is the reset value. Reset PMCCNTR_EL0 to 0. This bit is always RAZ. Resetting PMCCNTR_EL0 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.
Purpose Enables topology detection or integration testing, by putting the ETM trace unit into integration mode. Usage constraints Arm recommends that you perform a debug reset after using integration mode. Configurations Available in all configurations. Attributes C11.1 ETM register summary on page C11-733.
B AArch32 UNPREDICTABLE Behaviors B.2 UNPREDICTABLE instructions within an IT Block UNPREDICTABLE instructions within an IT Block Conditional instructions within an IT Block, described as being unpredictable in the Arm Architecture ® Reference Manual Armv8, for Armv8-A architecture profile pseudo-code, are executed unconditionally.
Need help?
Do you have a question about the Cortex-A35 and is the answer not in the manual?
Questions and answers