Visible to Intel only — GUID: ret1644958070400
Ixiasoft
1. Introduction
2. Interface Overview
3. Parameters
4. Designing with the IP Core
5. Block Description
6. Cryptographic IP Data Profiles
7. Configuration Registers
8. Design Example
9. Symmetric Cryptographic Intel FPGA Hard IP User Guide Archives
10. Document Revision History for the Symmetric Cryptographic Intel FPGA Hard IP User Guide
4.1. Installing and Licensing Intel® FPGA IP Cores
4.2. Specifying the IP Core Parameters and Options
4.3. Generated File Structure
4.4. Symmetric Cryptographic IP Core Flow
4.5. Dynamically Disabling SM4 Capability
4.6. Error Handling
4.7. Error Reporting
4.8. Resetting the IP Core
4.9. Channel Definition and Allocation
4.10. Byte Ordering
4.11. AXI-ST Single Packet Mode
4.12. AXI-ST Multiple Packet Mode
7.1. Cryptographic Primary Control Register
7.2. Cryptographic Secondary Control Register
7.3. Cryptographic Primary Status Register
7.4. Cryptographic Error Status Register
7.5. Cryptographic Error Control Register
7.6. Cryptographic Packet Error Control 1 Register
7.7. Cryptographic Packet Error Control 2 Register
7.8. Cryptographic Error Code Control 1 Register
7.9. Cryptographic Error Code Control 2 Register
7.10. Cryptographic Error Code Internal Control Register
7.11. Cryptographic Internal Error Control Register
7.12. Cryptographic First Error Log Register
7.13. Cryptographic Packet Error Log 1 Register
7.14. Cryptographic Packet Error Log 2 Register
7.15. Cryptographic Internal Error Log Register
7.16. Cryptographic Wall Clock LSB Register
7.17. Cryptographic Wall Clock MSB Register
7.18. Ternary Control Register
Visible to Intel only — GUID: ret1644958070400
Ixiasoft
4.12. AXI-ST Multiple Packet Mode
The AXI-ST Multiple Packet Mode is supported for MACsec and IPsec profiles. The AXI specification defines the Multiple Packet Mode as following:
- No two start of packet (SOP) within the same clock cycle.
- No two end of packet (EOP) within the same clock cycle.
- Two packets packed within the same clock cycle are allowed as long as both packets are from the same stream.
TID | 0 | 0 | 0 | 0 |
tuser | port 0 | port 0 | port 0 | port 0 |
tlast | 0 | 1 | 1 | 1 |
tuser_last_segment0 | 0 | 1 | 0 | 1 |
tuser_last_segment1 | 0 | 0 | 1 | 0 |
tuser_last_segment2 | 0 | 0 | 0 | 0 |
tuser_last_segment3 | 0 | 0 | 0 | 0 |
tkeep | 11111111_11111111 11111111_11111111 11111111_11111111 11111111_11111111 |
11111111_11111111 11111111_11111111 11111111_11111111 11111111_11111111 |
11111111_11111111 11111111_11111111 00000000_11111111 11111111_11111111 |
00000000_00000000 00000000_00000000 00000000_00000000 11111111_11111111 |
DATA | ||||
tdata[511:448] | Data 0 | Data 1 | Data 2 | — |
tdata[447:384] | Data 0 | Data 1 | Data 2 | — |
tdata[383:320] | Data 0 | Data 1 | Data 2 | — |
tdata[319:256] | Data 0 | Data 1 | Data 2 | — |
tdata[255:192] | Data 0 | Data 1 | 64'b0 | — |
tdata[191:128] | Data 0 | Data 1 | Data 1 | — |
tdata[127:64] | Data 0 | Data 0 | Data 1 | Data 2 |
tdata[63:0] | Data 0 | Data 0 | Data 1 | Data 2 |