Navigation

    VEYE IMAGING Forum

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

    SOLVED VEYE-imx462 and Orin Nano developer kit problem

    VEYE MIPI camera
    2
    17
    1617
    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.
    • J
      joe @veye_xumm last edited by

      @veye_xumm
      Thank you for your online response.
      What about my second question. Have I do something wrong that the values of parameters do not set?
      ./veye_mipi_i2c.sh -b 9 -r -f mshutter
      r mshutter is 0x 1
      ./veye_mipi_i2c.sh -b 9 -w -f mshutter -p1 0x44
      w mshutter is 0x44
      ./veye_mipi_i2c.sh -b 9 -r -f mshutter
      r mshutter is 0x 1
      It have the fix value every time i get it!

      Thank you for your ongoing support

      veye_xumm 1 Reply Last reply Reply Quote 0
      • veye_xumm
        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
        
        J 1 Reply Last reply Reply Quote 0
        • J
          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_xumm 1 Reply Last reply Reply Quote 0
          • veye_xumm
            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

            J 1 Reply Last reply Reply Quote 0
            • J
              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_xumm 1 Reply Last reply Reply Quote 0
              • veye_xumm
                veye_xumm @joe last edited by

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

                J 1 Reply Last reply Reply Quote 0
                • J
                  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_xumm 1 Reply Last reply Reply Quote 0
                  • veye_xumm
                    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

                    J 1 Reply Last reply Reply Quote 0
                    • J
                      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
                        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_xumm 1 Reply Last reply Reply Quote 0
                        • veye_xumm
                          veye_xumm @joe last edited by

                          @joe yes

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