The project encountered an issue OTA upgrade the bootloader.
The machine initially used the L4T R35.4.1 software version. According to the official documentation for OTA operation. First , Through OTA update the bootloader to R35.5.0 version. Then, The second OTA update playload package with modified UEFI program base on R35.5.0 version . If the power off was interrupted during the update process( at Update Progress - 8% ****++++++++++++++++++++++++++++++++++++++++++++++), the machine would not be able to startup
Below log is operating the machine from debug uart.
*** Please note that this reply is generated by LLM automatically ***
The issue you’re encountering with the Jetson Orin Nano during an OTA (Over-the-Air) upgrade of the bootloader seems to be related to a problem with the partition management or the loading of firmware. Here’s a breakdown of the problem and potential solutions based on the provided log and context.
Problem Analysis:
Interrupted Update Process: The update process was interrupted during the power-off at Update Progress 8. This interruption likely caused the system to not complete the necessary steps for a successful update, leading to a failure in the bootloader update process.
Partition Not Found Error: The log indicates an error where the partition “Bspefw” cannot be found. This partition is crucial for the firmware loading process, and its absence or inaccessibility can prevent the system from booting correctly.
MB2FWLOAD Failed to Load FW: This error suggests that the MB2 (Bootloader) failed to load the necessary firmware, which is a critical step in the boot process. Without the correct firmware, the system cannot proceed with the boot process.
Comparison with Similar Issues:
The issue you’re facing is somewhat similar to the one described in the context under “Jetson Orin Nano Flash Complete boot issue “OTA work directory is not found on internal and external storage devices””. Although the specific error messages differ, both issues seem to stem from problems during the OTA update process that affect the system’s ability to boot correctly.
Another related issue is “OTA Update causing unbootable state Jetson Orin Nano ota”. While the details of the error messages are not identical, both cases involve an OTA update causing issues that lead to an unbootable state, suggesting that there might be common underlying causes or vulnerabilities in the OTA update process for the Jetson Orin Nano.
Potential Solutions:
Re-attempt the OTA Update: Ensure that the update process is not interrupted and that the system has a stable power supply throughout the update.
Verify Partition Integrity: Check the partition table and ensure that the “Bspefw” partition exists and is accessible. You might need to use a tool like fdisk or gparted to inspect the partition layout.
Manual Firmware Loading: If the automatic loading of firmware fails, you might need to manually load the firmware using tools provided by NVIDIA or through the use of a serial console.
Revert to Previous Version: If the issue persists, consider reverting to the previous software version (R3541) and then attempt the OTA update again, ensuring that the process is not interrupted.
Contact NVIDIA Support: Given the complexity of the issue and the potential for it being a bug in the OTA update process or the bootloader, it might be necessary to contact NVIDIA support for further assistance or to report the issue.
In summary, the problem seems to be related to the interruption of the OTA update process and the subsequent failure to load necessary firmware, leading to a boot failure. Addressing these issues by ensuring a stable update process, verifying partition integrity, and potentially manually loading firmware or reverting to a previous version might resolve the problem.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
The issue still requires support. It can also be replicated on the development kit and official L4T version. Unfortunately, The OTA upgrade will cause the machine can't boot up.
Thanks！
This issue was first discovered , when the mass production via OTA upgrading from JetPack 5.1.2(L4t 35.4.1) to JetPack 5.1.3(L4t 35.5.0) , and next step upgrading to Jetpack 6.2(L4T 36.4.3 ) . We believe the NVIDIA Teams can verify this issue using the Orin Nano development kit.