> > Don't use Win32 Disk Imager, grab: > > https://etcher.io/ >
I got Etcher, and it can read img.xz. However, the speed is slower (by half from what I see) compared to unpacking to an img file, then use it. Considering the img file will be used over and over again, this seems worth it. On the other hand, Win32 Disk Imager can be used to image the SD card content to be unpacked to another one later. I wish not to go through the exercise on eewiki, so I am imaging the newly prepped SD card to an img file. Will have to see if this prepped SD card is bootable, then I will use the img to clone other cards. Speedwise, Win32 Disk Imager write an image at ~27MB/s whereas Etcher gives ~9.5MB/s. After the write, Etcher has a validating steps which runs at ~31MB/s. The SD card is a Samsung Evo (orange one). The image is 'bone-debian-9.3-lxqt-2gb-armhf-2017-12-24-2gb', and an SD card slot is use for the task. Etcher has a nice and simple interfaces, and is open source. However, Win32 Disk Imager is faster and can image an SD card. Seems like Etcher leaves a lot to be desired. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/676954c3-f29a-485c-a2c7-a411fb01f137%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
