microSD slot fried?

Dmitry Makovey dmakovey at yahoo.com
Sat Sep 6 09:32:20 CEST 2008

--- Andy Green <andy at openmoko.com> wrote:

> Hash: SHA1
> Somebody in the thread at some point said:
> | [    3.165000] mmcblk0: mmc0:b368 SMI   498176KiB
> That's the good part above, it talked to the card
> and got information
> out of it (512MB card).
> | [    3.170000]  mmcblk0:<6>glamo-mci glamo-mci.0:
> | Error after cmd: 0x302
> Then it all went wrong, 0x0302 is actually CRC error
> with data ready,
> never seen it before.  After that it's dead meat.
> Looks like bulk transfer on that card doesn't work
> under current default
> conditions, eg max clock speed.
> You can meddle with max clock speed on kernel
> commandline, try eg
> glamo_mci.sd_max_clk=10000000

I have borrowed solution from parallel thread:

echo 1 > /sys/module/glamo_mci/parameters/sd_idleclk

now I get:

# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 510 MB, 510132224 bytes
8 heads, 7 sectors/track, 17792 cylinders
Units = cylinders of 56 * 512 = 28672 bytes

        Device Boot      Start         End      Blocks
 Id System
/dev/mmcblk0p1               5       17792     
498058+  6 FAT16

which is way more pleasing to the eye.

Now big question for me is: how do I install QTopia on
this microSD and get it to boot? I mean I know the
steps to install QTopia, but if it's kernel is tweaked
the same way - wouldn't it bomb on boot failing to
recognize the card? (I might end up trying anyway but
it's better to ask first in case there are
consequences/workarounds I'm not aware of).

More information about the support mailing list