Build the system.img for TX2 4GB module

Autonomous Machines Jetson & Embedded Systems Jetson TX2
#1

Hi Sir,

What is the board name of TX2 4GB module with the flash.sh command ?
I follow up the r32.5 document to build the system.img.
But I always can’t get the correct action.

sudo ./flash.sh jetson-tx2 mmcblk0p1 (OK)
sudo ./flash.sh jetson-tx2-4GB mmcblk0p1 (Failed)
sudo ./flash.sh jetson-tx2-devkit-4GB mmcblk0p1 (Failed)

[r32.5 doc]
(https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/quick_start.html#wwpID0EAAMNHA)

Yours Sincerely,
S.K.

#3

sudo ./flash.sh jetson-tx2-4GB mmcblk0p1 (Failed)

This one looks correct. What error did you get when you use this command?

#4

Hi,

sudo ./flash.sh --no-flash jetson-tx2-4GB mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 5.0

###############################################################################
Board ID() version() sku() revision()
Error: missing dtbfile (/home/skhuang/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_TX2_4GB/Linux_for_Tegra/kernel/dtb/tegra186-quill-p3489-0888-c03-00-base.dtb).

#5

Are you sure your whole folder is installed completed?

The error tells your the dtb file is missing, then could you check if it is really missing?

#6

Hi,

I installed two times with the different host computer.
I got the identical error messages.

Yours Sincerely,
S.K.

#7

What is your method to install this? If you use the wrong method twice, then changing the host does not help.

Why do you use “–no-flash” instead of real flash?

#8

Hi,

  1. The “SDK manager application” will install automatically the related component.
    (NVIDIA SDK Manager | NVIDIA Developer)
  2. just build the system.img.
#9

What will show up if you really flash the board?

#10

Also, could you share us the list of your Linux_for_Tegra/kernel/dtb?

#11

The dtb indicated by jetson-tx2-4GB.conf is a00-00-base.dtb and there is no c03-00-base.dtb. Could you check this config file too?

EMMC_BCT=P3489_Sku888_4GB_Hynix_4GB_lpddr4_204Mhz_P138_A02_l4t.cfg
DTB_FILE=tegra186-quill-p3489-0888-a00-00-base.dtb;
TBCDTB_FILE=tegra186-quill-p3489-0888-a00-00-base.dtb;
#12

skhuang@vmi428428:~/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_TX2_4GB/Linux_for_Tegra/kernel/dtb$ ls
tegra186-quill-p3310-1000-a00-00-base.dtb
tegra186-quill-p3310-1000-as-0888.dtb
tegra186-quill-p3310-1000-c03-00-base-adafruit-sph0645lm4h.dtbo
tegra186-quill-p3310-1000-c03-00-base.dtb
tegra186-quill-p3310-1000-c03-00-base.dtb.rec
tegra186-quill-p3310-1000-c03-00-base-fe-pi-audio.dtbo
tegra186-quill-p3310-1000-c03-00-base-hdr40.dtbo
tegra186-quill-p3310-1000-c03-00-base-respeaker-4-mic-array.dtbo
tegra186-quill-p3310-1000-c03-00-dsi-hdmi-dp.dtb
tegra186-quill-p3489-0888-a00-00-base.dtb
tegra186-quill-p3489-1000-a00-00-ucm1.dtb
tegra186-quill-p3489-1000-a00-00-ucm2.dtb
tegra194-p2888-0001-p2822-0000-adafruit-sph0645lm4h.dtbo
tegra194-p2888-0001-p2822-0000.dtb
tegra194-p2888-0001-p2822-0000-fe-pi-audio.dtbo
tegra194-p2888-0001-p2822-0000-hdr40.dtbo
tegra194-p2888-0001-p2822-0000-maxn.dtb
tegra194-p2888-0001-p2822-0000-respeaker-4-mic-array.dtbo
tegra194-p2888-0004-e3900-0000-adafruit-sph0645lm4h.dtbo
tegra194-p2888-0004-e3900-0000.dtb
tegra194-p2888-0004-e3900-0000-fe-pi-audio.dtbo
tegra194-p2888-0004-e3900-0000-hdr40.dtbo
tegra194-p2888-0004-e3900-0000-respeaker-4-mic-array.dtbo
tegra194-p2888-0006-p2822-0000.dtb
tegra194-p2888-as-0006-p2822-0000.dtb
tegra194-p2888-as-p3668-p2822-0000.dtb
tegra194-p3668-all-p3509-0000-adafruit-sph0645lm4h.dtbo
tegra194-p3668-all-p3509-0000.dtb
tegra194-p3668-all-p3509-0000-fe-pi-audio.dtbo
tegra194-p3668-all-p3509-0000-hdr40.dtbo
tegra194-p3668-all-p3509-0000-respeaker-4-mic-array.dtbo

#13

And the board config file too.

#14

jetson-tx2-4GB.conf

p2771-0000-0888.conf: configuration for T186-A02 te770m P3489 SKU888

BPFDTB_FILE=tegra186-a02-bpmp-lightning-p3489-a00-00-te770m.dtb;
source “${LDK_DIR}/p2771-0000.conf.common”;
EMMC_BCT=P3489_Sku888_4GB_Hynix_4GB_lpddr4_204Mhz_P138_A02_l4t.cfg
DTB_FILE=tegra186-quill-p3489-0888-a00-00-base.dtb;
TBCDTB_FILE=tegra186-quill-p3489-0888-a00-00-base.dtb;

PROD_CONFIG=“tegra186-mb1-bct-prod-storm-p3489-1000-a00.cfg”;
PINMUX_CONFIG=“tegra186-mb1-bct-pinmux-quill-p3489-1000-a00.cfg”;
PMIC_CONFIG=“tegra186-mb1-bct-pmic-lightning-p3489-1000-a00.cfg”;
PMC_CONFIG=“tegra186-mb1-bct-pad-quill-p3489-1000-a00.cfg”;
BOOTROM_CONFIG=“tegra186-mb1-bct-bootrom-quill-p3489-1000-a00.cfg”;
ROOTFSSIZE=14GiB;
RECROOTFSSIZE=100MiB;

#15

The dtb file is also tegra186-quill-p3489-0888-a00-00-base.dtb.

Please directly run the command without --no-flash and see if any error.

#16

OK.
I will get the carrier board from my colleague.

#17

Hi,

I also get the another topic via the keyword.

→ sudo BOARDID=3489 FAB=A00 ./flash.sh jetson-tx2-4GB mmcblk0p1

I can get the system.img now. (Before I get the carrier board, I still need to use “–no-flash”)

Is it OK for r32.5?

#18

When you hit the error in your last try, you didn’t connect any board on your host, right?

#19

Hi,

It was Chinese New Year Holiday at that moment without any board.
I think It was the build flow error.

When the system.img is ready, I can focus to use “-r” option to flash our device.(It’s OK for TX1 & NANO)

Is it ok for r32.5 and TX2 4GB Module?
sudo BOARDID=3489 FAB=A00 ./flash.sh jetson-tx2-4GB mmcblk0p1

Thanks.

#21

Hi sk1977.huang,

Run below command is working on TX2-4GB module with JP-4.5:
$ sudo BOARDID=3489 FAB=A00 ./flash.sh --no-flash jetson-tx2-4GB mmcblk0p1

1 Like
#22

Hi,

Just make it easier for you to understand

If there is no board which is in recovery mode connected on your host, then you have to directly tell the FAB and BOARDID to flash.sh.

if you don’t know what are FAB and BOARDID, then please connect the board.

1 Like