Intel Agilex® 7 F-Series and I-Series FPGA Memory Subsystem IP User Guide
ID
789389
Date
10/02/2023
Public
A newer version of this document is available. Customers should click here to go to the newest version.
1. About the Intel Agilex® 7 F-Series and I-Series FPGA Memory Subsystem IP
2. Introduction to Memory Subsystem IP
3. Memory Subsystem IP Architecture and Feature Description
4. Memory Subsystem Features
5. Memory Subsystem Interfaces and Signals
6. Memory Subsystem User Operations
7. Memory Subsystem Register Descriptions
8. Parameterizing the Memory Subsystem IP
9. Simulating Your Design
10. Document Revision History for Intel Agilex® 7 F-Series and I-Series FPGA Memory Subsystem IP User Guide
5.3.1. TCAM AXI-ST Request Interface
5.3.2. TCAM AXI-ST Response Interface
5.3.3. TCAM AXI-Lite Interface
5.3.4. BCAM AXI-ST Request Interface
5.3.5. BCAM AXI-ST Response Interface
5.3.6. BCAM AXI-Lite Interface
5.3.7. MBL AXI-ST Request Interface
5.3.8. MBL AXI-ST Response Interface
5.3.9. MBL AXI-Lite Interface
6.4.1. MBL Flush Operation
6.4.2. MBL Insert Key Operation
6.4.3. MBL Delete Key Operation
6.4.4. MBL Lookup Operation Using Key
6.4.5. MBL Modify Operation
6.4.6. MBL Modify Result Using Handle Operation
6.4.7. MBL Delete Key Using Handle Operation
6.4.8. MBL Lookup Using Handle Operation
6.4.9. MBL Insert Key if Not Present or Modify Result if Present Operation
6.4.10. MBL Get Handle Operation
7.2.1. Offset 0x0000 Version
7.2.2. Offset 0x0004 Feature List
7.2.3. Offset 0x0010h Interface Attribute Parameters
7.2.4. Offset 0x0020 Scratch Pad
7.2.5. Offset 0x0050 Status
7.2.6. Offset 0x0 0100 - 0x0 0xxx (+0x8h per instance), Additional Attributes Per Instance Lower DW (1 to 16)
7.2.7. Offset 0x0 0104 - 0x0 0xxx (+0x8h per instance) Additional Attributes per Instance Upper DW (1 up to 16)
7.2.8. Offset 0x0 1000 (+0x0 1000h per instance) Efficiency Monitor registers (per instance)
7.4.2.1. Version
7.4.2.2. Feature List
7.4.2.3. Interface Attribute Parameters
7.4.2.4. Interface Attribute Parameters 1
7.4.2.5. Scratch Pad
7.4.2.6. General Control (GEN_CTRL)
7.4.2.7. Management Control (MGMT_CTRL)
7.4.2.8. Hash function_0 seed
7.4.2.9. Hash function_1 seed
7.4.2.10. Hash function_2 seed
7.4.2.11. Warning 0 (WARNING_0)
7.4.2.12. Fatal Error (FATAL_ERROR_0)
7.4.2.13. Monitor 0 (MON_)
7.4.2.14. Total Entries (TOTAL_ENTRIES)
7.4.2.15. Max. Rehouse Iterations (Max_Rehouse_Iterations)
7.4.2.16. Statistics Control (STATS_CTRL)
7.4.2.17. Active Table Entries (TABLE_ENTRIES)
7.4.2.18. Key_N
7.4.2.19. Result_N
7.6.1. General MBL Registers
7.6.2. Version
7.6.3. Mbl_scratch
7.6.4. Mbl_gen_ctrl
7.6.5. Mbl_mgmt_ctrl
7.6.6. Mbl_key_handle
7.6.7. Mbl_nxt_handle_req
7.6.8. Mbl_nxt_handle
7.6.9. Mbl_warning_0
7.6.10. Mbl_fatal_0
7.6.11. Mbl_mon_0
7.6.12. Mbl_total_entries
7.6.13. Mbl_total_rehashes
7.6.14. Mbl_max_used_bins
7.6.15. Mbl_stats_ctrl
7.6.16. Mbl_stats_result
7.6.17. Mbl_max_lkup_latency
7.6.18. Mbl_max_rehash_index
7.6.19. Mbl_key
7.6.20. Mbl_res
8.2.5.1. Parameterizing the External Memory Interface (EMIF) IP
8.2.5.2. Parameterizing the Memory-Specific Adapter
8.2.5.3. Parameterizing the Content-Addressable Memory (CAM) IP
8.2.5.4. Parameterizing the External Memory Interfaces Intel Calibration IP
8.2.5.5. Saving the IPs Within the Memory Subsystem
8.2.5.6. Propagation of Changes Across IPs within the Memory Subsystem IP
4.3.1. TCAM
If you connect an associative storage with a M20K memory interface in the high-level topology parameter editor, a CAM IP is enabled for configuration in the Platform Designer shown after clicking Dive Into Packaged Subsystem.
If you select the Wildcard Match traffic type, the TCAM algorithm is used and the following parameters are available for you to configure.
Parameter | Default | Description | Range/Values |
---|---|---|---|
Traffic Type | Exact match | Specify the type of traffic | Exact match, wildcard match |
TCAM Basic | |||
Lookup key width | 68 | Specify lookup key width. | 16-512 |
Result width | 56 | Specify result width. | 8-1024 |
Packet processing metadata width | 1 | Specify packet processing user metadata width. | Up to 1024 |
User metadata width | 1 | Specify user metadata width. | Up to 1024 |
Number of entries | 256 | Specify number of entries in the lookup table. | 32-1024 |
TCAM Advanced | |||
Number of core tables | 1 | Specify the number of core tables, it decides the lookup rate of TCAM. | 1–4 |
Entry slice width | 40 | Specify each TCAM Key RAM data width. | Should be smaller than entries. Recommended values: 10, 20, or 40. |
Key slice width | 8 | Specify each TCAM Key RAM address width. | Should be smaller than the key width. |
Pipe control | 19 | ||
Return highest matching entry | Enabled | When enabled, returns the highest matching entry. When disabled, returns all matching entries. |
N/A |
Enable on-chip RAM ECC | Disabled | Enable on-chip RAM error correction code. | |
Enable AXI ST interface ready latency | Disabled | Enable ready latency on AXI ST interface. | N/A |
AXI ST valid path pipe stages | 0 | Defines the number of pipe stages required on the AXI ST interface valid path to the IP. | 0–16 |
AXI ST ready path pipe stages | 0 | Defines the number of pipe stages required on the AXI ST interface ready path to the IP. | 0–16 |
AXI ST interface ready latency | 0 | Defines the association between assertion of ready signal and the corresponding valid. | 0–32 |
Enable AXI Lite interface ready latency | Disabled | Enable ready latency on AXI Lite interface. | N/A |
AXI Lite write address channel valid path pipe stages | 0 | Defines the number of pipe stages required on the AXI Lite interface write address channel valid path to the IP. | 0–16 |
AXI Lite write address channel ready path pipe stages | 0 | Defines the number of pipe stages required on the AXI Lite interface write address channel ready path to the IP. | 0–16 |
AXI Lite write address channel ready latency | 0 | Defines the association between assertion of ready signal and the corresponding valid. | 0–32 |
AXI Lite write data channel valid path pipe stages | 0 | Defines the number of pipe stages required on the AXI Lite interface write data channel valid path to the IP. | 0–16 |
AXI Lite write data channel ready path pipe stages | 0 | Defines the number of pipe stages required on the AXI Lite interface write data channel ready path to the IP. | 0–16 |
AXI Lite write data channel ready latency | 0 | Defines the association between assertion of ready signal and the corresponding valid. | 0–32 |
AXI Lite read address channel valid path pipe stages | 0 | Defines the number of pipe stages required on the AXI Lite interface read address channel valid path to the IP. | 0–16 |
AXI Lite read address channel ready path pipe stages | 0 | Defines the number of pipe stages required on the AXI Lite interface read address channel ready path to the IP. | 0–16 |
AXI Lite read address channel ready latency | 0 | Defines the association between assertion of ready signal and the corresponding valid. | 0–32 |
TCAM Controls and Diagnostics | |||
DHF Enable | Enabled | Enable DFH headers. | |
Grouping ID | 0x0000 | Grouping ID can be used to categorize multiple instances of the same IP into separate groups. | |
Instance ID | 0x0000 | A unique Instance ID can be used to differentiate between multiple instances of the same IP. | |
End of list | Disabled | Specify if it is DFH CSR end of list. | N/A |
Next DFH byte offset | 0 | Specify next DFH byte offset. | |
AXI Lite interface data width | 32 | Specify AXI Lite interface data width. | 32, 64 |