Program only ROOTFS on Orin with doflash.sh

[MichaelPres]

Hi,

Maybe I miss something in the manual but is there a way on the Orin, with kirkstone branch, to call ./doflash.sh for rootfs only. It take a while to program!

Thanks!

[joekale-pp]

initrd-flash is faster than doflash.sh. And to speed it up initrd-flash more install bmaptool to your host operating system that is flashing the device.

[madisongh]

And it has a --skip-bootloader flag you can use to omit the programming of the SPI flash, for when you just need to update the kernel/rootfs.

[MichaelPres]

I cannot use initrd-flash. It is not completed after 1h30:

Starting at 2024-04-08T14:33:31-04:00
Machine:       jetson-agx-orin-devkit
Rootfs device: mmcblk0p1
Waiting for Jetson to appear on USB.........[found: 1-2]
== Step 1: Signing binaries at 2024-04-08T14:33:38-04:00 ==
== Step 2: Boot Jetson via RCM at 2024-04-08T14:33:49-04:00 ==
Found Jetson device in recovery mode at USB 1-2
== Step 3: Sending flash sequence commands at 2024-04-08T14:33:52-04:00 ==
Waiting for USB storage device flashpkg from 8967fe02........[/dev/sdc]
Device size in blocks: 262144
Unmounted /dev/sdc.
== Step 4: Writing partitions on internal storage device at 2024-04-08T14:34:19-04:00 ==
Waiting for USB storage device mmcblk0 from 8967fe02...[/dev/sdc]
Creating partitions
  [02] name=A_kernel start=0 size=262144 sectors
  [03] name=A_kernel-dtb start=0 size=1536 sectors
  [04] name=A_reserved_on_user start=0 size=64768 sectors
  [05] name=B_kernel start=0 size=262144 sectors
  [06] name=B_kernel-dtb start=0 size=1536 sectors
  [07] name=B_reserved_on_user start=0 size=64768 sectors
  [08] name=recovery start=0 size=163840 sectors
  [09] name=recovery-dtb start=0 size=1024 sectors
  [10] name=esp start=0 size=131072 sectors
  [11] name=recovery_alt start=0 size=163840 sectors
  [12] name=recovery-dtb_alt start=0 size=1024 sectors
  [13] name=esp_alt start=0 size=131072 sectors
  [14] name=UDA start=0 size=819200 sectors
  [15] name=reserved start=0 size=982016 sectors
  [01] name=APP (fills to end)
Writing partitions
  Writing boot.img (size=35536896) to /dev/sdc2 (size=134217728)...
  Writing kernel_tegra234-p3701-0000-p3737-0000.dtb (size=439669) to /dev/sdc3 (size=786432)...
  Writing boot.img (size=35536896) to /dev/sdc5 (size=134217728)...
  Writing kernel_tegra234-p3701-0000-p3737-0000.dtb (size=439669) to /dev/sdc6 (size=786432)...
  Writing esp.img (size=67108864) to /dev/sdc10 (size=67108864)...
  Writing rhc-generic.ext4 (size=30064771072) to /dev/sdc1 (size=62087216640)...

[joekale-pp]

That's where bmaptool will come in. If you are writing to a very large disk then it will take a very long time to write block by block, but bmaptool will allow writing only what is populated in your ext4 filesystem.