Fresh JetPack 4.5 and 4.5.1 cannot work with MIPI CSI camera

Hi,
I need to use JetPack 4.5 or 4.5.1 because these two versions worked well on Xavier NX before (encountered problem with JetPack 4.6 or higher versions when building Eex with Pyinstaller). I downloaded JetPack from this web page: JetPack Archive | NVIDIA Developer, and flashed the image to SD card. After booting the system for the first time, I encountered a problem when testing MIPI SCI camera (Arducam IMX219 SKU: B0182) with GStreamer. Below is the error output:

$ gst-launch-1.0 nvarguscamerasrc ! nvoverlaysink
Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Setting pipeline to PLAYING …
New clock: GstSystemClock
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:645 No cameras available
(gst-launch-1.0:22239): GStreamer-CRITICAL **: 16:42:03.498: gst_mini_object_set_qdata: assertion β€˜object != NULL’ failed
Got EOS from element β€œpipeline0”.
Execution ended after 0:00:00.041492575
Setting pipeline to PAUSED …
Setting pipeline to READY …
Setting pipeline to NULL …
Freeing pipeline …
(Argus) Error EndOfFile: Unexpected error in reading socket (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 266)
(Argus) Error EndOfFile: Receive worker failure, notifying 1 waiting threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 340)
(Argus) Error InvalidState: Argus client is exiting with 1 outstanding client threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 357)
(Argus) Error EndOfFile: Receiving thread terminated with error (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadWrapper(), line 368)
(Argus) Error EndOfFile: Client thread received an error from socket (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 145)
(Argus) Error EndOfFile: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 87)

I also tried JetPack 4.5.1 but end up with the same error output.
Please help.
Thanks.

1 Like

I also tested the Xavier NX with another SD card which was installed JetPack 4.6.1 before. I can operate the camera without any issue.

What’s you camera? Didn’t you integrate the sensor driver and device tree to enable it?

I use this camera: Arducam IMX219-AF Programmable/Auto Focus Camera Module for Nvidia Jetson Nano - Arducam. I have used a few of such cameras on my Xavier NX devices before. Every time when I purchase a new Xavier NX, I can directly connect the camera to it and then use the camera immediately. There is no need to integrate the camera/sensor and device tree to enable it.

You can check by below command for sensor driver loaded.

v4l2-ctl --list-devices
dmesg | grep -i imx219

I got following feedback when trying to obtain imformation:
$ sudo pip3 install v4l2
Collecting v4l2
Downloading https://files.pythonhosted.org/packages/1f/3c/a4e9abe360c76c7268cde9e7fbf7164c357063b29debbf0d36836097318c/v4l2-0.2.tar.gz
Installing collected packages: v4l2
Running setup.py install for v4l2 … done
Successfully installed v4l2-0.2
$ v4l2-ctl --list-devices
bash: v4l2-ctl: command not found
$ dmesg | grep -i imx219
[ 2.210424] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[ 2.233996] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.234316] imx219 9-0010: board setup failed
[ 2.234532] imx219: probe of 9-0010 failed with error -121
[ 2.234990] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[ 3.233511] tegra194-vi5 15c10000.vi: subdev imx219 10-0010 bound

Install v4l2-ctl by below command.

sudo apt-get install v4l-utils

Hi, below is the information:
$ v4l2-ctl --list-devices
vi-output, imx219 10-0010 (platform:15c10000.vi:2):
/dev/video0

$ dmesg | grep -i imx219
[ 2.210424] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[ 2.233996] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.234316] imx219 9-0010: board setup failed
[ 2.234532] imx219: probe of 9-0010 failed with error -121
[ 2.234990] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[ 3.233511] tegra194-vi5 15c10000.vi: subdev imx219 10-0010 bound

When I connected 2 CSI cameras, I got following output during test:
$ v4l2-ctl --list-devices
vi-output, imx219 9-0010 (platform:15c10000.vi:0):
/dev/video0

vi-output, imx219 10-0010 (platform:15c10000.vi:2):
/dev/video1

$ dmesg | grep -i imx219
[ 1.985294] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[ 2.010076] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[ 2.978037] tegra194-vi5 15c10000.vi: subdev imx219 9-0010 bound
[ 2.979017] tegra194-vi5 15c10000.vi: subdev imx219 10-0010 bound

Well this log looks like connect two imx219, still the same error when launch gst-launch-1.0?
Please dump the device tree by below command to check.

sudo dtc -I fs -O dts -o extracted_proc.dts /proc/device-tree

