MIPI D-PHY IP User Guide: Agilex™ 3 and Agilex™ 5 FPGAs

Download PDF
ID 817561
Date 6/30/2025
Public
Document Table of Contents
Document Table of Contents x
1. About the MIPI D-PHY IP 2. Configuring and Generating the MIPI D-PHY IP 3. MIPI D-PHY Interface Design Guidelines 4. Simulating the MIPI D-PHY IP 5. Validating the MIPI D-PHY IP 6. Debugging the MIPI-PHY IP 7. MIPI D-PHY Architecture 8. Interface Signals and Register Maps 9. Verification Test Plan 10. Document Revision History for the MIPI D-PHY IP User Guide
1. About the MIPI D-PHY IP x
1.1. MIPI D-PHY IP Features 1.2. Unsupported Features 1.3. MIPI D-PHY IP Release Information 1.4. MIPI D-PHY IP Block Diagram 1.5. Supported Data Lanes and Clock Lane Per Single HSIO Bank 1.6. MIPI D-PHY IP Design Flow
2. Configuring and Generating the MIPI D-PHY IP x
2.1. Creating a MIPI D-PHY Project 2.2. Generating a MIPI D-PHY IP 2.3. Generating the Design Example 2.4. MIPI D-PHY IP Parameters 2.5. Compiling the Design Example
2.3. Generating the Design Example x
2.3.1. Generating the Synthesizable MIPI D-PHY Design Example
2.3.1. Generating the Synthesizable MIPI D-PHY Design Example x
2.3.1.1. Design Example Block Diagram 2.3.1.2. External Interfaces
2.4. MIPI D-PHY IP Parameters x
2.4.1. MIPI D-PHY IP Configuration Parameters 2.4.2. MIPI D-PHY Link n Tab: RX Parameters 2.4.3. MIPI D-PHY Link n Tab: TX Parameters
3. MIPI D-PHY Interface Design Guidelines x
3.1. Identifying Pin Assignments Based on Byte Location 3.2. Assigning the RZQ pin and Dedicated Reference Clock Pin for MIPI D-PHY IP 3.3. Rules for the Remaining I/O Pin from Same Byte Location 3.4. I/O Bank Sharing 3.5. MIPI D-PHY Placement Rules 3.6. Handling MIPI D-PHY IP Reset
3.4. I/O Bank Sharing x
3.4.1. MIPI I/O Bank Sharing with External Memory Interface Protocol
4. Simulating the MIPI D-PHY IP x
4.1. Simulating the MIPI D-PHY IP Design Example with External Loopback Enabled
4.1. Simulating the MIPI D-PHY IP Design Example with External Loopback Enabled x
4.1.1. Simulation Design Example with External Loopback Enabled Block Diagram 4.1.2. Simulating MIPI D-PHY IP Design Example with Modelsim* and Questasim* 4.1.3. Simulating MIPI D-PHY IP Design Example with Synopsys VCSMX* and Xcelium*
5. Validating the MIPI D-PHY IP x
5.1. Adding Signal Tap Logic Analyzer to MIPI D-PHY IP Design Example 5.2. Testing the MIPI D-PHY Design Example
6. Debugging the MIPI-PHY IP x
6.1. Creating a Simplified Design that Demonstrates the Same Problem 6.2. Evaluating FPGA Timing Problems 6.3. Determining if the Problem Exists in Previous Quartus Prime Versions 6.4. Determining if the Problem Exists in the Current Version of Software 6.5. Verifying the MIPI D-PHY IP Using the Signal Tap Logic Analyzer 6.6. Varying the Voltage 6.7. Operating at Lower Speed 6.8. Trying a Different PCB
7. MIPI D-PHY Architecture x
7.1. MIPI D-PHY IP TX 7.2. MIPI D-PHY IP RX 7.3. Initialization and Reset Sequences 7.4. Calibration 7.5. CSR Clock Domain Crossing (CDC)
8. Interface Signals and Register Maps x
8.1. Interface Signals 8.2. Register Maps
8.1. Interface Signals x
8.1.1. General Interface Signals 8.1.2. AXI-Lite Interface 8.1.3. Core Register Bus 8.1.4. D-PHY RX PPI Interface Signals 8.1.5. D-PHY TX PPI Interface Signals 8.1.6. AXI-Lite CSR Access
8.2. Register Maps x
8.2.1. D-PHY IP Registers 8.2.2. D-PHY Traffic Generator (TG) Registers
8.2.1. D-PHY IP Registers x
8.2.1.1. IP_ID 8.2.1.2. IP_CAP 8.2.1.3. D0_CAP 8.2.1.4. DN_CAP 8.2.1.5. RX_CAP 8.2.1.6. TX_CAP 8.2.1.7. TX_PREAMBLE_LEN 8.2.1.8. D-PHY_CSR 8.2.1.9. TX_CLK_LANE_PS 8.2.1.10. RX_DLANE_ERR 8.2.1.11. SKEW_CAL_LEN_B0 8.2.1.12. SKEW_CAL_LEN_B1 8.2.1.13. SKEW_CAL_LEN_B2 8.2.1.14. SKEW_CAL_LEN_B3 8.2.1.15. ALT_CAL_LEN_B0 8.2.1.16. ALT_CAL_LEN_B1 8.2.1.17. ALT_CAL_LEN_B2 8.2.1.18. ALT_CAL_LEN_B3 8.2.1.19. CLK_CSR 8.2.1.20. CLK_STATUS 8.2.1.21. DLANE_CSR_0 8.2.1.22. DLANE_STATUS_0 8.2.1.23. RX_DLANE_DESKEW_DELAY_0 8.2.1.24. RX_DLANE_ERR_0 8.2.1.25. DLANE_CSR_1 8.2.1.26. DLANE_STATUS_1 8.2.1.27. RX_DLANE_DESKEW_DELAY_1 8.2.1.28. RX_DLANE_ERR_1 8.2.1.29. DLANE_CSR_2 8.2.1.30. DLANE_STATUS_2 8.2.1.31. RX_DLANE_DESKEW_DELAY_2 8.2.1.32. RX_DLANE_ERR_2 8.2.1.33. DLANE_CSR_3 8.2.1.34. DLANE_STATUS_3 8.2.1.35. RX_DLANE_DESKEW_DELAY_3 8.2.1.36. RX_DLANE_ERR_3 8.2.1.37. DLANE_CSR_4 8.2.1.38. DLANE_STATUS_4 8.2.1.39. RX_DLANE_DESKEW_DELAY_4 8.2.1.40. RX_DLANE_ERR_4 8.2.1.41. DLANE_CSR_5 8.2.1.42. DLANE_STATUS_5 8.2.1.43. RX_DLANE_DESKEW_DELAY_5 8.2.1.44. RX_DLANE_ERR_5 8.2.1.45. DLANE_CSR_6 8.2.1.46. DLANE_STATUS_6 8.2.1.47. RX_DLANE_DESKEW_DELAY_6 8.2.1.48. RX_DLANE_ERR_6 8.2.1.49. DLANE_CSR_7 8.2.1.50. DLANE_STATUS_7 8.2.1.51. RX_DLANE_DESKEW_DELAY_7 8.2.1.52. RX_DLANE_ERR_7 8.2.1.53. TX_LPX 8.2.1.54. TX_HS_EXIT 8.2.1.55. TX_LP_EXIT 8.2.1.56. TX_CLK_PREPARE 8.2.1.57. TX_CLK_ZERO 8.2.1.58. TX_CLK_POST 8.2.1.59. TX_CLK_PRE 8.2.1.60. TX_HS_PREPARE 8.2.1.61. TX_HS_ZERO 8.2.1.62. TX_HS_TRAIL 8.2.1.63. TX_INIT 8.2.1.64. TX_WAKE 8.2.1.65. RX_CLK_LOSS_DETECT 8.2.1.66. RX_CLK_SETTLE 8.2.1.67. RX_HS_SETTLE 8.2.1.68. RX_INIT 8.2.1.69. RX_CLK_POST 8.2.1.70. RX_CAL_REG_CTRL 8.2.1.71. RX_CAL_STATUS_D-PHY 8.2.1.72. RX_CAL_SKEW_W_START_MUX 8.2.1.73. RX_CAL_SKEW_W_END_MUX 8.2.1.74. RX_CAL_ALT_W_START_MUX 8.2.1.75. RX__CAL_ALT_W_END_MUX 8.2.1.76. RX_DESKEW_DELAY_MUX 8.2.1.77. RX_CAL_STATUS_LANE_MUX 8.2.1.78. PRBS_INIT_0 8.2.1.79. PRBS_INIT_1 8.2.1.80. PRBS_INIT_2 8.2.1.81. PRBS_INIT_3 8.2.1.82. PRBS_INIT_4 8.2.1.83. PRBS_INIT_5 8.2.1.84. PRBS_INIT_6 8.2.1.85. TX_TM_CONTROL 8.2.1.86. TX_MNL_IO_0 8.2.1.87. TX_MNL_D_LP_EN 8.2.1.88. RX_TM_CONTROL
8.2.2. D-PHY Traffic Generator (TG) Registers x
8.2.2.1. TG_TOP_CTRL_0 8.2.2.2. TG_TOP_CTRL_1 8.2.2.3. TG_TOP_DONE 8.2.2.4. TG_TOP_FAIL 8.2.2.5. TG_TOP_TEST_EN 8.2.2.6. TG_TOP_TEST_LINK 8.2.2.7. TARGET_TEST_CNT 8.2.2.8. TCHK_CONTROL 8.2.2.9. TCHK_LINK_STATUS 8.2.2.10. HS_DONE_LANES 8.2.2.11. TCHK_LINK_ERR_STATUS 8.2.2.12. LANE_ERROR_SOT_LANES 8.2.2.13. CAL_ERROR_LANES 8.2.2.14. HS_ERR_LANES 8.2.2.15. HS_TEST_CNT 8.2.2.16. LPDT_TEST_CNT 8.2.2.17. TRIGGER_TEST_CNT 8.2.2.18. ULPS_TEST_CNT 8.2.2.19. TG_RX_OVRD_DATA_PAT 8.2.2.20. TG_RX_BIT_ERROR_CNT 8.2.2.21. TG_RX_HS_TXFER_CNT 8.2.2.22. TG_LINK_CONTROL 8.2.2.23. TG_INIT_CNT 8.2.2.24. TG_HS_LEN 8.2.2.25. TG_LP_LEN 8.2.2.26. TG_SKEW_CAL 8.2.2.27. TG_ALT_CAL 8.2.2.28. TG_PER_SKEW_CAL_LEN 8.2.2.29. TG_TEST_CNT 8.2.2.30. TG_OVRD_DATA_PAT 8.2.2.31. TG_TX_HS_TXFER_CNT
9. Verification Test Plan x
9.1. MIPI D-PHY Tests
1. About the MIPI D-PHY IP
2. Configuring and Generating the MIPI D-PHY IP
3. MIPI D-PHY Interface Design Guidelines
4. Simulating the MIPI D-PHY IP
5. Validating the MIPI D-PHY IP
6. Debugging the MIPI-PHY IP
7. MIPI D-PHY Architecture
8. Interface Signals and Register Maps
9. Verification Test Plan
10. Document Revision History for the MIPI D-PHY IP User Guide

