Problem of kernel and DTB from TFTP and rootfs from NFS

Is your device able to ping 192.168.1.100?

yes

on host ,tftp server use 192.168.1.100 too,it can work

Can you post the full dmesg?

dmesg.txt (93.5 KB)

i uploaded

and i use r32.2 on xavier

Can you try 32.4.3? I am not sure whether 32.2 can make this work.

21/5000
I have tried r32.4.3 and have the same problem

All my steps are as follows,Did I miss some steps?

$ sudo apt-get install nfs-common nfs-kernel-server
•Modify /etc/exports to look somewhat like this:
/home/red/nfsroot *(rw,sync,no_subtree_check,no_root_squash)
$ sudo /etc/init.d/nfs-kernel-server restart
$ sudo mkdir /home/red/nfsroot
$ cd ./Linux_for_Tegra/rootfs
$ sudo cp –a * ~/nfsroot
$ sudo exportfs -a
$ sudo ufw disable
$ sudo apt-get install nfs-common

To RAM boot to NFS (Jetson AGX Xavier series only)
1.Put the device into reset/recovery mode.
•Power on the carrier board and hold the RECOVERY button.
•Then press the RESET button.
2.Execute the command:
$ sudo ./flash.sh -N 192.168.1.100:/home/red/nfsroot --rcm-boot jetson-xavier eth0

Is there another way to mount NFS? For example, configure parameters in Cboot,like bootargus in uboot. My xavier cannot be flashed in Recover mode now

Hello hong.wang,

I am a bit confused about this setting in the cbo.dts. The tftp-server-ip and all other entries are different than what you are trying to use.

oh,That’s the setting in the example, and my setting is as follows

/dts-v1/;

/ {
compatible = “nvidia,cboot-options-v1”;
boot-configuration {
boot-order = “sd”, “usb”, “net”, “emmc”;
tftp-server-ip = /bits/ 8 <192 168 1 100>;
static-ip = /bits/ 8 <192 168 1 123>;
ip-netmask = /bits/ 8 <255 255 255 0>;
ip-gateway = /bits/ 8 <192 168 1 1>;
};
};

i used the R32.4.3 , and have the same problem,dmesg-R32.4.3.txt (96.9 KB) this is the full dmesg

Is your network switch support dhcp?

[ 0.000000] Kernel command line: console=ttyTCU0,115200 root=/dev/nfs rw net

The kernel cmdline looks shorter than I expect.

you mean my host-pc network must switch support dhcp?

I guess the problem is the cboot boots the kernel from tftp server but it didn’t pass the boot args to kernel command line correctly.

If you don’t boot the kernel from tftp, then nfs may probably work.

I will try

[ 0.000000] Kernel command line: console=ttyTCU0,115200 root=/dev/nfs rw netdevwait ip=:::::eth0:on nfsroot=192.168.1.100:/home/red/nfsroot console=ttyTCU0,115200n8 conso

It didn’t show everything last time. Is there any problem with this one