TX2 4GB flash error !

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

I flashed TX2 of 4GB SDK according to tx2_as_4GB_overlay.tbz2,report errors as follow:

[ 4.9027 ] […] 100%
[ 4.9416 ] Sending bct_mb1
[ 4.9717 ] […] 100%
[ 5.3993 ]
[ 5.3995 ] Generating blob
[ 5.4022 ] tegrahost_v2 --align blob_nvtboot_recovery_cpu.bin
[ 5.4043 ]
[ 5.4064 ] tegrahost_v2 --appendsigheader blob_nvtboot_recovery_cpu.bin zerosbk
[ 5.4098 ]
[ 5.4132 ] tegrasign_v2 --key None --list blob_nvtboot_recovery_cpu_sigheader.bin_list.xml
[ 5.4152 ] Assuming zero filled SBK key
[ 5.4285 ]
[ 5.4309 ] tegrahost_v2 --updatesigheader blob_nvtboot_recovery_cpu_sigheader.bin.encrypt blob_nvtboot_recovery_cpu_sigheader.bin.hash zerosbk
[ 5.4329 ]
[ 5.4345 ] tegrahost_v2 --align blob_nvtboot_recovery.bin
[ 5.4359 ]
[ 5.4382 ] tegrahost_v2 --appendsigheader blob_nvtboot_recovery.bin zerosbk
[ 5.4647 ]
[ 5.4665 ] tegrasign_v2 --key None --list blob_nvtboot_recovery_sigheader.bin_list.xml
[ 5.4677 ] Assuming zero filled SBK key
[ 5.4706 ]
[ 5.4724 ] tegrahost_v2 --updatesigheader blob_nvtboot_recovery_sigheader.bin.encrypt blob_nvtboot_recovery_sigheader.bin.hash zerosbk
[ 5.4741 ]
[ 5.4756 ] tegrahost_v2 --align blob_preboot_d15_prod_cr.bin
[ 5.4769 ]
[ 5.4781 ] tegrahost_v2 --appendsigheader blob_preboot_d15_prod_cr.bin zerosbk
[ 5.4795 ]
[ 5.4811 ] tegrasign_v2 --key None --list blob_preboot_d15_prod_cr_sigheader.bin_list.xml
[ 5.4822 ] Assuming zero filled SBK key
[ 5.4851 ]
[ 5.4867 ] tegrahost_v2 --updatesigheader blob_preboot_d15_prod_cr_sigheader.bin.encrypt blob_preboot_d15_prod_cr_sigheader.bin.hash zerosbk
[ 5.4894 ]
[ 5.4907 ] tegrahost_v2 --align blob_mce_mts_d15_prod_cr.bin
[ 5.4919 ]
[ 5.4933 ] tegrahost_v2 --appendsigheader blob_mce_mts_d15_prod_cr.bin zerosbk
[ 5.4989 ]
[ 5.5008 ] tegrasign_v2 --key None --list blob_mce_mts_d15_prod_cr_sigheader.bin_list.xml
[ 5.5020 ] Assuming zero filled SBK key
[ 5.5700 ]
[ 5.5717 ] tegrahost_v2 --updatesigheader blob_mce_mts_d15_prod_cr_sigheader.bin.encrypt blob_mce_mts_d15_prod_cr_sigheader.bin.hash zerosbk
[ 5.5765 ]
[ 5.5783 ] tegrahost_v2 --align blob_bpmp.bin
[ 5.5794 ]
[ 5.5804 ] tegrahost_v2 --appendsigheader blob_bpmp.bin zerosbk
[ 5.5828 ]
[ 5.5843 ] tegrasign_v2 --key None --list blob_bpmp_sigheader.bin_list.xml
[ 5.5854 ] Assuming zero filled SBK key
[ 5.6027 ]
[ 5.6043 ] tegrahost_v2 --updatesigheader blob_bpmp_sigheader.bin.encrypt blob_bpmp_sigheader.bin.hash zerosbk
[ 5.6063 ]
[ 5.6075 ] tegrahost_v2 --align blob_tegra186-a02-bpmp-p3310-1000-c04-as-0888-ucm2.dtb
[ 5.6085 ]
[ 5.6094 ] tegrahost_v2 --appendsigheader blob_tegra186-a02-bpmp-p3310-1000-c04-as-0888-ucm2.dtb zerosbk
[ 5.6118 ]
[ 5.6131 ] tegrasign_v2 --key None --list blob_tegra186-a02-bpmp-p3310-1000-c04-as-0888-ucm2_sigheader.dtb_list.xml
[ 5.6141 ] Assuming zero filled SBK key
[ 5.6245 ]
[ 5.6260 ] tegrahost_v2 --updatesigheader blob_tegra186-a02-bpmp-p3310-1000-c04-as-0888-ucm2_sigheader.dtb.encrypt blob_tegra186-a02-bpmp-p3310-1000-c04-as-0888-ucm2_sigheader.dtb.hash zerosbk
[ 5.6277 ]
[ 5.6290 ] tegrahost_v2 --align blob_tos.img
[ 5.6301 ]
[ 5.6318 ] tegrahost_v2 --appendsigheader blob_tos.img zerosbk
[ 5.6332 ]
[ 5.6346 ] tegrasign_v2 --key None --list blob_tos_sigheader.img_list.xml
[ 5.6355 ] Assuming zero filled SBK key
[ 5.6379 ]
[ 5.6391 ] tegrahost_v2 --updatesigheader blob_tos_sigheader.img.encrypt blob_tos_sigheader.img.hash zerosbk
[ 5.6406 ]
[ 5.6422 ] tegrahost_v2 --align blob_eks.img
[ 5.6432 ]
[ 5.6441 ] tegrahost_v2 --appendsigheader blob_eks.img zerosbk
[ 5.6451 ]
[ 5.6462 ] tegrasign_v2 --key None --list blob_eks_sigheader.img_list.xml
[ 5.6472 ] Assuming zero filled SBK key
[ 5.6478 ]
[ 5.6492 ] tegrahost_v2 --updatesigheader blob_eks_sigheader.img.encrypt blob_eks_sigheader.img.hash zerosbk
[ 5.6504 ]
[ 5.6515 ] tegrahost_v2 --align blob_tegra186-quill-p3310-1000-as-0888.dtb
[ 5.6526 ]
[ 5.6535 ] tegrahost_v2 --appendsigheader blob_tegra186-quill-p3310-1000-as-0888.dtb zerosbk
[ 5.6558 ]
[ 5.6571 ] tegrasign_v2 --key None --list blob_tegra186-quill-p3310-1000-as-0888_sigheader.dtb_list.xml
[ 5.6580 ] Assuming zero filled SBK key
[ 5.6785 ]
[ 5.6801 ] tegrahost_v2 --updatesigheader blob_tegra186-quill-p3310-1000-as-0888_sigheader.dtb.encrypt blob_tegra186-quill-p3310-1000-as-0888_sigheader.dtb.hash zerosbk
[ 5.6816 ]
[ 5.6829 ] tegrahost_v2 --generateblob blob.xml blob.bin
[ 5.6837 ] number of images in blob are 9
[ 5.6844 ] blobsize is 3610200
[ 5.6847 ] Added binary blob_nvtboot_recovery_cpu_sigheader.bin.encrypt of size 190048
[ 5.6868 ] Added binary blob_nvtboot_recovery_sigheader.bin.encrypt of size 79600
[ 5.6882 ] Added binary blob_preboot_d15_prod_cr_sigheader.bin.encrypt of size 63024
[ 5.6893 ] Added binary blob_mce_mts_d15_prod_cr_sigheader.bin.encrypt of size 2076832
[ 5.6915 ] Added binary blob_bpmp_sigheader.bin.encrypt of size 529440
[ 5.6930 ] Added binary blob_tegra186-a02-bpmp-p3310-1000-c04-as-0888-ucm2_sigheader.dtb.encrypt of size 327584
[ 5.6951 ] Added binary blob_tos_sigheader.img.encrypt of size 62976
[ 5.6960 ] Added binary blob_eks_sigheader.img.encrypt of size 1488
[ 5.6968 ] Added binary blob_tegra186-quill-p3310-1000-as-0888_sigheader.dtb.encrypt of size 279056
[ 5.7003 ]
[ 5.7004 ] Sending bootloader and pre-requisite binaries
[ 5.7017 ] tegrarcm_v2 --download blob blob.bin
[ 5.7026 ] Applet version 01.00.0000
[ 5.9471 ] Sending blob
[ 6.2059 ]
Error: Return value 1
Command tegrarcm_v2 --download blob blob.bin
Failed flashing t186ref.

