VEYE IMAGING Forum
    • Categories
    • Tags
    • Recent
    • Popular
    • Users
    • WIKI
    • veye.cc
    • Register
    • Login

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

    Scheduled Pinned Locked Moved Rockchip App camera
    15 Posts 2 Posters 2.5k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • X Offline
      xLWvU7mX @veye_xumm
      last edited by

      @veye_xumm
      Sure, here is my setup.

      2026-02-02-13-36-31-303 (2).jpg
      2026-01-31-14-49-32-189 (2).jpg
      623a5d12-b85b-48e8-93a6-f524d5258cfe (2).jpg

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

      veye_xummV 1 Reply Last reply Reply Quote 0
      • veye_xummV Offline
        veye_xumm @xLWvU7mX
        last edited by

        @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.
        efa107c1-7fe2-4ce4-ab96-d28934fc0c42-image.png

        Questions will be answered as soon as possible, please be patient.
        如果你使用中文,请直接用中文提问。
        May the force be with YOU. (This is the translation of the mysterious Chinese symbol above.)

        X 1 Reply Last reply Reply Quote 0
        • X Offline
          xLWvU7mX @veye_xumm
          last edited by

          @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_xummV 1 Reply Last reply Reply Quote 0
          • veye_xummV Offline
            veye_xumm @xLWvU7mX
            last edited by

            @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

            Questions will be answered as soon as possible, please be patient.
            如果你使用中文,请直接用中文提问。
            May the force be with YOU. (This is the translation of the mysterious Chinese symbol above.)

            X 1 Reply Last reply Reply Quote 0
            • X Offline
              xLWvU7mX @veye_xumm
              last edited by

              @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_xummV 1 Reply Last reply Reply Quote 0
              • veye_xummV Offline
                veye_xumm @xLWvU7mX
                last edited by

                @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

                Questions will be answered as soon as possible, please be patient.
                如果你使用中文,请直接用中文提问。
                May the force be with YOU. (This is the translation of the mysterious Chinese symbol above.)

                X 1 Reply Last reply Reply Quote 0
                • X Offline
                  xLWvU7mX @veye_xumm
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • X Offline
                    xLWvU7mX
                    last edited by

                    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

                    veye_xummV 1 Reply Last reply Reply Quote 0
                    • veye_xummV Offline
                      veye_xumm @xLWvU7mX
                      last edited by

                      @xLWvU7mX
                      Regarding your question, we have recently made some research progress that I'd like to share with you.

                      Concerning the signal robustness of MIPI CSI-2, we are planning a major board revision for the GX-MIPI-IMX662 in the near future. We will be adding a MIPI equalizer chip to it. We've already tested this addition, and it will significantly optimize and improve the transmission adaptability and robustness of the MIPI CSI-2 signals.

                      Additionally, during this board revision, we will also update the PCB dimensions to a 29x29mm two-board structure, which is identical to our MV series cameras. This redesign is expected to be completed within two months. Meanwhile, we will soon release a firmware update to optimize and upgrade the ISP image quality.

                      Additionally, during this board revision, we will also update the PCB dimensions to a 29x29mm two-board structure, which is identical to our MV series cameras. This redesign is expected to be completed within two months. Meanwhile, we will soon release a firmware update to optimize and upgrade the ISP image quality.

                      Questions will be answered as soon as possible, please be patient.
                      如果你使用中文,请直接用中文提问。
                      May the force be with YOU. (This is the translation of the mysterious Chinese symbol above.)

                      X 1 Reply Last reply Reply Quote 0
                      • X Offline
                        xLWvU7mX @veye_xumm
                        last edited by

                        @veye_xumm
                        I am looking forward to check out the revised version as soon as it is available. Thanks for digging into the signal integrity issues.

                        It would help greatly if you could provide newer version's connector pinout when it is stabilized so I could adjust and order the adapter FPC beforehand.

                        veye_xummV 1 Reply Last reply Reply Quote 0
                        • veye_xummV Offline
                          veye_xumm @xLWvU7mX
                          last edited by

                          @xLWvU7mX As planned, the interface of our redesigned camera module will be fully compatible with our current MV series products. You can check its pinout from this link: https://wiki.veye.cc/index.php?title=MV-MIPI-GMAX4002M_Data_Sheet.
                          Based on this, our ADP-MV1-V2 adapter board will be fully compatible and will convert the signals of the new GX-MIPI-IMX662 to match the legacy version. You can refer to the interface definition of the ADP-MV1-V2 here: https://wiki.veye.cc/index.php?title=ADP-MV1-V2_Adapter_Board_Data_Sheet

                          Questions will be answered as soon as possible, please be patient.
                          如果你使用中文,请直接用中文提问。
                          May the force be with YOU. (This is the translation of the mysterious Chinese symbol above.)

                          1 Reply Last reply Reply Quote 0

                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                          With your input, this post could be even better 💗

                          Register Login
                          • First post
                            Last post