8.1.2. AXI-Lite Interface

The D-PHY IP allows AXI-Lite bus to access the CSR of the D-PHY.

Aside from allowing access to the D-PHY internal IP registers, the AXI-Lite bus is designed to allow access to external registers which is used for accessing the PPI TG. The following shows the AXI-Lite signal port and function. For details of the AXI-Lite internal memory map, refer to the tables in the AXI-Lite CSR Access topic.

Table 22.  AXI-Lite Interface Signals
Signal Direction Width Description
axil_clk Input 1 AXI-Lite clock.
srst_axil_n Input 1 AXI_lite synchronous reset.
axi_lite_awaddr Input 12 Write address.
axi_lite_awvalid Input 1 Write address valid. This signal indicates that the channel is signaling valid write address and control information.
axi_lite_awready Output 1 Write address ready. This signal indicates that the slave is ready to accept an address and associated control signals.
axi_lite_wdata Input 32 Write data.
axi_lite_wstrb Input 4 Write strobes. This signal indicates which byte lanes hold valid data. There is one write strobe bit for each eight bits of the write data bus.
axi_lite_wvalid Input 1 Write valid. This signal indicates that valid write data and strobes are available.
axi_lite_wready Output 1 Write ready. This signal indicates that the slave can accept the write data.
axi_lite_bresp Output 2 Write data.
axi_lite_bvalid Output 1 Write response valid. This signal indicates that the channel is signaling a valid write response.
axi_lite_bready Input 1 Response ready. This signal indicates that the master can accept a write response
axi_lite_araddr Input 12 Read address.
axi_lite_arvalid Input 1 Read address valid. This signal indicates that the channel is signaling valid read address and control information.
axi_lite_arready Output 1 Read address ready. This signal indicates that the slave is ready to accept an address and associated control signals.
axi_lite_rdata Output 32 Read data.
axi_lite_rresp Output 2 Read response. This signal indicates the status of the read transfer.
axi_lite_rvalid output 1 Read valid. This signal indicates that the channel is signaling the required read data.
axi_lite_rready Input 1 Read ready. This signal indicates that the master can accept the read data and response information.
axi_lite_arprot Input 3 Unused.
axi_lite_awprot Input 3 Unused.
Level Two Title