2

please help me.

3

Which flash config are you using? The correct flash config should be jetson-tx2-4GB.conf but not jetson-tx2-as-4GB.conf.

4

I also encountered this problem, how can I switch to jetson-tx2-4GB.conf?

5

Just use sudo ./flash jetson-tx2-4GB mmcblk0p1

6

lz@ubuntu:~/L4T_28.2.1/Linux_for_Tegra$ sudo ./flash.sh jetson-tx2-4GB mmcblk0p1
Error: Invalid target board - jetson-tx2-4GB.

Usage: sudo ./flash.sh [options] <target_board>
Where,
target board: Valid target board name.
rootdev: Proper root device.
options:
-b --------- nvflash boot control table config file.
-c --------- nvflash partition table config file.
-d --------- device tree file.
-e ------- Target device’s eMMC size.
-f -------- Path to flash application: nvflash or tegra-rcm.
-h ------------------- print this message.
-i ------------------- pass user kernel commandline as-is to kernel.
-k ---- partition name or number specified in flash.cfg.
-m ----- MTS preboot such as mts_preboot_si.
-n -------- Static nfs network assignments
:::
-o --------- ODM data.
-p --------- Total eMMC HW boot partition size.
-r ------------------- skip building and reuse existing system.img.
-s ----- PKC key used for signing and building bl_update_payload.
-t ------- tegraboot binary such as nvtboot.bin
-u -------- PKC server in @ format.
-w --------- warm boot binary such as nvtbootwb0.bin
-x --------- Tegra CHIPID. default = 0x18(jetson-tx2)
0x21(jetson-tx1), 0x40(jetson-tk1).
-y -------- PKC for secureboot, NS for non-secureboot.
-z -------------- Serial Number of target board.
-B --------- BoardId.
-C --------- Kernel commandline arguments.
WARNING:
Each option in this kernel commandline gets
higher preference over the same option from
fastboot. In case of NFS booting, this script
adds NFS booting related arguments, if -i option
is omitted.
-F --------- Flash server such as fastboot.bin.
-G ------- Read partition and save image to file.
-I ---------- initrd file. Null initrd is default.
-K ---------- Kernel image file such as zImage or Image.
-L ------ Bootloader such as cboot.bin or u-boot-dtb.bin.
-M -------- MTS boot file such as mts_si.
-N --------- i.e. :/my/exported/nfs/rootfs.
-P <end of PPT + 1> – Primary GPT start address + size of PPT + 1.
-R ------ Sample rootfs directory.
-S ------------ Rootfs size in bytes. Valid only for internal
rootdev. KiB, MiB, GiB short hands are allowed,
for example, 1GiB means 1024 * 1024 * 1024 bytes.
-T -------- ITS file name. Valid only for u-boot.
–no-flash ----------- perform all steps except physically flashing the board.
This will create a system.img.
–bup ---------------- Generate bootloader update payload(BUP).
–multi-spec---------- Enable support for building multi-spec BUP.
–clean-up------------ Clean up BUP buffer when multi-spec is enabled.
–usb-instance – Specify the USB instance to connect to; integer
ID (e.g. 0, 1), bus/dev (e.g. 003/091), or USB
port path (e.g. 3-14). The latter is best.

