Kernel Panic with eMMC flasher

I am trying to flash my eMMC with the image here: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases I am using the 4Gb flasher for the RevC. I can flash the microSD but all of the images ive tried cause Kernel Panics when I try to flash the BBB. Im sure this is something I am doing but Im not sure.

Here are the steps Im using:

  1. Wget the image
  2. md5sum check
  3. xzcat BBB-eMMC-Flasher… …img.xz | sudo dd bs=4096 of=/dev/sdc
  4. load SD and apply power
  5. kernel panic

So what am I missing here?

Can you try flashing using https://github.com/ungureanuvladvictor/BBBlfs .Also post a console log here so we can see what is happening.

Well 3.8 always panic's (drm) when shutdown at the completion of the
flashing procedure.

If you have the serial log from the flashing procedure this would confirm that.

Regards,

This might not be part of the problem, but I have created much mysterious misery by forgetting to “sync” after “dd”-ing my sd card. If you forgot to do this and yanked your card out after dd finished you cannot trust that you have an accurate and functional image. spread the word.

I dont have a serial cable. Probably need to pick one up.

I am properly ejecting the card from my laptop after completing dd. Is that what you mean by sync?

I dont have a serial cable. Probably need to pick one up.

Okay, I'm a little confused.. How then do you know your getting a
kernel panic? While flashing all debug info gets directed over the
serial. I still haven't mirrored any of the progress back to hdmi
output..

I am properly ejecting the card from my laptop after completing dd. Is that
what you mean by sync?

Regards,

There is definitely a text output from the HDMI That is where Im seeing the kernel panic. I am trying to flash a new uSD now to try it. If it happens again Ill just take a picture of the screen.

IMG_20141118_073426.jpg

Humm, that’s 5 minutes into the flasher…

What was the exact name of the image you flashed?

How are you powering the board? any other capes attached?

https://rcn-ee.net/deb/testing/2014-11-11/lxde-4gb/BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-11-11-4gb.img.xz is the image. Im powering through USB plugged into a wall outlet. No Capes, just power, and HDMI.

I was able to successfully flash https://rcn-ee.net/deb/testing/2014-11-11/console/BBB-eMMC-flasher-debian-7.7-console-armhf-2014-11-11-2gb.img.xz and pull up the console. There was some concern on the machinekit page that I was using an older boot loader but that should have fixed that I would think.

I am for sure using a RevC with the 4g eMMC and I am pushing the boot button to boot from the SD.

Flashing while powered through USB is not recommended.

Can you please retry with a 5volt DC jack. rsync really hits the
microSD/eMMC hard while flashing, thus it's fast, but any voltage ripples
can mess with the mmc devices.

Since the console image is so much smaller (200mb vs 1.7gb) we don't
normally see any mmc write errors during the flashing procedure.

Regards,

change step 3 to:

. xzcat BBB-eMMC-Flasher... ...img.xz | sudo dd bs=4096 of=/dev/sdc; sync

sync ensures that whatever is in the buffers actually gets written to the
disk. The sdcard shouldn't even be mounted on the desktop while you dd
it. At least with unity it will still dd properly but the desktop is not
aware and shows it mounted in it's previous state. A desktop unmount at
this point is potentially harmful.

I wish there was a simple way to verify the image after you've flashed it
to the card -- does anyone know how to do this?

Cheers.

First of all, as far as the sdcard is concerned. sync has nothing to do with it, UNLESS, you are trying to remount the same exact sdcard.

sync is not infallible, and as such will not always do what you think it may do. sync can take a considerable amount of time to achieve what you think it should achieve.

What does a UI(Unity ) have to do with DD ? An application that has been around for YEARS longer than Unity ?

All you can do is:

write data

remove media.

sync.

If the OS you’re using screws this up, then it does not deserve to be used. Otherwise, it is user error.

Latest failure. This time I flashed from windows 7 just to try something new, different PC and card reader, and used a wallwart. No dice. Slightly different t error message with the panic though. Progress??

Thanks for re-testing.. This looks to be evil v3.8.x, never saw it
fail on the eMMC, but i get that error alot of microSD cards..

So here's a v3.14.x based kernel snapshot using jessie:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot

It's using a newer kernel (v3.14.x) vs the old v3.8.x

Once the eMMC has been flashed, you can safely downgrade to the v3.8.x
based kernel via: (and get capemgr)

sudo apt-get update
sudo apt-get install linux-image-3.8.13-bone67
sudo reboot

Regards,

Advice ? Use Linux to flash Linux. I use windows on a daily basis, and honestly it is is my prerecorded OS. But when dealing with Linux, use Linux. . .

“prerecorded” ? I never wrote that

. . . Preferred is what I wrote,

write data
sync
and then remove media.

That's all I'm really trying to convey. "dd" does not sync by default.
Unmounting from your gui should sync. But might not if you've been
sudo-ing things behind it's back. Once "sync" has completed you can safely
remove it regardless of what some gui thinks is going on.