Clarification on flashing Xavier NX to 5.1.2 and adjusting APP size

So I have followed the directions of previous posts to change to flash_l4t_external and re-run SDK manager for 5.1.2. I see the APP partition is created to 14GB. I still run out of space on the 1TB NVME drive loading the APIs.

Is using SDK manager for the NX with 5.1.2 the wrong way to go?
I can’t find where the APP partition size value gets set to change it.

I’ve seen the command line to run the flashing to the NVME drive, does that do something different than SDK manager?

Sorry this is a repeat but I’ve read and tried all the other psots with the same answer for the switching the .xml file and using the command line.
Still having the issue. I must be missing the final post to this issue with my searches. Can you please point me to it?

Then please try this:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_l4t_t194_qspi_p3668.xml" \
  --showlogs --network usb0 jetson-xavier-nx-devkit internal

Hi DaveYYY,

That worked very nicely!! Thank you.
So I understand…what is the -p option with the string doing in this command? Similar to others I found but it appears you are passing in a parameter file. Does this override the l4t_external.xml config?

Hi,

The xml file directly comes after -c is for the external device (rootfs, kernel, device tree, etc.), and the xml file wrapped in -p is for the internal QSPI memory, which stores the bootloader, or UEFI.