In between the step 4. and 5. and after installing nvidia-l4t-jetson-orin-nano-qspi-updater, the following part was not happening
automatically runs its script to schedule the entire QSPI update to be performed during the next boot process, so that the firmware is ready for JetPack 6.x.
As a result, it’s stuck in an awkward “L4T Support Protocol - Not Found”
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are experiencing an issue with the Jetson Orin Nano, specifically with the L4T Support Protocol not being found. This issue is preventing you from completing the initial setup guide.
To resolve this issue, I would recommend the following steps:
Verify the firmware version: Ensure that your Jetson Orin Nano is running the latest firmware version. You can check the firmware version by running the command nvbootctrl get-firmware-version in the terminal.
Update the firmware: If your firmware is not up-to-date, update it to the latest version. You can do this by running the command sudo apt-get update && sudo apt-get install nvidia-l4t-jetson-orin-nano-qspi-updater and then following the prompts to update the firmware.
Check the L4T version: Ensure that you are running the correct version of L4T (Linux for Tegra) for your Jetson Orin Nano. You can check the L4T version by running the command cat /etc/nv_tegra_release in the terminal.
Update L4T: If your L4T version is not compatible with JetPack 6.2, update it to the latest version. You can do this by running the command sudo apt-get update && sudo apt-get install nvidia-l4t-jetson-orin-nano-qspi-updater and then following the prompts to update L4T.
Reset the device: If the above steps do not resolve the issue, try resetting the device to its default settings. You can do this by running the command sudo nvbootctrl reset in the terminal.
In comparison to other issues mentioned in the context, this issue seems to be related to the firmware and L4T version. The issue mentioned in the context “R36.4.3 L4T 版本 HDMI 不显示” seems to be related to HDMI display issues, whereas the issue “Jetson Orin Nano I was following Initial Setup Guide” seems to be related to the initial setup process.
Additionally, the context mentions other issues related to the Jetson Orin Nano, such as camera issues, fan issues, and boot issues. However, these issues do not seem to be directly related to the L4T Support Protocol not being found.
In terms of software versions, the context mentions linux 5.10.120, R36.4.3 L4T, and JetPack 6.2. It is essential to ensure that the firmware and L4T versions are compatible with the software versions being used.
In conclusion, to resolve the issue of the L4T Support Protocol not being found, it is essential to verify the firmware version, update the firmware and L4T if necessary, and reset the device to its default settings if the issue persists.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Based on your screen shot, the UEFI still in JP5.1.3.
Please prepare a native ubuntu to flash your machine.
The sdk manager is more straightforward way to flash dev kit.
Attention
This part may look very confusing as neither the attached monitor nor the debug UART shows any explicit message on what action to take next.
In fact, it was beyond very confusing without knowing the underlying processes. My speculation (after making it work) is: right after the reboot with old 5.1.3 kernel, the boot process will still need to read some files from the 5.1.3. SD card, UNTIL it’s stuck by design. However, the doc did NOT mention what ‘update is one’ means:
Once the update is done, it reboots and tries to boot, however it will get stuck UNLESS you change the SD card to JetPack 6.x one .
In my case, I took the JP5.1.3 SD card too early. The first part of rebooting (until the intentional stuck) was incomplete. The issue got solved after I delayed the SD card replacement (from 5.1.3 to 6.1.2) until it’s actually stuck, as instructed by the doc.
This indeed turned to be an interesting story that, if you know it, it’s never a problem. But for newcomers, this can be more than very confusing as the doc. itself also claimed. Thinking about improvement to save folks’ time on the same, maybe the document should explain the internal processes behind the scenes first, instead of just asking to wait for ‘stuck’. That way, the readers can determine the better/right timing to replace SD card, if not other more user-friendly way…
FYI
P.S.: during this troubleshooting process, I used Cytrence Kiwi (the small black gadget in the photos below) which really helped to observe the subtle changes with its video recording feature. It was also very convenient to access Jetson’s GUI without extra monitor, keyboard/mouse - all I needed was just my laptop. I could even copy&paste commands to Jetson without network. Happy to share my setup:
