Jetson TK1 output issue

If system.img.raw is exactly 2311197100 bytes (please check to see if the original “2,31,11,97,100” has a typographic error, the commas are spaced wrong), then the image is not valid. On a TK1 the size would be evenly divisible by 1024 (or powers of 2 like 1024*1024 or 1024*1024*1024). Note that 1024 is sometimes referred to as KiB, 1024 twice is MiB, and three times is GiB (like KB, MB, and GB, except in base 2).

It is unlikely that a clone or system.img.raw of size 2311197100 is valid.

Sorry,there was a mistake on my part. The actual values are reversed:

Linux_for_Tegra/bootloader/system.img.raw - 15.3GB(15,28,82,38,080)
Linux_for_Tegra/bootloader/system.img - 2.3GB(2,31,11,97,100)

The raw image size 15,28,82,38,080 is valid. Divided by 1024 twice gives MiB of 14580 Assuming the sparse image was created from this image, the command line flash could include this to guarantee proper space reservation for the rootfs (there are other partitions too, and they would just “fit” if this is an NVIDIA system and not a third party system):
-S 14580 MiB -r
(the -r is so the image is not overwritten with a new default image; if you have ever flashed without -r, and if your clone is in bootloader/, then it was overwritten)

Note that flashing with either the raw or sparse image should work and create the same exact final partition size. The key is that the one named system.img and placed in Linux_for_Tegra/bootloader/, then that is what is used. Assuming you have a safe copy somewhere, if you place either of those files there with the name system.img (you’d have to change the name if using the .raw, but you can do that during copy), then reusing the image would use that clone and it should work. Do note that it takes a long time to copy just a 2.3 GB file, and that a 15.3 GB file takes a much longer time; the same is true for flash since it is transferring that much data over a 480 Mb/s USB connection (and that is raw speed, not actual throughput).

I will emphasize that VMs mess things up most of the time unless you’ve learned to configure it correctly, and that Ubuntu 22.04 won’t work with JetPack of this release version, but command line flash should still succeed from almost any Ubuntu flavor (except for the VM types). I’ve even used Fedora for this many times. A typical command line might be:
sudo ./ -r -S 14580 MiB jetson-tk1 mmcblk0p1

You could log a flash if you choose via:
sudo ./ -r -S 14580 MiB jetson-tk1 mmcblk0p1 2>&1 | tee log_flash.txt

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