Navigation

    VEYE IMAGING Forum

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

    SOLVED How to rotate VEYE-MIPI-IMX385 camera video on Jetson Xavier NX?

    VEYE MIPI camera
    2
    8
    651
    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.
    • M
      maponarooo last edited by

      Hi~
      I would like to rotate my VEYE-MIPI-IMX385 camera video on Jetson Xavier NX.
      How do I do?

      quad@xavier-nx:~/raspberrypi/i2c_cmd/bin$ ./veye_mipi_i2c.sh -r -f mirrormode
      ./veye_mipi_i2c.sh: line 216: ./i2c_write: No such file or directory
      ./veye_mipi_i2c.sh: line 217: ./i2c_write: No such file or directory
      ./veye_mipi_i2c.sh: line 218: ./i2c_write: No such file or directory
      ./veye_mipi_i2c.sh: line 220: ./i2c_read: No such file or directory
      r mirrormode is 0x7f

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

        @maponarooo
        Hi,

        ./i2c_write: No such file or directory
        

        So you have to check this file first.
        2. Please refer to http://wiki.veye.cc/index.php/VEYE_CS_Camera_for_Jetson_TX2#Video_Control_Toolkits_Manual
        part 4.3
        Use -b [bus number ] to identify the i2c bus you should use.

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

          @veye_xumm I have read already but I don't know....
          It's right?

          quad@xavier-nx:~/raspberrypi/i2c_cmd/bin$ dmesg | grep veye
          [ 2.027455] veyecam 9-003b: probing v4l2 sensor
          [ 2.027665] veyecam 9-003b: tegracam sensor driver:veyecam_v2.0.6
          [ 2.036713] veyecam 9-003b: probe failed
          [ 2.036892] veyecam 9-003b: board setup failed
          [ 2.037173] veyecam 10-003b: probing v4l2 sensor
          [ 2.037425] veyecam 10-003b: tegracam sensor driver:veyecam_v2.0.6
          [ 2.048517] veyecam 10-003b: camera id is veyecam
          [ 2.049259] veyecam 10-003b: sensor is IMX385
          [ 2.049399] veyecam 10-003b: board type is ONE board
          [ 2.049735] veyecam 10-003b: Detected VEYECAM sensor

          [ 3.086272] tegra194-vi5 15c10000.vi: subdev veyecam 10-003b bound
          quad@xavier-nx:~/raspberrypi/i2c_cmd/bin$ ./veye_mipi_i2c.sh -b 10
          quad@xavier-nx:~/raspberrypi/i2c_cmd/bin$

          quad@xavier-nx:~/raspberrypi/i2c_cmd/bin$ ./veye_mipi_i2c.sh -r -f mirrormode -b 10
          ./veye_mipi_i2c.sh: line 216: ./i2c_write: No such file or directory
          ./veye_mipi_i2c.sh: line 217: ./i2c_write: No such file or directory
          ./veye_mipi_i2c.sh: line 218: ./i2c_write: No such file or directory
          ./veye_mipi_i2c.sh: line 220: ./i2c_read: No such file or directory
          r mirrormode is 0x7f

          quad@xavier-nx:~/raspberrypi/i2c_cmd/bin$ ./veye_mipi_i2c.sh -r -f mirrormode -b 10-003b
          ./veye_mipi_i2c.sh: line 216: ./i2c_write: No such file or directory
          ./veye_mipi_i2c.sh: line 217: ./i2c_write: No such file or directory
          ./veye_mipi_i2c.sh: line 218: ./i2c_write: No such file or directory
          ./veye_mipi_i2c.sh: line 220: ./i2c_read: No such file or directory
          r mirrormode is 0x7f

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

            @maponarooo
            I see the problem, you are using the jetson board but using the program under raspberry pi.
            Please use the program at this link below.

            https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/i2c_cmd/bin

            M 2 Replies Last reply Reply Quote 0
            • M
              maponarooo @veye_xumm last edited by

              @veye_xumm Oh! my god....
              I'm so stupid...
              It works well... Thank you so much.

              I think this is a very good camera.
              But I prefer GUI apps over textual settings like this.
              When will VEYE-Imageing's GUI app be developed?
              I am very much looking forward to it.

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

                @veye_xumm But how can save the setting parameter against reboot?
                After rebooting, all configuration information was lost.

                and cannot change YUYV.

                quad@xavier-nx:~/nvidia_jetson_veye_bsp/i2c_cmd/bin$ sudo ./veye_mipi_i2c.sh -w -f yuvseq -p1 YUYV
                ====I2C write:<0x3b> <0x7> <0xfe>====
                Failed to write register index 0w YUVseq is YUYV
                quad@xavier-nx:~/nvidia_jetson_veye_bsp/i2c_cmd/bin$ sudo ./veye_mipi_i2c.sh -r -f yuvseq
                ====I2C write:<0x3b> <0x7> <0xfe>====
                Failed to write register index 0r YUVseq is UYVY

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

                  @maponarooo

                  When will VEYE-Imageing's GUI app be developed?

                  This feature would be great, but sorry, we don't have it in our development plans right now.

                  After rebooting, all configuration information was lost.

                  Yes, VEYE modules with 2M resolution do not support parameter saving now. It's a pity.

                  Failed to write register index 0w YUVseq is YUYV

                  Again,I think you lost -b [i2c bus] option. Please refer to this.
                  However, do not do this. jetson platform does not support YUYV format now.

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

                    @veye_xumm Can't save? Oh... It's really disappointing.
                    Anyway... Okay. Thank you.
                    I'll close this agenda.

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