Boot fails with Cannot find any partition table for 00030000 after flashing

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

We are flashing devices with Jetson Orin NX 8GB modules.
Even though we use the same process, on some devices we observe that they do not boot properly after flashing.
Booting fails with the following message in the MB2 step:

I> Task: Partition Manager Init
I> strt_pg_num(1) num_of_pgs(1) read_buf(0x273801000)
I> strt_pg_num(131071) num_of_pgs(1) read_buf(0x273801000)
W> Cannot find any partition table for 00030000
W> PARTITION_MANAGER: Failed to publish partition.
... (some lines left out) ...
I> Partition name: A_spe-fw
E> Cannot find partition A_spe-fw
E> Partition A_spe-fw not found
E> MB2_FW_LOAD: Failed to load FW.
C> Task 0x0 failed (err: 0x224d090d)
E> Top caller module: LOADER, error module: PARTITION_MANAGER, reason: 0x0d, aux_info: 0x09

(This first happens for Slot 0, then it switches to Slot 1 and the same issue happens again.)

Those modules were brand new and never flashed before by us.
What exactly does this error mean and how could this be fixed?

3

Hi jonathan.schnitzler,

Are you using the devkit or custom board for Orin NX?
What’s the Jetpack version in use?

How did you flash them?
Could you share the flash command and full flash log for further check?

4

Hi KevinFFF,

we are using a custom carrier board for the Orin NX.
We use Jetpack 6.0 (Jetson Linux 36.3.0).
We use initrd-flash from https://github.com/OE4T/meta-tegra to flash the device. It internally calls some of the Nvidia scripts.
I attached the flash log of a device that failed to boot after flashing.
log.initrd-flash.2024-10-25-09.22.18_stripped.txt (171.4 KB)

5

Sorry that we don’t support and never verified with yocto project on the devkit.
You can also verify with our official L4T(Linux_for_Tegra) and check if there’s still flash/boot issue.

Final status: SUCCESS
Successfully finished at 2024-10-25T09:24:52+00:00

From the log you shared, it seems the flash process finished w/o errors.

7

It seems like we ran into Different charge numbered jetson orin nano's behave differently when writing to QSPI on custom carrier boards - #7 by DaveYYY.
We adapted our flashing procedure to properly handle the QSPI protetion bit and it now works.

1 Like
8

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