rt-net/JetsonNano_DT_SPI

update for L4T R32.2.0, R32.2.1

Opened this issue · 4 comments

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.

It seems like the new version of L4T, R32.2 uses a new dts.

$ head -n15 tegra210-p3448-0000-p3449-0000-a02.dts
/dts-v1/;

/memreserve/	0x0000000080000000 0x0000000000020000;
/ {
	compatible = "nvidia,jetson-nano", "nvidia,tegra210";
	interrupt-parent = <0x1>;
	#address-cells = <0x2>;
	#size-cells = <0x2>;
	nvidia,dtbbuildtime = "Jul 16 2019", "17:09:34";
	nvidia,boardids = "3448";
	nvidia,proc-boardid = "3448";
	nvidia,pmu-boardid = "3448";
	nvidia,fastboot-usb-pid = <0xb442>;
	model = "NVIDIA Jetson Nano Developer Kit";
	nvidia,dtsfilename = "/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-a02.dts";

I've used dd to replace the required partitions and move back and forth between standard and spi-enabled system. basically, just used the 5 partitions that change: p3, p4, p5, p9 and p10.
would it be possible to set this up such that we can just run a script using pre-built partition images straight from the device itself?
thanks