cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
murali_4i2i
Participant
Participant
328 Views
Registered: ‎07-27-2016

Frame buffer write: Streaming Video Format vs Memory Video Format support


We have built an SDI RX subsystem on a custom MPSoC board.

However our Gstreamer is not supporting this device.
When enabled GST_DEBUG, it says the XV20 and XM20 are unknown formats.

My question is this:
Xilinx Frame-buffer-write should be able to write the SDI output as NV16 format.
But the gstreamer and v4l2-ctl --list-formats are not seeing this capability.
It seems gstreamer and
v4l2-ctl --list-formats
only looks at the capability of the SDI-RX-Sub (excluding
FB-Write)
Am I missing something?

See the commands bellow:
Note that Yavta tool tell the current format as NV16 (see output of command 2 bellow,
but v4l2-ctl (COMMAND-4)  and gstreamer are not seeing format NV16.


here the standard status outputs:
COMMAND-1
#yavta -n 3 -c10 -f NV16 -s 1920x1080 --skip 7 -F /dev/video0
This command write 3 frames in to memory

COMMAND-2
# yavta -F /dev/video0 -l
Device /dev/video0 opened.
Device `vcap_sdirx output 0' on `platform:vcap_sdirx:0' (driver 'xilinx-vipp') supports video, capture, with mplanes.
--- User Controls (class 0x00980001) ---
control 0x0098ca21 `Low Latency Controls' min 2 max 8 step 1 default 4 current 4
1 control found.
Video format: NV16 (3631564e) 1920x1080 field none, 1 planes:
* Stride 1920, buffer size 4147200

COMMAND-3
# media-ctl -d 0 -p
Media controller API version 4.19.0

Media device information
------------------------
driver xilinx-video
model Xilinx Video Composite Device
serial
bus info
hw revision 0x0
driver version 4.19.0

Device topology
- entity 1: vcap_sdirx output 0 (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video0
pad0: Sink
<- "a0000000.v_smpte_uhdsdi_rx_ss":0 [ENABLED]

- entity 5: a0000000.v_smpte_uhdsdi_rx_ss (1 pad, 1 link)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev0
pad0: Source
[fmt:UYVY10_1X20/1920x1080@1000/50000 field:none]
[dv.detect:BT.656/1120 1920x1080p50 (2640x1125) stds:CEA-861 flags:CE-video,has-cea861-vic]
-> "vcap_sdirx output 0":0 [ENABLED]

 

COMMAND-4
# v4l2-ctl --list-formats
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture Multiplanar

[0]: 'XM20' (Y/CrCb 4:2:2 10-bit (N-C))
[1]: 'XV20' (Y/CrCb 4:2:2 10-bit)

 

 

 

Tags (1)
0 Kudos
Reply
2 Replies
watari
Teacher
Teacher
303 Views
Registered: ‎06-16-2013

Hi @murali_4i2i 

 

What version are you using ?

Does this version's petalinux support XV20 on SDI Rx ?

 

Also, if you use petalinux 2019.1, you might have to use xmedia-ctl instead of media-ctl.

 

BTW, did you set proper supported video formats on gui of "Video Frame Buffer Writer" ?

 

Best regards,

 

murali_4i2i
Participant
Participant
283 Views
Registered: ‎07-27-2016

Hi @watari Thanks for the reply.

We use Linux 2019.2

In the Vivado, we checked all the formats available for frame-buffer.

Not sure how to get xmedia-ctrl, we use build-root.

My question was that the yavta managed to write the frame in the expected format.

We opened that in YUV player as well. But why the V4l2 capabilities is not recognizing it ?

 

 

0 Kudos
Reply