Hi all, Can any one help me with issue I am having. I am trying to build and F1Tenth car with ROS2 (Humble) as the middleware. So I got a Jetson Nano Orin board. I am following the steps outlines in this link. My current UEFI version is “4.1-33958178” which is less than 36( <36.0) and I followed the steps highlighted in step-3 on the same link. Flashed an SD-card with Jetpack 5.1.3 and then - did “sudo apt update” and “sudo apt upgrade”. Then waited for 20-30 minutes for the firmware to update. I also get a message the l4t-driver has been updated and reboot is required. After reboot, my firmware version is still not updated. I am attaching my log files. Any help would be appreciated.
JetsonBoot.txt (121.3 KB)
For reference, L4T is what one would call the Ubuntu software after NVIDIA drivers are added. JetPack/SDK Manager is flash software used to install/flash that L4T software. JetPack 4.x is for L4T R32.x; JetPack 5.x is for L4T R35.x; JetPack 6.x is for L4T R36.x.
I don’t think the 4.1 at the end of the log is a JetPack version, but is instead related to boot software (which perhaps was flashed using a different JetPack). JP 4.1 was never compatible with any Orin, and any attempt to flash that release would have failed.
Is this a developer kit? Or is it an Orin module with a third party carrier board? Dev kits boot to an SD card and do not have eMMC storage memory. Third party carrier boards use a module with eMMC. On dev kits any SD card slot is on the module itself, while any SD card slot on a third party carrier board is on the carrier board itself, and no such slot would exist on the module.
The reason this is important is that a dev kit has QSPI memory on the module itself, and that memory is where the boot chain content is stored, along with what might be considered the equivalent of the BIOS software. On an eMMC model that same boot/BIOS software is in partitions of the eMMC memory. As a result, the flash is different depending on the model.
For what follows I assume you do not have an eMMC model, but instead have a dev kit. If this is incorrect, then please note what the actual carrier board/module combination is.
The dev kit Orin Nano requires flashing the actual module QSPI once for any major release. Orin Nano is compatible with L4T R35.x (JetPack 5.x) or L4T R36.x (JetPack 6.x), and then it uses a separate SD card for the actual Ubuntu/L4T operating system software. If the major release of the QSPI is different than the major release of the SD card, then it will fail for compatibility reasons. For example, if the Jetson has R36.x in QSPI, but the SD card has R35.x in it (or vice-versa), then boot fails. If you flashed using JetPack 5 (L4T R35.x) once to QSPI, and then had a failed SD card which was itself also L4T R35.x, then this would be a problem which should not occur. It sounds like it isn’t certain what the QSPI is.
Thank you for your help. I am working with the Jetson Orin Nano Dev Kit. I was able to flash the Jetson with 5.1.3 with the SDK Manager using a host machine with Ubuntu 20.04. When doing this the Jetson UEFI firware updated from 4.1 to 5.0-35550185. After going through the BIOS setup I waited for the nvidia-l4t-bootloader Post Install Notification to show up on the screen stating that reboot is required to complete installation. Then I restart the Jetson and this message still appears.
I also run the following command ‘sudo nvbootctrl dump-slots-info’ and it returns the following
Current version: 0.0.1
Capsule update status: 0
Current bootloader slot: A
Active bootloader slot: A
num_slots: 2
slot: 0, status: normal
slot: 1, status: normal
Showing that the Jetson has not been updated. Any help would be much appreciated.
I have not worked with the A/B options, but have you created an SD card from that same release? Also, there is a JetPack release 5.1.4 which you should probably try since it can change the boot chain. If the 5.1.4 install does not work with that SD card, then you can be certain it has valid software. If that software is valid, then it is still possible that UEFI environment might need an update (the environment setup can change even when the flash is the same).
If JP 5.1.4 does not work, and if the SD card is from JP 5 (L4T R35.x), and it still does not work, then you’ll want to attach (A) the flash log from JetPack/SDK Manager from the flash, and (B) any serial console boot log you might have of the failed boot.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.