Fail to preview from adv7280m since Jetpack-4.6.1 onward

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Dear Experts,

I would like to re-open an old ticket of myself as it was automatically closed 14 days after the last reply and also I needed to wait for new BSP releases in expecting that the issue could be resolve but it has not been the case yet: Cannot capture from adv7280m with Jetpack-4.6.1

For shortening the story, I borrowed and adapted the driver of adv7280m from the following post : ADV7280m configuration - #105 by hoanganhv1svm

Then I successfully ported for Xavier NX with Jetpack-4.5.1 : ADV7280M Special Effect

Until today, I have been testing the driver with Jetpack-4.6.1, Jetpack-4.6.2, Jetpack-4.6.3 and even Jetpack-5.0.2 but the issue still persists on Jetson Xavier NX.

However, the driver works perfectly with the TX2 NX for any Jetpack-4.6.x with the following patch : ADV7280m configuration - #69 by ShaneCCC

I found that in another discussion, @ShaneCCC proposed similar patch for Xavier NX (Jetpack-4.6.x) : Adv7282 PAL to MIPI CSI Linux Driver Development - #80 by ShaneCCC which is IMX219 Raw8 mode on the XavierNX: Disabling CRC - #9 by ShaneCCC

I then applied the patch and re-flash the rtcpu firmware as instructed but not any luck.

Below is the log with the patch applied to csi5_fops.c and the newly flashed rtcpu firmware :

nvidia@Jetson-XNX:~/Workspace$ v4l2-ctl --all -d /dev/video1 
Driver Info (not using libv4l2):
	Driver name   : tegra-video
	Card type     : vi-output, adv7280 8-0020
	Bus info      : platform:15c10000.vi:4
	Driver version: 4.9.255
	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 4: no power)
DV timings:
	Active width: 0
	Active height: 0
	Total width: 0
	Total height: 0
	Frame format: progressive
	Polarities: -vsync -hsync
	Pixelclock: 0 Hz
	Horizontal frontporch: 0
	Horizontal sync: 0
	Horizontal backporch: 0
	Vertical frontporch: 0
	Vertical sync: 0
	Vertical backporch: 0
	Standards: 
	Flags: 
Format Video Capture:
	Width/Height      : 720/507
	Pixel Format      : 'UYVY'
	Field             : None
	Bytes per Line    : 1536
	Size Image        : 778752
	Colorspace        : SMPTE 170M
	Transfer Function : Rec. 709
	YCbCr/HSV Encoding: ITU-R 601
	Quantization      : Limited Range
	Flags             : 

User Controls

                     brightness 0x00980900 (int)    : min=-128 max=127 step=1 default=0 value=0 flags=slider
                       contrast 0x00980901 (int)    : min=0 max=255 step=1 default=128 value=128 flags=slider
                     saturation 0x00980902 (int)    : min=0 max=255 step=1 default=128 value=128 flags=slider
                            hue 0x00980903 (int)    : min=-127 max=128 step=1 default=0 value=0 flags=slider
                 fast_switching 0x00981970 (bool)   : default=0 value=0

Camera Controls

           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=0
                override_enable 0x009a2065 (intmenu): min=0 max=1 default=0 value=0
                   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=1472
                   sensor_modes 0x009a2082 (int)    : min=0 max=30 step=1 default=30 value=30 flags=read-only


nvidia@Jetson-XNX:~/Workspace$ sudo ./max_clock.sh 
[sudo] password for nvidia: 
vi clock rate is:460800000
isp clock rate is:576000000
emc clock rate is:1866000000
nvcsi clock rate is:314000000
nvidia@Jetson-XNX:~/Workspace$ sudo ./trace_on.sh 
Run "sudo cat /sys/kernel/debug/tracing/trace" to visualize trace
nvidia@Jetson-XNX:~/Workspace$ sudo cat /sys/kernel/debug/tracing/trace > adv7280m.trace

adv7280m.trace (1.4 MB)

