hello hotspear89,
are you working with JetPack-4.5.1 release?
I’ve just verified with the offline approach, by generating Massflash image on the host machine.
for example,
$ sudo BOARDID=3668 BOARDSKU=0001 FAB=100 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-xavier-nx-devkit-emmc mmcblk0p1
...
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 5.1
###############################################################################
Board ID(3668) version(100) sku(0001) revision()
..
[ 20.2398 ] Using default ramcode 0
[ 20.2398 ] Generating BPMP dtb for ramcode - 0
[ 20.3093 ] Old BPMP dtb size - 223168 bytes
[ 20.3093 ] New BPMP dtb size - 168338 bytes
[ 20.3094 ]
[ 20.3107 ] tegrahost_v2 --chip 0x19 --align mem_rcm.bct
[ 20.3115 ]
[ 20.3124 ] tegrahost_v2 --chip 0x19 0 --magicid MEMB --appendsigheader mem_rcm.bct zerosbk
[ 20.3132 ] adding BCH for mem_rcm.bct
...
copying nvmflash.sh ... succeeded.
copying nvaflash.sh ... succeeded.
copying emmc_bootblob_ver.txt ... succeeded.
copying qspi_bootblob_ver.txt ... succeeded.
number of images in blob are 11
...
********************************************************************************
*** Mass Flashing tarball mfi_jetson-xavier-nx-devkit-emmc.tbz2 is ready.
********************************************************************************
BTW,
could you please also checks that. those two lines to export kernel as preferred PATH should be default included in the line(44-45) of nvmassflashgen.sh.
thanks