GX-MIPI-IMX662 on RK3588 with Kernel 6.1 - MIPI CSI Errors

[xLWvU7mX]

@veye_xumm
Thank you for your reply. The lenghts were:

• 20 cm from camera to adapter using stock white 22-pin FFC cable
• 10 cm from the adapter to the board itself using 31-pin cable.

I've done some experiments today with different cable length combinations and various results.

CSI0:

• 22-pin 20 cm + 31 pin 15 cm. 0 fps, ecc2, fs/fe, f_seq errors.
• 22-pin 10 cm + 31 pin 10 cm. 14-38 fps, very unstable with dropped buffers, ecc2, fs/fe, f_seq errors.
• 22-pin 20 cm + 31 pin 10 cm. 0 fps, ecc2, fs/fe, f_seq errors.
• 22-pin 10 cm + 31 pin 15 cm. 0 fps, ecc2, fs/fe, f_seq errors.

CSI1:

• 22-pin 20 cm + 31 pin 15 cm. 60 fps, no errors.
• 22-pin 10 cm + 31 pin 10 cm. 60 fps, crc, err_data errors.
• 22-pin 20 cm + 31 pin 10 cm. 60 fps, crc, err_data errors.
• 22-pin 10 cm + 31 pin 15 cm. 60 fps, no errors.

So, the new information is that CSI0 managed to receive at least some data and there are combinations of cable length (that are suprisingly longer) that make errors disappear completely on CSI1. As far as I can judge, this indicates hardware problems rather than issues with, for example, dt overlays.

Regarding your question about adapter board. Differential pairs are length matched. I will request information about impedance matching from the developer of that board. The adapter only contains voltage stab and I2C level adapter - MIPI lanes are connected directly.

[veye_xumm]

@xlwvu7mx
Based on our experience, under normal circumstances an FFC cable length within 50 cm does not cause any issues. We have tested a setup with a 20 cm FFC cable + an adapter board + a 50 cm FFC cable, and it worked normally. Could you please provide some photos of the actual setup so we can take a look?

[xLWvU7mX]

@veye_xumm
Sure, here is my setup.

The dev board is https://docs.armsom.org/armsom-sige7.

[veye_xumm]

@xlwvu7mx
I don't think it's a cable length issue or a DTS problem. Have you tried testing with a different adapter board or a different mainboard? I tested it with an Orange Pi CM5, using a 50cm FFC cable plus a 20cm FPC cable, and the image was very stable.

[xLWvU7mX]

@veye_xumm
With your setup in mind it seems that the issue can be in my adapter, main board or 31 pin FFC cable connection. I will continue investigation of the issue possibly with another main board and adapter. Thank you for your advice so far.

Also, I've noticed that GX manuals for Firefly and Orange Pi mention FFC cables that connect camera to the board directly and GX-MIPI-IMX662 Data Sheet page tells the camera now accepts I2C 1.8V level. So I think I will try direct connection as well.

[veye_xumm]

@xlwvu7mx said in GX-MIPI-IMX662 on RK3588 with Kernel 6.1 - MIPI CSI Errors:

Also, I've noticed that GX manuals for Firefly and Orange Pi mention FFC cables that connect camera to the board directly and GX-MIPI-IMX662 Data Sheet page tells the camera now accepts I2C 1.8V level. So I think I will try direct connection as well.

OK

[xLWvU7mX]

@veye_xumm
I have conducted some more experiments with another similar board, different kernel versions, with some electrical adapter modifications and a much shorter 31-pin FFC cable. The issue is exactly the same however.

I think the problem is probably in my adapter board, less likely in a board layout itself. I am considering making and FPC for direct connection from sensor to camera like ones that you now offer for Firefly boards.

Do you have any recomendations on a FPC cable design? And could you please confirm the 22-pin connector pinout featured on the GX-MIPI-IMX662 Data Sheet page (as I have seen both reset_gpio and pwdn_gpio pins in the driver source code where the page mentions only PWR_ENABLE).

[veye_xumm]

@xlwvu7mx said in GX-MIPI-IMX662 on RK3588 with Kernel 6.1 - MIPI CSI Errors:

Do you have any recomendations on a FPC cable design? And could you please confirm the 22-pin connector pinout featured on the GX-MIPI-IMX662 Data Sheet page (as I have seen both reset_gpio and pwdn_gpio pins in the driver source code where the page mentions only PWR_ENABLE).

Sorry, I am currently on the Spring Festival holiday. As for the camera, in fact only one pin is functional:PWR_ENABLE

https://wiki.veye.cc/index.php/GX-MIPI-IMX662_Data_Sheet

[xLWvU7mX]

@veye_xumm
Thanks for the answer, have a happy holiday!

[xLWvU7mX]

Sorry for bumping an old thread but I would like to provide an update that might be relevant.

Since the last post I've transitioned to custom designed FPC with length matching and impedance made correctly. With the same software stack, csi0 showed no progress (still getting those ecc errors), the csi1 worked perfectly.

I have also tried the recent fix to rk35xx_veye_bsp (13684db), and to my surprise, the situation is now different. The camera on csi0 now shows 60 fps picture, but with colors distorted (heavy red, green, blue splashes over the objects) and the dmesg shows the following:

[  110.638757] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638772] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638786] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638800] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638814] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638828] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638842] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638856] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638871] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) 
[  110.638891] (0xfdd30000)MIPI_CSI2 ERR1:0x1000 (err_data,vc: 0) 
[  110.638925] rockchip-mipi-csi2 mipi2-csi2: stream off, src_sd: 00000000ae59244c, sd_name:rockchip-csi2-dphy0
[  110.638935] rockchip-mipi-csi2 mipi2-csi2: stream OFF

When connected to csi1, the picture is as good as always.

I hope that my update will help you with your debugging effort. Feel free to ask me to do some additional testing.

@veye_xumm