In the log file :

     kworker/0:0-4     [000] ....   892.894599: rtcpu_vinotify_event: tstamp:28375149639 tag:RESERVED_19 channel:0x23 frame:2 vi_tstamp:27531433856 data:0x01020003
     kworker/0:0-4     [000] ....   892.894600: rtcpu_vinotify_event: tstamp:28375149770 tag:FE channel:0x00 frame:2 vi_tstamp:28375060379 data:0x00000024
     kworker/0:0-4     [000] ....   892.894601: rtcpu_vinotify_event: tstamp:28375149919 tag:ATOMP_FE channel:0x00 frame:2 vi_tstamp:28375060380 data:0x00000000
     kworker/0:0-4     [000] ....   892.894601: rtcpu_vinotify_event: tstamp:28375150046 tag:RESERVED_19 channel:0x23 frame:0 vi_tstamp:27533640384 data:0x07020004
     kworker/0:0-4     [000] ....   892.894602: rtcpu_vinotify_event: tstamp:28375150203 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:28375069511 data:0x00010000
     kworker/0:0-4     [000] ....   892.894603: rtcpu_vinotify_event: tstamp:28375150333 tag:FS channel:0x00 frame:1 vi_tstamp:28375107479 data:0x00000014
     kworker/0:0-4     [000] ....   892.894604: rtcpu_vinotify_event: tstamp:28375150482 tag:ATOMP_FS channel:0x00 frame:1 vi_tstamp:28375107480 data:0x00000000
     kworker/0:0-4     [000] ....   892.894604: rtcpu_vinotify_event: tstamp:28375150609 tag:CHANSEL_PXL_SOF channel:0x23 frame:1 vi_tstamp:28375107531 data:0x00000001
     kworker/0:0-4     [000] ....   892.894605: rtcpu_vinotify_event: tstamp:28375150758 tag:RESERVED_19 channel:0x23 frame:1 vi_tstamp:27535147968 data:0x08020004
     kworker/0:0-4     [000] ....   892.894606: rtcpu_vinotify_event: tstamp:28375615989 tag:CHANSEL_PXL_EOF channel:0x23 frame:1 vi_tstamp:28375614440 data:0x01fa0002
     kworker/0:0-4     [000] ....   892.894607: rtcpu_vinotify_error: tstamp:28375692476 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:28375691622 data:0x00010000
     kworker/0:0-4     [000] ....   892.894607: rtcpu_vinotify_error: tstamp:28375730469 tag:CHANSEL_NOMATCH channel:0x10 frame:2 vi_tstamp:28375729631 data:0x000003c9
     kworker/0:0-4     [000] ....   892.894608: rtcpu_vinotify_event: tstamp:28375928849 tag:ATOMP_FRAME_DONE channel:0x23 frame:1 vi_tstamp:28375614455 data:0x00000000
     kworker/0:0-4     [000] ....   892.894609: rtcpu_vinotify_event: tstamp:28375928983 tag:RESERVED_19 channel:0x23 frame:1 vi_tstamp:27551369824 data:0x02020004
     kworker/0:0-4     [000] ....   892.894609: rtcpu_vinotify_event: tstamp:28375929132 tag:CHANSEL_FAULT channel:0x23 frame:1 vi_tstamp:28375614616 data:0x01fb0040

With :

CHANSEL_FAULT data bit field
    bit 16:31  LINE_NUMBER
    bit 15	DTYPE_MISMATCH
    bit 14	EMBED_INFRINGE
    bit 13	EMBED_LONG_LINE
    bit 12	EMBED_SPURIOUS
    bit 11	EMBED_RUNAWAY
    bit 10	EMBED_MISSING_LE
    bit 9	PIXEL_SHORT_LINE
    bit 8	PIXEL_LONG_LINE
    bit 7	PIXEL_SPURIOUS
    bit 6	PIXEL_RUNAWAY
    bit 5	PIXEL_MISSING_LE
    bit 4	PIXEL_LINE_TIMER
    bit 3	EMBED_EOF
    bit 2	EMBED_SOF
    bit 1	PIXEL_EOF
    bit 0	PIXEL_SOF

