Hi,
I was flashing a CM3 module (at around 50%), when my computer (Windows 7) crashed.
The crash was probably not related to flashing, but I had to turn off the computer.
After rebooting I ran RPiBoot.exe tool again. (https://www.raspberrypi.org/documentati ... lashing.md)
It sent the bootcode.bin and start.elf just fine.
But the mass storage device (MSD) did not show up. I repeated the procedure several times without success.
Since I have another CM3 at hand I tested it and the MSD showed up as expected.
So I have a working CM3 and a "corrupt" CM3.
How can I find the problem? Here is what I did so far:
I prepared a directory "boot" with the contents of the Raspbian Lite boot partition.
Additionally I created a initramfs file including busybox (rescue shell) and edited the config.txt to use the initramfs file.
Then I ran the Rpiboot.exe with the parameter "-d boot" to boot the CM3 into a rescue shell.
This way I could download the kernel messages ("dmesg") onto an USB stick.
Good thing is that the corrupt CM3 is still booting the kernel and I could do things in the rescue shell.
However the eMMC does not seem to be accessible.
I attached two files showing the different dmesg logs. The differences are basically just the mmc0 messages.
You can ignore the messages of attaching my Cherry keyboard or USB stick.
My questions:
Is the eMMC and therefore the CM3 lost and dead?
Is it possible that the interruption of the flash action is responsible? Maybe there is some state that needs to be reset to make the flash accessible again?
Do you know any special kernel parameters or techniques or logs that can help me to debug the issue?
The corrupt log contains the line: "[ 1.591333] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)". Does that mean there is still something working? (I interpret it as the card reader is detected, but the card is not).
Thank you for reading and I hope you can help me.