LTPI

Features：
– Supports LTPI (LVDS Tunneling Protocol & Interface) as defined in OCP DC-SCM 2.0, including SDR and DDR transfer modes
– Analyzes LTPI links up to 1.2Gbps
– Real-time frame decode: comma (K28.5 / K28.6 / K28.7) alignment, frame type / subtype classification, CRC-8 check with error marking
– Frame Report lists Tx / Rx frames with full field decode in table form
– Tunneled Report reconstructs the channel contents: complete I2C transactions (Start / address / R/W / ACK / data / Stop), GPIO bit changes and UART bytes, with Combined / Separate view modes
– Statistics by Tx / Rx / Error with click-to-jump to the corresponding frame
– Waveform view shows the four LTPI channels together with the decoded result
– LTPI trigger: CRC error, symbol error or disparity error, or a Tx / Rx data pattern up to 16 bytes; the comma character is selectable on the settings page
– OEM / Vendor custom fields via AqLTPI_Vendor.csv (field name, bit range, enumerations, engineering-unit scaling)

Description：
BusFinder with LTPI Solution ( Way station and other components). Supports LTPI links up to 1.2Gbps

Analysis Functions

Frame Report
Lists Tx / Rx frames in time order with frame type, subtype, CRC check result and full field decode; clicking a row shows the 16 raw bytes and a field-by-field breakdown in the detail pane.

Tunneled Report
Reconstructs the tunneled channels: complete I2C transactions on channels 0–5 (Start / address / R/W / ACK / data / Stop), GPIO bit changes (both low-latency LL and normal-latency NL classes), and UART byte reconstruction on channels 0–1 including RTS / CTS flow-control events; offers Combined (merged with the Frame Report) and Separate views.

Statistics
Accumulates frame counts by Tx / Rx / Error with per-type and per-subtype breakdown; errors are further classified as CRC, Symbol, Disparity and Incomplete; clicking an entry jumps to the corresponding frame.

OEM / Vendor Custom Fields
Reserved or vendor-specific fields can be described in AqLTPI_Vendor.csv — field name, bit range, enumerations and engineering-unit scaling — and the decoder presents them directly as custom fields, making proprietary protocol contents easy to analyze.