On 06/09/2024 14:53, Thomas Schmitt wrote:
Jeff wrote:
I've run into this situation (more than once)... `dd` fails to write a
bootable image with a block size of 1M. But using a block size of 512
results in a bootable image. It used to happen regularly on arm dev
boards, like BeagleBoards and CubieTrucks and Wandboards.
I would be interested in more details (error messages ? no booting ?).
My expectation is that "boot" is not really relevant here. Verification
of written data should fail. The question if it is an issue with flash
firmware or with a board where dd was running. Comparison of original
image and data read back may reveal some pattern of corrupted bytes.
Another variant that flash firmware could not tell the host to wait till
a portion of data was actually written.
I would be really surprised if reading resulted in exactly same data,
attempt to boot from the device failed.
