When trying to reflash the AGX Orin I received an error. The log is attached and screenshots provided.
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_AGX_Orin_modules_2024-06-16_16-26-07.zip (149.7 KB)
Your module is not even recognized.
Are you sure it’s in force recovery mode?
16:26:50.826 - Info:
16:26:50.836 - Info: Board ID() version() sku() revision()
16:26:50.836 - Info:
16:26:50.839 - Info: Chip SKU(00:00:00:D0) ramcode() fuselevel(fuselevel_production) board_FAB()
16:26:50.839 - Info:
16:26:50.839 - Info: Error: Unrecognized module SKU
16:26:50.839 - Info:
16:26:50.840 - Info: Error: /mnt/d/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/signed/flash.idx is not found
16:26:50.840 - Info: Error: failed to relocate images to /mnt/d/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/tools/kernel_flash/images
16:26:50.840 - Info:
16:26:50.840 - Info: Cleaning up...
This might be painful but the easiest way would be to reflash it all over again.
Before reflashing, delete the nvidia folder present in your home directory in your host machine:
sudo rm -rf ~/nvidia/
There is one more folder in your Downloads directory (something named as nvidia i think), delete that too
rm -rf ~/Downloads/*folder related to nvidia*
If you reflash now and all your settings are correct, then there should be no problem I think.
You can also delete ~/.nvsdkm
Well I did put the device in forced recovery mode. When that happens, SDK Manager cannot find the device so I never get pass Step 02 for flashing.
Given that the jetson device has already been flashed. I tried Automatic Setup and below is the error in SDK and the error log
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_AGX_Orin_modules_2024-06-25_18-34-23.zip (78.5 KB)
You should use Manual Setup and make sure the device is really in force covery mode with lsusb.
i ran the command on the jetson device “sudo reboot forced-recovery”. device went down.
then i ran lsusb in wsl on the host computer. the snippet is the before lsusb and the after lsusb command once the device went into recovery mode.
as a result of the device being in recovery mode. SDK Manager could not detect the device (see below)
When I proceeded to the next step in SDK Manager. As you can see below there is an error message at the top and the flash button is grayed out
OK, so I didn’t know you are using WSL until now…
Please don’t use WSL for flashing NVMe/USB unless you can handle kernel building stuff:
Even when flashing eMMC, which is supported, you need to take care of USB connection with USBIPD as mentioned here:
https://docs.nvidia.com/sdk-manager/wsl-systems/index.html
You are supposed to see 0955:7023, not 0955:7020.
ran through the steps several times. received a different error message.
here is the host computer steps
Can you understand what I mean here?
It won’t succeed no matter how many times you try if you have 7020 instead of 7023.
Make sure it’s really in force recovery mode by the pressing button method.
Or give up on WSL and find a real Ubuntu PC if it’s too complicated for you.
Dave - yes I understand.
ran the above. then I went into SDK Manager to Step 4 and received the below
went back to the host and ran lsusb and the device was no longer there
Are you flashing into eMMC this time?
NVMe/USB is not supported as I mentioned above.
Get the log here.
(SDK Manager flashing log/serial consoel log)
Get the zip file from SDKM here.
You need to add the --auto-attach option when using USBIPD.
usbipd.exe wsl attach --busid <BUSID> --auto-attach --distribution <distribution>
used the format you specified above and received the below:
PS C:\WINDOWS\system32> usbipd wsl attach --busid 2-2 auto-attach-distribution Ubuntu-20.04
usbipd: error: The ‘wsl’ subcommand has been removed. Learn about the new syntax at Connect USB devices | Microsoft Learn.
Went to the documentation and there was no mention of auto-attach. Only usbipd attach --wsl --busid . Nonetheless, I received an error as seen above
Then you use
usbipd.exe attach --wsl…
instead of
usbipd.exe wsl attach…
went back into SDK not that the code is 7023
Received this error again
Log below
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_AGX_Orin_modules_2024-06-25_20-32-33.zip (201.1 KB)
Maybe try another USB cable.
If all of them still fails, give up on WSL and find a real Ubuntu PC.