public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Przemyslaw Marczak <p.marczak@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] "Writing to MMC(%d)... failed"
Date: Tue, 10 Mar 2015 14:07:49 +0100	[thread overview]
Message-ID: <54FEECA5.8000405@samsung.com> (raw)
In-Reply-To: <BLU437-SMTP105D4C7DA6754615DB4E45DA2180@phx.gbl>

Hello Nathan,

On 03/10/2015 12:30 PM, Nathan wrote:
> I hope my last message didn't get lost during that outage last month.
>
> In the mean time, I had to finagle the HardKernel code to work with
> GCC 5.0 which ended up being only 1 line change which I may end up
> encountering in mainline if I ever get far enough.
> After transferring the "CONFIG_MMC_TRACE" to the HardKernel mmc.c, I
> have a comparable output for the U2 with the "Samsung" mainline.
>
> So the output comparison can be made more readable, I created a Google
> Drive Sheet, lining up the output when there were repeats,
> highlighting the differing output sections and changing the text color
> for the different values:
> https://docs.google.com/spreadsheets/d/1Gu10bG8wGJClorJjKoIMiAt4HR0nS22ugrL8-F5_Nbg/edit?usp=sharing
>

Now, I don't have too much time for this, but the only one you need is 
the documentation and a time to analyze the responds for commands.

Please check this site:
https://www.sdcard.org/downloads/pls/simplified_specs/index.html
you can also check some example spec from Jedec:
http://www.jedec.org/standards-documents/results/jesd84-a441

You will solve this problem with this.

By the way, did you tried another SD-Card?

Best regards,
-- 
Przemyslaw Marczak
Samsung R&D Institute Poland
Samsung Electronics
p.marczak at samsung.com

  parent reply	other threads:[~2015-03-10 13:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 19:14 [U-Boot] "Writing to MMC(%d)... failed" Nathan Royce
2015-02-26  0:30 ` Nathan
2015-02-26 23:59   ` Nathan
2015-02-27 13:16     ` Przemyslaw Marczak
2015-02-27 17:21       ` Nathan
2015-03-10 11:30         ` Nathan
     [not found]         ` <BLU437-SMTP105D4C7DA6754615DB4E45DA2180@phx.gbl>
2015-03-10 13:07           ` Przemyslaw Marczak [this message]
2015-03-10 13:14             ` Nathan
2015-03-10 15:12               ` Przemyslaw Marczak
2015-03-12 13:22                 ` Nathan
2015-02-27 13:08   ` Przemyslaw Marczak
  -- strict thread matches above, loose matches on Subject: below --
2015-04-28  5:39 Nathan
     [not found] <BLU436-SMTP127C338DB532C3DF004593EA2E80@phx.gbl>
2015-04-28  8:07 ` Przemyslaw Marczak
     [not found]   ` <BLU437-SMTP496E077CBDBF75F343C04FA2E80@phx.gbl>
2015-04-29  9:15     ` Przemyslaw Marczak
2015-04-29 23:34       ` Nathan
2015-04-30  2:44       ` Nathan

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=54FEECA5.8000405@samsung.com \
    --to=p.marczak@samsung.com \
    --cc=u-boot@lists.denx.de \
    /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