Yes, when 2 cameras connected, same problem.
Below is the output information:
$ sudo dtc -I fs -O dts -o extracted_proc.dts /proc/device-tree
extracted_proc.dts: Warning (unit_address_vs_reg): Node /aconnect@2a41000 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /aconnect@2a41000/ahub has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /aconnect@2a41000/ahub/ope@2908000/peq@2908100 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /aconnect@2a41000/ahub/ope@2908000/mbdrc@2908200 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /reserved-memory/fb3_carveout has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /reserved-memory/fb0_carveout has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /reserved-memory/fb1_carveout has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /reserved-memory/grid-of-semaphores has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /reserved-memory/fb2_carveout has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /lens_imx219@RBPCV2 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /aon@c000000/ivc-channels@80000000 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /bpmp_i2c/spmic@3c/pinmux@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /bpmp_i2c/spmic@3c/fps/fps0 has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /bpmp_i2c/spmic@3c/fps/fps1 has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /bpmp_i2c/spmic@3c/fps/fps2 has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /eeprom-manager/bus@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /eeprom-manager/bus@0/eeprom@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /eeprom-manager/bus@0/eeprom@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /eeprom-manager/bus@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /eeprom-manager/bus@1/eeprom@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /tegra-cvnas has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /camera-ivc-channels/dbg@2 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /camera-ivc-channels/echo@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /camera-ivc-channels/ivccapture@4 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /camera-ivc-channels/dbg@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /camera-ivc-channels/ivccontrol@3 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-pcie-c5-rp/override@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-pcie-c5-rp/override@2 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-pcie-c5-rp/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragement-tegra-sdhci-sd-dis/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-b00@2 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-b00@2/overrides@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-b00@2/overrides@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-fs-disable-isp/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-fs-disable-cv/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-fs-disable-dla/override@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-fs-disable-dla/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragement-tegra-pcie-c4-dis/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragement-tegra-wdt-dis/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-common@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-common@0/overrides@8 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-common@0/overrides@10 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-common@0/overrides@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-common@0/overrides@11 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-common@0/overrides@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-a00@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-a00@1/overrides@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-e2614-a00@1/overrides@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragement-tegra-pcie-c5-num-lanes/override@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragement-tegra-pcie-c5-num-lanes/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragement-tegra-sdhci-emmc-dis/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragement-tegra-wdt-en/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-fs-disable-pva/override@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-fs-disable-pva/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-fs-disable-nvenc/override@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-fs-disable-nvenc/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-pcie-c5-ep/override@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-pcie-c5-ep/override@2 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragment-pcie-c5-ep/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /plugin-manager/fragement-pmic-wdt-en/override@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /combined-uart has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /thermal-zones/CPU-therm/trips/eqos-m40@-40000 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /thermal-zones/CPU-therm/trips/eqos-p30@30000 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /thermal-zones/CPU-therm/trips/eqos-p100@100000 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /thermal-zones/CPU-therm/trips/eqos-p65@65000 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /thermal-zones/CPU-therm/trips/eqos-m5@-5000 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /bpmp has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /tegra_nvlink_controller has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/pva1 has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/dpaux@155F0000/pinmux@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/vi-thi@15f00000 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/sor3 has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/sor1 has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/dc_common has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/tegra_cec has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/sor has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/pva0 has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/nvcsi@15a00000/channel@0/ports/port@1/endpoint@1 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/nvcsi@15a00000/channel@0/ports/port@0/endpoint@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/nvcsi@15a00000/channel@1/ports/port@1/endpoint@3 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/nvcsi@15a00000/channel@1/ports/port@0/endpoint@2 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /host1x/sor2 has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /tegra_hv_xhci_debug@0 has a unit name, but no reg property
extracted_proc.dts: Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /mc has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /soctherm-oc-event has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_vs_reg): Node /gv11b has a reg or ranges property, but no unit name
extracted_proc.dts: Warning (unit_address_format): Node /miscreg@00100000 unit name should not have leading 0s
extracted_proc.dts: Warning (simple_bus_reg): Node /nvhs_p2u/p2u@03eb0000 simple-bus unit address format error, expected β€œ3eb0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /nvhs_p2u/p2u@03ef0000 simple-bus unit address format error, expected β€œ3ef0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /nvhs_p2u/p2u@03f10000 simple-bus unit address format error, expected β€œ3f10000”
extracted_proc.dts: Warning (simple_bus_reg): Node /nvhs_p2u/p2u@03ec0000 simple-bus unit address format error, expected β€œ3ec0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /nvhs_p2u/p2u@03f20000 simple-bus unit address format error, expected β€œ3f20000”
extracted_proc.dts: Warning (simple_bus_reg): Node /nvhs_p2u/p2u@03ed0000 simple-bus unit address format error, expected β€œ3ed0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /nvhs_p2u/p2u@03ee0000 simple-bus unit address format error, expected β€œ3ee0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /nvhs_p2u/p2u@03f00000 simple-bus unit address format error, expected β€œ3f00000”
extracted_proc.dts: Warning (simple_bus_reg): Node /mods-simple-bus/mods-clocks missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@200 simple-bus unit address format error, expected β€œc8”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@106 simple-bus unit address format error, expected β€œ6a”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@104 simple-bus unit address format error, expected β€œ68”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@112 simple-bus unit address format error, expected β€œ70”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@102 simple-bus unit address format error, expected β€œ66”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@107 simple-bus unit address format error, expected β€œ6b”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@105 simple-bus unit address format error, expected β€œ69”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@113 simple-bus unit address format error, expected β€œ71”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@111 simple-bus unit address format error, expected β€œ6f”
extracted_proc.dts: Warning (simple_bus_reg): Node /fixed-regulators/regulator@101 simple-bus unit address format error, expected β€œ65”
extracted_proc.dts: Warning (simple_bus_reg): Node /external-connection/disp-state missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/prod-settings missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/pva1 simple-bus unit address format error, expected β€œ16800000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/ctx3 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/dpaux@155F0000 simple-bus unit address format error, expected β€œ155f0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/ctx1 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/vi-thi@15f00000 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/sor3 simple-bus unit address format error, expected β€œ15bc0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/sor1 simple-bus unit address format error, expected β€œ15b40000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/dc_common simple-bus unit address format error, expected β€œ15200000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/tegra_cec simple-bus unit address format error, expected β€œ3960000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/ctx6 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/ctx4 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/sor simple-bus unit address format error, expected β€œ15b00000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/dpaux@155D0000 simple-bus unit address format error, expected β€œ155d0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/pva0 simple-bus unit address format error, expected β€œ16000000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/ctx2 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/ctx0 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/sor2 simple-bus unit address format error, expected β€œ15b80000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/disp_imp_table missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/dpaux@155E0000 simple-bus unit address format error, expected β€œ155e0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/ctx7 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /host1x/ctx5 missing or empty reg/ranges property
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e40000 simple-bus unit address format error, expected β€œ3e40000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e80000 simple-bus unit address format error, expected β€œ3e80000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e10000 simple-bus unit address format error, expected β€œ3e10000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e50000 simple-bus unit address format error, expected β€œ3e50000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e90000 simple-bus unit address format error, expected β€œ3e90000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e20000 simple-bus unit address format error, expected β€œ3e20000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e60000 simple-bus unit address format error, expected β€œ3e60000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03f30000 simple-bus unit address format error, expected β€œ3f30000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03ea0000 simple-bus unit address format error, expected β€œ3ea0000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e30000 simple-bus unit address format error, expected β€œ3e30000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03e70000 simple-bus unit address format error, expected β€œ3e70000”
extracted_proc.dts: Warning (simple_bus_reg): Node /hsio_p2u/p2u@03f40000 simple-bus unit address format error, expected β€œ3f40000”