The trace shows the 0x01fb0040, with 0x40 means CHANSEL_FAULT of PIXEL_RUNAWAY.

I am really stuck and hope that you could help to point out what did happen btw the Jetpack-4.5.x and the later ones, please?

Best Regards,
Khang

2

Additional information : the resolution 720x507 come from the following discussion : Solved: iMX7D : NTSC Video Capture - NXP Community

3

I would suggest move the r35.1 for this module.

Thanks

4

Hi @ShaneCCC ,

I would suggest move the r35.1 for this module.

I did :

Until today, I have been testing the driver with Jetpack-4.6.1, Jetpack-4.6.2, Jetpack-4.6.3 and even Jetpack-5.0.2 but the issue still persists on Jetson Xavier NX.

But I will provide the log/trace again for that version.

6

Hi @ShaneCCC.

I re-did the test with the rce firmware mentioned here : Camera failed with log:VIFALC_TDSTATE on Jetpack5.0.2 - #4 by JerryChang :

[  163.622618] adv7280: adv7180_s_stream( enable=1 )
[  163.646224] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[  163.673106] [RCE] VM0 deactivating.VM0 activating.NVCSILP clock rate = 204000000 Hz.
[  163.673129] [RCE] tegra_nvcsi_stream_set_config(vm0, stream=4, csi=4)
[  163.673142] [RCE] MIPI clock = 102000 kHz, tHS-SETTLE = 0, tCLK-SETTLE = 0
[  163.673151] [RCE] ===== NVCSI Stream Configuration =====
[  163.673160] [RCE] stream_id: PP 4, csi_port: PORT E
[  163.673169] [RCE] Brick: PHY 2, Mode: D-PHY
[  163.673178] [RCE] Partition: CIL A, LP bypass: Enabled, Lanes: 1
[  163.673187] [RCE] Clock information:
[  163.673196] [RCE] MIPI clock rate: 102.00 MHz
[  163.673204] [RCE] T_HS settle: 0, T_CLK settle: 0
[  163.673213] [RCE] ======================================
[  163.673222] [RCE] tegra_nvcsi_stream_open(vm0, stream=4, csi=4)
[  163.673231] [RCE] nvcsi_calc_ths_settle ths_settle 25
[  163.673240] [RCE] nvcsi_calc_ths_settle ths_settle 25
[  163.673249] [RCE] nvcsi_calc_tclk_settle tclk_settle 33
[  163.678901] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[  163.692651] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 1, flags: 0, err_data 131072
[  163.709547] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 1, flags: 0, err_data 131072

Full dmesg and trace are attached.

dmesg.txt (94.8 KB)
adv7280m.trace2 (1.9 MB)

In the following video, I was able to capture from the beginning and nearly the end of the vokoscreen video but this rarely happened, and then failed multiple of times (same as Jetpak-4.6.x) : jp502-adv7280m-unstable.mkv - Google Drive

Regards,
K.

7

Did you try to adjust the output size in sensor driver to verify CHANSEL_SHORT_FRAME message?

8

Hi @ShaneCCC,

From the document of ADV7280x, output formats are either 720x507 for NTSC and 720x576 for PAL:

QDV7280_Output_Format
QDV7280_Output_Format1538×970 185 KB

I am testing with NTSC. So I have not had idea of what could be other values of height.

