We flashed the Orin NX on our customized carrier board ( linux for Tegra version 36.4.3) successfully.
But after booting, we observed that it is booting to UEFI shell always.
We went in to Boot manager and checked and found that NVMe is not listing even though it was successfully flashed.
Any idea why this issue is happening?
Also if we try to do restore , then we get some error saying “your are trying to flash images from a board model that does not match the current board your flashing…”.
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, I’ll try to help you resolve the issue.
Issue Summary:
After successfully flashing the Jetson Orin NX on a customized carrier board with Linux for Tegra version 3643, the system always boots to the UEFI shell. The NVMe device is not listed in the Boot manager, despite being successfully flashed. Additionally, attempting to restore the system results in an error.
Possible Causes:
UEFI Configuration: The UEFI configuration might not be set correctly, causing the system to boot to the UEFI shell instead of the Linux kernel.
NVMe Device Detection: The NVMe device might not be properly detected or configured, leading to it not being listed in the Boot manager.
Flashing Issues: There might be issues with the flashing process, such as incorrect configuration or incomplete flashing, which could cause the system to not boot correctly.
Troubleshooting Steps:
Verify UEFI Configuration: Check the UEFI configuration to ensure that the boot order is set correctly. Make sure that the NVMe device is set as the first boot device.
Check NVMe Device Detection: Verify that the NVMe device is properly detected by the system. You can check the kernel logs or use tools like lspci or nvme list to detect the NVMe device.
Reflash the System: Try reflashing the system using the initrd flash method, as described in the context. Make sure to use the correct configuration files and options.
Check Boot Manager: Verify that the Boot manager is configured correctly. Check the boot order and ensure that the NVMe device is listed.
Restore System: If the issue persists, try restoring the system to its default configuration. This might help resolve any configuration issues.
Comparison with Other Scenarios:
The provided context mentions that the initrd flash method is used for flashing the Jetson Orin NX and Nano series with NVMe as the external storage device. This suggests that the flashing process is specific to these devices and might require specific configuration files and options.
In contrast, the flash.sh method is used for flashing the Jetson AGX Orin series, which might have different configuration requirements.
Additional Information:
To further troubleshoot the issue, please provide more information about the customized carrier board, such as the hardware configuration and any modifications made to the default configuration.
Additionally, please provide the exact error message when attempting to restore the system, as this might help identify the root cause of the issue.
By following these troubleshooting steps and providing additional information, we can work together to resolve the issue and get the Jetson Orin NX system booting correctly.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Yes. We realized it bit later as it was long time, we came across this issue of /dev/nvme0n1 causing problem during flashing.
Checked with the hardware team, probably the mounting of NVMe is not properly on the carrier board. We are trying to flashing again on the properly mounted NVMe and let you know.
This was some hardware related issue, the external NVMe on the carrier board was not mounted properly. After some touch ups in the circuitry it started detecting NVMe and booted fine.
