MIPI-CSI camera migration to Yocto Scarthgap

Hi @ritesh.tx,

Thank you for your help.
The kernel panic I see is what results from running the gst pipeline. I have not found a solution to that problem.
I had also noticed the “single-master” property and patched it out as shown below on the device tree as printed out via the “dtc -I fs /sys/firmware/devicetree/base” command. Unfortunately, the change had no effect on my problem.

                    i2c@30a40000 {
                            pinctrl-names = "default\0gpio";
                            #address-cells = <0x01>;
                            pinctrl-0 = <0x3e>;
                            interrupts = <0x00 0x25 0x04>;
                            clocks = <0x02 0xcf>;
                            #size-cells = <0x00>;
                            clock-frequency = <0x61a80>;
                            compatible = "fsl,imx8mp-i2c\0fsl,imx21-i2c";
                            pinctrl-1 = <0x3f>;
                            status = "okay";
                            reg = <0x30a40000 0x10000>;
                            phandle = <0xee>;
                            scl-gpios = <0x2f 0x12 0x06>;
                            sda-gpios = <0x2f 0x13 0x06>;

                            basler_camera_vvcam@36 {
                                    csi_id = <0x00>;
                                    compatible = "basler,basler-camera-vvcam\0basler-camera-vvcam";
                                    status = "okay";
                                    reg = <0x36>;

                                    port {

                                            endpoint {
                                                    data-lanes = <0x01 0x02 0x03 0x04>;
                                                    clock-lanes = <0x00>;
                                                    remote-endpoint = <0x40>;
                                                    max-pixel-frequency = <0x00 0x1dcd6500>;
                                                    max-lane-frequency = <0x00 0x2cb41780>;
                                                    phandle = <0x76>;
                                                    max-data-rate = <0x00 0x00>;
                                                    link-frequencies = <0x00 0x2cb41780>;
                                            };
                                    };
                            };
                    };

Please see the responses below to the commands you requested:
root@verdin-imx8mp-15335644:~# ls /dev/video*
/dev/video0 /dev/video1 /dev/video2
root@verdin-imx8mp-15335644:~# v4l2-ctl --list-devices
[ 647.429100] enter isp_mi_stop
():
/dev/v4l-subdev0
/dev/v4l-subdev2
/dev/v4l-subdev3

(csi0):
/dev/v4l-subdev1

FSL Capture Media Device (platform:32c00000.bus:camera):
/dev/media0

VIV (platform:viv0):
/dev/video2

vsi_v4l2dec (platform:vsi_v4l2dec):
/dev/video1

vsi_v4l2enc (platform:vsi_v4l2enc):
/dev/video0

viv_media (platform:vvcam-video.0):
/dev/media1

root@verdin-imx8mp-15335644:~# v4l2-ctl -V
Format Video Capture Multiplanar:
Width/Height : 320/240
Pixel Format : ‘HEVC’ (HEVC)
Field : None
Number of planes : 1
Flags :
Colorspace : Default
Transfer Function : Default
YCbCr/HSV Encoding: Default
Quantization : Default
Plane 0 :
Bytes per Line : 320
Size Image : 131072

The “uname -r” command retrieves the following kernel versions.
For the Toradex Scarthgap build it is:
6.6.54-7.1.0-devel-gc39f69f2099d
For the non-Toradex Scarthgap build it is:
6.6.23-imx8mp-imx8mp-g57758995c38a

According to your release matrix:

It seems my build is not using the correct kernel version for the Verdin i.MX8M Plus. How do I correctly set that within my build?