I’m using Jetson Nano Developer kit 4GB with jetpack v4.6.1 and I’m having trouble in enabling the SPI pins (SPI1).
I enabled the SPI pins using ’ sudo /opt/nvidia/jetson-io/jetson-io.py ’ command and I ran the command ’ ls /dev/spi* ', all the 4 Spidev folders were available.
Further I got the know that to use SPI pins I should disable the GPIO pin functionality, I followed the steps as mentioned in this thread : https://forums.developer.nvidia.com/t/jetson-nano-spi-bus-not-working/249482/9
I manually downloaded the kernel and extracted it, I was not able to find tegra210-porg-gpio-p3448-0000-b00.dtsi file. Then I tried to build the kernel (more than 2 times) but everytime resulted in the following error :
Error: Missing kernel image /home/sr/Linux_for_Tegra/source/public/kernel_out/arch/arm64/boot/Image.
Is there any other methods or am I missing something. Any suggestions would be appreciated.
Actually I again flashed OS to Jetson nano and upgraded it to the version R32.7.4 .
I followed all the steps from scratch. Manually downloaded the kernel and tegra210-porg-gpio-p3448-0000-b00.dtsi file was available in this path
Modified the above file and the used spidev-test to test SPI which was unsuccessful.
And I tried to build the kernel but resulted in same above error.
The Linux_For_Tegra folder is located in /home/jetson-nano/ , does the path matter while we build kernel?
When i ran dmesg command, I got the DTS file as :
[ 0.219972] DTS File Name: /dvs/git/dirty/git-master_linux/kernel/kernel-4.9/arch/arm64/boot/dts/…/…/…/…/…/…/hardware/nvidia/platform/t210/porg/kernel-dts/tegra210-p3448-0000-p3449-0000-b00.dts
As you requested previously for flash log, is the kern.log file you are looking for? If not kern.log file please, explain me how to get the flash log as I’m new to Jetson nano.
I have a Windows PC so, I tried Virtual Box with Ubuntu OS, but was unsuccessful.
In VM, the SDKM was not able to detect the board.
I even set the Jetson board to recovery mode by connecting PIN 3 & PIN 4 together later powering it using USB. But no luck.
Please suggest some alternatives or work-arounds to solve this issue.