rt-net / jetsonnano_dt_spi Goto Github PK

L4T R32.2.0 has published on July 19th, 2019.
https://devtalk.nvidia.com/default/topic/1057580/jetson-nano/jetpack-4-2-1-l4t-r32-2-release-for-jetson-nano-jetson-tx1-tx2-and-jetson-agx-xavier/2
According to #4(thanks to @ADV-LUT), the current script does not correspond to R32.2.0.

Hi,

First of all, thanks for this repo.
I am one more that wants to configure the SPI communication of the Nano, and I am trying to use your script. But when running the ./run.sh file this error comes out:

bzip2: Data integrity error when decompressing.
	Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

tar: Unexpected EOF in archive
tar: Linux_for_Tegra/nv_tegra: Cannot utime: Operation not permitted
tar: Linux_for_Tegra: Cannot utime: Operation not permitted
tar: Error is not recoverable: exiting now

Can you help?

Hi rt-net,

Thank you for the script to enable spi1 (Pin 19, 21, 23, 24) on Jetson Nano.

However there is 2nd spi (pins of 37 22 13 18), I tried to modify the dts file but not working. It did show /dev/spidev1.0, but loopback test returns all 00's

spi@7000d600 {
           ...........
	spi1_0 {
			#address-cells = <0x1>;
			#size-cells = <0x0>;
			compatible = "spidev";
			reg = <0x0>;
			spi-max-frequency = <0x1312d00>;
			nvidia,enable-hw-based-cs;
			nvidia,cs-setup-clk-count = <0x1e>;
			nvidia,cs-hold-clk-count = <0x1e>;
			nvidia,rx-clk-tap-delay = <0x1f>;
			nvidia,tx-clk-tap-delay = <0x0>;
	};

Please advise, Thanks in advance

JetPack 4.3 has released, and the version for L4T has updated.
https://devtalk.nvidia.com/default/topic/1068583/jetson-nano/jetpack-4-3-l4t-r32-3-1-released
https://docs.nvidia.com/jetson/jetpack/release-notes/index.html#jetpack-version

Hi @Tiryoh ,

thanks for the helpful script.
Unfortunately I do not get a graphical user interface during the reboot. But I can access and use the board via ssh. Any suggestion why it is so?

Hi @Tiryoh,

Thanks again for the script.

Now, I need to change the Nano SPI configuration from Master to Slave, Do you know what is the easiest and fastest way?

Regards,
Al3Co

Hello,

Thanks for a helpful tool. I used it to successfully update the DTB on my Jetson Nano with L4T R32.2.1. I have confirmed that the spidev module is loaded and that /dev/spi.0.0 exists.

However the default test program spidev_test (public_sources/kernel/kernel-4.9/tools/spi/spidev_test.c) fails. The bytes transmitted are not received.

anamud@jn268:~$ ./spidev_test -v -D /dev/spidev0.0 
spi mode: 0x0
bits per word: 8
max speed: 500000 Hz (500 KHz)
TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D  | ......@....�..................�.
RX | FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF  | ................................

Do you have any tips for me to debug the problem?

According to jtktchinou's post, the L4T Driver Package has been updated.

This line needs to be updated.

L4T Driver Package is published at
https://developer.nvidia.com/embedded/dlc/Jetson-210_Linux_R32.2.1
which redirects to
https://developer.download.nvidia.com/embedded/L4T/r32-2-1_Release_v1.0/Nano-TX1/Jetson-210_Linux_R32.2.1_aarch64.tbz2.

The MD5 hash of the old Jetson-210_Linux_R32.2.1_aarch64.tbz2 is 2d648bbc77c510c4e7e0c809996d24e8, and the new one is e5b613bb7638863beb47c3e8ff6a2066.

The difference between the old one and the new one is the kernel package.

$ diff -rq old/Linux_for_Tegra/ new/Linux_for_Tegra/
Only in old/Linux_for_Tegra/kernel: nvidia-l4t-kernel_4.9.140-tegra-32.2.1-20190812212815_arm64.deb
Only in new/Linux_for_Tegra/kernel: nvidia-l4t-kernel_4.9.140-tegra-32.2.1-20191019160621_arm64.deb

Dear Tiryoh,

Thank you so much for your document and great inputs in the jetson nano forum!
I am trying to enable the SPI on Jetson Nano too, however I am not sure what to do before the steps you mentioned in the forum: https://devtalk.nvidia.com/default/topic/1050427/jetson-nano/enabling-spidev-on-the-jetson-nano-is-hanging-when-flashing/post/5339816/#5339816. Do I have to install the NVIDIA SDK Manager in another Linux computer? Any details about enabling the SPI on Jetson Nano will be greatly appreciated! Thanks!