Some terminology will help here…
A raw image is a bit-for-bit exact image of a partition (this is what a dd command would read or write if a partition is named as a source or destination). A sparse image is the same image with empty disk space marked as such, but not present…it is a mix of content plus a recipe for recreating empty space. The log lines with “RAW” are indicators of non-empty content found in various blocks…the log lines with “SKP” are a record of blocks found to be empty and which are being skipped.
In the end the Jetson is able to be flashed with either a raw image or via a sparse image (the Jetson understands this version of a sparse file system and can recreate the empty space…the recognition of this sparse format is automatic within the Jetson itself). The sparse image is created and used because it is faster to send the smaller sparse image over a relatively slow communications medium. Earlier flash tools didn’t use sparse images, and a flash which now takes perhaps 20 minutes might have taken three hours.
If the conversion from raw to sparse begins (if a “SKP” is found in the log), then you’ve already had the full sized raw image created and you are in the process of creating the sparse image. If the host disk fills up prior to this, then the size and content of the raw image will be truncated. If instead the host disk fills up during creation of the sparse image, then the sparse image will be truncated. Of course there is the possibility that both (or neither) are truncated.
During flash the flash software has no concept of the kind of data it is flashing…if an image is corrupt or truncated, then the flash software has no means of knowing this and is quite happy to flash garbage…it only flashes what you tell it to flash regardless of whether it is what you wanted or whether the image is half missing. Flash knows when the data was flashed, but flash does not know if the data itself is valid.
The error I saw was that you had a raw image, but the sparse image was failing. No monitor will ever fix a truncated image. True, the monitor might not work if it is missing features like a VGA adapter would cause, but a bad image implies you can’t even test the monitor.
When you finish flash, do all of the “RAW” and “SKP” lines show up without “ERROR” (earlier logs had “ERROR” in this step)?
Does your host disk have room? What do you see from:
df -H -T /where/ever/flashed/from/Linux_for_Tegra/
In “/where/ever/flashed/from/Linux_for_Tegra/bootloader/” the file “system.img” is the resulting sparse file, and the file “system.img.raw” is the resulting raw file. What is the exact byte size of the raw file?
ls -l /where/ever/flashed/from/Linux_for_Tegra/bootloader/system.img.raw
If the raw image is divisible by 1024 at least twice, or perhaps a third time at dividing, then this image is probably not truncated (the option in how many MiB to create a partition size as is the MiB times 1024 twice…the option in how many GiB to create a partition size as is the GiB times 1024 three times…you need to know if the MiB or GiB is valid for the size of system.img.raw).