Visible to Intel only — GUID: ait1505116426095
Ixiasoft
1. About the Video and Image Processing Suite
2. Avalon Streaming Video
3. Clocked Video
4. VIP Run-Time Control
5. Getting Started
6. VIP Connectivity Interfacing
7. Clocked Video Interface IPs
8. 2D FIR II IP Core
9. Mixer II IP Core
10. Clipper II IP Core
11. Color Plane Sequencer II IP Core
12. Color Space Converter II IP Core
13. Chroma Resampler II IP Core
14. Control Synchronizer IP Core
15. Deinterlacer II IP Core
16. Frame Buffer II IP Core
17. Gamma Corrector II IP Core
18. Configurable Guard Bands IP Core
19. Interlacer II IP Core
20. Scaler II IP Core
21. Switch II IP Core
22. Test Pattern Generator II IP Core
23. Trace System IP Core
24. Warp Lite Intel FPGA IP
25. Avalon-ST Video Stream Cleaner IP Core
26. Avalon-ST Video Monitor IP Core
27. VIP IP Core Software Control
28. Security Considerations
29. Video and Image Processing Suite User Guide Archives
30. Document Revision History for the Video and Image Processing Suite User Guide
A. Avalon-ST Video Verification IP Suite
7.1. Supported Features for Clocked Video Output II IP
7.2. Control Port
7.3. Clocked Video Input IP Format Detection
7.4. Clocked Video Output IP Video Modes
7.5. Clocked Video Output II Latency Mode
7.6. Generator Lock
7.7. Underflow and Overflow
7.8. Timing Constraints
7.9. Handling Ancillary Packets
7.10. Modules for Clocked Video Input II IP Core
7.11. Clocked Video Input II Signals, Parameters, and Registers
7.12. Clocked Video Output II Signals, Parameters, and Registers
15.1. Deinterlacing Algorithm Options
15.2. Deinterlacing Algorithms
15.3. Run-time Control
15.4. Pass-Through Mode for Progressive Frames
15.5. Cadence Detection (Motion Adaptive Deinterlacing Only)
15.6. Avalon-MM Interface to Memory
15.7. Motion Adaptive Mode Bandwidth Requirements
15.8. Avalon-ST Video Support
15.9. 4K Video Passthrough Support
15.10. Behavior When Unexpected Fields are Received
15.11. Handling of Avalon-ST Video Control Packets
15.12. Deinterlacer II Parameter Settings
15.13. Deinterlacing Control Registers
A.3.1. c_av_st_video_control
A.3.2. c_av_st_video_data
A.3.3. c_av_st_video_file_io
A.3.4. c_av_st_video_item
A.3.5. c_av_st_video_source_sink_base
A.3.6. c_av_st_video_sink_bfm_’SINK
A.3.7. c_av_st_video_source_bfm_’SOURCE
A.3.8. c_av_st_video_user_packet
A.3.9. c_pixel
A.3.10. av_mm_transaction
A.3.11. av_mm_master_bfm_`MASTER_NAME
A.3.12. av_mm_slave_bfm_`SLAVE_NAME
A.3.13. av_mm_control_register
A.3.14. av_mm_control_base
Visible to Intel only — GUID: ait1505116426095
Ixiasoft
A.2.5.2. nios_control_model.sv
The register items mailboxes defined in the BFM drivers file are used in the testbench/nios_control_model.sv by creating a new control register object, setting the address and data as required, and passing it to the mailbox, as shown in the send_write_to_mixer task code:
task send_write_to_mixer(int unsigned address, int unsigned data); automatic c_av_mm_control_register register_update = new(1); register_update.use_event = 0; register_update.write = 1; register_update.address = address; register_update.value = data; m_register_items_for_mixer_control_bfm.put(register_update); endtask
The nios_control_model.sv code contains the writes to the Mixer II and Video Frame Buffer II IP cores, as required by both the example constrained random and video files tests:
`ifdef CONSTRAINED_RANDOM_TEST send_write_to_mixer(8, 0); // X offset repeat (10) @ (posedge (av_st_clk)); $display("%t NIOS CONTROL EMULATOR : Test harness writing 0 to the X offset of the Mixer",$time); send_write_to_mixer(9, 0); // Y offset repeat (10) @ (posedge (av_st_clk)); $display("%t NIOS CONTROL EMULATOR : Test harness writing 0 to the Y offset of the Mixer",$time); send_write_to_mixer(3, `MIXER_BACKGROUND_WIDTH_SW); repeat (10) @ (posedge (av_st_clk)); $display("%t NIOS CONTROL EMULATOR : Test harness writing a background layer of width %0d to the Mixer",$time,`MIXER_BACKGROUND_WIDTH_SW); send_write_to_mixer(4, `MIXER_BACKGROUND_HEIGHT_SW); repeat (10) @ (posedge (av_st_clk)); $display("%t NIOS CONTROL EMULATOR : Test harness writing a background layer of height %0d to the Mixer",$time,`MIXER_BACKGROUND_HEIGHT_SW); `else send_write_to_mixer(8, 20); // X offset repeat (10) @ (posedge (av_st_clk)); $display("%t NIOS CONTROL EMULATOR : Test harness writing 20 to the X offset of the Mixer",$time); send_write_to_mixer(9, 20); // Y offset repeat (10) @ (posedge (av_st_clk)); $display("%t NIOS CONTROL EMULATOR : Test harness writing 20 to the Y offset of the Mixer",$time); `endif
The control interfaces for each VIP core in the DUT has their own BFM driver and associated mailbox.
To port these tasks and test register accesses to C code for a Nios 2 processor to run on real hardware, you need to factor in the base addresses for each VIP IP core in the DUT.