SOLVED IMX385 on Jetson Xavier NX JetPack5.01DP can't find camera
-
@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 -
@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 -
@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. -
@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. -
@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.... -
@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 -
@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.
-
@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
-
@veye_xumm By any chance, does the IMX385 camera firmware version matter?
-
@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.
-
@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 -
@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.
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 -
@veye_xumm Which one is best way that solder off that part or wating JetPack5.02?
-
@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. -
@veye_xumm I have removed the part, but same...
$ 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?
-
@maponarooo
Please trydmesgcheck 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? -
@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 -
@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? -
@veye_xumm When I look the ffc connection is fine.
This is gstreamer error log....
~$ 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.
Caught SIGSEGV
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...
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 0x0000ffff8b6ddf08 in __GI___poll
#1 0x0000ffff8b80bb30 in () at /lib/aarch64-linux-gnu/libglib-2.0.so.0
#2 0x0000ffff8b80bef0 in g_main_loop_run ()
#3 0x0000ffff8b9aeac4 in gst_bus_poll
#4 0x0000aaaace904980 in event_loop
#5 0x0000aaaace9038c8 in main (argc=<optimized out>, argv=<optimized out>)
Spinning. Please run 'gdb gst-launch-1.0 2954' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.After, dmesg logs....
$dmesg
[ 153.864552] ------------[ cut here ]------------
[ 153.864582] WARNING: CPU: 4 PID: 2970 at /dvs/git/dirty/git-master_linux/kernel/nvidia/drivers/platform/tegra/rtcpu/capture-ivc.c:47 tegra_capture_ivc_tx+0x118/0x150
[ 153.864913] Modules linked in: fuse xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter lzo_rle lzo_compress zram overlay bnep aes_ce_blk crypto_simd rtk_btusb snd_soc_tegra186_asrc cryptd ofpart snd_soc_tegra186_arad snd_soc_tegra186_dspk snd_soc_tegra210_ope snd_soc_tegra210_mvc btusb snd_soc_tegra210_afc cmdlinepart snd_soc_tegra210_iqc aes_ce_cipher snd_soc_tegra210_dmic ghash_ce btrtl snd_soc_tegra210_adx input_leds qspi_mtd snd_soc_tegra210_amx sha2_ce btbcm sha256_arm64 snd_soc_tegra210_i2s snd_soc_tegra210_admaif snd_soc_tegra210_mixer mtd btintel snd_soc_tegra210_sfc sha1_ce snd_soc_tegra_pcm leds_gpio snd_soc_tegra210_adsp snd_soc_spdif_tx pwm_fan snd_soc_tegra_machine_driver tegra210_adma snd_soc_tegra_utils tegra_bpmp_thermal snd_soc_simple_card_utils snd_soc_tegra210_ahub max77620_thermal rtl8822ce nvadsp userspace_alert cfg80211 snd_hda_codec_hdmi
[ 153.865326] spi_tegra210_qspi veyecam(O) snd_hda_tegra snd_hda_codec snd_hda_core spi_tegra114 binfmt_misc loop nvgpu ina3221 ip_tables x_tables
[ 153.865380] CPU: 4 PID: 2970 Comm: v4l2src0:src Tainted: G W O 5.10.65-tegra #1
[ 153.865385] Hardware name: NVIDIA Jetson Xavier NX Developer Kit (DT)
[ 153.865392] pstate: 60400009 (nZCv daif +PAN -UAO -TCO BTYPE=--)
[ 153.865401] pc : tegra_capture_ivc_tx+0x118/0x150
[ 153.865407] lr : tegra_capture_ivc_tx+0x2c/0x150
[ 153.865411] sp : ffff8000174837d0
[ 153.865417] x29: ffff8000174837d0 x28: ffff0000e8b25200
[ 153.865433] x27: 0000000040045612 x26: 0000000000000000
[ 153.865453] x25: 0000000000000118 x24: ffff0000eaa7b580
[ 153.865466] x23: ffff800017483900 x22: ffff0000bbb58e80
[ 153.865478] x21: ffff000083368400 x20: 0000000000000118
[ 153.865490] x19: ffff000083222080 x18: 0000000000000010
[ 153.865503] x17: 0000000000000000 x16: 0000000000000000
[ 153.865514] x15: ffff0000bbb593f0 x14: ffffffffffffffff
[ 153.865528] x13: ffff800097483627 x12: ffff80001748362f
[ 153.865549] x11: 69762d6572757470 x10: 61632d6172676574
[ 153.865562] x9 : 0000000000000000 x8 : ffff800017483a18
[ 153.865574] x7 : 000000000000ffff x6 : 0000000000000002
[ 153.865585] x5 : 0000000000000000 x4 : 0000000000000049
[ 153.865597] x3 : 0000000000000000 x2 : ffff8000101b6d10
[ 153.865612] x1 : 0000000000000000 x0 : 0000000000000000
[ 153.865630] Call trace:
[ 153.865638] tegra_capture_ivc_tx+0x118/0x150
[ 153.865645] tegra_capture_ivc_control_submit+0x34/0x60
[ 153.865653] vi_capture_ivc_send_control.isra.0+0x68/0x120
[ 153.865660] csi_stream_tpg_disable+0x70/0xb0
[ 153.865666] csi_stream_release+0x68/0xd0
[ 153.865673] vi_capture_shutdown+0x48/0xf0
[ 153.865680] vi_channel_close_ex+0x2c/0x80
[ 153.865697] vi5_channel_start_streaming+0x230/0x320
[ 153.865707] tegra_channel_start_streaming+0x50/0x80
[ 153.865721] vb2_start_streaming+0x6c/0x150
[ 153.865729] vb2_core_streamon+0x98/0x1a0
[ 153.865736] vb2_streamon+0x30/0x80
[ 153.865743] vb2_ioctl_streamon+0x54/0x60
[ 153.865750] v4l_streamon+0x3c/0x50
[ 153.865756] __video_do_ioctl+0x180/0x3f0
[ 153.865763] video_usercopy+0x27c/0x730
[ 153.865796] video_ioctl2+0x3c/0x180
[ 153.865803] v4l2_ioctl+0x64/0x90
[ 153.865810] __arm64_sys_ioctl+0xa8/0xf0
[ 153.865818] el0_svc_common.constprop.0+0x7c/0x1c0
[ 153.865828] do_el0_svc+0x34/0xa0
[ 153.865836] el0_svc+0x1c/0x30
[ 153.865852] el0_sync_handler+0xa8/0xb0
[ 153.865859] el0_sync+0x16c/0x180
[ 153.865865] ---[ end trace 077e1aa560ee9778 ]---
[ 153.865981] tegra194-vi5 15c10000.vi: IVC control submit failed
[ 153.866126] tegra194-vi5 15c10000.vi: csi_stream_release: failed to disable nvcsi tpg on stream 2 virtual channel 0
quad@quad-nx:~$ -
@maponarooo
I think this is caused by a mipi data parsing error.
It could be hardware or it could be a software reason.
You can follow this link https://elinux.org/Jetson/l4t/Camera_BringUp#Tips_for_debugging to check the mipi errror details, but I don't recommend it because everything is working fine on my end.
Here is my suggestion that- Check the hardware connection.
- If you have another motherboard, like raspberry pi or jetson other boards that can be used to test the camera, I suggest you test it first.
- re-burn the nx's system with sdk manager, then do the driver and dtb installation. In other words, start over with the software installation.
