Jetson Orion NX not booting

[KevinFFF]

@nagesh_accord

where as in atf_and_Optee_README.txt file it says the UEFI STMM Image should be exported from the path:
<Linux_for_Tegra>/bootloader/standalonemm_optee_t234.bin

why is this difference?

This binary(uefi_StandaloneMmOptee_RELEASE.bin) is included in BSP package(<Linux_for_Tegra>/bootloader/standalonemm_optee_t234.bin) by default.
To apply the change, please use the binary you built from UEFI source.

I use optee_src_build.sh to build OP-TEE source and use make to build ATF source.

[nagesh_accord]

@KevinFFF

I’ve checked this with internal that the next release may be on early Janunary. (should be R36.4.2)

As Nividia released this version?

[KevinFFF]

@nagesh_accord

As Nividia released this versio

Sorry that it has not been released yet and it might be R36.4.3 instead.
Please let me update this topic once it is released.

[KevinFFF]

Hi @nagesh_accord,

It seems Jetpack 6.2(R36.4.3) is just released.
Please verify it to check if there’s still any boot issue.

[nagesh_accord]

Thanks for the updates.
Will check and let you know.

[nagesh_accord]

@KevinFFF

I have built the UEFI_STMM… bin file after modifying the code( applying the patch). But we see the the bin file size of the newly generated UEFI_STMM.bin is same as the earlier default UEFI_STMM.bin file present within ./bootloader folder as shown below:

Any idea about this?

Thanks

[KevinFFF]

It should be fine with the same size since the patch is light.

Have you tried to flash Jetpack 6.2 (R36.4.3) directly to verify?
It should include the fixes for this boot issue.

[nagesh_accord]

@KevinFFF

Have you tried to flash Jetpack 6.2 (R36.4.3) directly to verify?

It is in progress. Will let you know soon. Thanks.

[nagesh_accord]

@KevinFFF

It should be fine with the same size since the patch is light.

Have you tried to flash Jetpack 6.2 (R36.4.3) directly to verify?
It should include the fixes for this boot issue.

Hi Kevin,

As flashing the updated TOS image worked fine and repeated manual reboot is not causing any crash, we did not try flashing the new version as of now.

In case we get a chance to flash new version R36.4.3, we will update you.

Thanks.

[KevinFFF]

Congratuation!
It should be fine if you’ve confirmed that the fix has been applied correctly.

[nagesh_accord]

@KevinFFF

It should be fine if you’ve confirmed that the fix has been applied correctly.

As the below verification steps are not fully working, step no 3 not working, as there is no response from keyboard once, we enter on the “Reset Setting”

Verification steps

Step 1: Enter UEFI Menu.
Step 2: Select Device Manager → NVIDIA Configuration → Reset Setting.
Step 3: Go back top menu and press Reset to Exit.
Step 4: Check if it can boot with successful

We tried to verify by manually reboot the unit from external power button pressing, multiple times, it booted successfully. Can this be considered as the TOS image fix has been updated and its been working?

Is there any other verification method to test this TOS image fix?

[KevinFFF]

@nagesh_accord

We tried to verify by manually reboot the unit from external power button pressing, multiple times, it booted successfully. Can this be considered as the TOS image fix has been updated and its been working?

Yes, you can perform the reboot stress test to check if you would still hit that assertion issue after you updated the TOS image.
For no response from keyboard, it seems like another issue which we don’t hit on our setup.
From our verification, keyboard can work before and after updating TOS image.

@nagesh_accord

Is there any other verification method to test this TOS image fix?

We would suggest performing the reboot stress test to check if it would still hit any boot issue.

[nagesh_accord]

@KevinFFF

For no response from keyboard, it seems like another issue which we don’t hit on our setup.
From our verification, keyboard can work before and after updating TOS image.

1. What I meant was, keyboard works fine for us, but when we enter step No 3 after selecting “Reset Setting”, in your verification method steps, it stops responding.
   Could you confirm, if this works on your setup.

2. We have flashed latest r36.4.3 and we will try to check if we have same keyboard stuck up issue at Step No 3 and will let you know.

Thanks.

[nagesh_accord]

Continuing from the other thread as recommended:

Assertion issue in UEFI during boot

For your specific issue, please just discuss in Jetson Orion NX not booting - Jetson & Embedded Systems / Jetson Orin NX - NVIDIA Developer Forums topic.

