NVIDIA Jetson Xavier NX MassFlash error

Hi,
We created the mass flash tarball for Jetson NX (production module) in OFFLINE mode,
mfi_p3509-0000+p3668-0001-qspi-emmc.tbz2

The tarball is created by
sudo BOARDID=3668 BOARDSKU=0001 FAB=100 FUSELEVEL=fuselevel_production ${L4T_BSP_DIR}/nvmassflashgen.sh ${BOARD} mmcblk0p1

But when we flash it to the device, we face issues.

~/nvidia/factory_package/mfi_p3509-0000+p3668-0001-qspi-emmc$ sudo ./nvmflash.sh
Start flashing device: 3-2.1, PID: 5373
Ongoing processes: 5373
Ongoing processes: 5373
*** glibc detected *** /home/arvindh/nvidia/factory_package/mfi_p3509-0000+p3668-0001-qspi-emmc/tegraparser_v2: munmap_chunk(): invalid pointer: 0x096bd8fe ***
======= Backtrace: =========
[0x806f6d1]
[0x804d68f]
======= Memory map: ========
08048000-080da000 r-xp 00000000 08:01 7423834 /home/arvindh/nvidia/factory_package/mfi_p3509-0000+p3668-0001-qspi-emmc/tegraparser_v2
080da000-080db000 rw-p 00091000 08:01 7423834 /home/arvindh/nvidia/factory_package/mfi_p3509-0000+p3668-0001-qspi-emmc/tegraparser_v2
080db000-080df000 rw-p 00000000 00:00 0
096ba000-096dc000 rw-p 00000000 00:00 0 [heap]
f7fd9000-f7fdc000 r–p 00000000 00:00 0 [vvar]
f7fdc000-f7fde000 r-xp 00000000 00:00 0 [vdso]
ffd76000-ffd97000 rw-p 00000000 00:00 0 [stack]

Ongoing processes:
Flash complete (WITH FAILURES)

Please find attached the complete log file from mfilogs,
The log file fails as below,

/home/arvindh/nvidia/factory_package/mfi_p3509-0000+p3668-0001-qspi-emmc/tegraparser_v2 --storageinfo storage_info.bin --generategpt --pt flash.xml.bin
Partition secondary_gpt cannot fit to storage device, total sectors 30777344, current LBA 33554399
/home/arvindh/nvidia/factory_package/mfi_p3509-0000+p3668-0001-qspi-emmc/nvaflash.sh: line 61: 5392 Aborted (core dumped) ${cmd}
*** Error: Generating GPT failed.

The normal way of flashing is working successfully. Only the massflash is failing.
How can we correct this gpt error ? 20200623-233207_5313_flash_3-2.1.log (3.0 KB)

Thanks,

Hi,

This is known issue and will be fixed in next release.

Hi WayneWWW,
Is there a quick fix patch for this issue and when can we expect the next release ? Currently we are using 32.4.2.
Thanks,

We’re going to release the next version soon, please wait for our announcement.

1 Like