i have a Orin Nano 8GB SOM which i was actively developing with.
I tried to get it booting from an USB-Stick, but this still had some issues.
As soon as it started booting the Ubuntu from the NVMe, i turned off the power. After about one second, i turned it on again.
After a few of these tries, the device did start (the fan was spinning) but it did not boot.
Checking the debug-UART, i noticed an error. So i tried to reflash the device inside the Orin Nano DevKit Carrier board but i get the same error over and over again:
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are experiencing issues with booting your Jetson Orin Nano 8GB SOM from an NVMe drive. You’ve tried reflashing the device, but you’re still encountering errors.
To analyze and fix this issue, let’s break down the steps you’ve taken and the potential causes:
Boot issues from USB stick: You initially tried booting from a USB stick, but it had some issues. This could be due to various reasons such as incorrect boot configuration, corrupted boot files, or hardware issues.
Power cycling: You turned off the power and then turned it back on after a few seconds. This could have caused the device to enter a state where it’s unable to boot properly.
Fan spinning but no boot: After a few power cycles, the fan started spinning, but the device didn’t boot. This suggests that the device is partially functioning, but there’s an issue preventing it from booting completely.
Debug UART error: You checked the debug UART and noticed an error. Unfortunately, you didn’t provide the specific error message, which would be helpful in diagnosing the issue.
To troubleshoot this issue, you can try the following steps:
Check the debug UART error: Provide the specific error message from the debug UART. This will help identify the root cause of the issue.
Verify the boot configuration: Ensure that the boot configuration is correct. You can try reflashing the device with the same Linux for Tegra and hardware to rule out any configuration issues.
Check the NVMe drive: Verify that the NVMe drive is properly connected and configured. You can try booting from a different NVMe drive or a different storage device to isolate the issue.
Try a different boot method: Instead of booting from the NVMe drive, try booting from an SD card or a USB stick. This will help determine if the issue is specific to the NVMe drive or a more general boot issue.
Reflash the device: If none of the above steps resolve the issue, try reflashing the device again. Make sure to use the same Linux for Tegra and hardware to rule out any configuration issues.
In comparison to the provided context, your issue seems to be related to the “Jetson Orin Nano Developer Kit – Black Screen and Fan Stops After Boot (JetPack 5.1.3)” issue. However, the error messages and debug UART output would be helpful in determining the root cause of the issue.
Additionally, you can refer to the “Optimizing Boot Time on Jetson Orin with Jetpack 6.2” article for tips on optimizing the boot time, which might help resolve the issue.
If none of these steps resolve the issue, it’s possible that there’s a hardware problem with the Jetson Orin Nano SOM or the NVMe drive. In this case, you may need to contact NVIDIA support or the manufacturer of the NVMe drive for further assistance.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
The specific error message from the debug UART is appended (debug_uart_1421125042614.txt).
The 1421125042614 is, by the way, the serial number of the SOM.
The USB-Booting Problem is not part of the issue, it is just for explanation what happened before the error occurred.
The NVMe was working fine before the issue occurred. The orin booted from it when the USB Boot failed, so it was configured correctly.
Therefore “Try a different boot method” is irrelevant in this case
“Reflash the device”: This is what i tried to fix this issue but it also appeared during the reflash procedure, which was working before with just the same hardware and software.
I don’t consider a JP5.1.3 topic about black screens (maybe a pinmux error?) as relevant.
If you think that another issue could be relevant, it would be great if you can provide a direct link that people can follow since thread names in the forum can be quite similar. Human laziness greatly reduces the likelihood that someone will search for a thread by its name.
Boot time optimization might be a nice thing but will in no case help with flashing issues.
So to sum it up:
You had a small misunderstanding about the issue. It is not about boot devices, boot configuration and hardware installation. It instead is about a device failing after doing a thing that worked before.
Due to the misunderstanding, the troubleshoot hints are not matching.
As you already noticed, having a specific error log is very helpful. So it would be a good addition, if you can access and analyze it.
to clarify the situation:
I flashed the Jetson both times with the same software package to the NVMe. It was every time 1:1 the same procedure.
My goal was to later boot from the USB stick with the NVIDIA UEFI. This has no direct relation to this issue and is just for explaining what i have done.
My goal now is getting the SOM back working again with flashing a JetPack on it.