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

    IMX385 on Jetson Xavier NX JetPack5.01DP can't find camera

    Scheduled Pinned Locked Moved VEYE MIPI camera
    25 Posts 2 Posters 9.4k 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.
    • M Offline
      maponarooo
      last edited by maponarooo

      Hello~

      I have done as following manual.
      http://wiki.veye.cc/index.php/VEYE_CS_Camera_for_Jetson_TX2
      But can't find camera.
      What is the matter?

      ls /sys/bus/i2c/drivers/
      bd9571mwv ir-kbd-i2c max_gmsl_dp_ser rk808 tps65132
      bq27xxx-battery lp855x nvvrs_pseq rohm-bd718x7 veye_imx335
      dummy max77620 pca953x sec_pmic
      imx390 max9295 pca954x tegra_edid
      ina3221 max9296 'PEX9749 thermal sensor' tmpm32xi2c

      $ sudo ls /proc/device-tree/cam_i2cmux/i2c@*
      [sudo] password for quad:
      /proc/device-tree/cam_i2cmux/i2c@0:
      '#address-cells' name phandle rbpcv2_veyeimx335_a@3b reg '#size-cells'

      /proc/device-tree/cam_i2cmux/i2c@1:
      '#address-cells' name phandle rbpcv2_veyeimx335_c@3b reg '#size-cells'

      quad@quad-nx:~$ dmesg | grep veye
      [ 26.342849] veye_imx335: loading out-of-tree module taints kernel.
      [ 26.343769] veye_imx335 9-003b: probing v4l2 sensor
      [ 26.344068] veye_imx335 9-003b: tegracam sensor driver:veyecam_v2.0.6
      [ 26.403074] veye_imx335 9-003b: probe failed
      [ 26.403213] veye_imx335 9-003b: board setup failed
      [ 26.403519] veye_imx335 10-003b: probing v4l2 sensor
      [ 26.403737] veye_imx335 10-003b: tegracam sensor driver:veyecam_v2.0.6
      [ 26.462606] veye_imx335 10-003b: veyecam_identify_module: invalid sensor model id: 117217536
      [ 26.462826] veye_imx335 10-003b: board setup failed

      ls /dev/video*
      ls: cannot access '/dev/video*': No such file or directory

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

        @maponarooo
        Hi，
        Which camera do you use indeed?
        IMX385 or IMX335? Plese use the correct 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.)

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

          @veye_xumm These are Xavier NX dtbs. Which one is IMX385 dtb?

          quad@quad-nx:~/QIDS/nvidia_jetson_veye_bsp/dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb$ ls

          common CS-MIPI-SC132 VEYE-MIPI-CAM2M
          CS-MIPI-IMX307 CS-MIPI-SC132-fpdlink VEYE-MIPI-CAM2M-fpdlink
          CS-MIPI-IMX307-fpdlink MV-MIPI-CAM VEYE-MIPI-IMX335

          $ find . -name tegra194-p3668-0000-p3509-0000.dtb
          ./dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb/CS-MIPI-SC132/tegra194-p3668-0000-p3509-0000.dtb
          ./dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb/VEYE-MIPI-CAM2M-fpdlink/tegra194-p3668-0000-p3509-0000.dtb
          ./dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb/VEYE-MIPI-CAM2M/tegra194-p3668-0000-p3509-0000.dtb
          ./dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb/MV-MIPI-CAM/tegra194-p3668-0000-p3509-0000.dtb
          ./dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb/CS-MIPI-SC132-fpdlink/tegra194-p3668-0000-p3509-0000.dtb
          ./dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb/CS-MIPI-IMX307/tegra194-p3668-0000-p3509-0000.dtb
          ./dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb/VEYE-MIPI-IMX335/tegra194-p3668-0000-p3509-0000.dtb
          ./dtbs/Xavier-NX/JetPack_5.0.1_DP_Linux_JETSON_XAVIER_NX_TARGETS/dts dtb/CS-MIPI-IMX307-fpdlink/tegra194-p3668-0000-p3509-0000.dtb

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

            @maponarooo said in IMX385 on Jetson Xavier NX JetPack5.01DP can't find camera:

            VEYE-MIPI-CAM2M

            http://wiki.veye.cc/index.php/VEYE_CS_Camera_for_Jetson_TX2
            section 3.4

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

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

              @veye_xumm Okay. but can't play camera. What's the matter?
              4.2.3 gstreamer examples on Jetpack5.x

              $ gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)UYVY,width=(int)1920, height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)NV12" ! nv3dsink -e
              Setting pipeline to PAUSED ...
              Pipeline is live and does not need PREROLL ...
              Setting pipeline to PLAYING ...
              New clock: GstSystemClock
              ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed to allocate required memory.
              Additional debug info:
              gstv4l2src.c(660): gst_v4l2src_decide_allocation (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
              Buffer pool activation failed
              EOS on shutdown enabled -- waiting for EOS after Error
              Waiting for EOS...
              Caught SIGSEGV
              ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
              Additional debug info:
              gstbasesrc.c(3072): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
              streaming stopped, reason not-negotiated (-4)
              #0 0x0000ffff9b480f08 in __GI___poll
              #1 0x0000ffff9b5aeb30 in () at /lib/aarch64-linux-gnu/libglib-2.0.so.0
              #2 0x0000ffff9b5aeef0 in g_main_loop_run ()
              #3 0x0000ffff9b751ac4 in gst_bus_poll
              #4 0x0000aaaae8aa4980 in event_loop
              #5 0x0000aaaae8aa38c8 in main (argc=<optimized out>, argv=<optimized out>)
              Spinning. Please run 'gdb gst-launch-1.0 3457' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

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

                @maponarooo
                Sorry, I have not encountered this problem, this gstreamer command works just fine in our case.
                The 5.0.1DP version is unstable and has many bugs. NVIDIA should release a stable version soon, within a day or two, as far as I know.
                You can submit the problem to nvidia's forum, but I guess they won't give a solution and will make you wait for the next version. That's what I suggested.

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

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

                  @veye_xumm Oh! No.............

                  I have already build my applications all on JetPack5.01DP.
                  Why this is so complicate?
                  I can't wait new version....

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

                    @veye_xumm And this log is right?
                    $ dmesg | grep veye
                    [ 26.415448] veyecam: loading out-of-tree module taints kernel.
                    [ 26.418410] veyecam 9-003b: probing v4l2 sensor
                    [ 26.418573] veyecam 9-003b: tegracam sensor driver:veyecam_v2.0.6
                    [ 26.430446] veyecam 9-003b: probe failed VEYECAM_MODEL_ID_ADDR
                    [ 26.431893] veyecam 9-003b: board setup failed
                    [ 26.433188] veyecam 10-003b: probing v4l2 sensor
                    [ 26.433346] veyecam 10-003b: tegracam sensor driver:veyecam_v2.0.6
                    [ 26.444597] veyecam 10-003b: camera id is veyecam
                    [ 26.450485] veyecam 10-003b: sensor is IMX385
                    [ 26.451703] veyecam 10-003b: board type is ONE board
                    [ 26.453870] tegra-camrtc-capture-vi tegra-capture-vi: subdev veyecam 10-003b bound
                    [ 26.458594] veyecam 10-003b: Detected VEYECAM sensor

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

                      @maponarooo said in IMX385 on Jetson Xavier NX JetPack5.01DP can't find camera:

                      And this log is right?

                      Yes, the board have 2 mipi csi interface ,you connect just one camera.

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

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

                        @veye_xumm I have posted this matter at the nvidia forum site.
                        https://forums.developer.nvidia.com/t/xavier-nx-with-jetpack5-01dp-cant-play-veye-mipi-imx385-camera/223524
                        😢

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

                          @veye_xumm By any chance, does the IMX385 camera firmware version matter?

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

                            @maponarooo said in IMX385 on Jetson Xavier NX JetPack5.01DP can't find camera:

                            does the IMX385 camera firmware version matter?

                            I do not think so.

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

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

                              @veye_xumm NVIDIA has replied, but I don't know the meaning...
                              Pls explain what they say...

                              **Please collect the trace log to check.
                              Also be aware below for r35 release.

                              Skew calibration is required if sensor or deserializer is using DPHY, and the output data rate is > 1.5Gbps.
                              An initiation deskew signal should be sent by sensor or deserializer to perform the skew calibration. If the deskew signals is not sent, the receiver will stall, and the capture will time out.
                              You can calculate the output data rate with the following equation:**
                              https://elinux.org/Jetson/l4t/Camera_BringUp

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

                                @maponarooo
                                Hi, we had a little test on our side in the last two days. On top of Jetpack 5.0.1DP, VEYE-MIPI-IMX385 does have some stability issues in acquiring images.

                                The easiest way is to solder off the component below.

                                dc288187-fe73-4f6e-8b86-ad71d1a1a23b-770d10756264feae6546276525f1b22.jpg

                                It may seem strange that a problem with jetpack software does need to be solved by hardware. But that's what I'm suggesting. To remove this device, the camera's reset pin is no longer in effect and does not affect the image output.

                                According to the post below, Jetpack 5.0.2 will be released soon, so let's look forward to this version.
                                https://forums.developer.nvidia.com/t/jetpack-5-0-2/223564

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

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

                                  @veye_xumm Which one is best way that solder off that part or wating JetPack5.02?

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

                                    @maponarooo
                                    If you have a soldering iron, of course, direct soldering to remove the device is the fastest. Otherwise you can wait a little for the official version of jetpack.

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

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

                                      @veye_xumm I have removed the part, but same...
                                      alt text
                                      alt text

                                      $ gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)UYVY,width=(int)1920, height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)NV12" ! nv3dsink -e
                                      Setting pipeline to PAUSED ...
                                      Pipeline is live and does not need PREROLL ...
                                      Setting pipeline to PLAYING ...
                                      New clock: GstSystemClock
                                      ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed to allocate required memory.
                                      Additional debug info:
                                      gstv4l2src.c(660): gst_v4l2src_decide_allocation (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
                                      Buffer pool activation failed
                                      Caught SIGSEGV
                                      EOS on shutdown enabled -- waiting for EOS after Error
                                      Waiting for EOS...
                                      ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
                                      Additional debug info:
                                      gstbasesrc.c(3072): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
                                      streaming stopped, reason not-negotiated (-4)
                                      #0 0x0000ffffaa65ef08 in __GI___poll
                                      #1 0x0000ffffaa78cb30 in () at /lib/aarch64-linux-gnu/libglib-2.0.so.0
                                      #2 0x0000ffffaa78cef0 in g_main_loop_run ()
                                      #3 0x0000ffffaa92fac4 in gst_bus_poll
                                      #4 0x0000aaaadbc84980 in event_loop
                                      #5 0x0000aaaadbc838c8 in main (argc=<optimized out>, argv=<optimized out>)
                                      Spinning. Please run 'gdb gst-launch-1.0 3567' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

                                      What do I do?

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

                                        @maponarooo
                                        Please try

                                        dmesg

                                        check if any errors.

                                        I guess it's a mipi transfer issue. Please check if the ffc cable connection is good?
                                        Can you take a photo of the details at the connector for me to see?

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

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

                                          @veye_xumm I think so... A lot of erros have occured.
                                          What's the matter?

                                          I have downloaded dtb file from here, is right?
                                          https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/ v1.08

                                          $dmesg
                                          ...........
                                          [ 11.723697] tegra186-cam-rtcpu bc00000.rtcpu: using cam RTCPU IRQ (49)
                                          [ 11.724017] tegra186-cam-rtcpu bc00000.rtcpu: tegra_camrtc_mon_create is successful
                                          [ 13.728334] bc00000.rtcpu:hsp-vm1: request 0x46000000: response timeout
                                          [ 13.728577] bc00000.rtcpu:hsp-vm1: FW_HASH failed: 0xffffff92
                                          [ 15.744350] bc00000.rtcpu:hsp-vm1: request 0x44bff000: response timeout
                                          [ 15.744575] tegra186-cam-rtcpu bc00000.rtcpu: RTCPU trace: IOVM setup error: -110
                                          [ 15.744789] tegra186-cam-rtcpu bc00000.rtcpu: trace boot sync failed: -5
                                          [ 17.760379] bc00000.rtcpu:hsp-vm1: request 0x44bfef80: response timeout
                                          [ 19.776342] bc00000.rtcpu:hsp-vm1: request 0x44bfec00: response timeout
                                          [ 19.776636] tegra-ivc-bus bc00000.rtcpu:ivc-bus: IOVM setup error: -110
                                          [ 19.776863] tegra186-cam-rtcpu bc00000.rtcpu: ivc-bus boot sync failed: -5
                                          [ 19.777135] tegra186-cam-rtcpu bc00000.rtcpu: firmware version cpu=rce cmd=0 sha1=0000000000000000000000000000000000000000
                                          [ 19.780143] tegra_aon c1a0000.aon: Adding to iommu group 5
                                          [ 19.783372] tegra_aon c1a0000.aon: tegra aon driver probe OK
                                          [ 19.785642] tegra186-aondbg aondbg: aondbg driver probe() OK
                                          [ 19.788426] denver_knobs_init:MTS_VERSION:53250041
                                          [ 19.793245] misc nvmap: cvsram :dma coherent mem declare 0x0000000050000000,4194304
                                          [ 19.793483] misc nvmap: created heap cvsram base 0x0000000050000000 size (4096KiB)
                                          [ 19.795579] t19x_cache tegra-cache: probed
                                          [ 19.802597] nvpmodel: initialized successfully
                                          [ 19.805375] trusty-irq trusty:irq: trusty_irq_create_irq_mapping failed (-22)
                                          [ 19.805670] trusty-irq trusty:irq: failed to initialize irq 14, irq will be ignored
                                          [ 19.806572] trusty-irq trusty:irq: trusty_irq_create_irq_mapping failed (-22)
                                          [ 19.806860] trusty-irq trusty:irq: failed to initialize irq 15, irq will be ignored
                                          [ 19.807257] genirq: Flags mismatch irq 10. 00004408 (trusty) vs. 00004408 (trusty)
                                          [ 19.807445] trusty-irq trusty:irq: request_percpu_irq failed -16
                                          [ 19.807617] trusty-irq trusty:irq: failed to initialize irq 29, irq will be ignored
                                          [ 19.816117] trusty-virtio trusty:virtio: initializing

                                          .........

                                          [ 22.356665] handlers:
                                          [ 22.359314] [<00000000a96125ca>] tegra_mcerr_hard_irq threaded [<00000000453e20de>] tegra_mcerr_thread
                                          [ 22.368379] Disabling IRQ #73
                                          [ 22.371490] arm-smmu 10000000.iommu: Unexpected global fault, this could be serious
                                          [ 22.379067] arm-smmu 10000000.iommu: GFSR 0x80000001, GFSYNR0 0x00000000, GFSYNR1 0x00000009, GFSYNR2 0x00000000
                                          [ 22.389706] mc-err: (255) csr_nvdisplayr: EMEM address decode error
                                          [ 22.389728] tegradccommon 15200000.display-hub: dma mapping done
                                          [ 22.395405] mc-err: status = 0x20064092; addr = 0x ffffffff00; hi_adr_reg=0xff
                                          [ 22.409216] mc-err: secure: yes, access-type: read
                                          [ 22.423949] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 1304000 KHz, changing to: 1344000 KHz
                                          [ 22.426592] usb 1-2: New USB device found, idVendor=0bda, idProduct=5489, bcdDevice= 1.40
                                          [ 22.427181] irq: IRQ254: trimming hierarchy from :pmc@c360000
                                          [ 22.427211] sdhci-tegra 3400000.sdhci: Got CD GPIO
                                          [ 22.427274] sdhci-tegra 3400000.sdhci: BWMGR client registration for eMC Successful
                                          [ 22.432996] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
                                          [ 22.438592] irq: IRQ255: trimming hierarchy from :pmc@c360000
                                          [ 22.438834] usb-conn-gpio 3520000.xusb_padctl:ports:usb2-0:connector: repeated role: 0
                                          [ 22.443461] usb 1-2: Product: 4-Port USB 2.0 Hub
                                          [ 22.443466] usb 1-2: Manufacturer: Generic
                                          [ 22.477139] hub 1-2:1.0: USB hub found
                                          [ 22.477382] tegra194-isp5 13e10000.host1x:isp@14800000: initialized
                                          [ 22.481102] sdhci-tegra 3400000.sdhci: wakeup init done, cdirq 255
                                          [ 22.497718] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000

                                          ............

                                          [ 26.041038] veyecam 9-003b: probe failed VEYECAM_MODEL_ID_ADDR
                                          [ 26.041924] veyecam 9-003b: board setup failed
                                          [ 26.042845] veyecam 10-003b: probing v4l2 sensor
                                          [ 26.043017] veyecam 10-003b: tegracam sensor driver:veyecam_v2.0.6
                                          [ 26.056874] veyecam 10-003b: camera id is veyecam
                                          [ 26.060518] tegra-adma 2930000.adma: Tegra210 ADMA driver registered 16 channels
                                          [ 26.062498] veyecam 10-003b: sensor is IMX385
                                          [ 26.063356] veyecam 10-003b: board type is ONE board
                                          [ 26.064574] tegra-camrtc-capture-vi tegra-capture-vi: subdev veyecam 10-003b bound
                                          [ 26.066694] using random self ethernet address
                                          [ 26.067608] using random host ethernet address
                                          [ 26.085329] veyecam 10-003b: Detected VEYECAM sensor
                                          [ 26.315653] tegra-hda 3510000.hda: Adding to iommu group 32
                                          [ 26.316210] tegra-hda 3510000.hda: Override SDO lines to 4
                                          [ 26.453528] nvadsp 2993000.adsp: Adding to iommu group 33
                                          [ 26.453738] nvadsp 2993000.adsp: in probe()...
                                          [ 26.454310] nvadsp 2993000.adsp: nvadsp_app_module_probe
                                          [ 26.478915] tegra-asoc: sound: Adding to iommu group 33
                                          [ 26.484139] input: NVIDIA Jetson Xavier NX HDA HDMI/DP,pcm=3 as /devices/platform/3510000.hda/sound/card0/input7
                                          [ 26.484400] input: NVIDIA Jetson Xavier NX HDA HDMI/DP,pcm=7 as /devices/platform/3510000.hda/sound/card0/input8
                                          [ 26.484620] input: NVIDIA Jetson Xavier NX HDA HDMI/DP,pcm=8 as /devices/platform/3510000.hda/sound/card0/input9
                                          [ 26.484796] input: NVIDIA Jetson Xavier NX HDA HDMI/DP,pcm=9 as /devices/platform/3510000.hda/sound/card0/input10
                                          [ 26.566201] tegra210-adsp aconnect@2a41000:adsp_audio: Adding to iommu group 33
                                          [ 26.566257] tegra210_adsp_audio_probe: platform probe started
                                          [ 26.567403] tegra210-adsp tegra210-adsp: Default param-type to BYTE for mp3-dec1
                                          [ 26.568483] tegra210-adsp tegra210-adsp: Default param-type to BYTE for spkprot
                                          [ 26.569571] tegra210-adsp tegra210-adsp: Default param-type to BYTE for src
                                          [ 26.570751] tegra210-adsp tegra210-adsp: Default param-type to BYTE for aac-dec1
                                          [ 26.571806] tegra210-adsp tegra210-adsp: Default param-type to BYTE for aec
                                          [ 26.573328] tegra210-adsp tegra210-adsp: Default param-type to BYTE for wire
                                          [ 26.573344] tegra210-adsp tegra210-adsp: adma channel page address dt entry not found
                                          [ 26.573349] tegra210-adsp tegra210-adsp: using adma channel page 0
                                          [ 26.579987] nvadsp 2993000.adsp: ADSP OS firmware already loaded
                                          [ 26.683224] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd04000, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.684453] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd04000, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.685526] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd04040, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.686589] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd04080, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.688021] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd040c0, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.689272] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd040c0, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.690298] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd04100, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.691320] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd04140, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.692764] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd04140, fsynr=0x20012, cbfrsynra=0x1e, cb=31
                                          [ 26.692842] arm-smmu 12000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0x5fd04180, fsynr=0x20012, cbfrsynra=0x1e, cb=31

                                          [ 27.757176] nvadsp 2993000.adsp: ADSP OS Hanged or Crashed! Restarting...
                                          [ 27.758128] nvadsp 2993000.adsp: Dumping ADSP logs ........
                                          [ 27.759262] nvadsp 2993000.adsp: End of ADSP log dump .....
                                          [ 27.760045] nvadsp 2993000.adsp: dumping hwmailbox registers ...
                                          [ 27.760054] nvadsp 2993000.adsp: recv_hwmbox(): 0x0
                                          [ 27.760060] nvadsp 2993000.adsp: send_hwmbox(): 0x0
                                          [ 27.760065] nvadsp 2993000.adsp: dumping fault frame...
                                          [ 27.760892] nvadsp 2993000.adsp: r0 0x00000000 r1 0x00000000 r2 0x00000000 r3 0x00000000
                                          [ 27.761744] nvadsp 2993000.adsp: r4 0x00000000 r5 0x00000000 r6 0x00000000 r7 0x00000000
                                          [ 27.762602] nvadsp 2993000.adsp: r8 0x00000000 r9 0x00000000 r10 0x00000000 r11 0x00000000
                                          [ 27.763530] nvadsp 2993000.adsp: r12 0x00000000 usp 0x00000000 ulr 0x00000000 pc 0x00000000
                                          [ 27.764473] nvadsp 2993000.adsp: spsr 0x00000000
                                          [ 27.765262] nvadsp 2993000.adsp: dumping arm mode register data...
                                          [ 27.766037] nvadsp 2993000.adsp: fiq r13 0x00000000 r14 0x00000000
                                          [ 27.766820] nvadsp 2993000.adsp: irq r13 0x00000000 r14 0x00000000
                                          [ 27.767578] nvadsp 2993000.adsp: svc r13 0x00000000 r14 0x00000000
                                          [ 27.768467] nvadsp 2993000.adsp: und r13 0x00000000 r14 0x00000000
                                          [ 27.769204] nvadsp 2993000.adsp: sys r13 0x00000000 r14 0x00000000
                                          [ 27.769961] nvadsp 2993000.adsp: abt r13 0x00000000 r14 0x00000000

                                          [ 31.712362] nvadsp 2993000.adsp: ADSP OS loading timed out
                                          [ 31.713460] nvadsp 2993000.adsp: Unable to start ADSP OS
                                          [ 31.714423] nvadsp 2993000.adsp: adsp failed to boot with ret = -62
                                          [ 31.715415] nvadsp 2993000.adsp: Dumping ADSP logs ........
                                          [ 31.716835] nvadsp 2993000.adsp: End of ADSP log dump .....
                                          [ 31.717854] nvadsp 2993000.adsp: dumping hwmailbox registers ...
                                          [ 31.717866] nvadsp 2993000.adsp: recv_hwmbox(): 0x0
                                          [ 31.717874] nvadsp 2993000.adsp: send_hwmbox(): 0x0
                                          [ 31.717880] nvadsp 2993000.adsp: dumping fault frame...
                                          [ 31.718888] nvadsp 2993000.adsp: r0 0x00000000 r1 0x00000000 r2 0x00000000 r3 0x00000000
                                          [ 31.719960] nvadsp 2993000.adsp: r4 0x00000000 r5 0x00000000 r6 0x00000000 r7 0x00000000
                                          [ 31.721095] nvadsp 2993000.adsp: r8 0x00000000 r9 0x00000000 r10 0x00000000 r11 0x00000000
                                          [ 31.722195] nvadsp 2993000.adsp: r12 0x00000000 usp 0x00000000 ulr 0x00000000 pc 0x00000000
                                          [ 31.723240] nvadsp 2993000.adsp: spsr 0x00000000
                                          [ 31.724192] nvadsp 2993000.adsp: dumping arm mode register data...
                                          [ 31.725282] nvadsp 2993000.adsp: fiq r13 0x00000000 r14 0x00000000
                                          [ 31.726304] nvadsp 2993000.adsp: irq r13 0x00000000 r14 0x00000000
                                          [ 31.727314] nvadsp 2993000.adsp: svc r13 0x00000000 r14 0x00000000
                                          [ 31.728334] nvadsp 2993000.adsp: und r13 0x00000000 r14 0x00000000
                                          [ 31.729342] nvadsp 2993000.adsp: sys r13 0x00000000 r14 0x00000000
                                          [ 31.733239] nvadsp 2993000.adsp: abt r13 0x00000000 r14 0x00000000

                                          [ 31.763421] nvadsp 2993000.adsp: ADSP has crashed too many times(1)
                                          [ 31.796385] ADSP Driver is not initialized
                                          [ 31.797365] ADSP Driver is not initialized
                                          [ 31.798338] ADSP Driver is not initialized
                                          [ 31.799251] ADSP Driver is not initialized
                                          [ 31.811470] tegra210-adsp: probe of tegra210-adsp failed with error -62
                                          [ 40.360373] [eqos_poll_for_swr][588][type:0x4][loga-0x0] poll_for_swr: timeout
                                          [ 40.360639] net eth0: failed to poll MAC Software reset

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

                                            @maponarooo
                                            What you post is the log of the system startup phase, which is normal.
                                            What I want to see is that you execute gstreamer to try to PREVIEW first, then run dmesg and see the corresponding error report.

                                            I guess it's a mipi transfer issue. Please check if the ffc cable connection is good?
                                            Can you take a photo of the details at the connector for me to see?

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

                                            M 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