Assertion issue in UEFI during boot

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
65

Hi, @KevinFFF, I applied the patch from Assertion 3 to address the assertion error on our end:

ASSERT [FvbNorFlashStandaloneMm]
/dvs/git/dirty/git-master_linux/out/nvidia/optee.t234-uefi/StandaloneMmOptee_RELEASE/edk2-nvidia/Silicon/NVIDIA/Drivers/FvbNorFlashDxe/FvbNorFlashStandaloneMm.c(978): ((BOOLEAN)(0==1))

However, now I’m wondering if applying this patch alone doesn’t fully resolve the issue —it looks like we also need to update the TOS image. So, 1) I’d like to know if that means the patch isn’t necessary once the TOS update is applied? 2) If we do need the TOS image fix, could you advise how to apply it on top of JetPack 5.1.4, is there a patch for that?

66

Hi daniel.chaves,

Please note that the fix is included in tos image(i.e. A_secure-os, B_secure-os partition) rather than UEFI binary(i.e. A_cpu-bootloader, B_cpu-bootloader partition).
You can simply update the tos image in BSP package(i.e. <Linux_for_Tegra>/bootloader/tos-optee_t234.img) and reflash the board or create the capsule payload for capsule update to apply the change.

67

Got it, so, do you think it’s okay if we use the JP6 TOS image in our JP5.1.4 system? Thanks!

68

No, we don’t suggest doing so as they are from different releases.
Please apply the patches and update tos image instead.

69

If I download the Driver Package (BSP) from JP5.1.5, I see that the TOS image is from May:

$ ls -lh ./Linux_for_Tegra/bootloader/tos*t234.img
-rw-rw-rw- 1 dchvs dchvs 1.3M May 15 19:54 ./Linux_for_Tegra/bootloader/tos-optee_t234.img
lrwxrwxrwx 1 dchvs dchvs   18 Nov 13 08:36 ./Linux_for_Tegra/bootloader/tos_t234.img → tos-optee_t234.img

$ md5sum  ./Linux_for_Tegra/bootloader/tos*t234.img
34a94cafae4df0cc8afc26dbe5275d51  ./Linux_for_Tegra/bootloader/tos-optee_t234.img
34a94cafae4df0cc8afc26dbe5275d51  ./Linux_for_Tegra/bootloader/tos_t234.img

  1. Please confirm that the assertion issues had already been resolved by then in that file.

  2. This binary works for the Orin AGX and NX as well, right?

70

Please check my original post that the assertion 3 is not included in JP5.1.5.

Yes, AGX Orin and Orin NX/Nano are all Orin series(T234) and they use the same tos image.

71

Latest JP5.1.5 is a L4T 35.6.2.
The TOS image for 35.6.1 is from March, and the one for 35.6.2 is from May, as mentioned. Does that make any difference?

72

r35.6.2 is just a minor update from r35.6.1, there’s no related fix included for the current assertion issue.

74

Dear Nvidia support team, Dear KevinFFF.
Is there a plan to include patch for assertion 3 error to Jetpack 5.1.X ?
I am using 5.1.6 and the problem is still here.
Thank you.

1 Like
75

I think Jetpack 5.1.6(r35.6.4) should have the fix included.
How did you install Jetpack 5.1.6?

76

I have used SDK manager to flash jetson orin nano with jetpack 5.1.6.
Boot device is SD card.

77

Are you using the Orin Nano devkit so you used SDK manager to flash?
If so, how did you reproduce the issue?
Could you share the detailed steps with us to verify?

78

Yes, I am using Orin Nano Devkit 8GB Ram.
Yes, I have used SDK manager to flash it. (SDK manager installation file : sdkmanager_2.4.0-13235_amd64.deb)
Assertion issue has occurred when I tried your method.: Select Device Manager → NVIDIA Configuration → Reset Setting. ; Go back top menu and press Reset to Exit ; repeat

More details in attached files:

  1. SDK Manager log
  2. Screenshots + host OS info
  3. Output from jetson console during last reboot

SDKM_logs_JetPack_5.1.6_Linux_for_Jetson_Orin_Nano_[8GB_developer_kit_version]_2026-03-11_15-26-54.zip (7.0 MB)

jetson_orin_nano_5.1.6_ assertion_issue.log (35.6 KB)

SDKManager_On_Ubuntu.zip (1.3 MB)

79

maybe one more important information:
I have repeating post install notification with no effect

Screenshot from 2026-03-12 22-25-24
Screenshot from 2026-03-12 22-25-241920×1080 279 KB