Check the extracted_proc.dts generate by the command.

HI, I don’t understand the content of this file. I attach this file here. Please help to investigate. Thanks.
extracted_proc.dts (249.2 KB)

Hi, Have you found the root cause? Can you provide the solution?

The device tree looks fine. Does the same error?

yes, same error when 2 cameras are used.

Restart the nvargus-daemon by below command to try.

sudo service nvargus-daemon restart

Hi, I restarted the nvargus-daemon, but came up with the same error as shown below when testing camera:

$ sudo service nvargus-daemon restart

$ gst-launch-1.0 nvarguscamerasrc ! nvoverlaysink

Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Setting pipeline to PLAYING …
New clock: GstSystemClock
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:645 No cameras available

(gst-launch-1.0:9902): GStreamer-CRITICAL **: 22:06:45.341: gst_mini_object_set_qdata: assertion β€˜object != NULL’ failed
Got EOS from element β€œpipeline0”.
Execution ended after 0:00:00.046142375
Setting pipeline to PAUSED …
Setting pipeline to READY …
Setting pipeline to NULL …
Freeing pipeline …
(Argus) Error EndOfFile: Unexpected error in reading socket (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 266)
(Argus) Error EndOfFile: Receive worker failure, notifying 1 waiting threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 340)
(Argus) Error InvalidState: Argus client is exiting with 1 outstanding client threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 357)
(Argus) Error EndOfFile: Receiving thread terminated with error (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadWrapper(), line 368)
(Argus) Error EndOfFile: Client thread received an error from socket (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 145)
(Argus) Error EndOfFile: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 87)

Could you try latest release r32.7.x

what is r32.7.x? how to upgrade?