Unable to flash own customized image on xavier nx emmc

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hello,

I am trying to flash a minimal customized image for xavier nx using below command:
But i get below error.

~/JETSON_BUILD_DIR/Linux_for_Tegra$ sudo ./flash.sh --image /home/l4t/jetson_nx.img jetson-xavier-nx-devkit-emmc mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 6.1

###############################################################################
Error: missing -k option to specify partition name

How can I flash this correctly ?

Thanks

2

Where does this “jetson_nx.img” come from? and what is the file you want to replace it with? the system.img?

3

the “jetson_nx.img” is an image with minimal customized rootfs(added a user, no gnome,enabling basic networking services ) small in size instead of the official image. If the system.img is the official Nvidia image you refer to, then yes!

4

It is created using ./jetson-disk-image-creator.sh -o jetson_nx.img -b jetson-xavier-nx-devkit script !

5

Hi,

Such image is not working for emmc module and the flash tool for emmc module.

6

can I use SD card to flash such an image ? will it work with SD card ?

7

But you are using a emmc module… which has no sdcard slot on it…

8

For emmc case, you can customize the rootfs by using

https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-325/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/rootfs_custom.html#

Or you can customize it on the device first and then use the clone method to clone out the APP parition.

https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/flashing.html

→ To clone a Jetson device and flash

9

I meant, I can write the image to SD card like below as described in ./flash.sh and boot from SD card:

./flash.sh <target_board> mmcblk1p1 - boot <target_board> from SDCARD

10

It is not just a simple "yes"or “no” answer to this.

Please tell me what is the exact module you want to use so that I can give you the precise answer.

11

I want to flash a customised image “jetson_nx.img” using either emmc or sd card whichever method works but I don’t know exactly how to do it. Could you please provide the steps for it or refer me to the docs I can refer to.
Thanks

12

If you are using sdcard module, then you can just use the same method as how the official sdcard image install to the card.

Which means etcher or dd can do the work.

If you are using emmc module, then your image cannot directly work, you need to use the post I shared above to create a new system image.

In brief, flash.sh does not support your “jetson_nx.img”.

1 Like
13

Also, your new image created by the method I shared could be used for flash.sh to flash both emmc and sdcard module.

Actually, flash.sh is the one that has full support. Sdcard image is more like a method for beginners.

1 Like
14

BTW, I forgot to say the most important things…if your customization is already done under Linux_for_Tegra/rootfs… then you can directly run flash.sh to flash. No need to think about sdcard image or the method I shared above…

No parameters are needed. Just

sudo ./flash.sh <board_config> mmclbk0p1

1 Like
15

Actually, I created sample rootfs and copied to Linux_for_Tegra/rootfs, applied binaries with $ sudo ./apply_binaries.sh .

In this case (sudo ./flash.sh <board_config> mmclbk0p1), from which path does the ./flash.sh script pick up my image “jetson_nx.img” ? as I ran the ./jetson-disk-image-creator.sh -o jetson_nx.img -b jetson-xavier-nx-devkit script in separate Python script or in other words where should I keep my image to ensure correct image is being flashed ?

16

flash.sh will use your rootfs to create system.img and that one will have all the customization you have done in rootfs.

17

I set the Jetson board in recovery mode but it is failing to probe,

~/JETSON_BUILD_DIR/Linux_for_Tegra$ sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 6.1

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
~/JETSON_BUILD_DIR/Linux_for_Tegra$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 019: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 004: ID 047f:c039 Plantronics, Inc. Plantronics Blackwire 320
Bus 001 Device 018: ID 046a:0023 Cherry GmbH Keyboard
Bus 001 Device 021: ID 0955:7e19 NVIDIA Corp. APX
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

18

Are you still able to see activity on your board like desktop screen overt he HDMI monitor?

19

no

20

Is your host machine a VM/VB?