1. Agilex™ 3 Embedded Memory Overview
2. Agilex™ 3 Embedded Memory Architecture and Features
3. Agilex™ 3 Embedded Memory Design Considerations
4. Agilex™ 3 Embedded Memory IP References
5. Agilex™ 3 Embedded Memory Debugging
6. Document Revision History for the Embedded Memory User Guide: Agilex™ 3 FPGAs and SoCs
2.1. Byte Enable in Agilex™ 3 Embedded Memory Blocks
2.2. Address Hold Support
2.3. Asynchronous Clear and Synchronous Clear
2.4. Memory Blocks Error Correction Code Support
2.5. Agilex™ 3 Embedded Memory Clocking Modes
2.6. Agilex™ 3 Embedded Memory Configurations
2.7. Force-to-Zero
2.8. Coherent Read Memory
2.9. Freeze Logic
2.10. True Dual Port Dual Clock Emulator
2.11. Initial Value of Read and Write Address Registers
2.12. Automatic Timing/Power Optimization in M20K Blocks
3.1. Consider the Memory Block Selection
3.2. Consider the Concurrent Write Behavior
3.3. Read-During-Write
3.4. Consider Power-Up State and Memory Initialization
3.5. Reduce Power Consumption
3.6. Avoid Providing Non-Deterministic Input
3.7. Avoid Changing Clock Signals and Other Control Signals Simultaneously
3.8. Advanced Settings in Quartus® Prime Software for Memory
3.9. Consider the Memory Depth Setting
3.10. Consider Registering the Memory Output
4.2.5.1. FIFO Functional Timing Requirements
4.2.5.2. SCFIFO ALMOST_EMPTY Functional Timing
4.2.5.3. FIFO Output Status Flag and Latency
4.2.5.4. FIFO Metastability Protection and Related Options
4.2.5.5. FIFO Synchronous Clear and Asynchronous Clear Effect
4.2.5.6. SCFIFO and DCFIFO Show-Ahead Mode
4.2.5.7. Different Input and Output Width
4.2.5.8. DCFIFO Timing Constraint Setting
4.2.5.9. Gray-Code Counter Transfer at the Clock Domain Crossing
4.2.5.10. Guidelines for Embedded Memory ECC Feature
4.2.5.11. Reset Scheme
2.2. Address Hold Support
While active, the address hold captures and holds the previous address value until the next clock cycle. You can use this capability to control the pipeline, avoid metastability, or perform specific asynchronous operations. To enable the address hold feature, assert the addresstall signal.
Note:
- Simple dual-port mode only—address latching is supported only in simple dual-port mode and is not available in other dual-port configurations or single-port mode.
- First clock cycle restriction—to avoid unpredictable data output caused by potential initialization issues, do not assert the addressstall signal during the first clock cycle of operation after device configuration.
- Dual-port considerations—if you use dual-port memory blocks, each port has its own independent addressstall signal, allowing you to control address latching for each port individually.
Figure 2. Address HoldThis figure shows an address hold block diagram
Figure 3. Address Hold During Read CycleThis figure shows the address hold behavior during read cycle.
Figure 4. Address Hold During Write Cycle This figure shows the address hold behavior during write cycle.