public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001764] Enhancement of MMC/SD over SPI driver Date: Thu, 18 Apr 2013 19:10:00 -0000 [thread overview] Message-ID: <bug-1001764-13-rRhSPmGuW9@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001764-13@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 #15 from Mike Jones <mjones@linear.com> --- On the hardware with micro SD, the return from 48 00 00 01 AA 87 on my 2GB micro SD card puts the 01 in response[2] and the AA in response[3] which means the original code works with my custom board.. So now differences. The Tower K60 is Rev 1 silicon and the custom board is Rev 2 silicon. The revisions in my CDL are correct. The Tower is using a fx patched packages, and the custom is not, so I differenced the trees and found no MMC/SD or SPI related differences. So at this point the differences are silicon and board. The failing board is the Tower K60 large SD card socket with old silicon, and the working board is a custom K60 board with micro SD card socket. I now move to the original problem Samsung card. In this code: if (MMC_REPLY_ILLEGAL_COMMAND & reply) { // V1 cards do not understand CMD8 disk->sd_version = 1; disk->sd_capacity = STANDARD_CAPACITY; mmc_spi_end_command(disk); return ENOERR; } It enters as a V1 card. I don't have the Beagle attached yet. But this is the difference from the working cards. It then fails to enter the idle state. I'll get the Beagle on it later. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-04-18 19:10 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: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 [this message] 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 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 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
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-13-rRhSPmGuW9@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-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: linkBe 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).