@KevinFFF

Please check if you can perform above steps w/o any changes.

1. After flashing the QSPI with old TOS img file, the unit is always entering the UEFI Shell ( Note: I had kept updated StandaloneSTMM bin file under /bootloader directory, is this causing the issue?) and it not booting further.

please find the serial log for the same attached below:

UEFI_Boot_error_21_Jan.txt

2. We tried, “Reset Setting” option, but again it is not booting.

Let us know how to fix this issue.

3. Also we are facing NVMe flash issue, I have raised a seperate thread for that. Please let us know, how to fix these issues as soon as possible.

Orin Nx 16GB restoring/reflashing fail - "Error: Unable to partprobe /dev/nvme0n1"

Hi, We had flashed our Orin NX 16GB SOM with Jetson version r36.3.0 and delivered the unit to the customer. Later due to repeated abnormal power on and power off, UEFI assertion crash issue happened and unit was returned back to us as it was not booting. We flashed the QSPI internal memory with the updated TOS.img and later and it was booted successfully. Now, we want to do a complete re-flashing/restoring to NVMe memory for testing purpose. But to our surprise, we see some NVME re…

4. Also I tried flashing 36.4.3 latest Jetson Linux version( Note: I have downloaded this version on USB SSD drive as we have shoratge of space on the hard disk in the Host PC) on Orin NX 16 GB and it flashed fine. Unit booted fully normally.

But we want to configure this Orin NX as EP device, so I modified the ‘jetson-orin-nano-devkit.conf’, file as per the below link and tried reflashing, but we are getting flashing error in the middle, saying “No file found /dev/nvme01”. Any idea why?

https://docs.nvidia.com/jetson/archives/r36.4.3/DeveloperGuide/SD/Communications/PcieEndpointMode.html#flashing-pcie-as-endpoint-on-a-jetson-orin-nx-nano-series-system

Thanks.

[KevinFFF]

@nagesh_accord

What I meant was, keyboard works fine for us, but when we enter step No 3 after selecting “Reset Setting”, in your verification method steps, it stops responding.
Could you confirm, if this works on your setup.

yes, it is working on our setup also when I select “Reset Setting”.
Could you get a devkit to clarify the issue?

[nagesh_accord]

@KevinFFF

yes, it is working on our setup also when I select “Reset Setting”.
Could you get a devkit to clarify the issue?

Thanks for the confirmation.
Sorry, We dont have Orin NX Dev kit with us to verify.

[KevinFFF]

Please help to clarify what causes the keyboad hang issue on your setup.
We don’t receive other users reporting similar issue with current patch.

[nagesh_accord]

@KevinFFF

Please help to clarify what causes the keyboad hang issue on your setup.
We don’t receive other users reporting similar issue with current patch.

Hi Kevin,

Thanks for your support.

As the UEFI Assertion crash issue was solved with the latest release 36.4.3, we did not get time to try to further experiment/debug on UEFI Assertion patch with older version 36.3.0.

But I will try to explain what I did:

1. I followed the steps provided by you and some other links and downloaded UEFI source and updated the patch and built UEFI_StandaloneMM…bin file and copied it as " standalonemm_optee_t234.bin" under /bootloader directory.

2. Later used Export command to set the path to the updated “standalonemm_optee_t234.bin”

3. Next built the TOS image using nv_build…sh scripts as per the link in other thread.

4. Later copied this updated TOS image to /bootloader directory and did the internal memory flash.

5. We tested with back to back, external power on/off and did not observe any crash.

6. Actually this crash issue was reported by our customer and we dont knw exactly how he got this issue( dont know exact scenario )

In future, we may get time to experiment/try on another Orin NX module, that time, will try to do a rebuild once again and flash the internal memory and see, if this keyboard hang issue occurs again.

Thanks

Regards,
Nagesh R

[KevinFFF]

Hi nagesh_accord,

Thanks for your update.
Yes, we would suggest verifying reboot stress test to confirm the reliability.

[nagesh_accord]

@KevinFFF

Yes, we would suggest verifying reboot stress test to confirm the reliability.

For revision 36.4.3

1. We performed reboot steps 2-3 times as per the verification steps (involving UEFI menu and choosing Reset settings and reboot) , provided by you. There is no boot issues.

2. We performed reboot stress test back to back by external power-on and power-off steps and did not observe any boot issues/errors.