From: Nathan <naroyce@hotmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] "Writing to MMC(%d)... failed"
Date: Thu, 12 Mar 2015 08:22:58 -0500 [thread overview]
Message-ID: <BLU436-SMTP16416C23AC6DD8495DD16AA2060@phx.gbl> (raw)
In-Reply-To: <54FF09DE.2040408@samsung.com>
I had tried another card with the same result. I didn't think it would
be a problem since the hardkernel's release still works.
I expanded the output by defining "DEBUG" and am updating my thread
with my new findings:
...
Bound device i2c at 138d0000 to root_driver
- ignoring disabled device
- ignoring disabled device
bind node sdhci at 12530000
No match for node 'sdhci at 12530000'
- ignoring disabled device
bind node dwmmc at 12550000
No match for node 'dwmmc at 12550000'
bind node pinctrl at 11400000
- found match at 'gpio_exynos'
fdtdec_get_addr_size: reg: 11400000
...
i2c_get_chip: Searching bus 'i2c at 13860000' for address 09: found, ret=0
initcall: 43e068e4 (relocated to bde3d8e4)
MMC: fdtdec_add_aliases_for_id: warning: maxcount exceeded with alias 'mmc'
process_nodes: count = 1
fdtdec_get_int_array: interrupts
get_prop_check_min_len: interrupts
fdtdec_get_int: samsung,bus-width: 0x4 (4)
fdtdec_get_addr_size: reg: 12530000
_gpio_request_by_name_nodev: fdtdec_parse_phandle_with_args failed
_gpio_request_by_name_nodev: Node 'sdhci at 12530000', property
'pwr-gpios', failed to request GPIO index 0: -2
fdtdec_get_int: #gpio-cells: 0x2 (2)
...
gpio=118, bank=11000060
get_mmc_clk: invalid MMC index 4mmc init failed
SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
initcall: 43e06890 (relocated to bde3d890)
fdtdec_get_config_int: load-environment
...
I think the kicker is "No match for node 'sdhci at 12530000'".
I even manually set/forced the "status=okay" in the dts, but it still
says it's disabled.
I shall continue to pursue this, working my way back from
"lists_bind_fdt()" in "lists.c"
If you wish to NOT be included in the "reply to all", just let me
know. I won't take any offense.
I won't be inundating you with a lot of replies anyway as I slowly
work my way through this problem. Only updating after a notable
finding.
On Tue, Mar 10, 2015 at 10:12 AM, Przemyslaw Marczak
<p.marczak@samsung.com> wrote:
> We are often using the SD cards for a number of Odroid boards, in our
> office, with no issues.
>
> If you have other card, then I suggest to test it, the first one, could be
> tired :)
next prev parent reply other threads:[~2015-03-12 13:22 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
2015-03-10 13:14 ` Nathan
2015-03-10 15:12 ` Przemyslaw Marczak
2015-03-12 13:22 ` Nathan [this message]
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=BLU436-SMTP16416C23AC6DD8495DD16AA2060@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.