Referring to the content of the aforementioned link, I flashed the Orin QSPI with “sudo ./flash.sh jetson-orin-nano-devkit sda1” and the USB-SSD with “sudo BOARDID=3701 BOARDSKU=0000 FAB=TS4 ./tools/kernel_flash/l4t_initrd_flash.sh -c tools/kernel_flash/flash_l4t_external.xml --external-device sda1 --direct sdc jetson-orin-nano-devkit external”, but the flash to the Orin QSPI was not successful. (It stops at the following part.)
Is the method I followed incorrect? Additionally, when flashing the Orin QSPI, is it necessary for the sda1 device to be recognized? It seems that in Force-Recovery-Mode, the USB device is not being powered, which concerns me.
First of all, what you did with the rootfs only applies when the disk is directly connected to the host PC, instead of the Jetson device itself, and we call it “offline flashing”. You don’t do this when your disk is connected to Jetson.
Moreover, BOARDID=3701 BOARDSKU=0000 FAB=TS4 is for AGX Orin, which is stated in the document; for Orin NX, you need BOARDID=3767 BOARDSKU=0000/0001 FAB=300``. (0000 for 16GB, 0001 for 8GB).
Lastly, please use 36.3 instead of 36.2.
We don’t recommend using a developer preview version anymore when a more stable production version is released.
Firstly, I must apologize. The command I mentioned in my question for flashing to the USB SSD was incorrect. In fact, I am flashing with the device changed to Orin NX 8G as you suggested.
Additionally, it is not the flash to the USB SSD that is failing, but the flash to the Orin-QSPI. (The flash to the USB SSD was successful.)
Could there be any mistakes in the usage of “sudo ./flash.sh jetson-orin-nano-devkit sda1” or any preliminary preparations required?
Moreover, when attempting the simultaneous writing you suggested, I encountered the following error:
***************************************
* *
* Step 3: Start the flashing process *
* *
***************************************
...
Waiting for target to boot-up...
Waiting for device to expose ssh ......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: Serial Number: 1420923046797
[ 0]: l4t_flash_from_kernel: Starting to create gpt for emmc
Active index file is /mnt/internal/flash.idx
Number of lines is 79
max_index=78
writing item=62, 6:0:primary_gpt, 512, 19968, gpt_primary_6_0.bin, 16896, fixed-<reserved>-0, d88febb644fd37567b684d128c54277f2eeb9477
Error: Could not stat device /dev/mmcblk0 - No such file or directory.
Flash failure
Either the device cannot mount the NFS server on the host or a flash command has failed. Debug log saved to /tmp/tmp.c2flfhqEP9. You can access the target's terminal through "sshpass -p root ssh root@fc00:1:1:0::2"
Cleaning up...
Also, I have connected the USB SSD to the following port. Could this be the mistake?
If you don’t specify any additional config file, this command will only work with an Orin Nano SKU5, the DevKit module, with SD card plugged in.
It will not work when you are using a commercial module or when the SD card is not plugged in.
For flashing QSPI bootloader, you should use:
sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal
I hadn’t been able to find that this command requires an SD card.
It seems that using the alternative flashing method you taught me to write to the Orin QSPI, I can boot an environment where the rootfs is written to a USB-SSD.
