public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001764] Enhancement of MMC/SD over SPI driver
Date: Thu, 18 Apr 2013 18:35:00 -0000	[thread overview]
Message-ID: <bug-1001764-777-BRaUCvgNVy@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001764-777@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001764

--- Comment #14 from Mike Jones <mjones@linear.com> ---
I took several micro cards and plugged them into the larger carrier and tested
on the K60 Tower, leaving the code to use response[3].

The SanDisk Ultra 8GB micro SDHC 1 does not respond to the init command 40 00
00 00 00 95.

The Samsung 4GB micro SDHC discussed earlier and having problems does not
respond to init command 40 00 00 00 00 95.

The SanDisk 2GB micro SD responds to the init command... and fails in this
code:

    if ( 1 == disk->sd_csd_version) {
      // There is information available about the file format, e.g.
      // partitioned vs. simple FAT. With the current version of the
      // generic disk code this needs to be known statically, via
      // the mbr field of the disk channel structure. If the card
      // is inappropriately formatted, reject the mount request.
      if ((0 != MMC_CSD_REGISTER_FILE_FORMAT_GROUP(&csd)) ||
          (0 != MMC_CSD_REGISTER_FILE_FORMAT(&csd))) {
          return -ENOTDIR;
      }
    } // Acco

Just like the SD 2GB mentioned in the last comment. Next steps will be to move
to my custom board with micro connector and test.

-- 
You are receiving this mail because:
You are the assignee for the bug.


  parent reply	other threads:[~2013-04-18 18:35 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 20:24 [Bug 1001764] New: " bugzilla-daemon
2013-03-14 14:25 ` [Bug 1001764] " bugzilla-daemon
2013-03-15  0:47 ` bugzilla-daemon
2013-03-15  7:52 ` bugzilla-daemon
2013-03-15 14:04 ` bugzilla-daemon
2013-03-18  9:52 ` bugzilla-daemon
2013-03-19 13:36 ` bugzilla-daemon
2013-03-20  7:29 ` bugzilla-daemon
2013-03-23 16:00 ` bugzilla-daemon
2013-04-15 22:41 ` bugzilla-daemon
2013-04-16 14:41 ` bugzilla-daemon
2013-04-18 18:35 ` bugzilla-daemon [this message]
2013-04-18 19:10 ` bugzilla-daemon
2013-04-22 15:03 ` bugzilla-daemon
2013-05-01 15:10 ` bugzilla-daemon
2013-05-05 16:09 ` bugzilla-daemon
2013-06-19 11:04 ` bugzilla-daemon
2013-06-30 13:59 ` bugzilla-daemon
2013-07-01 17:36 ` bugzilla-daemon
2013-07-01 20:27 ` bugzilla-daemon
2013-07-02 16:28 ` bugzilla-daemon
2013-02-18 20:24 [Bug 1001764] New: " bugzilla-daemon
2013-03-14 14:24 ` [Bug 1001764] " bugzilla-daemon
2013-03-15  0:47 ` bugzilla-daemon
2013-03-15  7:52 ` bugzilla-daemon
2013-03-15 14:04 ` bugzilla-daemon
2013-03-18  9:52 ` bugzilla-daemon
2013-03-19 13:36 ` bugzilla-daemon
2013-03-20  7:29 ` bugzilla-daemon
2013-03-23 16:00 ` bugzilla-daemon
2013-04-15 22:41 ` bugzilla-daemon
2013-04-16 14:41 ` bugzilla-daemon
2013-04-18 17:33 ` bugzilla-daemon
2013-04-18 18:35 ` bugzilla-daemon
2013-04-18 19:10 ` bugzilla-daemon
2013-04-18 21:16 ` bugzilla-daemon
2013-04-19 16:17 ` bugzilla-daemon
2013-04-22 15:03 ` bugzilla-daemon
2013-05-01 15:10 ` bugzilla-daemon
2013-05-05 16:09 ` bugzilla-daemon
2013-06-19 11:04 ` bugzilla-daemon
2013-06-30 13:59 ` bugzilla-daemon
2013-07-01 17:36 ` bugzilla-daemon
2013-07-01 20:27 ` bugzilla-daemon
2013-07-02 16:28 ` bugzilla-daemon

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=bug-1001764-777-BRaUCvgNVy@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=unassigned@bugs.ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).