We created our own image and use Balena Etcher for flashing. We use CM3 modules and the CM3 IO board for this. RPI Boot is installed properly.
It works on fresh/clean CM3. It does NOT always work on CM3 modules with an (other) image on it.
Mostly works on second or third time. The image does not boot. Does Balena change settings in the tables?
Used versions 1.5.50 and 1.5.59
There are other users here reporting failed images on other devices. Perhaps this is the same effect.
We know that there are side effects with the FLASH and partitions with FAT/FAT32 (Raspberry page talking about RPIBOOT at the bottom, images not booting properly). We fixed this to be always FAT32 (table and dump of one partition is now FAT32), but this is not the reason of the failure. Rufus always works with our image.
We presently use Rufus instead for this reason.
There also is a difference in speed:
Use rpiboot to detect CM3 -> speed in Rufus only 5MB/s+
Use Balena etcher to detect CM3 -> speed in Rufus >15MB/+.
I would like to stick to balena, because balena shows 21MB/s, but image does not always work.
Also Eject after Successful does not work here (WIN7 / 10 64bit), because image is not mounted at all after flashing (FAT32 partition). Rufus instead opens this partion after flashing as a readable drive.