How should I fill in the options for target_board and rootdev ?
sudo ./flash.sh -r <target_board> <rootdev>
flash.sh cannot flash nvme or usb drive. Need to use initrd flash.
How to use initrd? Is there any documentation available?
Please read Linux_for_Tegra/tools/kernel_flash/README_initrd_flash.txt.
This seems somewhat complex.
My current issue is that, due to the limited capacity of the emmc, I want to install Jetson SDK Components on the NVMe hard drive, but the system is still being flashed to the emmc. Is this feasible?
If it is feasible, how should I proceed? Thank you.
So your L4T OS is installed in the eMMC, but you want the JetPack SDK (CUDA, TensorRT…) to be present on the NVMe drive?
Yes, because the emmc capacity is not large enough.
I don’t think you can do that.
You have to re-flash the device so the whole system lives in the NVMe.
Alright, I will try flashing the system to the NVMe hard drive using initrd.
During the system flashing with initrd, I encountered the following error message:
morevision2@morevision2:Linux_for_Tegra$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme.xml -S 8GiB --showlogs jetson-xavier-nx-devkit nvme0n1p1
[sudo] password for morevision2:
/home/morevision2/l4t/l4t_32_6_1/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme.xml -S 8GiB --showlogs jetson-xavier-nx-devkit nvme0n1p1
Please install the Secureboot package to use initrd flash
Cleaning up...
How do I install the Secureboot package?
Also, could you please check if my command parameters are correct?
You need this:
https://developer.nvidia.com/embedded/l4t/r32_release_v6.1/t210/secureboot_r32.6.1_aarch64.tbz2
I have successfully flashed it, but the system size displayed by df is only 8GB, which is likely restricted by the size specified by the -S option. I’m using a 128GB NVMe hard drive. What would be the appropriate value to specify for the -S option?
nvidia@nx:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 7.8G 5.1G 2.3G 70% /
none 3.5G 0 3.5G 0% /dev
tmpfs 3.8G 40K 3.8G 1% /dev/shm
tmpfs 3.8G 30M 3.8G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
tmpfs 777M 12K 777M 1% /run/user/120
tmpfs 777M 104K 777M 1% /run/user/1000
Why are you setting -S 8GiB when you don’t need it?..
Just take it out.
Removing the -S option, the total size is 14GB. Why is it 14GB?
nvidia@nx:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 14G 5.1G 7.9G 40% /
none 3.5G 0 3.5G 0% /dev
tmpfs 3.8G 40K 3.8G 1% /dev/shm
tmpfs 3.8G 32M 3.8G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
tmpfs 777M 4.0K 777M 1% /run/user/0
tmpfs 777M 152K 777M 1% /run/user/1000
<device type="nvme" instance="0" sector_size="512" num_sectors="195312500">
That’s the default size, and it should get enlarged by some scripts running in the background upon first boot.
I didn’t understand how to operate.
Where is the default size set, and can I change the default size and flash it again？
There’s nothing you need to do.
Just wait for a while and the partition size will be corrected.
How long does it take, it is still 14GB now.
This is the command I used to flash the system：
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme.xml --external-only --showlogs jetson-xavier-nx-devkit nvme0n1p1
Is it related to the --external-only option?
Then can you try flashing with SDK Manager?
I can try flashing with the SDK Manager to see the results. I am using Jetson Linux R32.6.1. Which version of JetPack should I flash?