LVDS Tunneling Protocol and Interface (LTPI) IP User Guide: Agilex™ 3 and Agilex™ 5 FPGAs and SoCs
ID
844310
Date
8/15/2025
Public
1. Overview
2. Configuring and Generating the IP
3. Simulating the IP
4. Validating the IP
5. Troubleshooting and Debugging Issues
6. Appendix A: Functional Description
7. Appendix B: Registers
8. Document Revision History for the LVDS Tunneling Protocol and Interface (LTPI) IP User Guide: Agilex™ 3 and Agilex™ 5 FPGAs and SoCs
1.4.4.1. Link Detect and Link Speed Selection Frames
1.4.4.2. Link Detect Frame
1.4.4.3. Link Speed Frame
1.4.4.4. Advertise, Configure, and Accept Frames
1.4.4.5. Advertise Frames
1.4.4.6. Configure Frame
1.4.4.7. Accept Frame
1.4.4.8. LTPI Operational Frames
1.4.4.9. Default I/O Frame
1.4.4.10. Default Data Frame
4.1.2.3. Running the Hardware Test
- In the Quartus® Prime Pro Edition software, select Tools > System Debugging Tools > System Console or enter the following command in a terminal to launch the system console:
system-console &
- In the Tcl Console panel, type the following command to navigate to the hardware test directory:
cd <design_example>/ltpi_0_example_design/hwtest/
- Load the main Tcl script by running the following command:
source main.tcl
- Start the hardware test by running one of the following commands:
Table 47. Hardware Test Commands Test Command All protocol tests run_hwtest
Individual protocol tests GPIO gpio_hw_test
OEM oem_hw_test
UART uart_hw_test
I2C i2c_hw_test
Data Channel dc_hw_test
Note:- The JTAG index for data channel is 2 by default. To change the JTAG index, parse the correct index on set_jtag $index in the procedure dc_hw_test in main.tcl.
- The JTAG index for LTPI CSR is 0 for controller and 1 for target by default. Set the index accordingly for respective CSR access.
set_jtag $index
- Access the CSR space using the following commands after setting the JTAG index:
- For read:
reg_read $base_address $offset
- For write:
reg_write $base_address $offset $write_data
For example: To access LTPI CSR of controller, type the following commands:set_jtag 0
reg_read 0x200 0x80 (read)
reg_write 0x200 0x80 0x1 (write)
- For read:
The following figure illustrates a sample output of a successful hardware test run for one complete test.
Figure 29. Hardware Result Output