Content provided in the HeadStart lounge is for Xilinx HeadStart customers.
If you have any questions, please contact ea_kits@xilinx.com
ZIP file. Do not refer this Wiki page for building and running the VCU TRD.
{under.jpg}
1 Revision History
This wiki page complements the 2017.3 version of the VCU TRD.
Change Log:
Updated all projects, IPs, and tools versions to 2017.3
New MIPI CSI-2 Rx capture pipeline
New HDMI Tx display pipeline
New configurable demo mode (GUI)
Support 4k60 (except for DP Tx)
Various fixes and clean-up
2 Overview
The primary goal of this targeted reference design (TRD) is to demonstrate the capabilities of video codec unit (VCU) hard block present in Zynq UltraScale+ MPSoC EV devices. The TRD serves as a platform to tune the performance parameters of VCU and arrives at an optimal configuration for encoder and decoder blocks. The TRD uses Vivado IP Integrator (IPI) flow for building the hardware design and Xilinx Yocto PetaLinux flow for software design. It uses Xilinx IPs and software drivers to demonstrate the capabilities of different components.
The design supports the following video interfaces:
Sources:
Test pattern generator (TPG) implemented in the PL
HDMI Rx capture pipeline implemented in the PL
MIPI CSI-2 Rx capture pipeline implemented in the PL
File source (SD card, USB storage, SATA hard disk)
Sinks:
DP Tx display pipeline in the PS
HDMI Tx display pipeline implemented in the PL
This wiki contains information about:
How to setup the ZCU106 evaluation board and run the reference design.
How to build all the TRD components based on the provided source files via detailed step-by-step tutorials.
Additional material that is not hosted on the wiki:
Zynq UltraScale+ MPSoC VCU TRD user guide, UG1250: The UG provides the list of features, software architecture and hardware architecture.
3 Software Tools and System Requirements
3.1 Hardware
Required:
ZCU106 evaluation board (rev B or newer) with power cable
Monitor with DisplayPort/HDMI input supporting 3840x2160 resolution
Display Port cable (DP certified)
HDMI cable
Class-10 SD card
GooBang Doo ABOX 2017 player with resolution set to 4KP30, color space to VUY24 and HDMI cable
NVIDIA SHIELD Pro
USB mouse
Optional:
USB pen drive formatted with FAT32 file system and hub
SATA drive formatted with FAT32 file system , external power supply and data cable
Ethernet cable
LI-IMX274MIPI-FMC image sensor daughter card
3.2 Software
Required:
Linux host machine for all tool flow tutorials (see UG1144 for detailed OS requirements)
PetaLinux Tools version 2017.3 (see UG1144 for installation instructions)
Git distributed version control system
Silicon Labs quad CP210x USB-to-UART bridge driver
Serial terminal emulator e.g. teraterm
Reference Design Zip File
ZCU106 rev B or newer: including all source code and project files.
3.3 Download, Installation and Licensing
The Vivado Design Suite User Guide explains how to download and install the Vivado® Design Suite tools, which includes the Vivado Integrated Design Environment (IDE), High Level Synthesis tool, and
System Generator for DSP. This guide also provides the information about licensing and administering evaluation and full copies of Xilinx design tools and intellectual property (IP) products. The Vivado Design Suite can be downloaded from here.
LogiCORE IP Licensing
The following IP cores require a license to build the design.
Video Test Pattern Generator (TPG) - Free License but must be downloaded
Video Timing controller (VTC) - Free License but must be downloaded
Video Mixer- Purchase license (Hardware evaluation available)
Video PHY Controller - Free License but must be downloaded
HDMI-Rx/Tx Subsystem - Purchase license (Hardware evaluation available)
Video Processing Subsystem (VPSS) - Purchase license (Hardware evaluation available)
MIPI CSI Controller Subsystems (mipi_csi2_rx_subsystem)- Purchase license (Hardware evaluation available)
To obtain the LogiCORE IP license, please visit the respective IP product page and get the license.
AR# 44029 - Licensing - LogiCORE IP Core licensing questions?
Xilinx Licensing FAQ
LogiCORE IP Project License Terms
3.4 Compatibilitycompat
The reference design has been tested successfully with the following user-supplied components.
DisplayPort Monitor:
Make/Model
Native Resolution
Viewsonic VX2475SMHL-4K (VS16024)
3840x2160 (30Hz)
LG 27MU67-B
3840x2160 (30Hz)
HDMI Monitor:
Make/Model
Resolutions
LG 27UD88
3840x2160 (30Hz)
Philips BDM4350UC
3840 x 2160 @ 60Hz
DisplayPort Cable:
Cable Matters DisplayPort Cable-E342987
Monster Advanced DisplayPort Cable-E194698
HDMI 2.0 compatible cable
4 Design Files
The top-level directory structure shows the the major design components organized by execution unit (APU). A pre-built SD card image is provide along with a basic README and legal notice file.
rdf0428-zcu106-vcu-trd-2017-3
├── apu
│ ├── vcu_apm_lib
│ ├── vcu_gst_lib
│ ├── vcu_petalinux_bsp
│ ├── vcu_qt
│ └── vcu_video_lib
├── images
│ ├── rev-b
│ └── rev-c
├── IMPORTANT_NOTICE_CONCERNING_THIRD_PARTY_CONTENT
├── README
├── pl
│ ├── board_files
│ ├── constrs
│ ├── scripts
│ └── srcs
Note:
Rev-c design files can be used for rev-d board.
5 Tutorials
5.1 Board Setupboard_setup
Figure below shows the ZCU106 board with interfaces highlighted.
{vcu_trd_17p3_board.png}
Setting up the ZCU106 Board
Connect the Micro USB cable into the ZCU106 Board Micro USB port J83, and the other end into an open USB port on the host PC. This cable is used for UART over USB communication.
Insert the SD card with the images copied into the SD card slot J100.
Set the SW6 switches as shown in the below Figure. This configures the boot settings to boot from SD.
Connect 12V Power to the ZCU106 6-Pin Molex connector. {vcu_trd_17p3_fig2.png}
Connect one end of Display Port (DP) cable to board’s U129 connector and the other end to DP port of 4K monitor.
Connect one end of HDMI cable to board’s P7 stacked HDMI connector (lower port) and another end to HDMI source.
Connect one end of HDMI cable to board’s P7 stacked HDMI connector (upper port) and another end to HDMI monitor.
For USB storage device, connect USB hub along with the mouse. (Optional)
For SATA storage device, connect SATA data cable to SATA 3.0 port. (Optional).
For MIPI CSI-2, Insert the LI-IMX274MIPI-FMC image sensor daughter card into the FMC0 connector and set VADJ to 1.8V (See FMC VADJ Voltage Settings).
Set up a terminal session between a PC COM port and the serial port on the evaluation board (See the below section for more details).
Switch ON SW1 to power the ZCU106 board.
Figure below shows the ZCU106 board connections.
{vcu_trd_17p3_fig24.jpg}
It takes about a minute for Linux to boot. User may miss the boot sequence while the terminal session is being configured.
FMC VADJ Voltage Settings
VADJ voltage needs to be set to 1.8V for LI-IMX274MIPI-FMC image sensor daughter card. Refer to AR# 67308 for setting VADJ to 1.8V.
Determine which COM to use to access the USB serial port on the ZCU106 board.
Make sure that the ZCU106 board is powered on and the serial UART device USB cable is in place. This ensures that the USB-to-serial bridge is enumerated by the PC host. Open your computer's Control Panel by clicking on Start > Control Panel. Note that the Start button is typically located in the lower left corner of the screen. Occasionally, it is in the upper left corner.
Click Device Manager to open the Device Manager window. Note: You may be asked to confirm opening the Device Manager. If so, click YES.
Expand Ports (COM & LPT).
Locate the Silicon Labs Quad CP210x USB to UART Bridge: Interface 0 (COM#).
Note down the COM Port number for further steps. {vcu_trd_17p3_fig4.png}
Close the Device Manager by clicking the red X in the upper right corner of the window.
Launch any Terminal application like Tera term to view the serial messages
Launch Tera Term and open the COM port that is associated to Silicon Labs Quad CP210x USB to UART Bridge: Interface 0 of the USB-to-serial bridge.
Set the COM port to 115200 Baud rate, 8, none, 1 –Set COM port.
Power ON the board which has SD card. It boots Linux on board.
5.2 Build Flowtutorials
The following tutorials assume that the $TRD_HOME environment variable has been set as below.
% export TRD_HOME=</path/to/downloaded/zip-file>/rdf0428-zcu106-vcu-trd-2017-3
NOTE: It is recommended to follow the build steps in sequence.
5.2.1 Hardware Design
Refer to the Vivado Design Suite User Guide UG973 (v2017.3) for setting up Vivado 2017.3 environment.
NOTE:
It is recommended to use the Linux for building the Vivado project.
In Windows, if the path length is more than 260 characters, then design implementation using the Vivado Design Suite might fail. This is due to a Windows OS limitation. Refer to the AR# 52787 for the possible solution to avoid the Windows specific path length issue.
To build the hardware design, execute the following steps:
On Linux:
Open a Linux terminal
Change directory to $TRD_HOME/pl
To create the Vivado IPI project and invoke the GUI, run the following command.
% vivado -source scripts/create_project.tcl
On Windows 7:
Click Start > All Programs > Xilinx Design Tools > Vivado 2017.3 > Vivado 2017.3.
On the getting started page, click on Tcl Console, see the below figure.
In the Tcl console type:
cd </path/to/downloaded/zip-file>/rdf0428-zcu106-vcu-trd-2017-3/pl
source scripts/create_project.tcl
{vcu_trd_17p3_fig5.png}
After executing the script, the vivado IPI block design comes up as shown in the below Figure.
{vcu_trd_17p3_fig6.png}
Click on “generate bitstream”.
Note: If the user gets any pop-up with “No implementation Results available”. Click “Yes”. Then, if any pop-up comes up with “Launch runs”, Click "OK”.
The design is implemented and a pop-up window comes up saying “open implemented design”. Click "OK".
{vcu_trd_17p3_fig7.png}
After opening implemented design, the window looks as shown in the below figure.
{vcu_trd_17p3_fig8.png}
Go to File > Export > Export Hardware
{vcu_trd_17p3_fig9.png}
In the Export Hardware Platform for SDK window select "Include bitstream" and click "OK".
{vcu_trd_17p3_fig10.png} The HDF is created at $TRD_HOME/pl/project/zcu106_vcu_trd.sdk/zcu106_vcu_trd_wrapper.hdf
5.2.2 VCU PetaLinux BSP
This tutorial shows how to build the Linux image and boot image using the PetaLinux build tool.
PetaLinux Installation: Refer to the PetaLinux Tools Documentation (UG1144) for installation.
% source <path/to/petalinux-installer>/Petalinux-v2017.3/petalinux-v2017.3-final/settings.sh
% echo $PETALINUX
Post PetaLinux installation $PETALINUX environment variable should be set.
Configure the PetaLinux project.
% cd $TRD_HOME/apu/vcu_petalinux_bsp
% petalinux-config --get-hw-description=$TRD_HOME/pl/project/zcu106_vcu_trd.sdk --oldconfig
NOTE:
In above step user can optionally pass pre-generated HDF ($TRD_HOME/ apu/vcu_petalinux_bsp/hw-description/system.hdf).
If Vivado project is modified, then --oldconfig can't be used. User need to clean up the directory and rebuild from scratch.
Apply TMDS patch (Only for rev-b board) - Edit recipes-kernel to include 0001-xilinx-hdmi-rx-Add-HPD-hack-for-ZCU106.patch
vi project-spec/meta-user/recipes-kernel/linux/linux-xlnx_%.bbappend
SRC_URI_append = " \
file://0001-media-xilinx-TPG-Add-IOCTL-to-set-PPC.patch \
file://0001-staging-xilinx-hdmitx-Give-preference-to-Standard-Ti.patch \
file://0001-xilinx-hdmi-rx-Add-HPD-hack-for-ZCU106.patch \
"
Build all Linux image components
% petalinux-build
Create a boot image (BOOT.BIN) including FSBL, ATF, bitstream and u-boot.
% cd images/linux
% petalinux-package --boot --bif=vcu.bif
Copy the generated boot image and Linux image to the SD card directory. Replace rev-x with board revision.
cp BOOT.BIN image.ub $TRD_HOME/images/rev-x
5.2.3 VCU APM library
This tutorial shows how to build the VCU APM library.
NOTE: SYSROOT needs to be pre-configured before building VCU libraries and QT project.
% export SYSROOT=/tmp/vcu_petalinux_bsp_2017_3/sysroots/plnx_aarch64
Open the SDK workspace using the Xilinx SDK tool.
% cd $TRD_HOME/apu
% xsdk -workspace . &
From the menu bar, select File -> Import.., then select General -> Existing Projects into Workspace. Click Next.
{vcu_trd_17p3_fig11.png}
Browse to the $TRD_HOME/apu directory. Select “Deselect All” and then select vcu_apm_lib project. Click Finish.
{vcu_trd_17p3_fig12.png}
Right-click the vcu_apm_lib project and select 'Build Project'
{vcu_trd_17p3_fig13.png}
5.2.4 VCU Video library
This tutorial shows how to build the VCU video library.
From the menu bar, select File -> Import…, then select General -> Existing Projects into Workspace. Click Next.
Browse to the $TRD_HOME/apu directory. Select “Deselect All” and select vcu_video_lib project. Click Finish.
{vcu_trd_17p3_fig14.png}
Right-click the vcu_video_lib project and select 'Build Project'
5.2.5 VCU GST library
This tutorial shows how to build the VCU GST library.
From the menu bar, select File -> Import…, then select General -> Existing Projects into Workspace. Click Next.
Browse to the $TRD_HOME/apu directory. Select “Deselect All” and select vcu_gst_lib project. Click Finish.
{vcu_trd_17p3_fig15.png}
Right-click the vcu_gst_lib project and select 'Build Project'
5.2.6 VCU Qt Application
This tutorial shows how to build the VCU Qt application.
Source the Qt setup script to generate the Qt Makefile reflecting these changes.
% cd $TRD_HOME/apu/vcu_qt
% source qmake_set_env.sh
% qmake VCU.pro -r -spec linux-oe-g++
% make
Copy the generated vcu_qt executable to the SD card directory.
% cp -f vcu_qt $TRD_HOME/images/rev-x/bin/
5.3 Run Flow
Setup the board as explained in “Board Setup” Section.
Prepare the SD card. Use SD formatter tool to create a FAT partition, https://www.sdcard.org/downloads/formatter_4/
{vcu_trd_17p3_fig16.png}
Please note that Windows formatter can't be used and partition should be FAT, not FAT32.
Copy all the files from the $TRD_HOME/images/rev-c SD card directory to a FAT formatted SD card. For ZCU106 Rev-b board, use $TRD_HOME/images/rev-b
Power on the board; make sure INIT_B, done and all power rail LEDs are lit green.
After ~30 seconds, the display will turn on and the application will start automatically, targeting the max supported resolution of the monitor (3840x2160).
The user can now control the application from the GUI's control bar (top left) displayed on the monitor.
The user can quit the application by clicking on exit [X] icon. To restart the application type run_vcu.sh on the shell.
NOTE: The SD card file system is mounted at /media/card. Optional storage medium SATA and USB are mounted at /media/sata and /media/usb respectively.
Graphic User Interface
A QT based graphical user interface (GUI) provides control and monitoring interface. By default GUI will run on HDMI-Tx when both DP/HDMI-Tx are connected. It’s recommended to connect one display device at a time to avoid bandwidth usage. Figure below shows the default home screen, i.e. HDMI-Tx.
{home HdmiTx_122117.jpeg}
Figure below shows the home screen of DP when only DP is connected.
{HomeDP_122117.jpeg}
QT GUI has following options for user to select:
Number of Input
This determines the number of active video sources. In 2017.3, Max two input sources are supported.by default number is 1.
Output
This option allows the user to select sink for the pipeline. Supported output sink types are display port, HDMI-Tx, record, and stream. For the Display Port and HDMI-Tx, the available Codec options are either enc-dec or Pass-through. For Record and Stream Out, the available Codec option is Enc.
Monitor Refresh Rate
Refresh rate needs to be aligned with the monitor refresh rate. Please honor the following restrictions to get the expected performance.
4kp30
To run 4kp30 pipeline on HDMI Tx, make sure that monitor is locked to 4kp30 if the max resolution is 4kp60.
When both DP and HDMI Tx are connected, then by default the GUI will displayed on HDMI Tx.
4kp60
To run 4kp60 pipeline on HDMI Tx, make sure that monitor is locked to 4kp60 if the max resolution is 4kp60 and DP is not connected.
Input Settings
Based on the number of inputs selected, a pop up window appears in QT GUI with configuration options for each input. Below snapshot depicts the pop up window for Number of Input setting as 2.
{vcu_trd_17p3_fig19.JPG}
Different configuration options available in the QT pop up window are:
Input Source (Input’x’)
The following video sources (4K) are available as part of input video selection:
HDMI-Rx: GooBang Doo ABOX 2017 (Android 6.0 TV Box) with optional splitter
File: Mp4 streams reside in SD-Card/USB/SATA.
Test Pattern Generator (TPG): Implemented in the PL
MIPI: LI-IMX274 MIPI-FMC v1.1.
Codec
The following options are available as part of Codec functionality
Enc-Dec: This option is to select encode and decode in the pipeline.
Enc: This option is to select encode only in the pipeline for record or stream out use case.
Pass-through: This option is to display raw video.
Preset
There are six predefined presets. If the user edits any control options preset mode switches to “Custom”.
AVC Low Encoder type = H264, bitrate = 10Mbps
AVC Medium Encoder type = H264, bitrate = 30Mbps
AVC High Encoder type = H264, bitrate = 60Mbps
HEVC Low Encoder type = H265, bitrate = 10Mbps
HEVC Medium Encoder type = H265, bitrate = 30Mbps
HEVC High Encoder type = H265, bitrate = 60Mbps
Profile= Main, QP=uniform, Rate Control= CBR, B-frame = 0, Slice=4, and GoP Len=30 common for all above options.
Custom User specific options
Settings
User can control the encoder, record and stream out configuration from the GUI, Settings option are enabled when the pipeline is in the stop state. User can control the encoder parameters when output option is selected as Display port/HDMI-Tx/Record/Stream.
{vcu_trd_17p3_fig20.JPG}
Encoder
This can be either H264 or H265.
Profile
The standard defines a set of capabilities, which are referred to as profiles, targeting specific classes of applications. These are declared as a profile code (profile_idc) and a set of constraints applied in the encoder. This allows a decoder to recognize the requirements to decode that specific stream.
H264 supports baseline, main and high profile. In H265 only main profile is supported.
QP
Quantization in an encoder is controlled by a quantization parameter. It specifies how to generate the QP per coding unit (CU). Two modes are supported-
Uniform: All CUs of the slice use the same QP
Auto: VCU encoder change the QP for each coding unit according to its content.
Rate Control
Only Constant bitrate (CBR) is supported. This mode generates a constant bit rate that can be predefined by a user. CBR is recommended for limited bandwidth use cases.
Bitrate
Encoding bit rate. In digital multimedia, bit rate often refers to the number of bits used per unit of playback time to represent a continuous medium such as audio or video after source coding (data compression).
B-frame
Short for bi-directional frame, or bi-directional predictive frame, a video compression method used by the MPEG standard. It ranges from 0 to 4.
Slice
In the H264/H265 standard, the granularity of prediction types is brought down to the "slice level." A slice is a spatially distinct region of a frame that is encoded separately from any other region in the same frame. I-slices, P-slices, and B-slices take the place of I, P, and B frames. In H265 slice ranges from 4-22 and in H264 it ranges from 4-135.
GoP Length
In video coding, a group of pictures, or GOP structure, specifies the order in which intra and inter-frames are arranged. And GoP-length is a length between two Intra frames. The GOP is a collection of successive pictures within a coded video stream. Each coded video stream consists of successive GOPs, from which the visible frames are generated. Its range is from 1 to 100.
Record
When Output option is selected as Record, A tab will be enabled in settings window through which user can record the video in to the storage medium.
{vcu_trd_17p3_fig21.jpg}
Storage
This option specifies storage device for the recorded file. The list is dynamically populated based on mounted storage devices. Supported storage devices are SD, USB and SATA.
Output File Name
Name of the output file. For H264, recorded file get saved as <Source name>_H264_rec_<timestamp>.mp4 and for H265 it will be <Source name>_H265_rec_<timestamp>.mp4
Duration
This option will specify the Recording time duration. It ranges from 1-3 mins.
NOTE: Due to speed and storage constraints it is recommended to use USB/SATA storage devices for the record.
Stream-out
Stream-out panel allows the user to configure streaming parameters.
Stream-out Prerequisites:
Host server machine (with GPU) capable of playing 4K60 stream.
Setup Ethernet connection between ZCU106 board and the host machine. Ensure connection is alive by doing a ping from the board to host machine.
VLC player installed on the host machine.
Firewall is turned off on the host machine.
Start VLC player on the host before streaming from GUI.
{vcu_trd_17p3_fig22.jpg} Sink
Provides sink option for the stream-out. It is set to PS Ethernet.
Host IP
IP address of a computer or other Zynq® UltraScale+™ MPSoC board in which streamed video will be played on. It is set to 192.168.25.89 by default.
IP
This option will show the IP address of the board if the Ethernet link is up. If no Ethernet link is connected then it will show “Not Connected”.
Port
Port number of the Ethernet link. By default, it is set to 5004.
Steps for Stream Out
Here are the steps to get the ZCU106 TRD to play out to VLC.
Make sure that your machine can play 4Kp60 streams and turned off the Firewall.
Connect your PC to the ZCU106 board. It is recommended a direct connection between ZCU106 board and PC to minimize the network traffic.
Set the IP address for the ZCU106 board and PC to use the same subnet (i.e. ZCU106 - ifconfig eth0 192.168.25.90 and PC - 192.168.25.89).
Create .sdp file on host. For H265 RTP client, add below configs in host_h265.sdp file.
v=0
c=IN IP4 192.168.25.90
m=video 5004 RTP/AVP 96
a=rtpmap:96 H265/90000
a=framerate=30
Depending on the network, change IP address and port number. IP address given in .sdp is ZCU106 board's IP. For H264 RTP client, change encoder to H264.
Launch VLC on your PC and open the SDP file (Click on media -> Open File. Select host_h265.sdp file and click on open.)
Setup output option to “Stream” in the ZCU106 VCU TRD GUI.
Configure the Stream out settings and make sure that the ZCU106 VCU TRD GUI is pointing to the IP address of your PC.
Select the HDMI-Rx/MIPI or the TPG as an input.
Press play in VLC on your PC. (The Client must start first, but VLC times out if you wait too long before starting the ZCU106 VCU TRD Stream).
Press play on the ZCU106 VCU TRD GUI
NOTE: In video streaming use case it is recommended to set b-frame=0
Multi stream
When more than 1 source is selected in the GUI, it's a multi-stream use case. GUI support multi streaming, multi recording or multi display. In the multi stream, source type can be either TPG, HDMI or MIPI but two sources can not be of same type. In the multi display, first pipeline output will display in first half and second pipeline output will be displayed on second half. Only half of each video will be displayed. Figure below shows an example.
{multistream_122117.jpeg}
Codec options are either Enc-dec or Pass-through.In the multi streaming/recording codec option is fixed as Enc.
6 Other Information
6.1 Known Issues
On repeated start/stop pipeline hangs/report an error after some iterations.
Frequency: Occasional
Workaround: User has to quit the application as described in the pop up message. Relaunch the GUI by running $autostart.sh from command line.
Kernel crash on hot-plugging HDMI-Rx with/without connecting source.
Frequency: Rare
Workaround: None
Runtime DP/HDMI connection will not work.
Frequency: Always
Workaround: None
4kp60 pipeline will not work with AVC enc-dec for all bitrates due to the PS DDR bandwidth limitation as there is an additional bandwidth of 2GB/s with graphics primary plane (GUI).
Frequency: Always
Workaround: None
Blank screen is observed while running 4kp60 pipeline for HEVC
Frequency: Rare
Workaround: None (it will get recovered automatically after few milliseconds)
In multistream use case, wrong fps is displayed for MIPI
Frequency: Always
Workaround: Test with 4kp30 HDMI monitor
Launch and quitting GUI without any action will cause GUI hang.
Frequency: Always
Workaround: Relaunch the GUI by running $autostart.sh from command line.
GUI hangs when stop multistream playback.
Frequency: Always
Workaround: Relaunch the GUI by running $autostart.sh from command line.
6.2 Limitations
Prefetch encoder buffer is enabled in the design by default for a single pipeline. In the multistream use case, the prefetch encoder buffer is enabled for HDMI-Rx/MIPI only. For TPG, it is disabled for getting a better performance.
All VCU parameters are not exposed at GStreamer level so for certain video pattern, it is not possible to optimize it further for increased quality. It will be supported in next release.
Mouse clicks seem to “bounce”. I.e. sometimes when you select a drop-down it drops down and then immediately pops back up.
The application does not support audio.
Make sure the Display Port/HDMI-Tx cable is plugged in when you power on the board, otherwise the application will not start.
This design is validated with HDMI sources (ABOX/Nvidia shield Pro) and DP/HDMI-Tx monitors that are mentioned earlier in compatibility section.
In HEVC, max supported bitrate is 60Mbps for 4kp30/4kp60 pipeline
In 4kp60 HEVC, only preset options are supported. With custom configuration frame drops are observed.
Only single pipeline with 4Kp30 fps is supported for AVC.
In AVC, max supported bitrate is 60Mbps for 4kp30 pipeline.
In a stream-out use case, local display of non-processed stream is not supported.
Split screen feature is not supported as huge frame drops are observed due to addition of Tee elements.
Max supported bitrate for multistream is 10 Mbps. Only preset option HEVC Low is supported. With custom configuration frame drops are observed.
In multistream-out use case, port number should not be same.
AVC is not supported for multistream.
Only CBR (constant bitrate) option is supported for Rate Control in the Encoder Parameter settings.
7 Appendix
H264 and H265 streams used in this reference design are available in public domain.
Elecard_about_Tomsk_part1_HEVC_UHD.mp4 (https://www.elecard.com/videos)
4K-Chimei-inn-60mbps.mp4
8 Support
To obtain technical support for this reference design, go to the:
Xilinx Answers Database to locate answers to known issues
Xilinx Community Forums to ask questions or discuss technical details and issues. Please make sure to browse the existing topics first before filing a new topic. If you do file a new topic, make sure it is filed in the sub-forum that best describes your issue or question e.g. Embedded Linux for any Linux related questions. Please include "ZCU106 VCU TRD" and the release version in the topic name along with a brief summary of the issue.