I’m trying to backup a Nvidia Jetson NX orin 16GB using the tool (backup and restore) of jetpack.
I followed the instructions that the board carrier manufacturer (Aetina) gave to me, but for some reason I’m getting a “Waiting for target to boot-up…“ message until it times out.
***************************************
* *
* Step 3: Start the flashing process *
* *
***************************************
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 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 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 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 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 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 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 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 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 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 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 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...
Timeout
Cleaning up...
I’m assuming the board is in recovery mode as I did the steps mentioned by the manufacturer (Press RESET button, Press RECOVERY butoon while the RESET button is pressed, release the RESET button and then release the recovery button).
Noting that the HOST is a ubuntu 20.04 that is installed in a VM (VMware Workstation). The procedure for recovery triggers a popup in the VM asking to choose where the board should be connected (Standard HOST, i.e. my machine or VM HOST).
I know that years ago I flashed a board using a VM and it worked (the waiting for target to bootup didn’t timeout). If I recall correctly, after the first 10 or so “Waiting for target to boot-up…”, the popup to connect the board to VM appeared, I chose the VM HOST and the flash procedure worked just fine.
In sum, I did the following:
Download the jetpack 5.1.2 from sdk manager
Put the nvidia in recovery mode
Used the “sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit” command, while on the Linux_for_tegra directory.
*** Please note that this reply is generated by LLM automatically ***
I’d be happy to help you troubleshoot the issue with backing up your Nvidia Jetson NX Orin 16GB using the backup and restore tool from Jetpack.
Firstly, it’s great that you’ve followed the instructions provided by the board carrier manufacturer, Aetina, and that you’ve tried to put the board in recovery mode by pressing the RESET and RECOVERY buttons. However, it seems like the backup process is getting stuck at the “Waiting for target to bootup” message, which is timing out.
Based on your description, it’s possible that the issue is related to the VM environment you’re using. You’ve mentioned that you’re using a Ubuntu 20.04 VM installed on VMware Workstation, and that you’ve encountered a popup asking you to choose where the board should be connected (Standard HOST or VM HOST).
Here are a few potential solutions you could try:
Try connecting the board to the Standard HOST: Instead of choosing the VM HOST, try selecting the Standard HOST option. This might allow the backup process to complete successfully.
Disable the VM’s USB redirection: Sometimes, the VM’s USB redirection feature can cause issues with device connectivity. Try disabling this feature and see if it resolves the issue.
Use a different USB port: Try using a different USB port on your host machine to connect the Jetson board. This might help resolve any issues related to USB connectivity.
Check the Jetson board’s recovery mode: Ensure that the Jetson board is properly in recovery mode by checking the LEDs on the board. The LEDs should be blinking in a specific pattern to indicate recovery mode.
Try using a different backup command: Instead of using the sudo tools/backup-restore/l4t_backup_restore.sh command, try using the sudo tools/backup-restore/nvbackup_partitions.sh command. This command is specifically designed for backing up the Jetson board’s partitions.
Check the backup log files: Check the backup log files to see if there are any error messages that might indicate what’s causing the issue.
In comparison to your previous experience with flashing a board using a VM, it’s possible that the issue is related to changes in the VM environment or the Jetpack version. However, by trying the above solutions, you should be able to resolve the issue and complete the backup process successfully.
If none of these solutions work, please provide more details about your setup, including the exact commands you’re using and any error messages you’re seeing. I’ll do my best to help you troubleshoot the issue.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
This is expected, as the backup/restore process goes through similar stages as flashing.
Regarding the timeout issue, please use a native Ubuntu environment to perform the flash/backup/restore.
I tried doing the same in local machine, but the symptom remains.
I noticed something on the board:
When I put it in recovery mode using the buttons, the fan stops spinning and the ethernet port doesn’t turn on.
If I use the command line to force recovery, the ethernet port has a light blinking.
After I run the backup and restore script, when the message “Waiting for target to boot up” appears, the fan starts spinning. The state of the ethernet port remains the same on both recovery modes.
By the way, does the script “sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit“ works on boards with nvme? I mean the -e nvme0n1 should force it, but I noticed on the logs that the “mmcblk” strings shows up.
I found out that the Nvidia Jetson doesn’t recognize the host, i.e. the lsusb command on the nvidia, doesn’t show it. However the lsusb command on the host shows the Nvidia. Is this expected?
I also noticed that there is no boot screen, when the nvidia is turned on. Only a top left cursor blinking.
Is it possible that the host recognizes de nvidia, but the nvidia doesn’t recognize the host because of some parameter or configuration?
Ok, so I contacted Aetina and they pointed out the issue: I needed to apply a patch to the jetpack 5.1.2 on the Host. I did it and now I’m able to start the backup process. However I’m facing another issue. The backup stops/hangs at “tar: write checkpoint 3870000”. Why does it happen?