Here are the three points you provided:
1. Using MEDIA_BUS_FMT_YUYV8_1X16: Since MIPI is a serial interface, I have naturally been using MEDIA_BUS_FMT_YUYV8_1X16. In this format, the first lane transmits Y values, while the second lane transmits CrCB values. I only tried MEDIA_BUS_FMT_YUYV8_2X8 on a whim, but it was not my primary setting.
2. Link Frequency: The rp1_cfe driver automatically calculates the link frequency based on the pixel rate. In the dummy sensor driver, I set the pixel rate to match our image sensor, and when I start the stream, the message "Using a link rate of 594Mbps" is displayed. Although I manually configured the link rate using the v4l2_ctrl_new_int_menu function, I still could not receive the video.
For reference, I only have the OV5647 image sensor available. When I configured the media-controller pipeline correctly, I was able to receive Bayer RAW data successfully. Even though the OV5647 driver does not explicitly set the link frequency, it displayed "Using a link rate of 416Mbps" and received RAW data without issues.
With the correct media-controller setup, the command v4l2-ctl -d 0 --stream-mmap --stream-count=10 --stream-to=output.raw successfully captured the stream.
3. Adapter Board and Cable: The PX6130 adapter board successfully received YUV422 video on the Raspberry Pi 4. I am also using the "RPI camera cable," which has successfully received video from the OV5647 sensor. Therefore, I do not suspect any hardware issues with the adapter board or the cable.
I believe the procedures I followed are correct. Although 6by9 kindly suggested reviewing examples using HDMI to MIPI or Analog to MIPI converters, those are not relevant in my case since I do not need to configure any HDMI or analog settings like these:
v4l2-ctl -d /dev/v4l-subdev2 --set-edid=file=1080P30EDID.txt (HDMI-related)
v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query (HDMI-related)
v4l2-ctl -d /dev/v4l-subdev2 -s pal (Analog-related)
Therefore, my question is: Is there anything else I need to configure regarding v4l-subdev2 like HDMI or Analog to MIPI convertor?
I truly appreciate 6by9's dedication and support. Thank you very much for your efforts!
1. Using MEDIA_BUS_FMT_YUYV8_1X16: Since MIPI is a serial interface, I have naturally been using MEDIA_BUS_FMT_YUYV8_1X16. In this format, the first lane transmits Y values, while the second lane transmits CrCB values. I only tried MEDIA_BUS_FMT_YUYV8_2X8 on a whim, but it was not my primary setting.
2. Link Frequency: The rp1_cfe driver automatically calculates the link frequency based on the pixel rate. In the dummy sensor driver, I set the pixel rate to match our image sensor, and when I start the stream, the message "Using a link rate of 594Mbps" is displayed. Although I manually configured the link rate using the v4l2_ctrl_new_int_menu function, I still could not receive the video.
For reference, I only have the OV5647 image sensor available. When I configured the media-controller pipeline correctly, I was able to receive Bayer RAW data successfully. Even though the OV5647 driver does not explicitly set the link frequency, it displayed "Using a link rate of 416Mbps" and received RAW data without issues.
With the correct media-controller setup, the command v4l2-ctl -d 0 --stream-mmap --stream-count=10 --stream-to=output.raw successfully captured the stream.
3. Adapter Board and Cable: The PX6130 adapter board successfully received YUV422 video on the Raspberry Pi 4. I am also using the "RPI camera cable," which has successfully received video from the OV5647 sensor. Therefore, I do not suspect any hardware issues with the adapter board or the cable.
I believe the procedures I followed are correct. Although 6by9 kindly suggested reviewing examples using HDMI to MIPI or Analog to MIPI converters, those are not relevant in my case since I do not need to configure any HDMI or analog settings like these:
v4l2-ctl -d /dev/v4l-subdev2 --set-edid=file=1080P30EDID.txt (HDMI-related)
v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query (HDMI-related)
v4l2-ctl -d /dev/v4l-subdev2 -s pal (Analog-related)
Therefore, my question is: Is there anything else I need to configure regarding v4l-subdev2 like HDMI or Analog to MIPI convertor?
I truly appreciate 6by9's dedication and support. Thank you very much for your efforts!
Statistics: Posted by stupid dog — Wed Feb 05, 2025 3:57 am