My tx2 nx board uses the lt6911c chip as a bridge chip from hdmi to CSI, and connects the HDMI output of another PC to the HMDI input interface of the board. Is there any tool that can test whether the video stream is input? How can I verify that the device tree modification is correct?
Is the PC HDMI input the same as the camera input?
hello yunhuzhou,
yes, since it’s a HDMI2CSI bridge driver, you may consider it create a video node for the coming signal.
I use the command
gst-launch-1.0 v4l2src num-buffers=2000 device=/dev/video0 ! 'video/x-raw, format=BGRA, width=1920, height=1080, framerate=60/1' ! videoconvert ! omxh264enc ! qtmux ! filesink location=test.mp4 -ev
The output message is
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0.GstPad:src: caps = video/x-raw, format=(string)BGRA, width=(int)1920, height=(int)1080, framerate=(fraction)60/1, colorimetry=(string)sRGB, interlace-mode=(string)progressive
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:src: caps = video/x-raw, format=(string)BGRA, width=(int)1920, height=(int)1080, framerate=(fraction)60/1, colorimetry=(string)sRGB, interlace-mode=(string)progressive
/GstPipeline:pipeline0/GstVideoConvert:videoconvert0.GstPad:src: caps = video/x-raw, width=(int)1920, height=(int)1080, format=(string)I420, framerate=(fraction)60/1, interlace-mode=(string)progressive
Framerate set to : 60 at NvxVideoEncoderSetParameterNvMMLiteOpen : Block : BlockType = 4
===== NVMEDIA: NVENC =====
NvMMLiteBlockCreate : Block : BlockType = 4
H264: Profile = 66, Level = 40
/GstPipeline:pipeline0/GstOMXH264Enc-omxh264enc:omxh264enc-omxh264enc0.GstPad:sink: caps = video/x-raw, width=(int)1920, height=(int)1080, format=(string)I420, framerate=(fraction)60/1, interlace-mode=(string)progressive
/GstPipeline:pipeline0/GstVideoConvert:videoconvert0.GstPad:sink: caps = video/x-raw, format=(string)BGRA, width=(int)1920, height=(int)1080, framerate=(fraction)60/1, colorimetry=(string)sRGB, interlace-mode=(string)progressive
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:sink: caps = video/x-raw, format=(string)BGRA, width=(int)1920, height=(int)1080, framerate=(fraction)60/1, colorimetry=(string)sRGB, interlace-mode=(string)progressive
Then the generated mp4 file size is alway 616. How can I solve it?
hello yunhuzhou,
is the pipeline executed correctly, is there any failure messages?
please see-also [Applications Using V4L2 IOCTL Directly] to use V4L2 IOCTL to verify basic camera functionality.
No errors. I execute $ v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=AR24 --stream-mmap --stream-count=1 -d /dev/video0 --stream-to=a.mp4 and the output was hanging on. After interrupting, the output file a.mp4 size is 0.
hello yunhuzhou,
I assume there’s timeout failure from kernel side, please double check kernel logs, $ dmesg > klogs.txt for confirmation.
anyways,
it means the stream is not functional if you cannot use V4L2 IOCTL to fetch the camera stream correctly.
Here is the log file.
klogs.txt (147.6 KB)
hello yunhuzhou,
okay… there’s sync-point timeout failures for waiting start-of-frame,
for example,
[ 1433.565961] tegra-vi4 15700000.vi: PXL_SOF syncpt timeout! err = -11
[ 1433.572455] tegra-vi4 15700000.vi: tegra_channel_error_recovery: attempting to reset the capture channel
do you have oscilloscope to probe the MIPI signaling?
please check the signal is following the MIPI spec,
thanks
Could it be that my device tree file is not configured correctly?
hello yunhuzhou,
it could be, device tree are settings for driver layer to define hardware configurations. probing MIPI signaling by oscilloscope should be straightforward to confirm whether there’s steaming on CSI channel.
so,
you may review device tree settings if there’s MIPI signaling. otherwise, the error is something else.
The reason for the error is that there is a problem with the firmware of the Lontium lt6911c chip. Solved after updating the firmware. Thanks.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.