Navigation

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

    SOLVED VEYE-MIPI-IMX462 on Seeed J401 Carrier Board + Orin Nano 4GB (JetPack 6.2 / L4T 36.4.3) – No /dev/video Device Detected

    VEYE MIPI camera
    3
    11
    2522
    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.
    • veye_xumm
      veye_xumm @joe last edited by

      @joe

      @joe said in VEYE-MIPI-IMX462 on Seeed J401 Carrier Board + Orin Nano 4GB (JetPack 6.2 / L4T 36.4.3) – No /dev/video Device Detected:

      Questions:
      What could be preventing /dev/video0 from being created, even though the sensor is detected by the kernel?

      Under normal circumstances, as long as the I2C communication is working, the /dev/video0 node should be generated properly. Based on my initial assessment, your issue likely stems from differences in the usage of MIPI CSI pins between the J401 carrier board and NVIDIA's official developer kit when paired with the Orin Nano core module. Since our DTBO is based on the device tree of NVIDIA's official developer board, it may not be fully compatible with the J401 out of the box. You can try analyzing the full dmesg output to identify any errors. I suggest reaching out to Seeed for further assistance on this issue.

      J 1 Reply Last reply Reply Quote 0
      • J
        joe @veye_xumm last edited by

        @veye_xumm
        As you advised, I contacted Seeed Studio support for assistance. Their official response has made the situation clear. In short, Seeed Studio has confirmed they cannot and will not support the VEYE IMX462 camera on their J401 carrier board.

        Since the carrier board is the source of the incompatibility (due to its lack of support for your sensor in its device tree and drivers), I now need your help to find a working solution.

        Could you please provide a list of carrier boards for the Jetson Orin Nano module that you have tested and verified to be fully compatible with the VEYE IMX462 camera?

        Furthermore, I need to ensure that whichever carrier board is recommended has at least two MIPI CSI-2 connectors to run the IMX462 and AR0234 cameras together.

        Thank you for your time and support. I look forward to your detailed recommendations.

        veye_xumm 1 Reply Last reply Reply Quote 0
        • veye_xumm
          veye_xumm @joe last edited by

          @joe
          Regarding the I2C issue with the J401 baseboard, we have previously resolved it, and the engineers at Seeed Studio have documented the solution on their wiki. Here are two links for your reference.

          https://wiki.seeedstudio.com/Solution_for_the_Compatibility_Issue_between_reComputer_and_VEYE_Camera/

          https://forum.veye.cc/topic/539/imx327s-with-recomputer-xavier-nano/10

          J 1 Reply Last reply Reply Quote 0
          • J
            joe @veye_xumm last edited by joe

            @veye_xumm
            As I detailed in my initial post, I have already successfully applied that exact solution. The USB firmware update from that link is what allowed the kernel to detect the sensor, as shown by the dmesg | grep veye output I included.

            The current state is:

            -The USB firmware update is applied.

            -The kernel probe is successful for the connected camera at 9-003b.

            -The sensor is correctly identified as IMX462.

            -The problem persists: No /dev/video0 device node is created.

            veye_xumm J 2 Replies Last reply Reply Quote 0
            • veye_xumm
              veye_xumm @joe last edited by

              @joe Sorry for overlooking the information in the earliest post. I think the board in the link below is suitable, as it is compatible with the official nVidia development board.
              https://www.alibaba.com/product-detail/Nvidia-jetson-orin-nano-development-board_1600993126148.html?spm=a2747.product_manager.0.0.61e871d2RIVAmD

              J 1 Reply Last reply Reply Quote 0
              • J
                joe @veye_xumm last edited by

                @veye_xumm
                Thank you for providing this option. I will review it and follow up if I encounter any issues.

                1 Reply Last reply Reply Quote 0
                • J
                  john @joe last edited by

                  Hi @joe, @veye_xumm I have just encountered this issue, i.e., with a VEYE-MIPI-IMX462 camera on the Seeed J401 carrier board, flashed with Jetpack V6.2, except in this case with an Orin NX 8GB module.

                  It previously did work on exactly the same board (i.e., the /dev/video0 device was created) at Jetpack V6.1. Does that help explain anything?

                  Any ideas? (I need Jetpack V6.2 for PPP support, which was omitted from Jetpack V6.1).

                  Thanks
                  John

                  PS I found the Seeed reComputer J4011B with Jetpack 6.2 does not detect the Veye I2C address even though it is supplied with the "fixed" USB hub firmware (version 08B3). Very similar to the J401, but with an internal USB connection that is used for a mini-PCIe adapter "extension board" (perhaps this has upset the firmware fix).

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    john @john last edited by

                    Hi @joe, @veye_xumm, I have now tested the VEYE-MIPI-IMX462 on the Seeed reComputer J4011B with Jetpack V6.1, and found the same result as at V6.2, i.e., the Veye I2C address 0x3b is not detected. And this is even though Jetpack V6.1 works on the J401 carrier board (with the USB hub firmware patch applied).

                    Seeed Tech Support are monitoring the situation, and it may be the J401 B based reComputers are now a priority for Seeed. There is a chance that some further information could also inform their response to the lack of video device generation on the J401 at Jetpack V6.2.

                    I can test the J4011B with Jetpack V6.1 using the modified camera @veye_xumm sent me with the I2C address 0x22. This was when we were diagnosing the original detection problem on the J401. As long as the CSI pins have not been remapped, the issue could be another version of the USB hub firmware fault (e.g., maybe the J401B mini-PCIe expansion board is doing something with I2C). If the 0x22 address is detected on the J4011B it should prove to Seeed that the issue it not the Veye driver. But I would appreciate help with the Device Tree overlay.

                    I have changed the references to 0x3b in the DTS and DTSI include source to 0x22, but am getting errors like:

                    i2c i2c-9: of_i2c: modalias failure on /bus@0/cam_i2cmux/i2c@1/rbpcv3_veyecam_c@3b
