About How to massflashing using cloned images

Hello,

image
The cloned image is copied to bootloader/system.img and mass flashing image is being created.

Even if I read README_Massflash.txt
sudo ./nvmassflashgen.sh mmcblk0p1
It is not guided to give any options other than secureboot options.

How do I create a mass flashing blob from a cloned image?

thank you.

Hello,

Hello,

sudo ./nvmassflashgen.sh -r jetson-nano-emmc mmcblk0p1

There’s no explanation, but I’ve randomly specified the -r option to generate a massflash blob.

Flashing the two nanomodules through the following procedure


*** Mass Flashing tarball mfi_jetson-nano-emmc.tbz2 is ready.


 1.Download mfi_jetson-nano-emmc.tbz2 to each flashing hosts.
 2. Untar mfi_jetson-nano-emmc.tbz2. (tar xvjf mfi_jetson-nano-emmc.tbz2)
 3. cd mfi_jetson-nano-emmc
 4.Connect Jetson boards(jetson-nano-emmc only) and put them in RCM mode.
 5. ./nvmflash.sh

Only the following message is coming out. It is currently 24 minutes.
What should i do?

Thank you.

hello neuezeal,

there’s currently not support to reuse existing system.img with nvmassflashgen.sh.
hence, -r options has no effects.

1 Like

Hello,

So, is there currently any way to massflash the cloned image?

hello neuezeal,

you may using flash script to include -r options to skip building and reuse existing system.img for your usage.
in the meanwhile, I’ll also arrange resources to check internally for massflash with the cloned image.
thanks

1 Like

Thank you for answer.
About when will the backed-up image be mass flashed?

hello neuezeal,

please stay tuned, I will update the status after we had conclusions,
thanks

1 Like

Hello,

Have you concluded?

Our products are in a hurry to mass-produce.
How long can I wait for that option to become available?

Thank you.

hello neuezeal,

to clarify,
you’re able to skip building and reuse existing system.img with “-r” option included.
for example,
below is workable commands.

$ sudo ./nvmassflashgen.sh -r jetson-nano-emmc mmcblk0p1
...
Reusing existing system.img... 

could you please have workaround by OFFLINE method, by assign board information.
please assign these board info into commands line and try to generate the massflash blob with OFFLINE method.
for example,
$ sudo BOARDID=3448 BOARDSKU=0002 FAB=200 USELEVEL=fuselevel_production ./nvmassflashgen.sh -x 0x21 -y PKC -u <pkc_keyfile> jetson-nano-emmc mmcblk0p1

you may also check TNSPEC on your board to have correct board info.
for example,
$ cat /etc/nv_boot_control.conf

while flashing, please also gather all details for reference,
i.e. $ sudo ./nvmflash --showlogs

1 Like

Hello,

Wasn’t it impossible?

This way, can I create a mass flashing blob from the backed up image (backup.img)?
There must have been a problem with the ONLINE method?

I’ll try it and let you know the result.

Thank you.

Hello

When creating a mass flashing blob offline like the following command
Where does the -r option correspond?

sudo BOARDID=3448 BOARDSKU=0002 FAB=200 USELEVEL=fuselevel_production ./nvmassflashgen.sh -x 0x21 -y PKC -u <pkc_keyfile> jetson-nano-emmc mmcblk0p1

Thank you.

Hello,

sudo BOARDID=3448 BOARDSKU=0002 FAB=200 USELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-nano-emmc mmcblk0p1

|| Generate Massflash Image in the master host: ||
|| Requires the Jetson connected in RCM mode. ||

0 Jetson devices in RCM mode. USB:
*** Error: No Jetson device found.
Connect 1 Jetson in RCM mode and rerun ./nvmassflashgen.sh jetson-nano-emmc mmcblk0p1

In offline mode, should the jetson module be physically connected in rcm mode?

Thank you.

