I think I understand the oem-config.
So now, what steps do I need to go through to massflash with the default user/password and our software installed?
Go back to what I said previously… check whether your system.img really has a default user account or not…
1 Like
Can you tell me how to check if I don’t know anything and system.img has a default user account?
I think it will be possible to check if you clone the Nano in the state of flashing and oem-config now and back up and restore it. Is it correct?
Thank you.
This is what you told me before.
If you try to restore it with the backup image and log in with the same account, you have checked it, right?
Thank you.
Hi,
What I wanted you to try is
-
Configure your user account /pwd as “nvidia/nvidia” on first jetson nano.
-
Clone the system.img from (1), because you already set user account and password in (1), this system.img should already have user and password (nvidia/nvidia).
And below parts are same as the page.
https://elinux.org/Jetson/Clone
-
Put this system.img to Linux_for_Tegar/bootloader.
-
run flash.sh with “-r” parameters to flash your board again
-
Check if you can directly have nvidia/nvidia on your nano but no need to configure it again.
1 Like
yes.
I was able to log in with my ID and password.
1 Like
Ok. That’s all. This system image now has default user account.
Hello,
Moved the question. And I deleted the duplicate questions.
Hello,
If we unzip our software to /Linux_for_Tegra/rootfs
In the Linux_for_Tegra/ directory
Should I run sudo ./apply_binaries.sh?
Thank you.
Your answer : Yes, you have to.
Loading the software we made with rootfs applied like this
After flashing is finished, cloning with our software installed
Can you explain what’s different?
thank you.
Hello,
I think I’m almost at the conclusion.
I have a question.
So, how can I create a mass flashing blob with system.img made like this?
Thank you.
what is your objective?
in the context of considerations about using mass flash?
What outputs do you anticipate after it got sorted out?
How many devices do you plan to flash simultaneously?
1 Like
Hello,
① what is your objective in the context of considerations about using mass flash?
=> Mass flashing with its own software and default user/password.
② What outputs do you anticipate after it got sorted out?
=> I didn’t understand the question.
③ How many devices do you plan to flash simultaneously?
I tried flashing up to 4 units per host pc.
Do you know how many flashing units can be stably flashed per host PC?
Thank you.
what prevents you from flashing the image to the 4 units?
it depends
1 Like
Hello,
============================================
Following the quick start guide, an image with its own software was installed, and an image with a default user/password was created, and it was cloned.
backup.img and backup.img.raw are created
I don’t know how to make a mass flash blob with this.
I guess this backup.img
Copy it to the Linux_for_Tegra/bootloader/ directory as system.img and
Can I enter the following command after executing the apply_binaries.sh command in the Linux_for_Tegra directory?
sudo ./nvmassflashgen.sh [] mmcblk0p1
Thank you.
I would say that apply binaries will do no impact to system image
given the system image will not be re-created
so you could enter the command as it will be of no impact to the system image file
actually you may like to make sure the system image is intact while flashing to devices;
with flash.sh -r argument was used for the purpose to re-utilize existing image
1 Like
at the point when system image got created already
the script is not supposed to be executed
as it is used in steps predceeding the image creation
so you may like to use it when creating a new image
1 Like
In a regular flash an unmodified Ubuntu filesystem is unpacked to “Linux_for_Tegra/rootfs/”. The “apply_binaries.sh” script unpacks some additional content which is custom to making the Jetson work. NVIDIA separates the shipping of Ubuntu content from their own content, and lets you combine the content during the flash. Unless you’ve done something to remove “Linux_for_Tegra/rootfs/” content, then you do not need to run “apply_binaries.sh” ever again. The final “bootloader/system.img” is a result of the “rootfs/” content, and will consistently match from one flash to the next if the “flash.sh” script arguments do not change.
Hello,
When the image creation is complete, how do you make a mass flashing blob with this?
Is what I guessed above is correct?
Thank you.
Hello,
https://elinux.org/Jetson/Clone
Can the content on this webpage be considered to be on the same level as the official document?
Is it okay if I follow the instructions here?
Thank you.
This is only opinion, but eLinux.org is probably “close” to authoritative. The main problem is that eLinux can fail to update for newer release changes. If what you see there seems wrong, then there is a chance that it is an out of date page.
1 Like