I’ve tried a lot of things to flash my Orin NX 16GB dev kit with an NVMe SSD, but can’t get it working.
Earlier I’ve tried sdkmanager from Ubuntu 22.04. That allowed me to install JP6 DP2 once but when I power cycled, it didn’t come alive again. Have been able to reproduce this.
Then I read that others had success when moving to Ubuntu 20.04, so I ran sdkmanager as a docker image using 20.04. Here flashing got stuck when reaching 99% and I had no success getting to a bootable system.
Now I have connected a serial-to-USB adapter, but there is no sign of life when booting after the previous unsuccessful attempt to install.
In an earlier post here lhoang instructed two methods. In both methods, the flash command fails with these famous last words:
No I don’t have a solution, sitting with a non-functional dev kit and spending my nights in unsuccessful attempts to flash it.
After the above attempts I again ran sdkmanager from Ubuntu 22.04 and it printed that it was able to generate a new GPT, but during the process I get a lot of flashing errors and when the dev kit finally reboots, the last famous words on the UART are now:
[ 311.232028] kvm: exiting hardware virtualization
[ 311.420319] tegra194-pcie 140a0000.pcie: Link didn’t transition to L2 state
[ 311.451211] arm-smmu 12000000.iommu: disabling translation
[ 311.451302] arm-smmu 8000000.iommu: disabling translation
[ 311.451384] reboot: Restarting system
����Shutdown state requested 1
Rebooting system …
Even after a restart there is no sign of life so my suspicion is that the boot process fails. Isn’t the QSPI a new element here that Nvidia hasn’t used earlier? I read that the boot loader doesn’t generate log output by default but I have no idea how I can enable it during the install process, before first boot.
The Xavier dev kits have been much more stable, just saying.
Sure. Attached you can find the logs from sdkmanager running on Ubuntu 22.04 and the UART output while flashing.
In the end it says rebooting but nothing happens after that. Even a cold restart doesn’t provoke any signs of life other than that the Jetson is getting moderately warm. No UART output or boot logo. The APX device is visible on USB.
That is unfortunately a bit more involved since JP5 requires Ubuntu 20.04 that I don’t have at hand.
I tried the approach to pack sdkmanager in a Ubuntu 20.04 docker container and started the flashing process. It stops at 99% and never finishes. These are the remaining processes:
I just found that Flashing Orin Nano Dev Kit NVMe hangs at 99% seems to be another report of the hang I observe with sdkmanager in docker. Unfortunately closed without solution.
I have spent just too many hours to get this thing running. I’m stuck and would so much only like to get started with Orin and the wonderful world of LLMs. Instead I’m forced to dig deep into QSPI, GPT, ratchets and why value 0x31 is out of range.
Guys, it is working now. I have managed to get hold of an older laptop with an Intel CPU and did a fresh Ubuntu 20.04 install, then using sdkmanager. I’ve first been flashing JP5, then JP6 as Wayne asked for.
The earlier unsuccessful attempts have been with an AMD R5 5600 CPU and Ubuntu 22.04. No idea why that fails while Intel CPU (8th gen) and Ubuntu 20.04 works.