GMSL setup for linux kernel and V4L2 Stack is too complicated.
- thurther more function argument and usage is changed across the kernel version
So
I have tried with different method. : Manually setup GMSL Serializer and Deserializer
using another I2C for GMSL Setup
Request
1. Register Value to set MAX96717 and MAX96716A for Transparent GMSL link
or
2. Perfect Demo description using MAX96716a + MAX96717 + IMX219(Rpi Camera V2)
- current state: QT V4L2 Utility does not power up the IMX219 Camera again.
- on debug message : media format is differ from camera and GMSL
I want to use GMSL as a transparent MIPI and I2C(or SPI) link.
Cameras and sensors is already tested for our CPU(Hailo5H or Qualcomm QCS6490)
For the GMSL test, On Rpi4 and Pri5, I use Kuiper linux ((MAX96716A EVK + RPI Camera Adapter + MAX96717 Board to RPI ) and its Qt V4L2 test utility.
I could not view from camera even though I use prebuilt KUIPER Linux.
- media format is not same among IMX219 and MAX96717, MAX96716A
- I2C setup is OK
But, Application or kernel is returned if the system does not have perfect parameter matching (camera to CPU(MIPI RX + ISP + V4L2+ Application) through GMSL Link.
...
Project Description
Drone Camera System
- EO Camera : IMX715 : MIPI 4-lane 3840x2160 30fps
- IR Camera : XenicsIR Dione320 : MIPI 2-lane 320x240 60fps
- IMU Sensor ( 6-axis Acc/Gygo) : I2C 400KHz)
- ToF sensor : SPI 25Mz
GMSL-1(max96717 : IR + IMU)
GMSL-2(max96717: EO + ToF)
--> Next Step : MAX9295 : EO+IR + ToF(SPI) + IMU(I2C) --- I-Pex Cable( Power(Seperated) + GMSL )