hello neuezeal,

  1. please confirm that you’re using correct board info,
    is your board TNSPEC also report, BOARDID=3448 BOARDSKU=0002 FAB=200?

  2. please have device physically connected in rcm mode.

  3. you may include -r options after ./nvmassflashgen.sh to make it works.

1 Like

Hello,

is it Ok?

here, What is FAB?

Thank you.

Hello,


Does not fall from 100 percent

Even if it is completed, it cannot boot.

What is the problem?

Thank you.

Hello,


I did the way you told me, but it doesn’t end at 100%
Can you tell what the problem is?

By any chance, I turned it on for about 12 hours, but it stays the same.

Due to the force shutdown, no log using the --showlogs option is left, and when the nanomodule is powered on, it will be in force recovery mode.

Thank you.

Hello,

I checked the logs like this:

*** Updating BFS information on BCT
/home/nanohostpc/coding/mass_production/realwave_oem_pure_nvr/mfi_jetson-nano-emmc/tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatebfsinfo flash.xml.bin
BFS:
0: [PT ] flash.xml.bin (size=4339/131072)
1: [TBC] nvtboot_cpu.bin.encrypt (size=65760/196608)
2: [RP1] tegra210-p3448-0000-p3449-0000-a00.dtb.encrypt (size=215520/1048576)
3: [EBT] cboot.bin.encrypt (size=483872/655360)
4: [WB0] warmboot.bin.encrypt (size=3952/131072)
5: [BPF] sc7entry-firmware.bin.encrypt (size=3376/262144)
BFS0: 131072 @ 2560 SUM 2ee6ed00 over 2883584 bytes
BFS:
0: [PT-1] flash.xml.bin (size=4339/131072)
1: [TBC-1] nvtboot_cpu.bin.encrypt (size=65760/196608)
2: [RP1-1] tegra210-p3448-0000-p3449-0000-a00.dtb.encrypt (size=215520/1048576)
3: [EBT-1] cboot.bin.encrypt (size=483872/655360)
4: [WB0-1] warmboot.bin.encrypt (size=3952/131072)
5: [BPF-1] sc7entry-firmware.bin.encrypt (size=3376/262144)
8: [VER_b] emmc_bootblob_ver.txt (size=91/32768)
9: [VER] emmc_bootblob_ver.txt (size=91/32768)
BFS1: 131072 @ 8704 SUM 2ee6ed00 over 2981888 bytes
KFS:
0: [DTB] tegra210-p3448-0000-p3449-0000-a00.dtb.encrypt (size=215520/1048576)
1: [TOS] tos-mon-only.img.encrypt (size=54208/6291456)
2: [EKS] eks.img (size=1028/81920)
3: [LNX] boot.img.encrypt (size=485376/67092480)
KFS0: 1048576 @ 29376546 SUM 6cf34438 over 7907328 bytes
KFS:
0: [DTB-1] tegra210-p3448-0000-p3449-0000-a00.dtb.encrypt (size=215520/1048576)
1: [TOS-1] tos-mon-only.img.encrypt (size=54208/6291456)
2: [EKS-1] eks.img (size=1028/81920)
3: [LNX-1] boot.img.encrypt (size=485376/67092480)
KFS1: 1048576 @ 29522082 SUM 6cf34438 over 7907328 bytes
*** Updating BFS information on BCT succeeded.

*** Boot Rom communication
/home/nanohostpc/coding/mass_production/realwave_oem_pure_nvr/mfi_jetson-nano-emmc/tegrarcm --instance 3-3 --chip 0x21 0 --rcm rcm_list_signed.xml
BR_CID: 0x321010016445b508200000000f0183c0
RCM version 0X210001
Boot Rom communication completed
*** Boot Rom communication succeeded.

*** Sending BCTs
/home/nanohostpc/coding/mass_production/realwave_oem_pure_nvr/mfi_jetson-nano-emmc/tegrarcm --instance 3-3 --download bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct
Applet version 00.01.0000
Sending bct
[…] 100%
*** Sending BCTs succeeded.

