Cann't boot after bup update

HI, We have an urgent matter, the device cann’t boot after bup update.
The below is the bup update log:
224282_20230331-nx4-uboot_manual_update.txt (36.0 KB)
There are some Warnings, Help to check the log.

Hi 18502109920,

Are you using the devkit or custom board for Jetson Nano?

From your log, it showed update successful and seems current version is identical to the update package.

Warning. BMP partition data on system is identical to payload data. Skipping update.
Update successful.

Could you help to provide the serial console log to check boot issue?

Our ustomer feedback serial has no output.

I had a question: I used customer bup to update, it will be error.
What caused this mistake?
The error log:
======================UPDATE BOOTLOADER BEGINE==============================
temp url =bl_update-av.img
updateEngine bl start
BLOB PATH:
/opt/ota_package/t21x/bl_update_payload

SPEC: 3448-401-0002-F.0-1-0-jetson-nano-devkit-emmc-smpsq-mmcblk0p1

Compatible SPEC: 3448-300-0002–1–jetson-nano-devkit-emmc-smpsq-

Error. Cannot find matched SPEC in blob.
No changes have been made. Exiting…

The serial log as below from customer:

root@localhost:/home/scala# [0000.246] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.252] Processing in cold boot mode Bootloader 2
[0000.256] A02 Bootrom Patch rev = 1023
[0000.260] Power-up reason: pmc por
[0000.263] No Battery Present
[0000.266] pmic max77620 reset reason
[0000.269] pmic max77620 NVERC : 0x80
[0000.272] RamCode = 0
[0000.275] Platform has DDR4 type RAM
[0000.278] max77620 disabling SD1 Remote Sense
[0000.282] Setting DDR voltage to 1125mv
[0000.286] Serial Number of Pmic Max77663: 0x2b30f2
[0000.294] Entering ramdump check
[0000.297] Get RamDumpCarveOut = 0x0
[0000.300] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.305] Last reboot was clean, booting normally!
[0000.310] Sdram initialization is successful
[0000.314] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.320] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.326] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.332] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.338] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.343] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.349] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.355] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.371] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.377] Platform-DebugCarveout: 0
[0000.381] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.386] BoardID = 3448, SKU = 0x2
[0000.390] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.395] Read GPT from (0:3)
[0000.410] Csd NumOfBlocks=0
[0000.422] Using GPT Primary to query partitions
[0000.427] Read PT from (0:3)
[0000.432] Using BFS PT to query partitions
[0000.436] PT: Partition RP5 NOT found !
[0000.440] Warning: Find Partition via PT Failed
[0000.444] Load RPB failed, skip RPB.
[0000.676] *** Failing over to BFS1.
[0000.300] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.306] Processing in cold boot mode Bootloader 2
[0000.310] A02 Bootrom Patch rev = 1023
[0000.314] Power-up reason: software reset
[0000.318] No Battery Present
[0000.320] pmic max77620 reset reason
[0000.324] pmic max77620 NVERC : 0x0
[0000.327] RamCode = 0
[0000.329] Platform has DDR4 type RAM
[0000.333] max77620 disabling SD1 Remote Sense
[0000.337] Setting DDR voltage to 1125mv
[0000.341] Serial Number of Pmic Max77663: 0x2b30f2
[0000.349] Entering ramdump check
[0000.352] Get RamDumpCarveOut = 0x0
[0000.355] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.360] Last reboot was clean, booting normally!
[0000.364] Sdram initialization is successful
[0000.369] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.375] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.380] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.386] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.392] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.398] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.404] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.410] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.426] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.432] Platform-DebugCarveout: 0
[0000.435] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.441] BoardID = 3448, SKU = 0x2
[0000.444] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.450] Read GPT from (0:3)
[0000.465] Csd NumOfBlocks=0
[0000.477] Using GPT Primary to query partitions
[0000.481] Read PT from (0:3)
[0000.486] Using BFS PT to query partitions
[0000.490] PT: Partition RP5 NOT found !
[0000.494] Warning: Find Partition via PT Failed
[0000.498] Load RPB failed, skip RPB.
[0000.714] *** Failing over to BFS2.

Is that your custom board for Jetson Nano?
And your customer(end-user) reported some errors?

It seems some partition missing from the serial console log.
Please provide the full serial console log as file for further check.

Or just suggest them to re-flash the board.

Do you understand that if it is a custom carrier board, then the software has to use the software for that board, and not the developer kit software?

Hi, we had a questiuon:
BOARDID=3448 BOARDSKU=0002 FAB=300
For Jetson Nano, what is the FAB? 300 or 400?
And What does FAB do ?

FAB is the one of the ID for different modules, relating to DRAM.
You could refer to the list in Linux_for_Tegra/README_Massflash.txt.

jetson-nano-devkit-emmc          3448     0002      400  N/A

if we always used FAB=300, What will be the impact?

You may modify the board related data in EEPROM, please use 400 for Jetson Nano.

the FAB from EEPROM is 401, is it right?

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Could you help to run the following command on the board and share the result?

$cat /etc/nv_boot_control.conf

$sudo i2cdump -y 0 0x50