Failure creating signed images to be used in factory environment and flashing them

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

I am following the steps laid out in the README_secureboot.txt to create the signedimage.tbz2 package. But I do not see any package being created.

  1. sudo rm -f bootloader/flashcmd.txt
  2. Generate the signed binary image, signedimage.tbz2:
    • For Jetson TX2:
      sudo ./flash.sh --no-flash -x 0x18 -y PKC -u jetson-tx2 mmcblk0p1

This does create some signed files and I can see a directory created called signed, but at the end prints out the message: “*** no-flash flag enabled. Exiting now… ***”

Is this expected?

I continued after this in spite of not finding the signedimage.tbz2 package and tried the following commands

$ cd bootloader
$ sudo bash ./flashcmd.txt

This then hung on the command: tegrarcm_v2 --isapplet. Not sure how to go forward with this one. The fuses were written successfully.

sudo bash ./flashcmd.txt
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[ 0.0588 ] Parsing partition layout
[ 0.0638 ] tegraparser_v2 --pt secureflash.xml.tmp
[ 0.0752 ]
[ 0.0754 ] Boot Rom communication
[ 0.0901 ] tegrarcm_v2 --chip 0x18 0 --rcm rcm_1_signed.rcm
[ 0.0982 ] BootRom is not running
[ 5.7875 ]
[ 6.7985 ] tegrarcm_v2 --isapplet

I would appreciate any help to move forward on the provisioning of TX2.

Thanks
Rayees

2

hello rayees.shamsuddin,

“–no-flash” command will generate all the images locally except flashing the board.
please refer to Flashing and Booting the Target Device → [Flash Script Usage] session for details.

you might need to check the “signed” folder for signed binaries.
for example,

$OUT/Linux_for_Tegra/bootloader/signed/