Re: microSD slot fried?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | mmcblk0: mmc0:b360 USD 7070656KiB | mmcblk0:<6>glamo-mci glamo-mci.0: Error after cmd: 0x8310 ... |> glamo_mci.sd_max_clk=1000 | | This did help, I followed instructions at | http://docs.openmoko.org/trac/ticket/1743 | | How is it possible that a previously working card suddenly becomes | non-working without the max clk, I wonder? The issue here is that timeout on Glamo MCI is in units of MMC clocks, but part of the latency for data access to the NAND in the card is in absolute time. So for example, it takes 100ms to get the data off the memory in the card. The absolute time that passes in the Glamo timeout depends entirely on the clock speed, it's double the duration at 12.5MHz than it is at 25MHz for example. So reduction of clock here is just extending the absolute timeout period to match what your (slow) card needs. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjKLyYACgkQOjLpvpq7dMq43wCbBPyb/SyE1mROkhkKYK6csbKM Qf8An3NzhubMZmuEMozI0vBme1LZks9J =iz// -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
2008/9/6 Andy Green <[EMAIL PROTECTED]>: > | [3.17] 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. I have now the a bit similar new problem with a non-working SD card some time after I switched to testing repositories. The SD card still works in a card reader, but gives in Neo (from dmesg): mmc0: new high speed SDHC card at address b360 mmcblk0: mmc0:b360 USD 7070656KiB mmcblk0:<6>glamo-mci glamo-mci.0: Error after cmd: 0x8310 mmcblk0: error -110 sending read/write command end_request: I/O error, dev mmcblk0, sector 0 (continues with similar I/O errors for some time) The card is brand new and used to work for a week or so, but then I noticed the problem yesterday evening when I tried to actually use the SD card (openstreetmap content) after some while. And like I said, it still works outside Neo without any problems. I'm using 2007.2 software, Neo from the first July batch with no hardware fixes applied. > echo 1 > /sys/module/glamo_mci/parameters/sd_idleclk This didn't help. > glamo_mci.sd_max_clk=1000 This did help, I followed instructions at http://docs.openmoko.org/trac/ticket/1743 How is it possible that a previously working card suddenly becomes non-working without the max clk, I wonder? -Timo ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
I believe that command is telling the SD reader to keep its clock on, even when idle. The ability to turn off the idle clock was implemented to prevent GPS interference. Perhaps the fact you have a capasitor on your SD connector has something to do with this. Mutually exclucive fixes in hardware and software, perhaps? I believe you can also pass a parameter on the u-boot kernel command line that will set this value to 1 for you. I don't know it off hand, so that there's less danger of your partition table being corrupted again. On September 6, 2008 04:43:09 Dmitry Makovey wrote: > --- Dmitry Makovey <[EMAIL PROTECTED]> wrote: > > 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). > > after some fiddling with the procedures etc. I did get > QTopia to run from microSD. Nothing special, but after > I have applied > > echo 1 > /sys/module/glamo_mci/parameters/sd_idleclk > > > fix even after reboot my card is recognized. Does that > mean that those parameters are written into ROM ? Does > it also mean that my GPS functionality is affected as > I recall that was the fix for slow "fix" times on GPS. > > So in my case I wanted to have QTopia on microSD as it > doesn't support GPS anyway and run OM2008.8 natively > to use GPS. Do I have to extract microSD card every > time to use GPS or should I script into OM2008.8 to: > > echo 0 > /sys/module/glamo_mci/parameters/sd_idleclk > > on startup and > > echo 1 > /sys/module/glamo_mci/parameters/sd_idleclk > > on shutdown ? > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
--- Dmitry Makovey <[EMAIL PROTECTED]> wrote: > 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). after some fiddling with the procedures etc. I did get QTopia to run from microSD. Nothing special, but after I have applied echo 1 > /sys/module/glamo_mci/parameters/sd_idleclk fix even after reboot my card is recognized. Does that mean that those parameters are written into ROM ? Does it also mean that my GPS functionality is affected as I recall that was the fix for slow "fix" times on GPS. So in my case I wanted to have QTopia on microSD as it doesn't support GPS anyway and run OM2008.8 natively to use GPS. Do I have to extract microSD card every time to use GPS or should I script into OM2008.8 to: echo 0 > /sys/module/glamo_mci/parameters/sd_idleclk on startup and echo 1 > /sys/module/glamo_mci/parameters/sd_idleclk on shutdown ? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
--- Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > 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.17] 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=1000 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). ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
--- Olivier Berger <[EMAIL PROTECTED]> wrote: > Dmitry Makovey <[EMAIL PROTECTED]> writes: > > > --- Daniel Benoy <[EMAIL PROTECTED]> wrote: > > > >> Looks like trouble. Have you ruled out the card > >> itself by checking it in another reader? > > > > And have you checked if the card is in > http://wiki.openmoko.org/wiki/Supported_microSD_cards > and what's > reported there ? that is out-of-the-box card - i.e. the one that came with device. :( ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
Dmitry Makovey <[EMAIL PROTECTED]> writes: > --- Daniel Benoy <[EMAIL PROTECTED]> wrote: > >> Looks like trouble. Have you ruled out the card >> itself by checking it in another reader? > And have you checked if the card is in http://wiki.openmoko.org/wiki/Supported_microSD_cards and what's reported there ? I myself have problems with a card now and suspect that there's something broken in the kernel, but will try to test more before reporting. There's http://docs.openmoko.org/trac/ticket/1743 in any case that you'd probably be interested in. Hope this helps. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
-BEGIN PGP SIGNED MESSAGE- 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.17] 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=1000 - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjB2fAACgkQOjLpvpq7dMrOZgCfe5ahhyOeWub+CQv4+Uhyo0bv GbUAmQGKAu9r+VQ8klnNq74hqDPWPqdX =YirJ -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
--- Daniel Benoy <[EMAIL PROTECTED]> wrote: > Looks like trouble. Have you ruled out the card > itself by checking it in another reader? just did with another FreeRunner: co-worker has NorthAmerican version and it did't have problem with my card (except that the card doesn't have partition information): # dmesg | grep mmc VFS: Can't find a valid FAT filesystem on dev mmcblk0. VFS: Can't find a valid FAT filesystem on dev mmcblk0. We tried both cards (his and mine) in both devices and both cards seem to behave the same in each device respectively - in mine they throw errors, in his - missing partition information (his was functional before though, so I'm thinking my device corrupted the card). Another difference is that my stack is OM2008.8 and his is QTopia. But my FreeRunner was unable to work with microSD regardless of image/software stack used. Interestingly enough it does detect the card itself and it's size, but then soon after it "blows up". > On Friday 05 September 2008 12:48:11 Dmitry Makovey > > # grep mmc om_dmesg > > [3.165000] mmcblk0: mmc0:b368 SMI 498176KiB > > [3.17] mmcblk0:<6>glamo-mci glamo-mci.0: > > Error after cmd: 0x302 > > [3.18] mmcblk0: error -84 sending > read/write > > command > > [3.185000] end_request: I/O error, dev > mmcblk0, > > sector 0 > > [3.185000] Buffer I/O error on device mmcblk0, > > logical block 0 > > [3.195000] glamo-mci glamo-mci.0: Error after > cmd: > > 0x8020 > > [3.195000] glamo-mci glamo-mci.0: Error after > cmd: > > 0x8122 > > [3.20] mmcblk0: error -84 sending > read/write > > command > > ... ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
Looks like trouble. Have you ruled out the card itself by checking it in another reader? On Friday 05 September 2008 12:48:11 Dmitry Makovey wrote: > > --- Andy Green <[EMAIL PROTECTED]> wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Somebody in the thread at some point said: > > | --- "Neng-Yu Tu (Tony Tu)" <[EMAIL PROTECTED]> > > wrote: > > |> These is marker from factory SMT line for > > |> distinguish 900/1800/1900 and > > |> 850/1800/1900 phones, not fired :) > > | > > | thanks! that's a definite releif. However question > > | remains - why wouldn't my FreeRunner see microSD? > > I'll > > | try to locate some "other" microSD card to > > testhoping > > | it's not controller or something. > > > > You need to do > > > > dmesg > > > > and post it here, it will try to talk to your card > > during boot and > > should give a clue where it went wrong, if it could > > even talk to it at > > all, etc. > > > this is what I was looking for: > > # grep mmc om_dmesg > [3.165000] mmcblk0: mmc0:b368 SMI 498176KiB > [3.17] mmcblk0:<6>glamo-mci glamo-mci.0: > Error after cmd: 0x302 > [3.18] mmcblk0: error -84 sending read/write > command > [3.185000] end_request: I/O error, dev mmcblk0, > sector 0 > [3.185000] Buffer I/O error on device mmcblk0, > logical block 0 > [3.195000] glamo-mci glamo-mci.0: Error after cmd: > 0x8020 > [3.195000] glamo-mci glamo-mci.0: Error after cmd: > 0x8122 > [3.20] mmcblk0: error -84 sending read/write > command > ... > > > # fdisk /dev/mmcblk0 > fdisk: cannot read from /dev/mmcblk0 > > (same for all 0, 1 and 2 devices) > > but in case I was looking for the wrong stuff, here's > the whole dmesg in attachment. > > -- Daniel Benoy http://daniel.benoy.name ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
--- Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | --- "Neng-Yu Tu (Tony Tu)" <[EMAIL PROTECTED]> > wrote: > |> These is marker from factory SMT line for > |> distinguish 900/1800/1900 and > |> 850/1800/1900 phones, not fired :) > | > | thanks! that's a definite releif. However question > | remains - why wouldn't my FreeRunner see microSD? > I'll > | try to locate some "other" microSD card to > testhoping > | it's not controller or something. > > You need to do > > dmesg > > and post it here, it will try to talk to your card > during boot and > should give a clue where it went wrong, if it could > even talk to it at > all, etc. this is what I was looking for: # grep mmc om_dmesg [3.165000] mmcblk0: mmc0:b368 SMI 498176KiB [3.17] mmcblk0:<6>glamo-mci glamo-mci.0: Error after cmd: 0x302 [3.18] mmcblk0: error -84 sending read/write command [3.185000] end_request: I/O error, dev mmcblk0, sector 0 [3.185000] Buffer I/O error on device mmcblk0, logical block 0 [3.195000] glamo-mci glamo-mci.0: Error after cmd: 0x8020 [3.195000] glamo-mci glamo-mci.0: Error after cmd: 0x8122 [3.20] mmcblk0: error -84 sending read/write command ... # fdisk /dev/mmcblk0 fdisk: cannot read from /dev/mmcblk0 (same for all 0, 1 and 2 devices) but in case I was looking for the wrong stuff, here's the whole dmesg in attachment. om_dmesg Description: 2234517856-om_dmesg ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
Dmitry Makovey wrote: > http://makovey.objectis.net/Members/dimon/issues/om/microSD1.jpg/view > http://makovey.objectis.net/Members/dimon/issues/om/microSD2.jpg/view > > I'm not a big expert in electronics but to me it > looked like something is not right. Am I correct that > the slot is defective (or at least has defective > soldering) or should I look for the source of problem > somewhere else? This doesn't help your problem, but looks like you have a capacitor soldered between pins 5&6, that is a hardware fix for the issue of the SD card interfering with the GPS. I'm guessing that you didn't solder that in yourself, so has that fix become part of the current production devices then? -stacy ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
Yep. One possibility is that the partition table was nuked (Which happens sometimes on the newest kernels due to the GPS interference workarounds). dmesg right after boot will reveal if this is the situation. On Friday 05 September 2008 05:11:49 Andy Green wrote: > Somebody in the thread at some point said: > | --- "Neng-Yu Tu (Tony Tu)" <[EMAIL PROTECTED]> wrote: > |> These is marker from factory SMT line for > |> distinguish 900/1800/1900 and > |> 850/1800/1900 phones, not fired :) > | > | thanks! that's a definite releif. However question > | remains - why wouldn't my FreeRunner see microSD? I'll > | try to locate some "other" microSD card to testhoping > | it's not controller or something. > > You need to do > > dmesg > > and post it here, it will try to talk to your card during boot and > should give a clue where it went wrong, if it could even talk to it at > all, etc. > > -Andy > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- Daniel Benoy http://daniel.benoy.name ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | --- "Neng-Yu Tu (Tony Tu)" <[EMAIL PROTECTED]> wrote: |> These is marker from factory SMT line for |> distinguish 900/1800/1900 and |> 850/1800/1900 phones, not fired :) | | thanks! that's a definite releif. However question | remains - why wouldn't my FreeRunner see microSD? I'll | try to locate some "other" microSD card to testhoping | it's not controller or something. You need to do dmesg and post it here, it will try to talk to your card during boot and should give a clue where it went wrong, if it could even talk to it at all, etc. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjA9vMACgkQOjLpvpq7dMqHLQCggmu4UNkqmvNajYIJfwerFFDD ksIAoI5WZG0VERdG4JTNwm7+dv52R18v =Qqgg -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
--- "Neng-Yu Tu (Tony Tu)" <[EMAIL PROTECTED]> wrote: > These is marker from factory SMT line for > distinguish 900/1800/1900 and > 850/1800/1900 phones, not fired :) thanks! that's a definite releif. However question remains - why wouldn't my FreeRunner see microSD? I'll try to locate some "other" microSD card to testhoping it's not controller or something. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: microSD slot fried?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Dmitry Makovey: everything properly and discovered this: > > http://makovey.objectis.net/Members/dimon/issues/om/microSD1.jpg/view > http://makovey.objectis.net/Members/dimon/issues/om/microSD2.jpg/view > > I'm not a big expert in electronics but to me it > looked like something is not right. Am I correct that > the slot is defective (or at least has defective > soldering) or should I look for the source of problem > somewhere else? > These is marker from factory SMT line for distinguish 900/1800/1900 and 850/1800/1900 phones, not fired :) - -- Neng-Yu Tu (Tony Tu) Openmoko, Inc. Support. Some questions could be answered by reference following link: Wiki - http://wiki.openmoko.org Download - http://downloads.openmoko.org Freerunner Introduction - http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjAyQcACgkQmV6sZhhBn2/mzACeJPcIz35Nb6iIyKUdt6Mhn0++ PlkAn36tfZi/CMGECC1YnPwXOIISJrSG =LPvt -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
microSD slot fried?
Hi, I have had my FreeRunner for a while now, but I have never touched microSD so far. However today I decided to load QTopia on it and to my surprise I have discovered that microSD card doesn't even show up on the list. So first thing I did - I opened up moko to check if I inserted everything properly and discovered this: http://makovey.objectis.net/Members/dimon/issues/om/microSD1.jpg/view http://makovey.objectis.net/Members/dimon/issues/om/microSD2.jpg/view I'm not a big expert in electronics but to me it looked like something is not right. Am I correct that the slot is defective (or at least has defective soldering) or should I look for the source of problem somewhere else? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
