About How to massflashing using cloned images

hello neuezeal,

please looking into TNSPEC for correct board info since there’re different Nano version,

FYI,
by using one device or multiple devices don’t have any differences in terms of flashing operation.
you may confirm with single device to verify mflash.sh
thanks

1 Like

Hello,

Do you have any plans to prepare a means for flashing on Windows PC?

Even if you sell the product by mass flashing, you may need to flash again if there is a problem.

You should also take into account if the customer has no knowledge of flashing and is unfamiliar with using Linux.

As for massflasing, I understand that the contents of the readme_Massflash.txt document in the current Linux_For_Tegra folder are all.

Is there any other way to think about nvidia internally?
Or is there a way to recommend it?

Thank you.

@forumuser were you able to use the image / massflash script for single deployment?

1 Like

Hello,

I just read and followed the readme.

I made an oem_image using clone

When massflasing, I used the -r option to flash.

Thank you.

did the device boot after flashing?

1 Like

Yes.

1 Like

Hello,

@JerryChang, @Andrey1984
Is it okay to delete a few scripts under lebre office or /udev/ as long as you ensure normal OS operation when backing up images?

Thank you.

@forumuser
it is up to you to figure out if it works for you
try it and see if it worked for your requirements/situation

1 Like

Thank you. 👍

How are you cloning the jetson in the first place? Are you cloning just the APP partition or cloning the whole device? Cos when i used

$ sudo ./flash.sh -r -k APP -G backup.img jetson-nano-emmc mmcblk0p1

$ sudo cp backup.img bootloader/system.img
and then created massflash blob with
$ sudo BOARDID=3448 BOARDSKU=0002 FAB=200 USELEVEL=fuselevel_production ./nvmassflashgen.sh -r 0x21 -y PKC -u <pkc_keyfile> jetson-nano-emmc mmcblk0p1
and then used
$ sudo ./nvmflash --showlogs

The Process finished successfully but the device is not booting up for some reason.

1 Like

hello WarHawk627,

that’s the command-line to clone APP partition only.
please gather the bootloader logs to understand why the Nano isn’t booting up.
thanks

Hello,

In the meantime, I have been making good mass flashing blobs with the USELEVEL option.
But today, I looked at the MassFlash README file again.
It says FUSELEVEL, not USELEVEL.
What’s right? Or is it okay to choose any one?

Thank you.

that might be documentation typo, it’s FUSELEVEL in the command-line.
for example,
sudo BOARDID=3448 BOARDSKU=0002 FAB=200 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh -x 0x21 -y PKC -u <pkc_keyfile> jetson-nano-emmc mmcblk0p1

1 Like

Hello,

There is a product made by making a mass flashing blob by giving an option with USELEVEL in the past. Does it matter?

Thank you.

hello Hodu,

may I know which release version it is? thanks

Hello,

it’s R32.4.4

Thank you.

hello Hodu,

could you please share which doc and which paragraph shown this?
I’m checking README_Massflash.txt, and it looks nothing wrong.
for example,

   To generate jetson-nano-emmc PKC signed massflash blob:
     sudo BOARDID=3448 BOARDSKU=0002 FAB=200 FUSELEVEL=fuselevel_production \
     ./nvmassflashgen.sh -x 0x21 -y PKC -u <pkc_keyfile> \
     jetson-nano-emmc mmcblk0p1
1 Like

Hello,

It’s not that the documentation is wrong, I’ve been using this as it is until now when you gave me instructions. The mass flashing blobs were made without any problems and are still in use today. But when I looked at the document, it said FUSELEVEL, so I asked again if there was any problem even with USELEVEL.

Thank you.

Hello,

Since I used the message JerryChang commented as it is, I have been making blobs with USELEVEL, not FUSELEVEL.
So far, no problems have been reported from customers.

Thank you.

hello Hodu,

we had never tried this,
it should behavior like you’re not specify this settings into the command-line since it’s unknown variable.

1 Like