According to your method, you will be prompted “Error: Invalid target board - jetson-tx2-4GB”, unable to execute flash

7

Hi,

Because rel-28.2.1 does not support tx2-4GB. It starts to support after rel-32.2.

8

Where is rel-32.2 downloaded?

9
10

Do we delete files and download the 32.1 files or what ? I don’t understand what we do once we download the from the website.

11

Hi chall012,

I am not pretty sure about your question. After you download sdkmanager on your host, you could install the deb and then run the command “sdkmanager”. Then, there would be a GUI showing up and you could just use it to flash your board.

12

FYI, if JetPack/SDK Manager arrives as a “.deb” file, it is just an Ubuntu package:

sudo dpkg -i SomePackage.deb

Once the “.deb” is installed you will have the actual executable file. In recent releases:

/usr/bin/sdkmanager

SDKM can flash or install extra packages. It won’t be obvious, but you can select to do just flash or just package install (host or Jetson). Don’t mix different versions of JetPack/SDKM.

The TX2 is in recovery mode if you flash, or fully booted normally if just adding packages. If you choose to both flash and add extras, then after the flash the Jetson will reboot itself before package install begins.

13

@WayneWWW

Will l4t-28.2.1 support TX2-4GB in the future?

Is there any plan on this issue?

Because our products are using 28.2.1. We want to use 28.2.1 on TX2-4GB.

Thanks.

14

Hi ShayWang,

No, currently no plan.

Also, the latest update of rel-28 based release is rel-28.3. rel-28.2.1 would not be updated anymore.