On Tue, Nov 22, 2016 at 7:36 AM, 'Ian Watts' via BeagleBoard < [email protected]> wrote:
> ... > although it will not complete a boot sequence via the built-in eMMC (not > so good news) > it WILL complete a boot sequence via the uSD card (-2-) (good news) and it > does appear to (re-) flash the eMMC from uSD card (-1-) when a Flasher > image is inserted. > > My questions : > Why ? Anyone with any bright ideas ? > Two ideas that may help you. Both of these have saved me in the last few months: *(1)* Instead of using dd to write the image to the uSD card, I now use Etcher. It verifies that the image has been written correctly. This has solved a number of strange problems that I was seeing every once in a while. https://etcher.io/ *(2)* Before inserting the uSD card into the BB, edit these files on it: .../opt/scripts/tools/eMMC/* Look for all the places where "ext4_options" is defined. Everywhere you see this: ext4_options="-c ... Change it to instead say this: ext4_options="-cc ... See man mkfs.ext4(8) which says this: -c Check the device for bad blocks before creating the file system. > If this option is specified twice, then a slower read-write test is used > instead of a fast read-only test. It takes about an hour (?) for flasher to run to completion with -cc, but this solved *all* my strange problems that only I was seeing. Turns out some bad sectors on the eMMC would guarantee that the installation would fail in mysterious ways. Stéphane -- 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/CA%2BHxBULQ0Cc0GFsHEGc0-KLq1jwMjrMLGjwrSY36rxpCTa-ExA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
