Visible to Intel only — GUID: nik1411442168856
Ixiasoft
2.1. Installation and Licensing
2.2. Generating CPRI Intel® FPGA IP Core
2.3. CPRI Intel® FPGA IP File Structure
2.4. CPRI Intel® FPGA IP Core Parameters
2.5. Integrating Your Intel® FPGA IP Core in Your Design: Required External Blocks
2.6. Simulating Intel FPGA IP Cores
2.7. Understanding the Testbench
2.8. Running the Design Example
2.9. Compiling the Full Design and Programming the FPGA
2.5.1. Adding the Transceiver TX PLL IP Core
2.5.2. Adding the Reset Controller
2.5.3. Adding the Transceiver Reconfiguration Controller
2.5.4. Adding the Off-Chip Clean-Up PLL
2.5.5. Adding and Connecting the Single-Trip Delay Calibration Blocks
2.5.6. Transceiver PLL Calibration
2.5.7. Reference and System PLL Clock for your IP Design
3.1. Interfaces Overview
3.2. CPRI Intel® FPGA IP Core Clocking Structure
3.3. CPRI Intel® FPGA IP Core Reset Requirements
3.4. Start-Up Sequence Following Reset
3.5. AUX Interface
3.6. Direct IQ Interface
3.7. Ctrl_AxC Interface
3.8. Direct Vendor Specific Access Interface
3.9. Real-Time Vendor Specific Interface
3.10. Direct HDLC Serial Interface
3.11. Direct L1 Control and Status Interface
3.12. L1 Debug Interface
3.13. Media Independent Interface (MII) to External Ethernet Block
3.14. Gigabit Media Independent Interface (GMII) to External Ethernet Block
3.15. CPU Interface to CPRI Intel® FPGA IP Registers
3.16. Auto-Rate Negotiation
3.17. Extended Delay Measurement
3.18. Deterministic Latency and Delay Measurement and Calibration
3.19. CPRI Intel® FPGA IP Transceiver and Transceiver Management Interfaces
3.20. Testing Features
3.19.1. CPRI Link
3.19.2. Main Transceiver Clock and Reset Signals
3.19.3. Arria V, Arria V GZ, Cyclone V, and Stratix V Transceiver Reconfiguration Interface
3.19.4. Intel® Arria® 10, Intel® Stratix® 10, and Intel® Agilex™ Transceiver Reconfiguration Interface
3.19.5. RS-FEC Interface
3.19.6. Interface to the External Reset Controller
3.19.7. Interface to the External PLL
3.19.8. Transceiver Debug Interface
5.1. INTR Register
5.2. L1_STATUS Register
5.3. L1_CONFIG Register
5.4. BIT_RATE_CONFIG Register
5.5. PROT_VER Register
5.6. TX_SCR Register
5.7. RX_SCR Register
5.8. CM_CONFIG Register
5.9. CM_STATUS Register
5.10. START_UP_SEQ Register
5.11. START_UP_TIMER Register
5.12. FLSAR Register
5.13. CTRL_INDEX Register
5.14. TX_CTRL Register
5.15. RX_CTRL Register
5.16. RX_ERR Register
5.17. RX_BFN Register
5.18. LOOPBACK Register
5.19. TX_DELAY Register
5.20. RX_DELAY Register
5.21. TX_EX_DELAY Register
5.22. RX_EX_DELAY Register
5.23. ROUND_TRIP_DELAY Register
5.24. XCVR_BITSLIP Register
5.25. DELAY_CAL_STD_CTRL1 Register
5.26. DELAY_CAL_STD_CTRL2 Register
5.27. DELAY_CAL_STD_CTRL3 Register
5.28. DELAY_CAL_STD_CTRL4 Register
5.29. DELAY_CAL_STD_CTRL5 Register
5.30. DELAY_CAL_STD_STATUS Register
5.31. DELAY_CAL_RTD Register
5.32. XCVR_TX_FIFO_DELAY Register
5.33. XCVR_RX_FIFO_DELAY Register
5.34. IP_INFO Register
5.35. DEBUG_STATUS Register
Visible to Intel only — GUID: nik1411442168856
Ixiasoft
3.10. Direct HDLC Serial Interface
If you turn on Enable direct HDLC serial interface in the CPRI parameter editor, the direct HDLC serial interface is available. This interface allows direct access to the slow control and management data in the CPRI frame. You can connect this interface to a user-defined HDLC PCS and MAC.
This interface is Avalon-ST compliant with a ready latency value of 1.
You can alter the transmit write latency with the Auxiliary and direct interfaces write latency cycle(s) parameter. However, you do not need to view the aux_tx_seq signal for correct alignment. You can monitor the hdlc_rx_valid and hdlc_tx_ready signals to discover the correct times to read and write data on this interface.
Direct HDLC Serial RX Interface | ||
---|---|---|
Signal Name |
Direction |
Description |
hdlc_rx_valid | Output | When asserted, indicates hdlc_rx_data holds a valid HDLC bit in the current clock cycle. |
hdlc_rx_data | Output | HDLC data stream received from the CPRI frame. The hdlc_rx_valid signal indicates which bits are valid HDLC bytes. |
Direct HDLC Serial TX Interface | ||
Signal Name |
Direction |
Description |
hdlc_tx_ready | Output | When asserted, indicates the IP core is ready to receive HDLC data from hdlc_tx_data on the next clock cycle. |
hdlc_tx_valid | Input | Write valid for hdlc_tx_data. Assert this signal to indicate that hdlc_tx_data holds a valid HDLC bit in the current clock cycle. |
hdlc_tx_data | Input | HDLC data stream to be written to the CPRI frame directly. The IP core writes the current value on hdlc_tx_data to the CPRI frame based on the hdlc_tx_ready signal from the previous cycle, and the hdlc_tx_valid signal in the current cycle. |
Figure 43. Direct HDLC Serial RX Timing DiagramHDLC Serial RX interface behavior in a CPRI IP core running at 0.6144 Gbps.
Figure 44. Direct HDLC Serial TX Timing DiagramExpected behavior on the HDLC Serial TX interface of a CPRI IP core running at 0.6144 Gbps.
Related Information