Intel Agilex® 7 F-Series and I-Series Known Issue List

Download PDF
ID 683584
Date 5/03/2023
Public
Document Table of Contents
Document Table of Contents x
1. About this Document 2. Known Issue List for Intel Agilex® 7 Devices 3. Arm* Cortex*-A53 MPCore* and CoreSight* Errata 4. Intel Agilex® 7 F-Series and I-Series User Guidelines 5. Document Revision History for the Intel Agilex® 7 F-Series and I-Series Known Issue List
2. Known Issue List for Intel Agilex® 7 Devices x
2.1. FPGA 2.2. Hard Processor System
2.1. FPGA x
2.1.1. Configuration and Security
2.1.1. Configuration and Security x
2.1.1.1. FPGA Reconfiguration May Cause Device to Halt 2.1.1.2. Secure Device Manager May Disable Physically Unclonable Function
2.2. Hard Processor System x
2.2.1. Write Data Can Appear at an AXI Interface before the Write Address, which can Cause a Deadlock Condition
3. Arm* Cortex*-A53 MPCore* and CoreSight* Errata x
3.1. 843819: Memory Locations May be Accessed Speculatively Due to Instruction Fetches When HCR.VM is Set 3.2. 845719: A Load May Read Incorrect Data 3.3. 855871: ETM Does Not Report IDLE State When Disabled Using OSLOCK 3.4. 855872: A Store-Exclusive Instruction May Pass When it Should Fail 3.5. 711668: Configuration Extension Register Has Wrong Value Status 3.6. 720107: Periodic Synchronization Can Be Delayed and Cause Overflow 3.7. 855873: An Eviction Might Overtake a Cache Clean Operation 3.8. 853172: ETM May Assert AFREADY Before All Data Has Been Output 3.9. 836870: Non-Allocating Reads May Prevent a Store Exclusive From Passing 3.10. 836919: Write of the JMCR in EL0 Does Not Generate an UNDEFINED Exception 3.11. 845819: Instruction Sequences Containing AES Instructions May Produce Incorrect Results 3.12. 851672: ETM May Trace an Incorrect Exception Address 3.13. 851871: ETM May Lose Counter Events While Entering WFx Mode 3.14. 852071: Direct Branch Instructions Executed Before a Trace Flush May be Output in an Atom Packet After Flush Acknowledgment 3.15. 852521: A64 Unconditional Branch May Jump to Incorrect Address 3.16. 855827: PMU Counter Values May Be Inaccurate When Monitoring Certain Events 3.17. 855829: Reads of PMEVCNTR<n> are not Masked by HDCR.HPMN 3.18. 855830: Loads of Mismatched Size May not be Single-Copy Atomic
1. About this Document
2. Known Issue List for Intel Agilex® 7 Devices
3. Arm* Cortex*-A53 MPCore* and CoreSight* Errata
4. Intel Agilex® 7 F-Series and I-Series User Guidelines
5. Document Revision History for the Intel Agilex® 7 F-Series and I-Series Known Issue List

3.12. 851672: ETM May Trace an Incorrect Exception Address

Description

The address in an exception packet is the preferred exception return address. Because of this erratum, the address may be equal to the target address of the exception. The trace stream is not corrupted, and decompression can continue after the affected packet.

The following sequence is required for this erratum to occur:

  1. The ETM must start tracing instructions because of one of the following:
    1. ViewInst starts.
    2. The security state changes indicating trace is now permitted.
    3. The values of the external debug interface (DBGEN, SPIDEN, NIDEN, SPNIDEN) change to indicate trace is now permitted.
    4. The CPU exits debug mode.
  2. Before the CPU executes any other behavior that causes a trace to be generated, it executes a direct branch instruction, which may or may not be taken.
  3. The next instruction is a load or store that causes a data abort or watchpoint exception.
After this sequence, provided certain timing specific conditions are met, the address in the exception packet may be incorrect.

Impact

The trace decompressor may incorrectly infer execution of many instructions from the branch target to the provided address.

Workaround

The trace decompressor can detect that this erratum has occurred by checking if the exception address is in the vector table and identifying if the branch was not expected to be taken to the vector table. A decompressor can infer the correct address of the exception packet. The target of the preceding branch (if the branch was taken), or the next instruction after the branch (if the branch was not-taken) provides the correct address of the exception packet.

Category

Category 3
Level Two Title