This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hi FPD-Link team,
I’m running FDP-Link III cameras with the Fusion 2 board on AM62A. Below is my setup:
So far, I've been successfully running IMX390 (based on FPD-Link III) with the above setup. However, I'm running into some issues with OV2312 (also FPD-Link III) which has 2 virtual channels, one for RGB and one for IR. The behaviors I’ve seen are:
When camera connected to CAM1:
When camera connected to CAM2:
This same OV2312 camera worked fine with Fusion 1 (FPD-Link III).
I'm using the UB960 driver in the Processor SDK Linux: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/media/i2c/ds90ub960.c?h=ti-linux-6.6.y.
Did I miss anything that made the 2-virtual-channel camera not to work?
Thank you.
Best regards,
Jianzhong
Hi Jianzhong,
I think the questions is for FPD Link team, so changing responsible organization.
Regards,
Brijesh
Hi Jianzhong,
In terms of FPD-Link devices there are not particular requirements to enable virtual channels. Do you know if the processor/SoC you are using is able to support virtual channels?
Hi Darrah,
Yes, the SoC supports virtual channels. The same OV2312 camera works fine with FPD-Link III deserializer. Could this be some compatibility issue between UB953 serializer and UB9702 deserializer?
I tried another FPD-Link III camera with Fusion 2. It's also not working. Streaming from camera to a display gives me a green screen.
Regards,
jianzhong
The 953 and 9702 are compatible devices. The FPDIV devices are backwards compatible with FPDIII devices, as long as you are operating in the backwards compatible mode. If the deserializer is receiving data from the serializer, it is likely being configured for the correct mode. It may be worth checking that the MIPI configurations between the camera - serializer interface and deserializer - processor interface match what is expected. For example, the number of MIPI lanes and the lane speeds. Additionally, have you checked the device registers for errors to determine if the data being output is valid?