-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Happy new year to the community! | I have this SD, Kingston SDC4 (N0043-012.A00LF) an SDHC 4GB, but i can't | use with openmoko, because i have glamo errors!
| glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: | 195kHz). Bus width=0 | glamo-mci glamo-mci.0: Error after cmd: 0x8120 | glamo-mci glamo-mci.0: Error after cmd: 0x120 | glamo-mci glamo-mci.0: Error after cmd: 0x8120 | glamo-mci glamo-mci.0: Error after cmd: 0x120 | mmc_set_power(power_mode=2, vdd=15 | SD power -> 2700mV ... | glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: | 195kHz). Bus width=0 | glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: | 195kHz). Bus width=0 | glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: | 195kHz). Bus width=0 ... | glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: | 195kHz). Bus width=0 ... | glamo-mci glamo-mci.0: Error after cmd: 0x310 | mmc_set_power(power_mode=0, vdd=0 The first errors are actually typical even on a correct recognition and mount of the SD Card, but towards the end there it would normally have cranked up the clock rate and moved to 4-bit mode. The status is telling there was a timeout error receiving data, but also that the data is in fact ready. This is what happens when the card takes longer to come up with the payload than we can wait with Glamo. When I have recovered from the trashing I did earlier to my stg tree for the history branch :-( I'll make a patch that treats this "timeout" and "data ready" indication as a success and see if it helps. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklg3NEACgkQOjLpvpq7dMqCpACeJDgZql/8NQVsQVODSrf9Pjo2 GH4AnRnI0K/+CrVAcHnlfIp22Z6ukQbH =Dpan -----END PGP SIGNATURE-----
