I tried to install the Arducam drivers for the NX Kernel version 32.7.2 using the install_full.sh script. It seems that there is no corresponding release yet.
Thanks for the release. I see you’ve made it available for the kernel version: 4.9.253-tegra-32.7.2-20220525063328
My kernel version is actually: 4.9.253-tegra-32.7.2-2022041724839
I still tried using the release you made available but after reboot I still have the tegracam sensor driver imx219_v2.0.6 installed instead of the arducam one.
Should I wait for a release for my kernel version or may the problem be due to something else ?
4.9.253-tegra-32.7.2-20220525063328 The timestamp here is the time when the deb package was packaged, not the kernel time. If you can install successfully, it means that the kernel version is correct.
You can execute the following command to see and provide me with the execution result:
dmesg | head
cat /boot/extlinux/extlinux.conf
ls /boot/arducam/dts/tegra194-p3668-0000-p3509-0000-user-custom.dtb
Thanks for your answer. Here are the results of the commands:
$ dmesg | head
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.253-tegra (buildbrain@mobile-u64-5374-d5000) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #1 SMP PREEMPT Sun Apr 17 02:37:44 PDT 2022
[ 0.000000] Boot CPU: AArch64 Processor [4e0f0040]
[ 0.000000] OF: fdt:memory scan node memory, reg size 48,
[ 0.000000] OF: fdt: - 80000000 , 2c000000
[ 0.000000] OF: fdt: - ac200000 , 44800000
[ 0.000000] OF: fdt: - 100000000 , 180000000
[ 0.000000] earlycon: tegra_comb_uart0 at MMIO32 0x000000000c168000 (options ‘’)
[ 0.000000] bootconsole [tegra_comb_uart0] enabled
[ 0.000000] Found tegra_fbmem: 00800000@a06bc000
$ cat /boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT JetsonIO
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/arducam/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet root=PARTUUID=6dd8cf17-8a57-417e-977e-84cec18bb805 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
# LABEL backup
# MENU LABEL backup kernel
# LINUX /boot/Image.backup
# INITRD /boot/initrd
# APPEND ${cbootargs}
LABEL JetsonIO
MENU LABEL Custom Header Config: <CSI Camera Arducam Dual>
LINUX /boot/arducam/Image
FDT /boot/arducam/dts/tegra194-p3668-all-p3509-0000-user-custom.dtb
INITRD /boot/initrd
APPEND ${cbootargs} quiet root=PARTUUID=6dd8cf17-8a57-417e-977e-84cec18bb805 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
$ ls /boot/arducam/dts/tegra194-p3668-all-p3509-0000-user-custom.dtb
/boot/arducam/dts/tegra194-p3668-all-p3509-0000-user-custom.dtb
Thanks for the link.
I’m still not sure of what the problem actually is. I’m booting from an external NVMe. Should I change the root path in the extlinux.conf file ? Or is it the cboot that should be rebuilt and reflashed ? Sorry the nvidia thread is quite confusing. I understand this is no longer an issue from your side.