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

    在orin nano 8G上尝试使用cssc132失败

    Scheduled Pinned Locked Moved CS MIPI camera
    10 Posts 2 Posters 130 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.
    • R Offline
      robot
      last edited by

      如题,我尝试在orin nano上测试cssc132相机,我第一次使用的是在我的内核中移植驱动的方式来操作的,但是取流失败,在内核中打印如下[sudo] password for mr123:
      mr123@mr123-desktop:~$ timeout 10s v4l2-ctl -d /dev/video0
      --stream-mmap=4
      --stream-count=30
      --stream-to=/dev/null
      --verbose
      VIDIOC_QUERYCAP: ok
      VIDIOC_REQBUFS returned 0 (Success)
      VIDIOC_QUERYBUF returned 0 (Success)
      VIDIOC_QUERYBUF returned 0 (Success)
      VIDIOC_QUERYBUF returned 0 (Success)
      VIDIOC_QUERYBUF returned 0 (Success)
      VIDIOC_QBUF returned 0 (Success)
      VIDIOC_QBUF returned 0 (Success)
      VIDIOC_QBUF returned 0 (Success)
      VIDIOC_QBUF returned 0 (Success)
      VIDIOC_STREAMON returned 0 (Success)
      mr123@mr123-desktop:~$ sudo dmesg -wT | grep -E 'cssc132|tegra-capture|nvcsi|rtcpu'
      [六 8月 1 17:38:50 2026] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
      [六 8月 1 17:38:53 2026] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
      [六 8月 1 17:38:55 2026] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
      [六 8月 1 17:38:58 2026] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
      ^C
      mr123@mr123-desktop:~$
      然后我换用预编译的驱动和设备树来测试,发现现象一致,其他信息,我用的版本是r36.5

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

        @robot 我有点怀疑你使用的相机型号是不是对应cssc132的驱动。可否拍个照片我看一下?

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

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          robot @veye_xumm
          last edited by

          @veye_xumm微信图片_20260803093003_68_2.jpg 微信图片_20260803093003_69_2.jpg 以上是我的相机照片,您确认一下

          R 1 Reply Last reply Reply Quote 0
          • R Offline
            robot @robot
            last edited by

            我今天会测试把nvidia的系统一烧进去,其他什么操作都不做就把git上预编译的ko和设备树按流程放进去来测试一下,测试完我也会同步进展,期待您的指导

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

              @robot 确实是CS-MIPI-SC32,这个型号挺老的了。你回头就按照这个步骤搞一下看看先。

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

              R 1 Reply Last reply Reply Quote 0
              • R Offline
                robot @veye_xumm
                last edited by

                @veye_xumm 我昨天测试了一天现象很奇怪,我第一次重刷成原厂系统后确实出图了,然后我又尝试的自编译驱动,也出图了,然后我逐步替换自编译的ko,然后替换到某个驱动的时候突然不行了,于是我回退开始确认这个现象,但是发现回退完还是不出图,然后我一路回退,回退到了预编译ko和设备树,发现也不行了!
                更离谱的是我再次重刷,然后按早上的步骤重刷系统和预编译驱动,还是不行!
                我现在想确认一下就是通过i2c配置的寄存器他是否会保存,断电后依然存在,是否可能是某个配置写死后没有清除导致的不恢复?

                R 1 Reply Last reply Reply Quote 0
                • R Offline
                  robot @robot
                  last edited by

                  另外我看wiki上面确实写了6.2.2搭配orin nano搭配cssc132相机确实是可以用的对吧,我只在昨天上午成功过一段时间,一直到现在都没有再成功过,我只能说我是完全按照wiki的步骤来的,这个现象太奇怪了,而且结合这个报错,有没有可能是我使用的fpc排线或者是开发板的差异,导致mipi信号畸变导致无法解析,如果可能的话能讲一下你们所使用的测试环境吗

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

                    @robot 我们就是用的nvidia orin nano的官方开发板,跟你图中差不多。
                    不过我们没有发不过【原厂系统】。 对于jetpack6.2.2,我们有发布dtbo和一套ko文件。只要把这些替换到nvidia原系统即可。
                    对应步骤是这个文章的:
                    7.4.3和7.5.3两步,然后按照8.1和8.2进行检测一下。
                    https://wiki.veye.cc/index.php?title=How_to_upgrade_the_Jetson_system_to_support_VEYE_cameras/zh

                    完成之后重新上电,可以执行 sudo dmesg |grep sc132,把输出结果给我看看。

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

                    R 2 Replies Last reply Reply Quote 0
                    • R Offline
                      robot @veye_xumm
                      last edited by

                      @veye_xumm 我说的原厂系统指的就是nvidia原厂系统,然后驱动用的是你们预编译的ko和dtbo,只做了这些操作

                      1 Reply Last reply Reply Quote 0
                      • R Offline
                        robot @veye_xumm
                        last edited by

                        @veye_xumm
                        mr123@ubuntu:~$ sudo dmesg |grep sc132
                        [sudo] password for mr123:
                        [ 11.962504] cs_sc132: module verification failed: signature and/or required key missing - tainting kernel
                        [ 11.964932] cssc132 9-003b: probing v4l2 sensor
                        [ 11.965743] cssc132 9-003b: tegracam sensor driver:cssc132_v2.0.6
                        [ 11.966346] cssc132 9-003b: read sensor id 0132
                        [ 11.966352] cssc132 9-003b: camera id is cs-mipi-sc132
                        [ 11.966405] tegra-camrtc-capture-vi tegra-capture-vi: subdev cssc132 9-003b bound
                        [ 11.970148] cssc132 9-003b: Detected CS_MIPI_SC132 camera
                        [ 11.977337] cssc132 10-003b: probing v4l2 sensor
                        [ 11.978659] cssc132 10-003b: tegracam sensor driver:cssc132_v2.0.6
                        [ 11.983230] cssc132 10-003b: cs_sc132_board_setup: error during i2c read probe (-121)
                        [ 11.983237] cssc132 10-003b: board setup failed
                        [ 11.983316] cssc132: probe of 10-003b failed with error -121
                        mr123@ubuntu:~$

                        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