Problem for MIPI data from Jetson Xavier NX

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
#1

Hi:
I have a problem with MIPI CSI-2 by Jetson Xavier NX, as described below：
Description:
1.I’m trying to connect single camera(IMX219) using MIPI CSI-2 interface on Jetson Xavier NX, when i use below command “gst-launch-1…” it works well.
“gst-launch-1.0 nvarguscamerasrc ! ‘video/x-raw(memory:NVMM),width=3820, height=2464, framerate=21/1, format=NV12’ ! nvvidconv flip-method=0 ! ‘video/x-raw,width=960, height=616’ ! nvvidconv ! nvegltransform ! nveglglessink -e” ! xvimagesink -e"
2.I am using the Jetpack 4.4 and my camera is correctly recognized:
v4l2-ctl --all
Driver Info (not using libv4l2):
Driver name : tegra-video
Card type : vi-output, imx219 10-0010
Bus info : platform:15c10000.vi:2
Driver version: 4.9.140
Capabilities : 0x84200001
Video Capture
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04200001
Video Capture
Streaming
Extended Pix Format
Priority: 2
Video input : 0 (Camera 2: ok)
Format Video Capture:
Width/Height : 3264/2464
Pixel Format : ‘RG10’
Field : None
Bytes per Line : 6528
Size Image : 16084992
Colorspace : sRGB
Transfer Function : Default (maps to sRGB)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Full Range)
Flags :

Camera Controls

                 group_hold 0x009a2003 (bool)   : default=0 value=0 flags=execute-on-write
                sensor_mode 0x009a2008 (int64)  : min=0 max=0 step=0 default=0 value=0 flags=slider
                       gain 0x009a2009 (int64)  : min=0 max=0 step=0 default=0 value=49 flags=slider
                   exposure 0x009a200a (int64)  : min=0 max=0 step=0 default=0 value=33330 flags=slider
                 frame_rate 0x009a200b (int64)  : min=0 max=0 step=0 default=0 value=21000000 flags=slider
       sensor_configuration 0x009a2032 (u32)    : min=0 max=0 step=0 default=0 flags=read-only, volatile, has-payload
     sensor_mode_i2c_packet 0x009a2033 (u32)    : min=0 max=0 step=0 default=0 flags=read-only, volatile, has-payload
  sensor_control_i2c_packet 0x009a2034 (u32)    : min=0 max=0 step=0 default=0 flags=read-only, volatile, has-payload
                bypass_mode 0x009a2064 (intmenu): min=0 max=1 default=0 value=1
            override_enable 0x009a2065 (intmenu): min=0 max=1 default=0 value=1
               height_align 0x009a2066 (int)    : min=1 max=16 step=1 default=1 value=1
                 size_align 0x009a2067 (intmenu): min=0 max=2 default=0 value=0
           write_isp_format 0x009a2068 (int)    : min=1 max=1 step=1 default=1 value=1
   sensor_signal_properties 0x009a2069 (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
    sensor_image_properties 0x009a206a (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
  sensor_control_properties 0x009a206b (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
          sensor_dv_timings 0x009a206c (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
           low_latency_mode 0x009a206d (bool)   : default=0 value=0
           preferred_stride 0x009a206e (int)    : min=0 max=65535 step=1 default=0 value=0
               sensor_modes 0x009a2082 (int)    : min=0 max=30 step=1 default=30 value=5 flags=read-only

Question:
1.How to get the MIPI raw data from the Jetson board for analysis?
2.Are there any tools or method to debug mipi data?

Do you have any suggestions can provide our reference,
Thanks in advance.

1 Like
#3
  1. Using v4l2-ctl to capture RAW data from sensor.
v4l2-ctl -d /dev/video0 --set-fmt-video=width=3264,height=2464 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=1 --stream-to=test.raw
  1. Debug what MIPI?
#4

Hi @ShaneCCC :
Thank you for your reply.

  1. Using v4l2-ctl to capture RAW data from sensor.
v4l2-ctl -d /dev/video0 --set-fmt-video=width=3264,height=2464 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=1 --stream-to=test.raw

It’s work for me,thanks.
2. Debug what MIPI?
I want to modify the raw data obtained from MIPI,
Can you give some idea on this for me.

#5

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Sorry I don’t understand your problem here.

#7