Btw, should I modify physical_w and physical_h in below device-tree node ?

            adv7280_e@20 {
                    compatible = "adi,adv7280-m";

                    /* I2C device address */
                    reg = <0x20>;

                    /* V4L2 device node location */
                    devnode = "video1";

                    /* Physical dimensions of sensor */
                    physical_w = "4.713";
                    physical_h = "3.494";

                    sensor_model = "adv7280-m";

                    use_sensor_mode_id = "false";

                    reset-gpios = <&mcp23008_27 2 GPIO_ACTIVE_LOW>;

                    ports {
                            #address-cells = <1>;
                            #size-cells = <0>;

                            port@0 {
                                    reg = <0>;
                                    adv7280_out0: endpoint {
                                            port-index = <4>; /* CSI E */
                                            bus-width = <1>;
                                            remote-endpoint = <&adv7280_csi_in0>;
                                    };
                            };
                    };
            };

Or should I add active_w and active_h as in following post : MIPI Streaming error issue - #3 by JerryChang ?

9

You can check by v4l2-ctl --list-formats-ext to confirm if modify the device tree otherwise need to modify from sensor driver.

10

Hi @ShaneCCC ,
There’s no such info from the driver in my system :

nvidia@Jetson-XNX:~$ v4l2-ctl --list-formats-ext -d /dev/video1 
ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

	[0]: 'UYVY' (UYVY 4:2:2)

Could it be a problem in recent BSPs?

While :

nvidia@Jetson-XNX:~$ v4l2-ctl --all -d /dev/video1 
Driver Info:
	Driver name      : tegra-video
	Card type        : vi-output, adv7280 8-0020
	Bus info         : platform:tegra-capture-vi:4
	Driver version   : 5.10.104
	Capabilities     : 0x84200001
		Video Capture
		Streaming
		Extended Pix Format
		Device Capabilities
	Device Caps      : 0x04200001
		Video Capture
		Streaming
		Extended Pix Format
Media Driver Info:
	Driver name      : tegra-camrtc-ca
	Model            : NVIDIA Tegra Video Input Device
	Serial           : 
	Bus info         : 
	Media version    : 5.10.104
	Hardware revision: 0x00000003 (3)
	Driver version   : 5.10.104
Interface Info:
	ID               : 0x0300001b
	Type             : V4L Video
Entity Info:
	ID               : 0x00000019 (25)
	Name             : vi-output, adv7280 8-0020
	Function         : V4L2 I/O
	Pad 0x0100001a   : 0: Sink
	  Link 0x0200001f: from remote pad 0x1000006 of entity '13e10000.host1x:nvcsi@15a00000-': Data, Enabled
Priority: 2
Video input : 0 (Camera 4: ok)
DV timings:
	Active width: 0
	Active height: 0
	Total width: 0
	Total height: 0
	Frame format: progressive
	Polarities: -vsync -hsync
	Pixelclock: 0 Hz
	Horizontal frontporch: 0
	Horizontal sync: 0
	Horizontal backporch: 0
	Vertical frontporch: 0
	Vertical sync: 0
	Vertical backporch: 0
	Standards: 
	Flags: 
Format Video Capture:
	Width/Height      : 720/507
	Pixel Format      : 'UYVY' (UYVY 4:2:2)
	Field             : None
	Bytes per Line    : 1472
	Size Image        : 746304
	Colorspace        : SMPTE 170M
	Transfer Function : Rec. 709
	YCbCr/HSV Encoding: ITU-R 601
	Quantization      : Limited Range
	Flags             : 

User Controls

                     brightness 0x00980900 (int)    : min=-128 max=127 step=1 default=0 value=0 flags=slider
                       contrast 0x00980901 (int)    : min=0 max=255 step=1 default=128 value=128 flags=slider
                     saturation 0x00980902 (int)    : min=0 max=255 step=1 default=128 value=128 flags=slider
                            hue 0x00980903 (int)    : min=-127 max=128 step=1 default=0 value=0 flags=slider
                 fast_switching 0x00981970 (bool)   : default=0 value=0

