All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan <naroyce@hotmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] "Writing to MMC(%d)... failed"
Date: Thu, 26 Feb 2015 17:59:23 -0600	[thread overview]
Message-ID: <BLU437-SMTP95124F81BC0A5364289E0CA2140@phx.gbl> (raw)
In-Reply-To: <BLU436-SMTP103FAEE11BEDD60CF8F599EA2140@phx.gbl>

I think I've been able to narrow down, a bit, where the issue is coming from.

"mmc_set_blocklen" led me to "mmc_send_cmd" which showed that there is
the "CONFIG_MMC_TRACE" I could use.

A notable difference between hardkernel's u-boot and mainline was the
"uint flags;" was no longer in the "mmc_cmd" struct.

I did see that this removal was noted as being a problem back in 2012:
http://lists.denx.de/pipermail/u-boot/2012-September/133409.html

The result from "saveenv":

Odroid # saveenv


Saving Environment to MMC...


Writing to MMC(0)... CMD_SEND:16


                ARG                      0x00000200


ret: -19


                MMC_RSP_R1,5,6,7         0x00000000

I added the "printf" for "ret".

  reply	other threads:[~2015-02-26 23:59 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 [this message]
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
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
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=BLU437-SMTP95124F81BC0A5364289E0CA2140@phx.gbl \
    --to=naroyce@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.