to flash orin nx, the script prints “/home/v2x/test/jp51/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --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”, then stuck for about 6 minutes without any printing. The flashing process goes on after that.
Is your host a VM, or native install? VMs tend to fail. You should also list which version of JetPack you are using, and if the host PC is Ubuntu 18.04, 20.04, so on.
Your comment itself already tells us that file is indeed missing. Did you accidentally delete it without notice?
Let me just give a simple example, If you use “_av123” in your flash command, it means flash script will search “_av123.conf” in the Linux_for_Tegra path. The string needs to be 100% matching so that the flash process can proceed.
So back to the case, you used “p3509-a02+p3767-0000”. Which means “p3509-a02+p3767-0000.conf” need to be there, but your ls result shows it is not…
BTW, this rule applies since TX1, which means it has been there since long time ago.
Your command has some weird parts. For example, we don’t have “flash_t234_gspi.xml” but only has flash_t234_qspi.xml.
Previously you said the board config is missing, now it is coming back again and I don’t know what happened on your side.
Also, you are the only guy reporting you need to change board config name to make it work on this forum. For example, guys in below thread hit some flash issue too, but they never needed to change the board config name…
If you really need us to help check this issue, please let us know how to reproduce your case step by step.
Please be aware that we really need “step-by-step” info here because we have flashed lots of device with initrd flash tools lots of times… and what you hit didn’t happen to us.
I have also noticed at one of iterations [ under iteration I mean wiping sdkmanager folder/ installation then installing Linux_for_tegra with sdkmanager] that copy paste of nvme0n1p1 would result with ‘l’ instead on ‘1’ . It must be a copy paste error q->g, in my opinion. Unless data corruption is caused by other processes.
I have run 4-7 iterations. None of them would find the config file with the latest sdkmanager by default.
I will run once again with 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
Experiment 1.
This time it worked after prior successful iteration though. I have also noticed that while I was executing you have published another question about the -c - I am not putting it currently. At some of iterations sdkmanager has put it at some of iterations I’ve put it eventually highly likely
Did it just complete each iteration at your side?
Above step is just a full clean-up and then re-install. Do not try to remove/rename or do anything that you want anymore. Just follow the steps and share the result.
1,2,3 - done;
4 [ the board isn’t connected right now maybe later with the board will try rather on Monday]
5 executes with no errors so far as it seems using
I added some debug message, and figured out tools/kernel_flash/l4t_initrd_flash_internal.sh stuck at line 117: network_prerequisite "${network}" "${LINUX_BASE_DIR}" "${NFS_ROOTFS_DIR}". I commented this line out and the script never stuck again.
Could you tell me what this line is doing? It seems that it’s checking network access, but I don’t know why I need it for flashing.