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
23.3.3. TCL Shell Commands
You can control the Trace System IP core components from the TCL scripting interface using trace service.
Command | Arguments | Function |
---|---|---|
get_service_paths | trace |
Returns the System Console names for all the Trace System IP core components which are currently visible. |
claim_service | trace <service_path> <library_name> |
Opens a connection to the specified trace service so it can be used. Returns a new path to the opened service. |
close_service | trace <open_service> |
Closes the service so that its resources can be reused. |
trace_get_monitors | <open_service> | Returns a list of monitor IDs—one for each monitor that is available on this trace system. |
trace_get_monitor_info | <open_service> <monitor_id> |
Returns a serialized array containing information about the specified monitor. You can use the array set command to convert this into a TCL array. |
trace_read_monitor | <open_service> <monitor_id> <index> |
Reads a 32-bit value from configuration space within the specified monitor. |
trace_write_monitor | <open_service> <monitor_id> <index> <value> |
Writes a 32-bit value from configuration space within the specified monitor. |
trace_get_max_db_size | <open_service> |
Gets the maximum (in memory) trace database size set for this trace system. If the trace database size exceeds this value, then the oldest values are discarded. |
trace_set_max_db_size | <open_service> <size> |
Returns the current maximum trace database size. Trace database sizes are approximate but can be used to prevent a high data rate monitor from using up all available memory. |
trace_start | <open_service> fifo |
Starts capturing with the specified trace system in real time (FIFO) mode. |
trace_stop | <open_service> |
Stops capturing with the specified trace system. |
trace_get_status | <open_service> |
Returns the current status (idle or running) of the trace system. In future, new status values may be added. |
trace_get_db_size | <open_service> |
Returns the approximate size of the database for the specified trace system. |
trace_save | <open_service> <filename> |
Saves the trace database to disk. |
trace_load | <filename> |
Loads a trace database from disk. This returns a new service path, which can be viewed as if it is a trace system. However, at this point, the start, stop and other commands will obviously not work on a file-based node. If you load a new trace database with the trace_load command, the trace user interface becomes visible if it was previously hidden. |