Hello everyone,
I have installed JetPack 5.0.1 Preview on Jetson Xavier NX, and was not able to get the IMX477 cameras running. I saw in here that I need to modify the device tree. But I do not understand how I can do that without flashing it again since I am new to this? Is there a solution to fix this without flashing it again? If so, I would be grateful if you can provide a guide on how to do this.
Thank you so much!
hello king_kaleb ,
you’re able to disassembler the dtb file into text file for modification,
$ dtc -I dtb -O dts -o temp.dts tegra194.dtb
after that, please convert the DTS into a new DTB file,
$ dtc -I dts -O dtb -o new-output.dtb temp.dts
Hi @JerryChang,
Thank you for the quick response. However, I was not able to find the tegra194-p3509-0000-a00.dtsi file. The closest file I could find was /boot/tegra194-p3668-all-p3509-0000.dtb. Can you please tell me where I can find the dts file I need to edit? or can you perhaps provide me a link where I can follow the exact steps to fix the issue?
Thank you so much!!
hello king_kaleb,
you may check /boot/extlinux/extlinux.conf for FDT entry, it shows the device tree file you’re using.
usually the binary file is located at /boot/, please modify the binary file for testing. thanks
HI @JerryChang,
Thank you! The device tree file is /boot/dtb/kernel_tegra194-p3668-0000-p3509-0000.dtb. I have edited the file, converted it back to dtb and replaced it. However, it is still not working. I have uploaded the dts file here:
kernel_tegra194-p3668-0000-p3509-0000.dts (297.4 KB)
Thank you so much!!
Hi @JerryChang,
Thank you! That was useful. I followed the instructions and also downloaded this file and replaced my dtb file. Now, running sudo /opt/nvidia/jetson-io/jetson-io.py does not work. It shows the gray screen and automatically closes.
Thank you for the continuous support!!
hello king_kaleb,
please setup a terminal and gather the kernel logs for reference,
thanks
Hi @JerryChang,
Sorry, I was not able to follow. Can you please elaborate more on how I can do that? Sorry for my ignorance on this.
Thank you!
I have viewed all the log files in /var/log/ but I couldn’t find anything relevant to jetson-io. Am I looking at a wrong location?
hello king_kaleb,
please running command, $ dmesg to gather kernel logs, you may also apply options, $ dmesg --follow to view kernel messages immediately.
Jetson-IO utility is under /opt/nvidia/jetson-io/, you may use the command $ sudo python jetson-io.py for running it.
Hi @JerryChang,
Thank you! The only error I could see in the log that’s relevant is the following:
[ 8.695570] rtl88x2ce 0004:01:00.0: enabling device (0000 -> 0003)
[ 8.700229] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[ 8.710928] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 8.711288] usb 1-2.3.2: new high-speed USB device number 6 using tegra-xusb
[ 8.717046] imx219 9-0010: board setup failed
[ 8.717287] imx219: probe of 9-0010 failed with error -121
[ 8.717697] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[ 8.719345] tegra-hda 3510000.hda: Adding to iommu group 32
[ 8.719860] tegra-hda 3510000.hda: Override SDO lines to 4
[ 8.728471] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[ 8.733920] imx219 10-0010: board setup failed
[ 8.734139] imx219: probe of 10-0010 failed with error -121
[ 8.753700] cpu-throttle-alert cooling device registered.
[ 8.756049] gpu-throttle-alert cooling device registered.
[ 8.756535] random: crng init done
[ 8.756672] random: 7 urandom warning(s) missed due to ratelimiting
[ 8.756758] aux-throttle-alert cooling device registered.
[ 8.757134] hot-surface-alert cooling device registered.
and I get the following output when I run cat /proc/config.gz | gunzip | grep IMX:
# CONFIG_TOUCHSCREEN_IMX6UL_TSC is not set
# CONFIG_VIDEO_IMX214 is not set
# CONFIG_VIDEO_IMX219 is not set
# CONFIG_VIDEO_IMX258 is not set
# CONFIG_VIDEO_IMX274 is not set
# CONFIG_VIDEO_IMX290 is not set
# CONFIG_VIDEO_IMX319 is not set
# CONFIG_VIDEO_IMX355 is not set
CONFIG_NV_VIDEO_IMX185=m
# CONFIG_VIDEO_IMX477 is not set
CONFIG_NV_VIDEO_IMX219=m
CONFIG_NV_VIDEO_IMX268=m
CONFIG_NV_VIDEO_IMX274=m
CONFIG_NV_VIDEO_IMX318=m
CONFIG_NV_VIDEO_IMX390=y
# CONFIG_VIDEO_IMX204 is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set
CONFIG_USB_CHIPIDEA_IMX=m
CONFIG_PHY_FSL_IMX8MQ_USB=y
Nothing is added to the log after running the jetson-io.py.
hello king_kaleb,
according to above, system level still trying to detect IMX219 camera sensors.
please review the device tree sources, tegra194-p3509-0000-a00.dtsi, had you removing the IMX219 sensor DTSI file from the main DTS file?
Hi @JerryChang,
I don’t have the file tegra194-p3509-0000-a00.dtsi in /boot. Is it stored somewhere else?
The files I edited were /boot/dtb/kernel_tegra194-p3668-0000-p3509-0000.dtb and /boot/tegra194-p3668-all-p3509-0000.dtb. I have restored the original files but still it doesn’t work.
Thank you!
hello king_kaleb,
JetPack 5.0.2 is now available, it’s the production release and we’ll deprecated l4t-r34.1.1 developer preview soon.
please access JetPack SDK 5.0.2 | NVIDIA Developer to download the latest NVIDIA JetPack SDK. thanks
Hi @JerryChang,
That’s great! Do I have to flash it again and loose my files or can I just install only JetPack runtime components?
Thank you!
hello king_kaleb,
currently, l4t-r34.x is supported with OTA update uses Debian packages obtained from an NVIDIA APT server. this OTA update approach will keep your user-space contents.
please also refer to developer guide, Over-the-Air Update, thanks
Hi @JerryChang,
I tried to update it following the guide, but it doesn’t even boot now. I even tried to flash it again but it got stuck at 99% of flashing!
Is there any chance I can get it back to where it was? or flash it successfully?
Thank you!
hello king_kaleb,
is it just stuck there, may I know what’s the messages show-up?
please also setup serial console to gather the logs for reference,
thanks