Camera Controls

           sensor_configuration 0x009a2032 (u32)    : min=0 max=4294967295 step=1 default=0 [22] flags=read-only, volatile, has-payload
         sensor_mode_i2c_packet 0x009a2033 (u32)    : min=0 max=4294967295 step=1 default=0 [1026] flags=read-only, volatile, has-payload
      sensor_control_i2c_packet 0x009a2034 (u32)    : min=0 max=4294967295 step=1 default=0 [1026] flags=read-only, volatile, has-payload
                    bypass_mode 0x009a2064 (intmenu): min=0 max=1 default=0 value=0
				0: 0 (0x0)
				1: 1 (0x1)
                override_enable 0x009a2065 (intmenu): min=0 max=1 default=0 value=0
				0: 0 (0x0)
				1: 1 (0x1)
                   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
				0: 1 (0x1)
				1: 65536 (0x10000)
				2: 131072 (0x20000)
               write_isp_format 0x009a2068 (int)    : min=1 max=1 step=1 default=1 value=1
       sensor_signal_properties 0x009a2069 (u32)    : min=0 max=4294967295 step=1 default=0 [30][18] flags=read-only, has-payload
        sensor_image_properties 0x009a206a (u32)    : min=0 max=4294967295 step=1 default=0 [30][16] flags=read-only, has-payload
      sensor_control_properties 0x009a206b (u32)    : min=0 max=4294967295 step=1 default=0 [30][36] flags=read-only, has-payload
              sensor_dv_timings 0x009a206c (u32)    : min=0 max=4294967295 step=1 default=0 [30][16] 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=1472
                   sensor_modes 0x009a2082 (int)    : min=0 max=30 step=1 default=30 value=30 flags=read-only
11

Not sure if below info is relevant, but I got this during the repetition of gst-launch :

[ 1447.476903] adv7280 8-0020: Autodetection result: 00
[ 1447.477394] adv7280 8-0020: Interlaced video detected (status3=0x69)

