Dear Shane,
If i use v4l2-ctl or ioctl to capture raw data, the raw data is sensor original output, Jetson nano wont do any other format process, is it right?
Yes, thatās correct.
Dear Shane,
As i discuss with sensor vendor, they confirm it output UYVY format data. I think we shoud not use RGB565 or RGB1555 to view raw data.
As i check the raw data with YUV422 UYVY with below selected channels.
-
only select U and V
-
only select Y
From above attached image , Seems Y data is incorrect .
Do you have any opinion about it?
Hope your kindness reply.
Thanks a lot.
Can you try to modify the VI driver to try different data type setting from the VI_CSI_0_CSI_IMAGE_DT_0 REG. You can find it from the TRM.
Dear Shane,
Do you think try below data_type in TRM?
But i think maybe itās not helpful for our case.
Because MAX9286 output datatype shows as below :
If we try to modify it from YUV422 8bit to any other type, We will capture whole Green Image all the time.
How about configure the max output as RAW16 and Nano configure as YUV422_8 both of them are 2 bytes per pixel?
Dear Shane,
Finally, We fix this issue by modify the register of MAX96705.
Thank you so much for your kindness help.
Thank you !!
Hiā¦ I was trying to do the same thing but itās not workingā¦
The Jetson Nano connects to max9286/ max 9271 serdes and ov10635 cameraā¦
The I2C communication between board to ov10635 works fineā¦
So, I develop the device tree and camera driver for max9286 (acts as a sensor) only, based on imx219ā¦ But seems like itās not detecting /dev/video0ā¦
Do I need to add any additional GMSL configuration?
Which address do you use to probe? the max9286 address or the camera sensor address?
Hi,
Actually, you should use max9286 address for the driver,
What do you mean by āadditional GMSL configurationā?
And did you check kernel log why can not detect /dev/video0.
Thanks .
Hi xxforeā¦
Thank you for your replyā¦
By kernel log, do you meant the dmesg?
I have attached the error message from the dmesg as link belowā¦
As far as I understand from forum, it says that the error is because of bad dtsi. But Iām not sure what is wrong with itā¦ Should I also register the address for max 9271 serializer and ov10635 camera sensor in the dtsi?
My camera attached to CSI4. So I configure my device tree to use port-index=<2> cause it supposed to use CSI_C. But Iām not sure if itās the correct configuration
tegra210-camera-max9286.dtsi (3.0 KB)
Hi,
you have no need to regist MAX9271 and OV10635 in the dtsi.
But from your attached image , you probe the max9286 driver at address 0x30(if append RW byte, it should be 0x60), does it correct address for your MAX9286 device? Actually i cant see that address in the datasheet of MAX9286.
Additionally , from the attached image, it occure internal error, I think you should check that error first.
Thanks a lot.
Hi xxfore,
May I know what register did you correct to solve green frame issue. Currently I have configured DT and driver into 2 cameras and stream 2 cameras in 2560x800 window. The streaming image output shown blinking between āgood frameā and āgreen frameā for both cameras. How to remove āgreen frameā blanking in āgood frameā?
Hope can get your advise.
Dear ch.loh,
I think you should check VSYNC related registers.
Such as 0x00 bit EN_VS_GEN.
thx a lot.
Hi xxfore,
I have tried configure register 0x00 bit EN_VS_GEN to 0 or 1, the output is still blinking.
Attach is using gst-launch-1.0 recorded 2 cameras blinking pattern. (cam2 on right, please ignore the green noise on good frame due to cam2 hardware problem)
Do you have any idea?
Hi xxfore,
I found the root cause. The tegra mode on resolution shall match to the total camera width.
Thanks.