Can't generate *_signed.tbz2 package

We can’t generate *_signed.tbz2 package use command“sudo BOARDID=3448 BOARDSKU=0002 FAB=400 FUSELEVEL=fuselevel_production ./ -x 0x21 -y PKC -u Product03/rsa_priv.pem jetson-nano-devkit-emmc mmcblk0p1”.
The attachment is build log,please help to analyze.

nvmassflashgen_log.txt (11.3 KB)

hello rd1,

seems the process works normally, and the tarball has also generated.
please extract the tarball to check you’re having binaries sign/encrypt with your own keys.

we now updated from L4T R32.4.2 to L4T R32.5.1, it cann’t generate secure signed package , but it is ok on L4T R32.4.2, we compare the log, The latest log didn’t have “secureflash” parameter,we didn’t know why .
For the bellow ,it is L4T R32.4.2 log:
./ --bl cboot.bin.signed --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --odmdata 0x94000 --bldtb smpsq-tegra210-p3448-0002-p3449-0000-b00.dtb.signed --applet rcm_1_signed.rcm --cmd “secureflash;reboot” --cfg flash.xml --chip 0x21 --bins “EBT cboot.bin; DTB smpsq-tegra210-p3448-0002-p3449-0000-b00.dtb” --key “/home/scala/work/NV_32.4.2/NVT210_07_22/bsp/Product03/rsa_priv.pem”

hello rd1,

for boards fused with PKC (or PKC+SBK), nvmassflashgen always used secureflash.

hello rd1,

we have verify locally with PKC fused Nano-eMMC.
it’s able to create massflash blob, mfi_jetson-nano-emmc_signed.tbz2 with r32.5.1 release.
here’re our steps in detail for your reference.

  1. $ sudo ./ -p -i 0x21 -c PKC -k <key.pem>
  2. $ sudo ./ -x 0x21 -y PKC -u <key.pem> jetson-nano-emmc mmcblk0p1
  3. $ sudo BOARDID=3448 BOARDSKU=0002 FAB=400 FUSELEVEL=fuselevel_production ./ -x 0x21 -y PKC -u <key.pem> jetson-nano-emmc mmcblk0p1
  4. $ tar xpvf mfi_jetson-nano-emmc_signed.tbz2
  5. $ cd mfi_jetson-nano-emmc_signed/
  6. $ sudo ./ --showlogs

it’s actually using correct commands in
for example, ./ ... --cmd "secureflash;reboot" ...


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