Visible to Intel only — GUID: jhm1653976610514
Ixiasoft
1. SDI II IP Core Quick Reference
2. SDI II IP Core Overview
3. SDI II IP Core Getting Started
4. SDI II IP Core Parameters
5. SDI II IP Core Functional Description
6. SDI II IP Core Signals
7. SDI II IP Core Design Considerations
8. SDI II IP Core Testbench and Design Examples
9. SDI II Intel® FPGA IP User Guide Archives
10. Document Revision History for the SDI II Intel® FPGA IP User Guide
5.3.1. Insert Line
5.3.2. Insert/Check CRC
5.3.3. Insert Payload ID
5.3.4. Match TRS
5.3.5. Scrambler
5.3.6. TX Sample
5.3.7. Clock Enable Generator
5.3.8. RX Sample
5.3.9. Detect Video Standard
5.3.10. Detect 1 and 1/1.001 Rates
5.3.11. Transceiver Controller
5.3.12. Descrambler
5.3.13. TRS Aligner
5.3.14. 3Gb Demux
5.3.15. Extract Line
5.3.16. Extract Payload ID
5.3.17. Detect Format
5.3.18. Sync Streams
5.3.19. Convert SD Bits
5.3.20. Insert Sync Bits
5.3.21. Remove Sync Bits
5.4.1. HD-SDI Dual Link to 3G-SDI (Level B) Conversion
5.4.2. 3G-SDI (Level B) to HD-SDI Dual Link Conversion
5.4.3. SMPTE RP168 Switching Support
5.4.4. SD 20-Bit Interface for Dual/Triple Rate
5.4.5. Dynamic TX Clock Switching for Arria V, Cyclone V, and Stratix V Devices
5.4.6. Intel FPGA Video Streaming Interface
7.1.2.1. Changing RX CDR Reference Clock in Transceiver Native PHY IP Core
7.1.2.2. Merging Simplex Mode Transceiver in the Same Channel
7.1.2.3. Using Generated Reconfiguration Management for Triple and Multi Rates
7.1.2.4. Ensuring Independent RX and TX Operations in the Same Channel
7.1.2.5. Potential Routing Problem During Fitter Stage in Intel® Arria® 10 and Intel® Cyclone® 10 GX Devices
7.1.2.6. Unconstrained Clocks in SDI Multi-Rate RX Using Intel® Arria® 10 and Intel® Cyclone® 10 GX Devices
7.1.2.7. Unused Transceiver Channels
7.1.2.8. Routing Transceiver Reference Clock Pins to Core Logic in Intel® Stratix® 10 Devices
Visible to Intel only — GUID: jhm1653976610514
Ixiasoft
6.6. Receiver Streaming Video and Control Signals
Signal | Width | Clock Domain | Direction | Description |
---|---|---|---|---|
rx_axi4s_vid_out_tdata | P | tx_axi4s_clk | Output | AXI4-S data out. |
rx_axi4s_vid_out_tvalid | 1 | tx_axi4s_clk | Output | AXI4-S data valid. |
rx_axi4s_vid_out_tready | 1 | tx_axi4s_clk | Input | AXI4-S data ready. |
rx_axi4s_vid_out_tlast | 1 | tx_axi4s_clk | Output | AXI4-S end of packet. |
rx_axi4s_vid_out_tuser | Q | tx_axi4s_clk | Output | AXI4-S tuser. tuser[0] indicates start of video frame when asserted. tuser[1] indicates the start of a non-video packet or metapacket when asserted. |
Note:
- P = max (16, floor[((bits per color sample x number of color planes) + 7) / 8] x pixels in parallel x 8) where bits per color sample = 10 or 12, number of color planes = 3 and pixels in parallel = 2.
-
Q = ceil (tdata width / 8)
Signal | Width | Clock Domain | Direction | Description |
---|---|---|---|---|
rx_av_mm_control_address | 9 | mgmt_clk | Input | Avalon memory-mapped control address. |
rx_av_mm_control_write | 1 | mgmt_clk | Input | Avalon memory-mapped control write. |
rx_av_mm_control_byteenable | 4 | mgmt_clk | Input | Avalon memory-mapped byte enable. |
rx_av_mm_control_writedata | 32 | mgmt_clk | Input | Avalon memory-mapped write data. |
rx_av_mm_control_read | 1 | mgmt_clk | Input | Avalon memory-mapped read. |
rx_av_mm_control_readdata | 32 | mgmt_clk | Output | Avalon memory-mapped read data. |
rx_av_mm_control_readdatavalid | 1 | mgmt_clk | Output | Avalon memory-mapped read data valid. |
rx_av_mm_control_waitrequest | 1 | mgmt_clk | Output | Avalon memory-mapped wait request. |