Visible to Intel only — GUID: nik1411442166701
Ixiasoft
Visible to Intel only — GUID: nik1411442166701
Ixiasoft
3.9. Real-Time Vendor Specific Interface
This option is only available if you specify a CPRI line bit rate of 10.1376 Gbps for your IP core.
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.
Real-Time Vendor Specific RX Interface | ||
---|---|---|
Signal Name |
Direction |
Description |
rtvsN_rx_valid[C:0] | Output | Each asserted bit indicates the corresponding 32-bit data on the current rtvs_rx_data bus is a valid real-time vendor-specific bytes. |
rtvsN_rx_data[D:0] | Output | Real-time vendor-specific word received from the CPRI frame. |
Real-Time Vendor Specific TX Interface | ||
Signal Name |
Direction |
Description |
rtvsN_tx_ready[C:0] | Output | Each asserted bit indicates corresponding 32-bit real-time vendor specific bytes on rtvs_tx_data is ready to be read on the next clock cycle |
rtvsN_tx_valid[C:0] | Input | Write valid for rtvs_tx_data. Assertion of each bit indicates corresponding 32-bit data of rtvs_tx_data holds a valid value in the current clock cycle. |
rtvsN_tx_data[D:0] | Input | Real-time vendor-specific word to be written to the CPRI frame. The IP core writes the current value of the rtvs_tx_data bus to the CPRI frame based on the rtvs_tx_ready signal from the previous cycle, and the rtvs_tx_valid signal in the current cycle. |
The aux_rx_x and aux_rx_seq signals are not part of this interface and are available only if you turn on the AUX interface in your CPRI IP core variation. However, their presence in the timing diagram explains the timing of the rtvs_rx_valid output signal that you use to identify the clock cycles with valid RTVS data.
The aux_tx_x and aux_tx_seq signals are not part of this interface and are available only if you turn on the AUX interface in your CPRI IP core variation. However, their presence in the timing diagram explains the timing of the rtvs_tx_ready output signal that you use to identify the clock cycles when you can write RTVS data to the CPRI frame.
Note that the write latency is one cpri_clkout clock cycle in this example.