Visible to Intel only — GUID: pdo1554100869699
Ixiasoft
1.1. Features
1.2. Hardware and Software Requirements
1.3. Design System Architecture Overview
1.4. Dynamic Reconfiguration Overview
1.5. PHY Lite Per-Bit Overview
1.6. Compiling the Reference Design
1.7. Hardware Testing
1.8. Document Revision History for AN 887: PHY Lite for Parallel Interfaces Reference Design with Dynamic Reconfiguration for Intel® Arria® 10 Devices
1.9. Appendix A: HiLo Loopback Card Pin Connections
1.10. Appendix B: Retrieving Lane and Pin Information
1.11. Appendix C: Decoding Parameter Table
Visible to Intel only — GUID: pdo1554100869699
Ixiasoft
1.11. Appendix C: Decoding Parameter Table
Figure 27. Parameter Table Example for Intel® Arria® 10 Devices
Notes to Figure 27:
- To access the parameter table = 24’hE000
- To determine the size of the parameter table, generate an address. For example:
addr = 24’hE000 + 24’h14 value at addr = 0xA4
The size of parameter table is AC, which means that information about the PHY Lite for Parallel Interfaces IP cores are spread from address 27’hE000 to 27’hE0A4.
- To determine the address offset of the PHY Lite for Parallel Interfaces IP cores in the parameter table.
- There are two PHY Lite for Parallel Interfaces IP cores in the parameter table at address offset. For example:
27’hE018 = 84000044 27’hE01C = 85000074
where 0x44 address offset points to PHY Lite for Parallel Interfaces IP core 1 and 0x74 address offset points to PHY Lite for Parallel Interfaces IP core 2.
- 4 and 5 (marked in yellow box) are the PHY Lite for Parallel Interfaces IP core interface IDs.
- There are two PHY Lite for Parallel Interfaces IP cores in the parameter table at address offset. For example:
- To determine the number of groups in the first PHY Lite for Parallel Interfaces IP core interface:
24’hE048 = 00000002
The underlined number indicates that there is only two groups.
- To determine the group information (for example, the number of lanes and pins in a PHY Lite for Parallel Interfaces IP core interface per group):
where
24’hE04C = 00000606
- num_lanes[7:6],num_pins[5:0] means lanes = 1 and pins = 6 of Group 0.
- and num_lanes[7:6],num_pins[5:0] means lanes = 1 and pins = 6 of Group 1.
- To determine the lane and pin address offsets of each group:
where lane_off[31:16],pin_off[15:0] means
24’hE054 = 00590068
- lane off = 0x58 and pin off = 0x5C of Group 0.
- lane off = 0x59 and pin off = 0x68 of Group 1.
- To determine the lane address of each group:
where
24’hE058 = 00003930
- Lane address of Group 0 = 0x30
- Lane address of Group 1 = 0x39
- To determine the pin address at 24’hE05C to 24’hE064 for Group 0:
where
24’hE05C = 30E530E4 (for Group 0)
- DQS_P = Pin 4; DQS_N = Pin 5
- DQ[0] = Pin 6; DQ[1] = Pin 7
- DQ[2] = Pin 0; DQ[3] = Pin 1
where24’hE068 = 39E539E4 (for Group 1)
- DQS_P = Pin 4; DQS_N = Pin 5
- DQ[4] = Pin 9; DQ[5] = Pin 6
- DQ[6] = Pin 3; DQ[7] = Pin 8
Note: {lane_addr[7:0],0xE,pin[3:0]} for strobe and {lane_addr[7:0],0xF,pin[3:0]} for data.