*** Sending bootloader and pre-requisite binaries
/home/nanohostpc/coding/mass_production/realwave_oem_pure_nvr/mfi_jetson-nano-emmc/tegrarcm --instance 3-3 --download ebt cboot.bin 0 0 --download rp1 tegra210-p3448-0000-p3449-0000-a00.dtb 0 0
Applet version 00.01.0000
Sending ebt
[…] 100%
Sending rp1
[…] 100%
*** Sending bootloader and pre-requisite binaries succeeded.

*** Booting Recovery
/home/nanohostpc/coding/mass_production/realwave_oem_pure_nvr/mfi_jetson-nano-emmc/tegrarcm --instance 3-3 --boot recovery
Applet version 00.01.0000
*** Booting Recovery succeeded.

*** Retrieving storage infomation
/home/nanohostpc/coding/mass_production/realwave_oem_pure_nvr/mfi_jetson-nano-emmc/tegradevflash --instance 3-3 --oem platformdetails storage 18534_storage_info.bin
Cboot version 00.01.0000
Saved platform info in 18534_storage_info.bin
*** Retrieving storage infomation succeeded.

*** Flashing the device
/home/nanohostpc/coding/mass_production/realwave_oem_pure_nvr/mfi_jetson-nano-emmc/tegradevflash --instance 3-3 --pt flash.xml.bin --storageinfo 18534_storage_info.bin --create
Cboot version 00.01.0000
Writing partition GPT with gpt.bin
[…] 100%
Writing partition PT with flash.xml.bin
[…] 100%
Writing partition PT-1 with flash.xml.bin
[…] 100%
Writing partition NVC with nvtboot.bin.encrypt
[…] 100%
Writing partition TBC with nvtboot_cpu.bin.encrypt
[…] 100%
Writing partition RP1 with tegra210-p3448-0000-p3449-0000-a00.dtb.encrypt
[…] 100%
Writing partition EBT with cboot.bin.encrypt
[…] 100%
Writing partition WB0 with warmboot.bin.encrypt
[…] 100%
Writing partition BPF with sc7entry-firmware.bin.encrypt
[…] 100%
Writing partition NVC-1 with nvtboot.bin.encrypt
[…] 100%
Writing partition TBC-1 with nvtboot_cpu.bin.encrypt
[…] 100%
Writing partition RP1-1 with tegra210-p3448-0000-p3449-0000-a00.dtb.encrypt
[…] 100%
Writing partition EBT-1 with cboot.bin.encrypt
[…] 100%
Writing partition WB0-1 with warmboot.bin.encrypt
[…] 100%
Writing partition BPF-1 with sc7entry-firmware.bin.encrypt
[…] 100%
Writing partition VER_b with emmc_bootblob_ver.txt
[…] 100%
Writing partition VER with emmc_bootblob_ver.txt
[…] 100%
Writing partition APP with system.img
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 000%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%
[ ] 001%

[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 099%
[…] 100%
*** Error: Flashing the device failed.

Thank you.

hello neuezeal,

the board information you read from TNSPEC shown as below formats,
BOARD_ID-FAB-BOARDSKU-BOARDREV-NV_PRODUCTION-CHIP_REV-BOARD_NAME-ROOTFS_DEV
hence,
please assign BOARDID=3448 BOARDSKU=0002 FAB=400 into your command lines.

it’s weird there’s no error reports after you complete flashing APP partition.
could you please help to confirm this only reproduce with massflash scripts?
in other words, please confirm you’re able to use cloned image for flashing Nano platforms with flash scripts.
thanks

1 Like

Hello,

If so, is the explanation in the README wrong?

In the case of jetson-nano-emmc, FAB is 200.

Thank you.

Hello,

I created a blob using the method you told me to confirm that up to two were mass-splashed.

Can you test it too?
As far as I know, nvidia has only tested up to 2 units internally.

Thank you.