Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: David Hagood <david.hagood@gmail.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Is anybody else having problems with SDHC cards on Beagleboard?
Date: Tue, 20 Jan 2009 06:38:38 -0600	[thread overview]
Message-ID: <1232455118.6982.14.camel@surfer> (raw)

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.

I've searched for this on Google and found no references, but I cannot
believe I'm the only person seeing this - but am I?




             reply	other threads:[~2009-01-20 12:38 UTC|newest]

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

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=1232455118.6982.14.camel@surfer \
    --to=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