Question about Bootloader version 0.0.1 on Jetson Orin – definition and OTA compatibility

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
, , ,
1

We are using Jetson Orin 32GB modules with JetPack 5.1.2. We tried to perform a UEFI OTA update (using nv_ota_start.sh) from the same JetPack 5.1.2 base to update only the UEFI firmware.

On some devices the update succeeds, but on others it fails. After the upgrade attempt, the device reboots without showing the UEFI progress bar. Checking the UEFI capsule update status gives error code 6162 (LAS_ERROR_FMP_LIB_UNINITIALIZED).

sudnvidia@nvidia-b:~$ sudo cat /sys/firmware/efi/esrt/entries/entry0/last_attempt_status
[sudo] password for nvidia:
6162

We then ran sudo nvbootctrl dump-slots-info on a failing device and saw:

nvidia@nvidia-b:~$ sudo nvbootctrl dump-slots-info
[sudo] password for nvidia:
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

On a successful device, the current version shows a normal version string (e.g., 35.5.0).

nvidia@nvidia-b:~$ sudo nvbootctrl dump-slots-info
[sudo] password for nvidia:
Current version: 35.5.0
Capsule update status:1
Current bootloader slot: B
Active bootloader slot:B
num slots:2
slot: 0,             status: normal
slot: 1,             status: normal

We suspect that devices showing Current version: 0.0.1 have a factory / pre-production bootloader that does not support OTA capsule updates. This suspicion is based on several community forum discussions (e.g., NVIDIA Developer forums) where 0.0.1 is referred to as a “factory bootloader” that is not OTA‑compatible.

Could you please clarify:

  1. What is the official definition of bootloader version 0.0.1 on Jetson Orin modules? Whether version 0.0.1 is a test version, not an official version？
  2. Is a device showing Current version: 0.0.1 considered to have a factory / engineering‑sample bootloader that does not support OTA (capsule) updates?
  3. If OTA is not supported on such devices, what is the recommended way to bring them to a fully OTA‑capable state (e.g., recovery mode reflash, or a special update tool like nvidia-l4t-jetson-orin-nano-qspi-updater)?
3

Have those problem device be flashed with full JetPack 5.1.2 before?

4

The images of JetPack 5.1.2 I wrote are the same. The difference is that the current versions of sudo nvbootctrl dump slots info are different, which leads to OTA success or failure. I don’t think this is related to images.

5

Here’s a post where the ultimate solution was to, I believe, update with sdkmanager Jetpack 5.1.2, the 0.0.1 nvbootctrl Orin devices. And after you’ve done that, if you have a golden image that your Orins require; then you can ota them from 5.1.2 to 5.1.2.

ota-works-on-some-jetsons-but-not-others

6

— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —

Based on the provided context, I found the following relevant information:

  • The nvbootctrl dump-slots-info command is used to check the bootloader version and status.
  • The Current version: 0.0.1 output is mentioned in the context as a possible indication of a factory or pre-production bootloader that may not support OTA capsule updates.
  • The Capsule update status: 0 output is mentioned as an error code 6162 (LAS_ERROR_FMP_LIB_UNINITIALIZED) when the UEFI OTA update fails.

However, I could not find clear support for the following in the provided Jetson AGX Orin documentation:

  • An official definition of bootloader version 0.0.1 on Jetson Orin modules.
  • Confirmation that version 0.0.1 is a test version or not an official version.
  • Information on whether a device showing Current version: 0.0.1 is considered to have a factory/engineering-sample bootloader that does not support OTA (capsule) updates.
  • A recommended way to bring devices with bootloader version 0.0.1 to a fully OTA-capable state.

Therefore, I can only provide partial support for this question. The provided context suggests that bootloader version 0.0.1 may be related to a factory or pre-production bootloader, but I could not find clear confirmation or official documentation to support this claim.

— We support team will also look into your issue to have further suggestions soon. please stay tuned. —

7

Hello kayccc

The question I’m about to ask is very important. Could you please confirm and get back to me?

    1. What is the official definition of bootloader version 0.0.1 on Jetson Orin modules? Whether version 0.0.1 is a test version, not an official version？
  2. Is a device showing Current version: 0.0.1 considered to have a factory / engineering‑sample bootloader that does not support OTA (capsule) updates?
  3. If OTA is not supported on such devices, what is the recommended way to bring them to a fully OTA‑capable state (e.g., recovery mode reflash, or a special update tool like nvidia-l4t-jetson-orin-nano-qspi-updater)?
9

I use the same computer to burn a batch of identical system images. Some display Current version: 0.0.1 and others display Current version: 35.5.0. Why does this difference occur? In addition, I hope you will reply to me as soon as possible

10

The answers to these questions are also important to me

11

hello jingyi.Li,

may I have more details.. what the difference of your boards that reproduced such failure?