Can you open either link A or link B camera on R32.6.1 or just link A camera ?
You could use the following tips to debug this:
gstreamer render green screen: no video received. It might be caused by MIPI lanes and MAX9296 pipeline incorrectly configuration.
check MAX9296 (0x48) video lock register (0x1DC => Pipeline X, 0x1FC => Pipeline Y, 0x21C => Pipeline Z, 0x23C => Pipeline U). If value is 0x01 which means there’s valid video on this pipeline), if value is 0x00, you might need to check your pipeline setting.
Make sure your serializer’s video is send by which stream id (st_id_sel in your code), this ID should match MAX9296 side pipeline’s receiving ID. e.g. MAX9296 0x50 = 0x02 , pipeline X is receiving stream ID = 2 from serializer.
I tried the boost, but it made no difference to the results.
gstreamer renders not green screen but background color of the desktop without the message " no reply from camera sensor…" on serial console. From my experience, the message “no reply from camera sensor…” is displayed on the serial console whenever gstreamer renders green screen.
checked the registers value and stream id and the value of the str_len acording to you advise.
I think there is no problem.
My code for the max9295 and max926 are resumble
variable st_id_sel for link A is 0x02 and for link B is 0x03.
As I mentioned before, even though two cameras connected with one max9296, I can see the video image from both of them on R32.5.1. with my drivers. It is no problem on R32.5.1 at all.
Even though two cameras connected with one max9296, gstreamer shows the video image from both of them on R32.5.1 with my drivers. I already confirmed the configuration for max9295 and max9296 was same as that for R32.6.1 by checking the values for all of the registers and variables to be written on max9295 and max9296. I have tried decreasing the CSI clock hz (by setting register at 0x320 ) from max9296 because the message like below appeared sometime.
I thought it was too high ( 1800Mhz : written value is 0x32). So I set the value to 0x2F(1500Mhz) , then I was able to see the video image from both cameras at 1 time in 2 times. But the stremaing the video image was stopped at the first frame when I set the value to 0x2C(1200Mhz).
It is able to see the video stream image of each port one by one with embedded_data_height=0 in DTB. So I don’t think the embedded data is attached to the video image data.
I don’t think VI or CSI driver works well in this case. Because there is no difference except L4T codes and because I confirmed there were many differences between the VI and CSI codes in R32.5.1 and those in R32.6.1 with executing diff.