Reflash ORIN NX errors

Hi,

I have an ORIN NX 16GB, custom carrier, NVME soldered on the carrier., using 5.1.1.
First time I flashed the board with the following command:
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_t234_qspi.xml" \ --showlogs --network usb0 p3509-a02+p3767-0000 internal

Everything worked OK, then I had to modify some device tree files. Recompiled from sources, copied the necessary files and ran the command again. The issue is like below:

Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
...RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
blockdev: cannot open /dev/mmcblk0boot0: No such file or directory
[ 0]: l4t_flash_from_kernel: Starting to create gpt for emmc
Active index file is /mnt/internal/flash.idx
Number of lines is 58
max_index=57
[ 2]: l4t_flash_from_kernel: Successfully create gpt for emmc
[ 2]: l4t_flash_from_kernel: Starting to create gpt for external device
Active index file is /mnt/external/flash.idx
Number of lines is 17
max_index=16
writing item=1, 9:0:primary_gpt, 512, 19968, gpt_primary_9_0.bin, 16896, fixed-<reserved>-0, 5828701633d5709e5513ad0d0a90f05375f3f454
Error: Could not stat device /dev/nvme0n1 - No such file or directory.
Flash failure
Cleaning up...

of course not booting again…

What could be a reason for this. What should I try?
Thank you

Apparently NVMe is screwed up because of your device tree changes.

I just enable some USB ports… What changes in the device tree could screw up the NVME?

What exact changes did you make?
Have you tried restoring those changes and see if NVMe is back?

I think this has nothing to do with the device tree changes screwing up the NVME.
I rerun the command with --erase-all flag and it worked.
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_t234_qspi.xml" \ --showlogs --erase-all --network usb0 p3509-a02+p3767-0000 internal

Could you explain this behavior?

It’s suggested to format the disk before flashing, so --erase-all does the same thing.

Great, thanks. I have not seen this in the documentation, though…