[U-Boot] "Writing to MMC(%d)... failed"

[Nathan]

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 at 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 :)