1. Introduction
2. Interface Overview
3. Parameters
4. Designing with the IP Core
5. Functional Description
6. Configuration Registers for MACsec IP
7. MACsec Intel® FPGA IP Example Design
8. MACsec Intel FPGA IP User Guide Archives
9. Document Revision History for the MACsec Intel FPGA IP User Guide
2.2.1.1. Common Port Mux Interface
2.2.1.2. Common Port Demux Interface
2.2.1.3. Controlled Port Mux Interface
2.2.1.4. Controlled Port Demux Interface
2.2.1.5. Uncontrolled Port RX Interface
2.2.1.6. Uncontrolled Port TX Interface
2.2.1.7. Management Interface
2.2.1.8. Decrypt Port Mux Management Interface
2.2.1.9. Decrypt Port Demux Management Interface
2.2.1.10. Encrypt Port Mux Management Interface
2.2.1.11. Encrypt Port Demux Management Interface
2.2.1.12. Crypto IP Management Bus
2.2.1.13. Miscellaneous Control Signals
2.2.2.1. Common Port Mux Interface Waveform
2.2.2.2. Common Port Demux Interface Waveform
2.2.2.3. Controlled Port Mux Interface Waveform
2.2.2.4. Controlled Port Demux Interface Waveform
2.2.2.5. Uncontrolled Port RX Interface Waveform
2.2.2.6. Uncontrolled Port TX Interface Waveform
2.2.2.7. Crypto RX Waveform
2.2.2.8. Crypto TX Waveform
2.2.2.9. MACsec Management Interface (Read)
2.2.2.10. MACsec Management Interface (Write)
5.1.2. AXI-ST Multi Packet Mode
The AXI-ST Multi Packet Mode is supported only on controlled and common ports. Uncontrolled ports support single packet mode only.
The waveform below shows the example of a two segment Multi-Packet mode implementation. Since the NUM_OF_SEG = 2, the 16 byte wide data bus is divided by 2 and each segment data bus width is 8 byte. If the NUM_OF_SOP = 2, then in this example, a new packet can start on byte 0 of segment 0 or byte 0 of segment 1 (i.e. byte 1 of the data bus) or BOTH for the same data transfer phase. If the NUM_OF_SOP = 1, then a new packet can start on byte 0 of segment 0 or byte 0 of segment 1 (but NOT BOTH) for the same data transfer phase.
Figure 21. Multi-Packet Mode