Flash bootloader and other necessary partitions only to boot from nvme

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

Hi,
We are helping out with a production line for jetson xavier nx based devices, and the idea is to have cloned nvme’s with the rootfs on them and just plug them into the carrier and be able to boot. From testing we know that we need to flash the emmc with:
sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1
With the same major JP version so its able to pick the nvme out and boot from it. This works for us, since after that flash, it boots fine with the cloned nvme.
But wanted to see if there is a faster way to only flash perhaps the bootloader and any other necessary file/partition to achieve that, in hopes of making the process faster. The whole emmc flash is taking too much time for it to be a viable option.
Here is what I’ve tried:

sudo ./flash.sh -k cpu-bootloader jetson-xavier-nx-devkit mmcblk0p1
Gets stuck at [ 7.3295 ] tegrarcm_v2 --isapplet

sudo ./flash.sh -k EBT jetson-xavier-nx-devkit mmcblk1p1
Fails with NV3P_SERVER: Failed to open partition EBT

We are currenlty using a known good devkit and nvme, boot work ok. And if we use the full emmc flash everything works fine, and boots normally.

Regards,
Andres
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

3

There is nothing called “necessary partitions”. The bootloader should be all there but not “I only want to flash some of them”.

4

@WayneWWW , I know that there is nothing called “necessary partitions”. Let me make myself clear on what I’m asking:

  1. Bare minimum or partitions that are required to be flashed to boot from a cloned NVME.
  2. How to flash said partitions only.
5

Mainly we want to avoid flashing APP, which takes the most time.

6

Does flashing QSPI only meet your requirement?

7

As long as we are able to boot from NVME and reduce the flashing time, should be fine.

8

sudo ./flash.sh -c bootloader/t186ref/cfg/flash_t194_qspi.xml --no-systemimg jetson-xavier-nx-devkit-emmc nvme0n1p1

I am actually not sure which jetpack version you are using. If that xml name is not correct, please just go to your cfg directory and see what the name should be.

Also, not sure why your are using a sdcard config while telling you are using emmc module. Thus, I changed to use xavier-nx-devkit-emmc.

9

Thanks for the info, I will go ahead and try it. And yeah forgot to mention, we are using JP5.1.3.

12

For JP5.1.3 the config is this one:

sudo ./flash.sh -c bootloader/t186ref/cfg/flash_l4t_t194_qspi_p3668.xml --no-systemimg jetson-xavier-nx-devkit-emmc nvme0n1p1

With that I was able to boot from a previously flashed jp4 board into a jp5 nvme. And takes way less time than a full flash. Thanks @WayneWWW .

13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.