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

    NVidia Jetson Jetpack 6 support?

    Scheduled Pinned Locked Moved VEYE MIPI camera
    55 Posts 3 Posters 33.5k Views 2 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.
    • O Offline
      Otca @Otca
      last edited by

      @otca Solved:

      ./mv_mipi_i2c.sh -r -f roi -b 9
      ./mv_mipi_i2c.sh -w -f roi -p1 0 -p2 0 -p3 1920 -p4 1080 -b 9
      ./mv_mipi_i2c.sh -r -f maxfps -b 9
      ./mv_mipi_i2c.sh -r -f fps -b 9
      ./mv_mipi_i2c.sh -w -f fps -p1 67 -b 9
      
      1 Reply Last reply Reply Quote 0
      • V Offline
        vitob
        last edited by

        Ok, I have the same mvcam imx296m with adp-mv1 adapter connected to Orin nx 16GB board from seeed studio.
        IMG_3473.jpg

        I used overlay dtbo loading method. The ‘sudo insmod veye_mvcam.ko’ ran w/o error returning.
        But I got these errors checking ‘dmesg| grep -i mvcam’:
        IMG_3475.jpg

        What could be the reason? I tried both local build .ko and downloaded (latest version) .ko files. Same symptom.

        My system is R36.3 Jetpack 6.0.

        BTW, where does the tegra_camera.ko come from? I seem do not find place to compile it. Thanks.

        veye_xummV 2 Replies Last reply Reply Quote 0
        • V Offline
          vitob
          last edited by

          Also, besides the tegra-camera.ko question, I noticed the v4l2-core/*.ko also different between nvidia_jetson_veye_bsp release tar ball and default *.ko in /lib/modules/$(uname -r)/kernel/drivers/media/v4l2-core/. How are these *.ko files are compiled in nvidia_jetson_veye_bsp.tar.gz and where are the source files?

          sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/upstream/*.ko /lib/modules/$(uname -r)/kernel/drivers/media/v4l2-core/ -f

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

            @vitob
            I think the first thing you need to check is whether this baseboard from seed is compatible with the official nVidia carrier board and whether it uses the same dtb?

            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.)

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

              @vitob Pls try to get version:
              https://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide#model

              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.)

              V 1 Reply Last reply Reply Quote 0
              • V Offline
                vitob @veye_xumm
                last edited by vitob

                @veye_xumm

                nvidia@ubuntu:/work/git_repo/nvidia_jetson_veye_bsp/mv_tools_jetson/i2c_tools$ ./mv_mipi_i2c.sh -r -f model -b 0
                model 0 not recognized
                nvidia@ubuntu:/work/git_repo/nvidia_jetson_veye_bsp/mv_tools_jetson/i2c_tools$ ./mv_mipi_i2c.sh -r -f model -b 1
                model 0 not recognized
                nvidia@ubuntu:/work/git_repo/nvidia_jetson_veye_bsp/mv_tools_jetson/i2c_tools$ ./mv_mipi_i2c_new.sh -r -f model -b 1
                NOT SUPPORTED!
                nvidia@ubuntu:/work/git_repo/nvidia_jetson_veye_bsp/mv_tools_jetson/i2c_tools$ ./mv_mipi_i2c_new.sh -r -f model -b 0
                NOT SUPPORTED!

                1 Reply Last reply Reply Quote 0
                • V Offline
                  vitob @veye_xumm
                  last edited by

                  @veye_xumm , let me confirm this, although I used sdkmanager to flash the board with nvidia native packages w/o issues.

                  veye_xummV 1 Reply Last reply Reply Quote 0
                  • V Offline
                    vitob @vitob
                    last edited by

                    @vitob said in NVidia Jetson Jetpack 6 support?:

                    tegra-camera.ko question, I noticed the v4l2-core/*.ko

                    In the meantime, can you help explain this question on tegra-camera.ko and v4l2-core/*.ko? Why they needs to be updated and where can I find the source code of them? Once updating them using the veye release .ko, will that affect other cameras (for example, I want to port/develop driver for another sensor myself)? Thanks.

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

                      @vitob
                      Please use -b 9 or -b 10 as an argument.

                      https://wiki.veye.cc/index.php/I2c_bus_number_and_video_node

                      For i2c bus number, please refer to this link above.

                      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
                      • veye_xummV Offline
                        veye_xumm @vitob
                        last edited by

                        @vitob said in NVidia Jetson Jetpack 6 support?:

                        In the meantime, can you help explain this question on tegra-camera.ko and v4l2-core/*.ko? Why they needs to be updated and where can I find the source code of them? Once updating them using the veye release .ko, will that affect other cameras (for example, I want to port/develop driver for another sensor myself)? Thanks.

                        These driver changes add support for RAW8 RAW10 RAW12 data types on the one hand, and externally triggered modes on the other.
                        Their code reference:
                        https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/kernel_patch_4_mv/l4t-r36.3

                        Compile step by step reference::
                        https://wiki.veye.cc/index.php/VEYE_CS_Camera_source_for_Jetson

                        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 1

                        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