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

    VEYE-imx462 and Orin Nano developer kit problem

    Scheduled Pinned Locked Moved VEYE MIPI camera
    17 Posts 2 Posters 4.8k 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.
    • veye_xummV Offline
      veye_xumm @joe
      last edited by

      @joe

      To confirm your I2C bus, please enter the following two commands and send the results back to me.

      ./veye_mipi_i2c.sh -r -f hdver -b 9
      
      ./veye_mipi_i2c.sh -r -f hdver -b 10
      

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

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

        @veye_xumm

        The results:

        ./veye_mipi_i2c.sh -r -f hdver -b 9
        hardware version is 0x 1
        release date is 20 1- 1- 1

        ./veye_mipi_i2c.sh -r -f hdver -b 10
        hardware version is 0x 7
        release date is 20 0- 0- 0

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

          @joe

          @joe said in VEYE-imx462 and Orin Nano developer kit problem:

          ./veye_mipi_i2c.sh -r -f hdver -b 10
          hardware version is 0x 7

          So your camera is connecting to i2c bus 10.

          Please use -b 10 as parameter for ./veye_mipi_i2c.sh

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

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

            @veye_xumm
            It seems that the parameters I've configured are retaining their previous values:

            ./veye_mipi_i2c.sh -b 10 -r -f mshutter
            r mshutter is 0x 0
            ./veye_mipi_i2c.sh -b 10 -w -f mshutter -p1 0x44
            w mshutter is 0x44
            ./veye_mipi_i2c.sh -b 10 -r -f mshutter
            r mshutter is 0x 0

            or

            ./veye_mipi_i2c.sh -b 10 -r -f mirrormode
            r mirrormode is 0x 0
            ./veye_mipi_i2c.sh -b 10 -w -f mirrormode -p1 0x02
            w mirrormode is 0x 2
            ./veye_mipi_i2c.sh -b 10 -r -f mirrormode
            r mirrormode is 0x 0

            Am I making a mistake somewhere?

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

              @joe Please try putting -b 10 at the end of the command.

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

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

                @veye_xumm
                I noticed that there is no difference when I change the order of '-b 10' to the end of the line in the command. I'm running the command from ~/nvidia_jetson_veye_bsp/i2c_cmd/bin; can you confirm if this path is correct? Additionally, I'm open to any alternative solutions or suggestions. Thanks in advance for your help!

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

                  @joe said in VEYE-imx462 and Orin Nano developer kit problem:

                  ./veye_mipi_i2c.sh -r -f hdver -b 10
                  hardware version is 0x 7

                  From this point, your program reads hdver correctly.

                  However, based on the feedback from all your other scripts, it seems that both reading and writing cannot be executed properly.

                  Here are the commands and displays from my side. The difference is that the camera is connected to i2c-9.
                  5023688b-591f-46d9-bea8-924c7817aab7-image.png

                  How about you try recompiling i2c_read and i2c_write?
                  i2c_cmd/source/i2c_tools

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

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

                    @veye_xumm
                    It work, after change the mipi connector! (I use -b 9.)
                    Thanks

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

                      @joe
                      It is indicated in the documents about "New function list" that:
                      "The following new features are only supported in camera's firmware versions with release time later than 2022-11-22."
                      My firmware version is exactly 2022-11-22. Is this version support "New function list"?

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

                        @joe yes

                        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