Zynq UltraScale+ MPSoC VCU TRD 2020.1 - PL DDR HDR10 HDMI Video Capture and Display

This page provides all the information related to VCU TRD PL DDR HDR10 HDMI design.

This is a beta release and will be included in the 2020.2 version of the TRD as an additional design module. Also note that this page stands alone and does not rely on the common VCU TRD “Build and Run Flow” page.

Table of Contents

1 Overview

This module supports the reception and insertion of HDR10 static metadata for HDMI. This HDR10 metadata that contains critical information needed to support HDR will be carried throughout the pipeline - from the source to the sink. It enables the capture of HDR10 video from an HDMI-Rx Subsystem implemented in the PL. The video can be displayed through HDR10 compatible HDMI-Tx through the PL and recorded in SD cards or USB/SATA drives. The module can Stream-in or Stream-out HDR10 encoded data through an Ethernet interface. This module supports single-stream for XV20 and XV15 format.

This is the new design approach proposed to use PL_DDR for decoding and PS_DDR for encoding so that DDR bandwidth would be enough to support high bandwidth VCU applications requiring simultaneous encoder and decoder operations and transcoding at 4k@60 FPS. This approach makes the most effective use of limited AXI4 read/write issuance capability in minimizing latency for the decoder. DMA buffer sharing requirements determine how capture, display, and intermediate processing stages should be mapped to the PS or PL DDR.

This design supports the following video interfaces:
Sources:

  • HDMI-Rx capture pipeline implemented in the PL.

  • File source (SD card, USB storage, SATA hard disk).

  • Stream-In from network or internet.

Sinks:

  • HDMI-Tx display pipeline implemented in the PL.

VCU Codec:

  • Video Encode/Decode capability using VCU hard block in PL 

    • AVC/HEVC encoding

    • Encoder/decoder parameter configuration.

Video format:

  • XV20, XV15

Supported Resolution:

The table below provides the supported resolution from the command line app only in this design.

Resolution

Command Line

Single Stream

Multi-stream

4kp60

NA

4kp30

x

1080p60

x

√ - Supported
NA – Not applicable
x – Not supported

The below table gives information about the features supported in this design. 

Pipeline

Input source

Format

HDR Mode

Output Type

Resolution

VCU codec

Pipeline

Input source

Format

HDR Mode

Output Type

Resolution

VCU codec

Serial pipeline

HDMI-Rx

XV20/XV15

HDR10

HDMI-Tx

4kp60/4kp30/1080p60

HEVC/AVC

Record/Stream-Out pipeline

HDMI-Rx

XV20/XV15

HDR10

File Sink/ Stream-Out

4kp60/4kp30/1080p60

HEVC/AVC

File/Streaming Playback pipeline

File Source/ Stream-In

XV20/XV15

HDR10

HDMI-Tx

4kp60/4kp30/1080p60

HEVC/AVC


The below figure shows the PL DDR HDR10 HDMI design hardware block diagram.

The below figure shows the PL DDR HDR10 HDMI design software block diagram.

1.1 Hardware, Software Tools and System Requirements

1.1.1 Hardware Tools

Required :

  • ZCU106 evaluation board (rev C/D/E/F/1.0) with power cable

  • HDR10 compatible Monitor with HDMI input supporting 3840x2160 resolution

  • HDMI cable 2.0 certified

  • Class-10 SD card

  • HDMI Receiver - NVIDIA SHIELD Pro

  • Ethernet cable

Optional :

  • USB pen drive formatted with the FAT32 file system and hub

  • SATA drive formatted with the FAT32 file system, external power supply, and data cable

1.1.2 Software Tools

Required :

Compatibility :
The VCU HDR10 design has been tested successfully with the following user-supplied components.

HDMI Monitor :

Make/Model

Resolutions

Make/Model

Resolutions

Samsung 4K Smart UHD TV - RU7100

3840 x 2160 @ 60Hz

HDMI Input Sources:

  • NVIDIA SHIELD Pro

Cable:

  • HDMI 2.0 compatible cable

