The R21.4 errors suggest the flash was completely corrupt, or the hardware is bad. vmware and other VM hosts are known to have issues that can get in the way if not careful, so I believe this is the issue and probably R21.4 should be re-attempted after working on the vmware install.
First, I do not know if 32 bit matters or not on host. It might…or might not, I can’t test (anyone know?). I suspect it does matter when generating and using the system.img file which is around 15 GB (2^32 implies 4 GB max without special handling), but I’m not sure. On your install attempts, there would be a file left over in the bootloader subdirectory, “system.img”. This file should be approximately the size of the “-S” parameter of flash. For “-S 14580MiB” or “-S 14GiB” this file approaches 15 GB…or for default I think it is around 12 GB. Check the directory and confirm that this file is in the approximate 12 to 15 GB size range.
Second, you need much more space for flash. Even if the flash software install can be put in with 20 GB spare (beyond the linux host use itself), temporary files (including the above system.img which itself occupies 15 GB all by itself) will at least momentarily occupy a lot of space. You might want to be sure that you have more like 50 GB spare space just to be sure.
Make sure that the partition type which the vmware lives on is a native linux type. If you run this command a “type” column will show something like “ext4”:
df -T /
Note that when a flash does succeed, it takes significant time. It’s building system.img (an entire linux root file system) from rootfs, then making a compressed version of it, and only then running flash, so it takes significant time.
You can log the flash via something like this:
sudo flash.sh -S 14580MiB jetson-tk1 mmcblk0p1 2>&1 | tee log_flash_r21-4.txt
Be sure to check after flash that the bootloader/system.img is around 15 GB…if around 4 GB or less 32 bit cut it off.