i2c i2c-9: Failed to create I2C device for /bus@0/cam_i2cmux/i2c@1/rbpcv3_veyecam_c@3b

                    I am not very familiar with DTS files, and clearly I have missed something, can you help with this please?

                    Thanks
                    John

                    veye_xumm 1 Reply Last reply Reply Quote 0
                    • veye_xumm
                      veye_xumm @john last edited by

                      @john
                      We compared the baseboards of the J401 and J401B and found no differences. Regarding the earlier issue with the J401, we suspect that the USB hub chip, which is mounted on the same I2C bus as the camera, was intercepting responses for the I2C address 0x3b. This aligns with your hypothesis.

                      Could you visually inspect the J401B and check if there are any version or sub-model changes in the USB hub chip compared to the J401?

                      Regarding your intention to test the response issue at address 0x22, you do not need to recompile the device tree blob (dtb). You can directly use the command i2cdetect -y -r i2cnum to perform the test.

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        john @veye_xumm last edited by

                        Hi @veye_xumm, thank you again for all your help. I found that the VEYE camera you made available with I2C address 0x22 does work on the J401B. And now, after a long series of follow-ups with Seeed Tech Support, I found that i2cdump generates I2C transfer timeouts at address 0x3b (but only 0x3b!).

                        Then Seeed noted that applying the VEYE "compatibility fix" updating the USB Hub firmware to 08C3 removed the timeouts. So I tried that with the VEYE camera and it works! (This with Jetpack 6.1).

                        A weird puzzle remains, I was sure the J401B had USB Hub Firmware version 08C3 as supplied, although with one of the "devices" giving different details to 08C3 on the J401. Hence I did not expect to need the "compatibility fix", and had some concerns that reapplying it could cause a problem. But reapplying the update just now the firmware version was initially 08B3!?

                        It has updated to 08C3, and has fixed camera access to 0x3b.

                        This has been time consuming, but I might now test JetPack 6.2

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post