1.2 Download, Installation, and Licensing

The Vivado Design Suite User Guide explains how to download and install the Vivado® Design Suite tools, which include the Vivado Integrated Design Environment (IDE), High-Level Synthesis tool, and System Generator for DSP. This guide also provides 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 Mixer- Included with Vivado - PG243

  • Video PHY Controller - Included with Vivado - PG203

  • HDMI-Rx/Tx Subsystem - Purchase license (Hardware evaluation available) - PG235 & PG236

  • Video Processing Subsystem (VPSS) - Included with Vivado - PG231

To obtain the LogiCORE IP license, please visit the respective IP product page and get the license.

Hardware Evaluation keys allow you to simulate and implement your design, run timing analysis and generate a time-limited bitstream to program a Xilinx FPGA. The core in the programmed device will function in hardware for anywhere from 2 to 8 hours, depending on the core.

1.3 Board Setup

The below section will provide the information on the ZCU106 board setup for running VCU HDR10 design.

  1. 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.

  2. Insert the SD card with the images copied into the SD card slot J100.

  3. Set the SW6 switches as shown in the below Figure. This configures the boot settings to boot from SD.

  4. Connect 12V Power to the ZCU106 6-Pin Molex connector.

  5. Connect one end of HDMI cable to the board’s P7 stacked HDMI connector (lower port) and another end to HDMI source.

  6. Connect one end of HDMI cable to the board’s P7 stacked HDMI connector (upper port) and another end to HDMI monitor.

  7. For SATA storage device, connect SATA data cable to SATA 3.0 port. (Optional)

  8. Set up a terminal session between a PC COM port and the serial port on the evaluation board (See the Determine which COM to use to access the USB serial port on the ZCU106 board for more details)

  9. Copy the VCU HDR10 images into the SD card and insert the SD card on the board.

  10. The below images will show how to connect interfaces on the ZCU106 board.

The above  figure shows all the ZCU106  board connections

 The above figure shows all the ZCU106 board connector slots

1.3.1 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 a micro USB cable is connected between the ZCU106 board and host PC. 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.

  1. Click Device Manager to open the Device Manager window. You may be asked to confirm opening the Device Manager. If so, click YES.

  2. Expand Ports (COM & LPT).

  3. Locate the Silicon Labs Quad CP210x USB to UART Bridge: Interface 0 (COM#).

4. Note down the COM Port number for further steps.
5. 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

  1. Launch Tera Term and open the COM the port that is associated with Silicon Labs Quad CP210x USB to UART Bridge: Interface 0 of the USB-to-serial bridge.

  2. Set the COM port to 115200 Baud rate, 8, none, 1 –Set COM port.

  3. Power ON the board which has an SD card. Switch ON SW1 to power the ZCU106 board.

  4. It boots Linux on board and It takes about a minute for Linux to boot. 

1.4 Download the TRD

1.5 Run Flow

The TRD package is released with the source code, Vivado project, Petalinux BSP, and SD card image that enables the user to run the demonstration. It also includes the binaries necessary to configure and boot the ZCU106 board. Prior to running the steps mentioned in this wiki page, download the TRD package and extract its contents to a directory referred to as TRD_HOME which is the home directory. TRD package contents are placed in the following directory structure.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 rdf0428-zcu106-vcu-hdr10-2020-1 ├── apu │   └── vcu_petalinux_bsp ├── images │   └── vcu_hdr10_hdmi ├── pl │   ├── constrs │   ├── designs │   ├── prebuild │   ├── README.md │   └── srcs └── README.txt 9 directories, 2 files

TRD package contents specific to VCU HDR10 HDMI design are placed in the following directory structure.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 rdf0428-zcu106-vcu-hdr10-2020-1 ├── apu │   └── vcu_petalinux_bsp │   └── xilinx-vcu-zcu106-v2020.1-final.bsp ├── images │   ├── vcu_hdr10_hdmi │   │   ├── autostart.sh │   │   ├── BOOT.BIN │   │   ├── boot.scr │   │   ├── config │   │   ├── image.ub │   │   ├── system.dtb │   │   └── vcu ├── pl │   ├── constrs │   ├── designs │   │   ├── zcu106_HDR10 │   ├── prebuild │   │   ├── zcu106_HDR10 │   ├── README.md │   └── srcs │   ├── hdl │   └── ip └── README.txt 15 directories, 8 files

Configuration files(input.cfg) for various resolutions are placed in the following directory structure.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 config ├── 4kp60 │   ├── Display │   ├── Record │   ├── Stream-in │   └── Stream-out ├── 4kp30 │   ├── Display │   ├── Record │   ├── Stream-in │   └── Stream-out ├── 1080p60 │   ├── Display │   ├── Record │   ├── Stream-in │   └── Stream-out └── input.cfg 15 directories, 1 file

1.5.1 Prepare a SD-Card

  • The user needs to copy all the files from the $TRD_HOME/images/vcu_hdr10_hdmi/ to FAT32 formatted SD card directory.

  • Power on the board; make sure INIT_B, DONE and all power rail LEDs are lit green

  • After a successful boot, a login prompt would appear as shown below. Enter username and password as root and root respectively to login to the board file system.

1 2 3 4 PetaLinux 2020.1 zcu106_vcu_trd /dev/ttyPS0 zcu106_vcu_trd login: root Password: root@zcu106_vcu_trd:~#

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.

1.5.2 GStreamer Application (vcu_gst_app)

The vcu_gst_app is a command-line multi-threaded Linux application. The command-line application requires an input configuration file (input.cfg) to be provided in plain text.

Run below modetest command to set CRTC configurations for 4kp60:

1 $ modetest -D a00c0000.v_mix -s 38:3840x2160-60@BG24

Run below modetest command to set CRTC configurations for 4kp30:

1 $ modetest -D a00c0000.v_mix -s 38:3840x2160-30@BG24

Execution of the application is shown below:

1 $ vcu_gst_app <path to *.cfg file>

Examples:

4kp60 XV20 HEVC_HIGH HDR10 Display Pipeline execution

1 $ vcu_gst_app /media/card/config/4kp60/Display/Single_4kp60_HEVC_HIGH.cfg

4kp60 XV20 HEVC_HIGH HDR10 Record Pipeline execution

1 $ vcu_gst_app /media/card/config/4kp60/Record/Single_4kp60_HEVC_HIGH.cfg

4kp60 XV20 HEVC_HIGH HDR10 Stream-out Pipeline execution

1 $ vcu_gst_app /media/card/config/4kp60/Stream-out/Single_4kp60_HEVC_HIGH.cfg

4kp60 XV20 HEVC_HIGH HDR10 Stream-in Pipeline execution

1 $ vcu_gst_app /media/card/config/4kp60/Stream-in/input.cfg

Make sure HDMI-Rx should be configured to 4kp60 mode

To measure the latency of the pipeline, run the below command. The latency data is huge, so dump it to a file.

1 $ GST_DEBUG="GST_TRACER:7" GST_TRACERS="latency" GST_DEBUG_FILE=/run/latency.log vcu_gst_app /media/card/config/input.cfg

1.6 Build Flow

The following tutorials assume that the $TRD_HOME environment variable is set as given below.

1 $ export TRD_HOME=</path/to/downloaded/zipfile>/rdf0428-zcu106-vcu-hdr10-2020-1

1.6.1 Hardware Design

Refer to the Vivado Design Suite User Guide: Using the Vivado IDE, UG893, for setting up the Vivado environment.

On Linux:

  1. Open a Linux terminal

  2. Change directory to $TRD_HOME/pl

  3. Run the following command in Vivado shell to create the Vivado IPI project for VCU HDR10 and invoke the GUI.

1 $ vivado -source designs/zcu106_HDR10/project.tcl

After executing the script, the Vivado IPI block design comes up as shown in the below figure.

  • Click on “Generate Bitstream”.

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".

After opening the implemented design, the window looks as shown in the below figure.

The actual results might graphically look different than the image shown

Go to File > Export > Export Hardware

In the Export Hardware Platform select Fixed in the Platform type and click Next.

In the next window, select Include bitstream and click Next.

The default XSA file name is <hardware design name_wrapper>. Choose the path where the XSA file has to be written.

The XSA is created at $TRD_HOME/pl/build/zcu106_HDR10/zcu106_HDR10_wrapper.xsa for VCU HDR10 hardware design .

Click Finish for the XSA file to be generated.

1.6.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.

It is recommended to follow the build steps in sequence.

1 2 $ source <path/to/petalinux-installer>/tool/petalinux-v2020.1-final/settings.sh $ echo $PETALINUX

Post PetaLinux installation $PETALINUX environment variable should be set.

  • Create a PetaLinux project.

1 2 $ cd $TRD_HOME/apu/vcu_petalinux_bsp $ petalinux-create -t project -s xilinx-vcu-zcu106-v2020.1-final.bsp
  • Configure the PetaLinux project.

1 2 $ cd xilinx-vcu-zcu106-v2020.1-final $ petalinux-config --get-hw-description=$TRD_HOME/pl/prebuild/zcu106_HDR10/
  • If the Vivado project is modified, the user is expected to configure the bsp with the modified .xsa file and build. e.g.

1 $ petalinux-config --get-hw-description=$TRD_HOME/pl/build/zcu106_HDR10/
  • Create a soft link of design dtsi file to system-user.dtsi using below command

1 2 3 $ cd project-spec/meta-user/recipes-bsp/device-tree/files/ $ ln -sf vcu_hdr10_hdmi.dtsi system-user.dtsi $ cd ../../../../../

Custom EDID Support
The TRD design is tested/validated with ABOX 2017 and NVIDIA SHIELD Pro. If you want to try with any new HDMI source, you need to generate the EDID of the new source and update it in the TRD bsp. Refer to Custom EDID Support for adding the newly generated EDID file.

  • Build the PetaLinux project

1 $ petalinux-build
  • Build SDK components to use it as sysroot for application development.

1 2 $ petalinux-build --sdk $ petalinux-package --sysroot
  • Create a boot image (BOOT.BIN) including FSBL, ATF, bitstream, and u-boot.

1 2 $ cd images/linux $ petalinux-package --boot --fsbl zynqmp_fsbl.elf --u-boot u-boot.elf --pmufw pmufw.elf --fpga system.bit
  • Copy the generated boot image and Linux image to the SD card directory.

1 cp BOOT.BIN image.ub boot.scr $TRD_HOME/images/vcu_hdr10_hdmi/

1.6.3 VCU GST APP

vcu_gst_app and supporting library will be built as a vcu-gst-app recipe inside petalinux-project. Refer project-spec/meta-user/recipes-apps/vcu-gst-app directory inside petalinux project for vcu-gst-app recipe. Source of vcu_apm_lib, vcu_video_lib, vcu_gst_lib and vcu_gst_app is provided as zip inside project-spec/meta-user/recipes-apps/vcu-gst-app/files/ directory. vcu_gst_app will be built as part of petalinux project and the executable is placed in /usr/bin/ location of rootfs. User can update the zip file if any source code modifications need to be and run following command to build vcu-gst-app recipe.

1 $ petalinux-build -c vcu-gst-app

2 Other Information

2.1 Known Issues

2.2 Limitations

2.3 Optimum VCU Encoder parameters for use-cases.

Video streaming:

  • Video streaming use-case requires a very stable bitrate graph for all pictures.

  • It is good to avoid periodic large Intra pictures during the encoding session

  • Low-latency rate control (hardware RC) is the preferred control-rate for video streaming, it tries to maintain equal amount frame sizes for all pictures.

  • Good to avoid periodic Intra frames instead use low-delay-p (IPPPPP…)

  • VBR is not a preferred mode of streaming.

Performance: AVC Encoder settings:

  • It is preferred to use 8 or higher slices for better AVC encoder performance.

  • AVC standard does not support Tile mode processing which results in the processing of MB rows sequentially for entropy coding.

Quality: Low bitrate AVC encoding:

  • Enable profile=high and use qp-mode=auto for low-bitrate encoding use-cases.

  • The high profile enables 8x8 transform which results in better video quality at low bitrates.


3 Appendix A - Input Configuration File (input.cfg)

The example configuration files are stored at /media/card/config/ folder.

Common Configuration:
It is the starting point of common configuration.
 
Num of Input:
1

Output:
Select the video interface.
Options: HDMI

Out Type:
Options: display, record, and stream

Display Rate:
Pipeline frame rate.
Options: 30 FPS or 60 FPS for each stream

Exit:
It indicates to the application that the configuration is over

Input Configuration:
It is the starting point of the input configuration.

Input Num:
Starting Nth input configuration.
Options: 1

Input Type:
Input source type.
Options: HDMI, File, Stream

Uri:
File path or Network URL. Applicable for file playback and stream-in pipeline only. Supported file formats for playback are ts, mp4, and mkv.
Options: file:///media/usb/abc.ts (for file path), udp://192.168.25.89:5004/ (for Network streaming, Here 192.168.25.89 is IP address and 5004 is port no)

Raw:
To tell the pipeline is processed or pass-through.
Options: False

The raw use-case is not supported with this design as mixer is not connected to PS DDR.


Width:
The width of the live source.
Options: 3840, 1920

Height:
The height of the live source.
Options: 2160, 1080

Format:
The format of input data.
Options: XV20, XV15

HDR Mode:
Specifies High Dynamic Range(HDR) mode
Options: HDR10, NONE

Exit:
It indicates to the application that the configuration is over.

Encoder Configuration:
It is the starting point of encoder configuration.

Encoder Num:
Starting Nth encoder configuration.
Options: 1

Encoder Name:
Name of the encoder.
Options: AVC, HEVC

Profile:
Name of the profile.
Options: high for AVC and main for HEVC.

Rate Control:
Rate control options.
Options: CBR, VBR, and low-latency.

Filler Data:
Filler Data NAL units for CBR rate control.
Options: True, False

QP:
QP control mode used by the VCU encoder.
Options: Uniform, Auto

L2 Cache:
Enable or Disable L2Cache buffer in encoding process.
Options: True, False

Latency Mode:
Encoder latency mode.
Options: normal, sub_frame

Low Bandwidth:
If enabled, decrease the vertical search range used for P-frame motion estimation to reduce the bandwidth.
Options: True, False

Gop Mode:
Group of Pictures mode.
Options: Basic, low_delay_p, low_delay_b

Bitrate:
Target bitrate in Kbps
Options: 1-60000

B Frames:
Number of B-frames between two consecutive P-frames
Options: 0-4

Slice:
The number of slices produced for each frame. Each slice contains one or more complete macroblock/CTU row(s). Slices are distributed over the frame as regularly as possible. If slice-size is defined as well more slices may be produced to fit the slice-size requirement.
Options:
4-22 4kp resolution with HEVC codec
4-32 4kp resolution with AVC codec
4-32 1080p resolution with HEVC codec
4-32 1080p resolution with AVC codec

GoP Length:
The distance between two consecutive I frames
Options: 1-1000

GDR Mode:
It specifies which Gradual Decoder Refresh(GDR) scheme should be used when gop-mode = low_delay_p
Options: Horizontal/Vertical/Disabled

GDR mode is currently supported with LLP1/LLP2 low-delay-p use-cases only

Entropy Mode:
It specifies the entropy mode for H.264 (AVC) encoding process
Options: CAVLC/CABAC/Default

Max Picture Size:
It is used to curtail instantaneous peak in the bit-stream. It works in CBR/VBR rate-control only. When it is enabled, max-picture-size value is calculated and set with 10% of AllowedPeakMargin.
i.e. max-picture-size = (TargetBitrate / FrameRate) * 1.1
Options: TRUE/FALSE

Preset:
Options: HEVC_HIGH, HEVC_MEDIUM, HEVC_LOW, AVC_HIGH, AVC_MEDIUM, AVC_LOW, Custom

Exit
It indicates to the application that the configuration is over.

Record Configuration:
It is the starting point of record configuration.

Record Num:
Starting Nth record configuration.
Options: 1

Out-File Name:
Record file path.
Options: /media/usb/abc.ts

Duration:
Duration in minutes.
Options: 1-3

Exit
It indicates to the application that the configuration is over.

Streaming Configuration:
It is the starting point of streaming configuration.

Streaming Num:
Starting Nth streaming configuration.
Options: 1

Host IP:
The host to send the packets to
Options: 192.168.25.89 or Windows PC IP

Port:
The port to send the packets to
Options: 5004

Exit
It indicates to the application that the configuration is over.

Trace Configuration:
It is the starting point of trace configuration.

FPS Info:
To display fps info on the console.
Options: True, False

APM Info:
To display the APM counter number on the console.
Options: True, False

Pipeline Info:
To display pipeline info on console.
Options: True, False

Exit
It indicates to the application that the configuration is over.


4 Appendix B - HDMI-Rx/Tx Link-up and GStreamer Commands

This section covers configuration of HDMI-Rx using media-ctl utility and HDMI-Tx using modetest utility, along with demonstrating HDMI-Rx/Tx link-up issues and steps to switch HDMI-Rx resolution. It also contains sample GStreamer HDMI video pipelines for Display, Record & Playback, Stream-in and Stream-out use-cases.

  • HDMI source can be locked to any resolution. Run the below command for all media nodes to print media device topology. where, mediaX represents different media nodes. In the topology, log look for the v_hdmi_rx_ss string to identify the HDMI input source media node.

1 $ media-ctl -p -d /dev/mediaX
  • To check the link status, resolution and video node of the HDMI input source, run below media-ctl command, where ,mediaX indicates media node for the HDMI input source.

1 $ media-ctl -p -d /dev/mediaX
  • When HDMI source is connected to 4KP60 resolution, it shows:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 root@vcu_trd:/media/card# media-ctl -p -d /dev/media0 -----> Media node for HDMI input source Media controller API version 5.4.0 Media device information ------------------------ driver xilinx-video model Xilinx Video Composite Device serial bus info hw revision 0x0 driver version 5.4.0 Device topology - entity 1: vcap_hdmi output 0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 -----> Video node for HDMI-Rx source pad0: Sink <- "a0040000.v_proc_ss":1 [ENABLED] - entity 5: a0040000.v_proc_ss (2 pads, 2 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:RBG888_1X24/3840x2160 field:none] <- "a0400000.v_hdmi_rx_ss":0 [ENABLED] pad1: Source [fmt:UYVY10_1X20/3840x2160 field:none] -> "vcap_hdmi output 0":0 [ENABLED] - entity 8: a0400000.v_hdmi_rx_ss (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Source [fmt:RBG888_1X24/3840x2160 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:0x0@25000000 max:4096x2160@297000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom ] [dv.detect:BT.656/1120 3840x2160p60 (4400x2250) stds:CEA-861 flags:CE-video] -----> Resolution and Frame-rate of HDMI-Rx source -> "a0040000.v_proc_ss":0 [ENABLED]

Check resolution and frame-rate of dv.detect under v_hdmi_rx_ss node.

  • When the HDMI source is not connected, it shows:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 root@vcu_trd:/media/card# media-ctl -p -d /dev/media0 -----> Media node for HDMI input source Media controller API version 5.4.0 Media device information ------------------------ driver xilinx-video model Xilinx Video Composite Device serial bus info hw revision 0x0 driver version 5.4.0 Device topology - entity 1: vcap_hdmi output 0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 -----> Video node for HDMI-Rx source pad0: Sink <- "a0040000.v_proc_ss":1 [ENABLED] - entity 5: a0040000.v_proc_ss (2 pads, 2 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:VYYUYY10_4X20/1280x720 field:none colorspace:srgb] <- "a0400000.v_hdmi_rx_ss":0 [ENABLED] pad1: Source [fmt:VYYUYY10_4X20/1920x1080 field:none colorspace:srgb] -> "vcap_hdmi output 0":0 [ENABLED] - entity 8: a0400000.v_hdmi_rx_ss (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Source [fmt:RBG888_1X24/1280x720 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:0x0@25000000 max:4096x2160@297000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom ] [dv.query:no-link] -----> HDMI-Rx Link Status -> "a0040000.v_proc_ss":0 [ENABLED]

Here dv.query:no-link under v_hdmi_rx_ss node shows HDMI-Rx source is not connected or HDMI-Rx source is not active (Try waking up the device by pressing a key on remote).

Notes for gst-launch-1.0 commands:

  • Video node for HDMI-Rx source can be checked using media-ctl command. Run below media-ctl command to check video node for HDMI-Rx source. where, media0 indicates media node for HDMI input source.

1 $ media-ctl -p -d /dev/media0
  • Make sure the HDMI-Rx media pipeline is configured for 4kp60 resolution and source/sink has the same color format for connected nodes. For XV20 format, run below media-ctl commands to set resolution and format of HDMI scaler node where media0 indicates media node for HDMI input source.

When HDMI Input Source is NVIDIA SHIELD

1 2 $ media-ctl -d /dev/media0 -V "\"a0040000.v_proc_ss\":0 [fmt:RBG888_1X24/3840x2160 field:none]" $ media-ctl -d /dev/media0 -V "\"a0040000.v_proc_ss\":1 [fmt:UYVY10_1X20/3840x2160 field:none]"

Make sure NVIDIA SHIELD is configured for 4K resolution and RBG888_1X24 format.

  • Follow the below steps to switch the HDMI-Rx resolution from 1080p60 to 4kp60.

    • Check current HDMI Input Source Resolution (1080p60) by following the steps mentioned earlier to check HDMI-Rx resolution using media-ctl command.

    • Run vcu_gst_app for current HDMI-Rx resolution (1080p60) by executing the following command.

1 $ vcu_gst_app /media/card/config/input.cfg

Below configurations needs to be set in input.cfg for HDMI-Rx 1080p60 resolution.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Common Configuration : START Num Of Input : 1 Output : HDMI Out Type : Display Frame Rate : 60 Exit Input Configuration : START Input Num : 1 Input Type : hdmi Raw : FALSE Width : 1920 Height : 1080 Format : XV20 HDR Mode : HDR10 Exit Encoder Configuration : START Encoder Num : 1 Preset : HEVC_HIGH Exit
  • Change Resolution of HDMI Input Source from 1080p60 to 4kp60 by following the below steps.

    • Set the HDMI source resolution to 4kp60 (Homepage → Settings → Display & Sound → Resolution → change to 4kp60).

    • Save the configuration to take place the change.

    • Verify the desired HDMI Input Source Resolution (4kp60) by following the above-mentioned steps.

  • If the HDMI-Tx link-up issue is observed after Linux booting, use the following command to get the blue screen on HDMI-Tx for 4kp60.

1 $ modetest -D a00c0000.v_mix -s 38:3840x2160-60@BG24
  • The table below lists the parameters of the pixel format.

Pixel Format

GStreamer Format

Media Bus Format

GStreamer HEVC Profile

GStreamer AVC Profile

Kmssink Plane-id

Pixel Format

GStreamer Format

Media Bus Format

GStreamer HEVC Profile

GStreamer AVC Profile

Kmssink Plane-id

XV20

NV16_10LE32

UYVY10_1X20

main-422-10

high-4:2:2

33

XV15

NV12_10LE32

VYYUYY10_4X20

main-10

high-10

34

  • Make sure HDMI-Rx supports HDR10 and should be configured to 4kp60 mode before running below pipelines.

  • Make sure HDMI-Tx (Monitor) is 4K HDR10 compatible before running below pipelines.

  • It is mandatory to use HDR10 recorded video for all below pipelines.

  • File location should be USB-3.0/SATA/RAMFS to avoid the read-write bandwidth issue - while running record/playback pipelines

  • 192.168.25.89 is host/client IP address and 5004 is port number in streaming pipeline

  • Video0 in the each gst-launch pipelines indicates a video node for the input source.

  • Run the following gst-launch-1.0 command to display the XV20 HDR10 video on HDMI-Tx using the GStreamer pipeline ( capture(HDR10) → encode → decode → display(HDR10) ).

1 $ gst-launch-1.0 v4l2src device=/dev/video0 io-mode=4 hdr-mode=1 ! video/x-raw, width=3840, height=2160, format=NV16_10LE32, framerate=60/1 ! omxh265enc qp-mode=auto gop-mode=basic gop-length=60 b-frames=0 target-bitrate=60000 num-slices=8 control-rate=constant prefetch-buffer=true low-bandwidth=false filler-data=true cpb-size=1000 initial-delay=500 ! video/x-h265, profile=main-422-10, alignment=au ! queue ! omxh265dec internal-entropy-buffers=5 low-latency=0 ! queue max-size-bytes=0 ! fpsdisplaysink text-overlay=false video-sink="kmssink bus-id="a00c0000.v_mix" plane-id=33 sync=true hdr-mode=1" sync=true
  • Run the following gst-launch-1.0 command to record the XV20 HDR10 video using the GStreamer pipeline.

1 $ gst-launch-1.0 v4l2src device=/dev/video0 io-mode=4 num-buffers=3600 hdr-mode=1 ! video/x-raw, width=3840, height=2160, format=NV16_10LE32, framerate=60/1 ! omxh265enc qp-mode=auto gop-mode=basic gop-length=60 b-frames=0 target-bitrate=60000 num-slices=8 control-rate=constant prefetch-buffer=true low-bandwidth=false filler-data=true cpb-size=1000 initial-delay=500 ! video/x-h265, profile=main-422-10, alignment=au ! h265parse ! queue ! mpegtsmux alignment=7 name=mux ! filesink location="/run/test.ts"
  • Run the following gst-launch-1.0 command to play XV20 HDR10 recorded file on HDMI-Tx using the GStreamer pipeline.

1 $ gst-launch-1.0 uridecodebin uri="file:///run/test.ts" ! queue max-size-bytes=0 ! fpsdisplaysink text-overlay=false video-sink="kmssink bus-id="a00c0000.v_mix" plane-id=33 hdr-mode=1"
  • Run the following gst-launch-1.0 command to stream-out the XV20 HDR10 video using the GStreamer pipeline.

1 $ gst-launch-1.0 v4l2src device=/dev/video0 io-mode=4 hdr-mode=1 ! video/x-raw, width=3840, height=2160, format=NV16_10LE32, framerate=60/1 ! omxh265enc qp-mode=auto gop-mode=basic gop-length=60 b-frames=0 target-bitrate=60000 num-slices=8 control-rate=constant prefetch-buffer=true low-bandwidth=false filler-data=true cpb-size=1000 initial-delay=500 periodicity-idr=60 ! video/x-h265, profile=main-422-10, alignment=au ! h265parse ! queue ! mpegtsmux alignment=7 name=mux ! rtpmp2tpay ! udpsink host=192.168.25.89 port=5004 buffer-size=60000000 max-bitrate=120000000 max-lateness=-1 qos-dscp=60 async=false
  • Run the following gst-launch-1.0 command to display XV20 HDR10 stream-in video on HDMI-Tx using the GStreamer pipeline.

1 $ gst-launch-1.0 udpsrc port=5004 buffer-size=60000000 caps="application/x-rtp, clock-rate=90000" ! rtpjitterbuffer latency=1000 ! rtpmp2tdepay ! tsparse ! video/mpegts ! tsdemux name=demux ! queue ! h265parse ! video/x-h265, profile=main-422-10, alignment=au ! omxh265dec internal-entropy-buffers=5 low-latency=0 ! queue max-size-bytes=0 ! fpsdisplaysink text-overlay=false video-sink="kmssink bus-id="a00c0000.v_mix" plane-id=33 hdr-mode=1" sync=true