When JetPack 5.1.4 flashes the system to nvme, the partition size is only 14G, not the entire nvme space size

[ziyu6060]

Hi.Alian
Thank you very much. I used SDKManager to burn the program. I referred to the solution in the following link, but it didn’t work. Which files should I modify?

After jetson nx is refreshed to NVME, the app partition has only 14G, and the UDA partition has 400G. How to give this 400G to the app partition?

I use the sdk manager to refresh the system directly to nvme instead of using the system in emmc. It is optional to use the system after refreshing, but I found that the app’s/under space is only 14G after refreshing, and the other space is in UDA. How to use the space in UDA to the app. I also tried to modify the configuration file ~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/tools/kernel_flash/flash_l4t_t234_nvme.xml, and changed the APPSIZE to the actual s…

Jetpack 5.1.2 creates small partition on nvme drive instead of using all the space

I would like to upgrade my xavier NX to use Jetpack 5.1.2 so that I can hit the ESC key on startup. The keyboard doesn’t work while booting with my current install of Jetpack 5.1.1 (rev. 1). The problem is that I have a 256 GB NMVE SSD and 5.1.2 installs on a tiny partition of 16 GB at the front while 5.1.1 (rev. 1) installs it at a large 255 GB partition at the back. Is this a problem that anyone else is seeing? I am just using the SDK manager to install and it will fail at the runtime or SDK…

However, I will try the method you mentioned later.

Regards,
ziv