[ 1453.074181] CPU:0, Error:rce-noc@0xbe00000,irq=21
[ 1453.074346] **************************************
[ 1453.074459] CPU:0, Error:rce-noc
[ 1453.074575]  Error Logger            : 0
[ 1453.074690]  ErrLog0                 : 0x80030000
[ 1453.074798]    Transaction Type      : RD  - Read, Incrementing
[ 1453.074912]    Error Code            : SLV
[ 1453.074986]    Error Source          : Target
[ 1453.075064]    Error Description     : Target error detected by CBB slave
[ 1453.075199]    Packet header Lock    : 0
[ 1453.075277]    Packet header Len1    : 3
[ 1453.075385]    NOC protocol version  : version >= 2.7
[ 1453.075489]  ErrLog1                 : 0x157600
[ 1453.075572]  ErrLog2                 : 0x0
[ 1453.075636]    RouteId               : 0x157600
[ 1453.075711]    InitFlow              : cpu_p_i/I/0
[ 1453.075794]    Targflow              : cbb_t/T/0
[ 1453.075872]    TargSubRange          : 27
[ 1453.075945]    SeqId                 : 0
[ 1453.076008]  ErrLog3                 : 0x5c01814
[ 1453.076081]  ErrLog4                 : 0x0
[ 1453.076146]    Address accessed      : 0x15c01814
[ 1453.076319]  ErrLog5                 : 0x387e31
[ 1453.076544]    Master ID             : RCE
[ 1453.076776]    Security Group(GRPSEC): 0x3f
[ 1453.077790]    Cache                 : 0x1 -- Bufferable
[ 1453.081990]    Protection            : 0x1 -- Privileged, Secure, Data Access
[ 1453.088203]    FALCONSEC             : 0x0
[ 1453.091609]    Virtual Queuing Channel(VQC): 0x0
[ 1453.096353]  **************************************
[ 1453.101544] CPU:0, Error:cbb-noc@0x2300000,irq=15
[ 1453.105959] **************************************
[ 1453.110944] CPU:0, Error:cbb-noc
[ 1453.113926]  Error Logger            : 0
[ 1453.117254]  ErrLog0                 : 0x80030000
[ 1453.120834]    Transaction Type      : RD  - Read, Incrementing
[ 1453.126170]    Error Code            : SLV
[ 1453.129325]    Error Source          : Target
[ 1453.133000]    Error Description     : Target error detected by CBB slave
[ 1453.139566]    AXI2APB_5 bridge error: RDFIFOF - Read Response FIFO Full interrupt
[ 1453.147176]    Packet header Lock    : 0
[ 1453.150850]    Packet header Len1    : 3
[ 1453.154521]    NOC protocol version  : version >= 2.7
[ 1453.159250]  ErrLog1                 : 0x9528aa
[ 1453.162834]  ErrLog2                 : 0x0
[ 1453.165463]    RouteId               : 0x9528aa
[ 1453.168789]    InitFlow              : rce_p2ps/I/rce_p2ps
[ 1453.173251]    Targflow              : host1x_p2pm/T/host1x_p2pm
[ 1453.178321]    TargSubRange          : 20
[ 1453.181557]    SeqId                 : 0
[ 1453.184357]  ErrLog3                 : 0x1814
[ 1453.187333]  ErrLog4                 : 0x0
[ 1453.189985]    Address accessed      : 0x15c01814
[ 1453.194682]  ErrLog5                 : 0x2af0fc71
[ 1453.198182]    Non-Modify            : 0x1
[ 1453.201595]    AXI ID                : 0x55
[ 1453.204488]    Master ID             : RCE
[ 1453.207830]    Security Group(GRPSEC): 0x3f
[ 1453.212009]    Cache                 : 0x1 -- Bufferable
[ 1453.216209]    Protection            : 0x3 -- Privileged, Non-Secure, Data Access
[ 1453.223033]    FALCONSEC             : 0x0
[ 1453.226183]    Virtual Queuing Channel(VQC): 0x0
[ 1453.230564]  **************************************
[ 1453.235980] Host read timeout at address 1814
[ 1453.240361] [RCE] VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.VM0 activating.VM0 deactivating.*** DATA ABORT EXCEPTION ***
[ 1453.240373] [RCE] R0:        15c00000        R1:     00001814        R2:     00008010        R3:     0000000a
[ 1453.349769] [RCE] R4:        0bcd0188        R5:     00000000        R6:     00000000        R7:     799ce800
[ 1453.349795] [RCE] R8:        0bcc27b0        R9:     0bcc27b2        R10:    0bcc27a8        R11:    00055ac0
[ 1453.349806] [RCE] R12:       0008e575        SP:     0bcc2768        LR:     0bcaaa2c        PC:     0bcaaa48
[ 1453.349813] [RCE] SPSR:      6000011f
[ 1453.349822] [RCE] DFSR:      00001008        DFAR:   15c01814        ADFSR:  00500000
[ 1453.349830] [RCE] IFSR:      00000000        IFAR:   00000000        AIFSR:  00000000
[ 1457.217836]  bc00000.rtcpu:hsp-vm1: request 0x42b640f4: response timeout
[ 1459.233810]  bc00000.rtcpu:hsp-vm1: request 0x42b640f4: response timeout
[ 1459.234004] tegra186-cam-rtcpu bc00000.rtcpu: rce full reset, retry 2/3
[ 1459.341767] [RCE] WARNING: core/hsp/hsp-vm.c:283 [camrtc_hsp_full_ss_isr] "VM0 issued IVC in inactive state."
[ 1460.321843] tegra194-vi5 15c10000.vi: capture control message timed out
[ 1460.322240] tegra-camrtc-capture-vi tegra-capture-vi: vi capture setup failed
[ 1461.345821] tegra194-vi5 15c10000.vi: capture control message timed out
[ 1461.346048] tegra194-vi5 15c10000.vi: csi_stream_release: failed to disable nvcsi tpg on stream 4 virtual channel 0

And gstreamer windows exits automatically after re-launching.

12

I would suggest using v4l2-ctl to verify the driver and HW first.
Looks like need to adjust the size by driver instead of device tree.

14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.