Boot failed with 'Find Partition via PT Failed"

VERY embarrassing morning today.

Jetson Nano Developer Kit A02, I use it almost everyday. Even Yesterday afternoon.
But it cannot boot-up at all this morning with short logs as follow:

[0000.163] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.168] Processing in cold boot mode Bootloader 2
[0000.173] A02 Bootrom Patch rev = 1023
[0000.177] Power-up reason: pmc por
[0000.180] No Battery Present
[0000.182] pmic max77620 reset reason
[0000.186] pmic max77620 NVERC : 0x40
[0000.189] RamCode = 0
[0000.191] Platform has DDR4 type RAM
[0000.195] max77620 disabling SD1 Remote Sense
[0000.199] Setting DDR voltage to 1125mv
[0000.203] Serial Number of Pmic Max77663: 0x2421e8
[0000.211] Entering ramdump check
[0000.214] Get RamDumpCarveOut = 0x0
[0000.217] RamDumpCarveOut=0x0,  RamDumperFlag=0xe59ff3f8
[0000.222] Last reboot was clean, booting normally!
[0000.227] Sdram initialization is successful 
[0000.231] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.237] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.243] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.248] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.254] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.260] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.266] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.272] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.288] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.294] Platform-DebugCarveout: 0
[0000.297] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.303] Non secure mode, and RB not enabled.
[0000.307] BoardID = 3448, SKU = 0x0
[0000.311] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.314] Nano-SD: checking PT table on QSPI ...
[0000.319] Read PT from (2:0)
[0000.334] Using BFS PT to query partitions 
[0000.338] PT: Partition TBC NOT found ! 
[0000.342] Warning: Find Partition via PT Failed
[0000.346] BoardID = 3448, SKU = 0x0
[0000.350] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.353] Nano-SD: checking PT table on QSPI ...
[0000.358] PT: Partition TBC NOT found ! 
[0000.361] Warning: Find Partition via PT Failed
[0000.366] Error is 1 

I put the microSD card into another Jetson Nano A02 dev. kit, runs OK
And B01 version, definitely OK.
And tested 5 other microSD cards. FAILED ONLY on this dev.kit.

No electrical/physical damages I’m sure.

Where should I dig in this case?

Could you put an empty sdcard to this board and flash it with sdkm r32.5?

Did you remember what caused this problem?


I think that flashing new microSD card is the last action.
I cannot remember any abnormal events, because I use it on the table most of time.


The steps I want to try is

  1. Use an empty sdcard, plug to this board → please note that this card is new one or some cards that you can format.

  2. Flash the board + this card with sdkm rel-32.5 → confirmed if this board can boot up now.

  3. Remove this new card and plug the old card. See if you can boot up now.

Is it ok for you to try that?

Definitely YES, it is.
I will update it


It’s very weird!
I flashed new microSD card through SDK manager, JetPack 4.5.1 latest one.
Jetson Nano dev.kit works quite well now even the old microSD cards, except one.

How can I understand it?
Hope it will work well tomorrow morning too.


1 Like

Jetson Nano dev.kit works quite well now even the old microSD cards, except one.

Which one? Is that problematic card in the beginning?

The troubled one is L4T R32.1.0 based image.
It does not boot at A02 version yet, but does well with B01.
And other sdcards are R32.4.x or later images.

This R32.1.0 based image shows following logs:

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
239 bytes read in 18 ms (12.7 KiB/s)
1:      primary kernel
Retrieving file: /boot/initrd
initrd not found or zero, skipping ...
Retrieving file: /boot/Image
34048008 bytes read in 1489 ms (21.8 MiB/s)
append: tegraid= ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0t
## Flattened Device Tree blob at 83100000
   Booting using the fdt blob at 0x83100000
ERROR: reserving fdt memory region failed (addr=0 size=0)
ERROR: reserving fdt memory region failed (addr=0 size=0)
   Using Device Tree in place at 0000000083100000, end 000000008317e68d
copying carveout for /host1x@50000000/dc@54200000...
copying carveout for /host1x@50000000/dc@54240000...

Starting kernel ...

Never meet these failures.

I would suggest maybe you should not use r32.1 since it is out-of-date.

The boot process includes the some bootloader on QSPI. If you only change/replace the sdcard on your device, for any release prior to rel-32.5, it would not update the QSPI on device.

Thus, it would cause a situation that your card is rel-32.1 while the bootloader on qspi is rel-32.5 or rel-32.4.3.

I think such case is lacking of QA verification. For example, we don’t check the combination of rel-32.5 bootloader + rel-32.1 sdcard image and it may cause problem like your current issue.

I think so, VERY out-of-date.
Something to keep is inside there. But I have to move to the latest env.

Very embarrassed morning yesterday.