[r36.3] UEFI FvbNorFlashStandaloneMm.c(937): ((BOOLEAN)(0==1)) error

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
,
1

I have an Orin agx which I have booted through an sd-card (JP6.0)
in one of the reboots , for some reason the device did not reboot any more.
I can not flash it again it’s stuck (all the image is runnnig from sd-card , so the information was not lost)

trying to flash it , or using the sdkmange , with no luck.

 Reserved shared memory is disabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualization support is disabled
I/TC: Asynchronous notifications are disabled
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !

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

this is the log in the terminal , any way to re-flash the Orin AGX ?

2

Hello @moshe.arad

You could check information about this issue at [Jetson Orin Nano] [OTA] [35.5.0][36.3] Failed to boot after OTA upgrade from 35.5.0 to 36.3 - #12 by KevinFFF

Is there a possibility that you could reflash your board with JetPack 6.1 or 6.2?

Regards!
Eduardo Salazar
Embedded SW Engineer at RidgeRun

Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com

3

Hi moshe.arad,

Are you using the devkit or custom board for AGX Orin?

It seems you hit Assertion 3 in Assertion issue in UEFI during boot - Jetson & Embedded Systems / Jetson AGX Orin - NVIDIA Developer Forums. Please refer to the details there or you can simply update to the latest JP6.2(r36.4.3)

1 Like
4

Seems I can not simply update as when I am executing

sudo ./flash.sh jetson-agx-orin-devkit internal

it always fails.

...
...
[   1.2314 ] Rebooting to recovery mode
[   1.2331 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[   1.2398 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   1.2412 ] MB2 Applet version 01.00.0000
[   1.2445 ] Booting to recovery mode
[   1.2463 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
[   1.2476 ] MB2 Applet version 01.00.0000
Parsing board information failed.

So I am looking for a command that will “reset” the Orin so I’ll be able to flash it (no matter what the procedure is)
I will upgrade to jp6.2 once I’ll be able to …

5

Hello @moshe.arad

Based on the post that KevinFFF shared, the command you have to run is

sudo ./flash.sh -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal

Regards!

6

it’s not a nano it’s an Orin AGX

ran this command (maye there is another command that can succeed)

sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1

(also thorough the sdkmanage).
in both cases there was no luck.

Parsing board information failed.

This is the log from sdkmanager…

17:07:08 INFO: Flash Jetson Linux - flash: Parsing module EEPROM:
17:07:08 ERROR: Flash Jetson Linux - flash: --- Parsing board ID (ERROR: calculated CRC8 0xbb != stored CRC8 0x0) succeeded.
17:07:08 ERROR: Flash Jetson Linux - flash: --- Parsing board version (ERROR: calculated CRC8 0xbb != stored CRC8 0x0) succeeded.
17:07:08 ERROR: Flash Jetson Linux - flash: --- Parsing board SKU (ERROR: calculated CRC8 0xbb != stored CRC8 0x0) succeeded.
17:07:08 ERROR: Flash Jetson Linux - flash: --- Parsing board REV (ERROR: calculated CRC8 0xbb != stored CRC8 0x0) succeeded.
17:07:08 ERROR: Flash Jetson Linux - flash: Error: Target board not found.
17:07:08 ERROR: Flash Jetson Linux - flash: [exec_command]: /bin/bash -c /home/lab/.nvsdkm/replays/scripts/JetPack_6.2_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: Error: Target board not found.
17:07:08 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
17:07:08 INFO: Flash Jetson Linux - flash: [host] [ 620.00 KB used. Disk Avail on Partition /dev/nvme0n1p2: 71.33 GB ]
17:07:08 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 3s ]
17:07:08 ERROR: command error code: 11
17:07:08 ERROR: Flash Jetson Linux - flash: command terminated with error
7

Hi moshe.arad,

Are you using the official devkit from us?

Or you are using the custom carrier board from 3rd-party?
If so, you have to use custom BSP package instead.

8

Hey, thanks for checking! Yeah, I’m using the official Orin AGX Devkit from NVIDIA, not a custom carrier board, so I should be fine with the standard BSP package, right? Here’s the situation: I’ve got a few of these devkits, and I’ve been running my software off an SD card. One specific Orin AGX got stuck recently, so I just swapped the SD card into another one that was sitting on my desk, and that worked fine. Now, I’m trying to “format” the stuck one to flash it and get it back up and running, but every time I try flashing it, it crashes. Any ideas on what might be going wrong? Appreciate the help!

9

Correct!

If you are using the devkit, you can simply use SDK Manager to flash your board.
There’s internal eMMC in AGX Orin module so that you don’t need to connect SD card when you are flashing the board.

10

As mentioned. I have several Orin AGX on my desk.
I have programmed them using

  1. ./flash.sh commang
  2. sdkmanager

since i got this assertion

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

when I try to program the device (flash it). I get the following

...
...
[   1.2314 ] Rebooting to recovery mode
[   1.2331 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[   1.2398 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   1.2412 ] MB2 Applet version 01.00.0000
[   1.2445 ] Booting to recovery mode
[   1.2463 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
[   1.2476 ] MB2 Applet version 01.00.0000
Parsing board information failed.

Parsing board information failed.

Meaning using the conventional flashing I always fail .
if there a way to “clear” its’ internal memory (like flashing the camera processor ?)
any command line to “bypass” the Parsing board information failed. so it will flash t he device brute force ?
again problem is that I can not flash the device using the conventional commands.

11

Anyone ?
Again , I have 2 devices that I can not flash (program) , do I need to use a Jtag or anything to clear the state ?
or is there a command to clear things up ? seems device is not recognized while in DFU mode…
TIA

12

Just to clarify above log… did you always see that one when you tried to flash?

If so, it means you corrupted some content in the EEPROM on the AGX module… and that one is fatal.

13

And in that case and way to re-flash it ? or there is no way out … (content is saved on sd-card, therefore all I need to do is to try and re-flash it , maybe we can re-flash the EEPROM ?).

14

try this post.

15

thanks.

sudo BOARDID=3701 BOARDSKU=0005 FAB=500 ./flash.sh jetson-agx-orin-devkit internal

this was the solution.

After it can be flashed and boots into kernel, use i2cset to correct the cheksum bit in EEPROM.
anyway I can program the eeprom to factory default ?

16

There is no factory default here. The content in each module is different and once you corrupted, you won’t restore to default anymore unless you write them back manually. But it is not possible for you to know it as you totally didn’t know why you corrupted the EEPROM.

You could calculate the CRC checksum for your EEPROM first.

If you don’t want to calculate it, then just write the value that the log already told you.

17:07:08 ERROR: Flash Jetson Linux - flash: — Parsing board REV (ERROR: calculated CRC8 0xbb != stored CRC8 0x0) succeeded.
17:07:08 ERROR: Flash Jetson Linux - flash: — Parsing board REV (ERROR: calculated CRC8 0xbb != stored CRC8 0x0) succeeded.

In some aspects, we don’t really guarantee this module is fine here. You could also RMA it.

17

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.