I have skipped the kernel/module compilation because there is already a file spidev.ko in /lib/modules/drivers/spi
cat /lib/modules/$(uname -r)/modules.dep is also showing entries which are depending on spidev.ko
Update the DTB by flash.sh instead of modification extlinux.conf
replace the dtb at nvidia_sdk/JetPack_4.2_Linux_P3310/Linux_for_Tegra/kernel/dtb/ and flash by below command
@ShaneCCC: Still no luck but fortunately I have found my mistake.
First difference: All commands are performed on the host
The second one: In step 3 I created the source from the existing dtb instead of /proc/device-tree
sudo apt-get install deveice-tree-compiler
cd ~/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3489/Linux_for_Tegra/kernel/dtb
Hi Viclpedia,
Please can you confirm you are using a TX2i? I use TX2 dev kit and I modified(tegra186-quill-p3489-1000-a00-00-ucm1.dtb) exactly as described following the 8 step guide. However, when I reboot my TX2 after flashing, I do not see any see spidev.
Could it be that I am supposed to modify a “tegra186-quill-p3310-xxxxxxxx.dtb” file instead of a “P3489”?
I have got 3 .dtb files for P3310. I am unsure which to edit if I initially edited the wrong file.
Am I supposed to add the line FDT /boot/dtb/tegra186-quill-p3489-1000-a00-00-ucm1.dtb in the file /boot/extlinux/extlinux.conf below LINUX /boot/Image ?
Although it was no part of the 8 step guide.
I simply used the command "dmesg | grep “DTS File Name” on the TX2 terminal dev kit and it showed the .dtb file in use as “tegra186-quill-p3310-1000-c03-00-base.dtb”.
I then followed the Viclpedia’s eight stepped process to edit the .dtb file. Rebooted … and it worked.
yes, I am using a TX2i. As you already figured out the TX2 uses the p3310 dtb file.
And with flashing the board there is no need to add the FTD line in the extconfig.