Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext David Hagood <david.hagood@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Is anybody else having problems with SDHC cards on Beagleboard?
Date: Wed, 21 Jan 2009 09:34:44 +0200	[thread overview]
Message-ID: <20090121093444.314804f6.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <1232455118.6982.14.camel@surfer>

On Tue, 20 Jan 2009 06:38:38 -0600
"ext David Hagood" <david.hagood@gmail.com> wrote:

> I have been trying to bring up a Beagleboard as a development platform
> for a project at work, but I am having a killer problem: any significant
> access of the memory card (a class 8 SDHC 8G card) will die with a
> transfer error, followed by about 10 failed sector accesses, followed by
> the system dying.
> 
> I've tried 2 different Beagleboards and 3 different cards by 2 different
> manufacturers, and the problem is repeatable on all permutations. I've
> put the cards into a card reader on my workstation and done a "dd
> if=/dev/sdf of=/dev/null" to verify the cards aren't wedged.
> 
For me both 2 GB microSD and 8 GB class 4 microSDHC cards are working
fine. E.g. no problems with these commands:

dd if=/dev/zero of=foo bs=1M count=500
dd if=foo of=/dev/null


My linux-omap head is

commit 45e5c5ffd32ade5a21a5e87b4040072590ec3ae1
Merge: c699464... 1de9e8e...
Author: Tony Lindgren <tony@atomide.com>
Date:   Sun Jan 18 14:08:53 2009 +0200

    Merge current mainline tree into linux-omap tree

And kernel is built with "make omap3_beagle_defconfig".


Jarkko

      parent reply	other threads:[~2009-01-21  7:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 12:38 Is anybody else having problems with SDHC cards on Beagleboard? David Hagood
2009-01-20 12:59 ` Premi, Sanjeev
2009-01-21  7:34 ` Jarkko Nikula [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090121093444.314804f6.jarkko.nikula@nokia.com \
    --to=jarkko.nikula@nokia.com \
    --cc=david.hagood@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox