All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Trouble with mmc 1 on exynos snow chromebook
Date: Fri, 17 Jul 2015 19:38:34 +0900	[thread overview]
Message-ID: <55A8DB2A.3080503@samsung.com> (raw)
In-Reply-To: <CAArymCnqYPTcWr+bh5RqSPks4mubWUPyyqAwb2ubgsssXgj5Aw@mail.gmail.com>

Hi,

On 07/17/2015 12:44 PM, bruce m beach wrote:
> Hello
> 
>  I have a samsung "snow" chromebook. Building u-boot from
> 
> git clone git://git.denx.de/u-boot.git
> 
> and changing #define CONFIG_SYS_TEXT_BASE 0x43E00000 to
>              #define CONFIG_SYS_TEXT_BASE 0x42400000
> 
> in include/configs/exynos5250-common.h I get a chained u-boot
> that boots. (if I don't make that change I just get a blank screen)
> The problem that I'm have is that dev mmc 1 (mmcblk1) doesn't seem to
> work. dev mmc 0 (mmcblk0) does work as far as I have tested it.
> Below are some of the messages that I get. (btw there are no
> mmc init or mmcinit commands)

"mmc rescan" command work to initialize mmc or sd.
I don't have the chromebook.

Could you enable the CONFIG_MMC_TRACE and share the log message?

Best Regards,
Jaehoon Chung

> 
> snow> mmc rescan
>       dwmci_send_cmd: data ERROR!
> snow> mmc dev 1
>       dwmci_send_cmd: Timeout
> snow> mmc list
>       EXYNOS DWMMC 0 (eMMC)
>       EXYNOS DWMMC 1
> snow> ext2load mmc 1:2 ${loadaddr} env.txt
>       dwmci_send_cmd: Timeout
>       ** bad device mmc 1 **
> 
> The ext2load command I regularly use on mmc1 using a precompiled version
> of u-boot works fine so mmc 1 (and the filesystem) is okay
> 
> Thanks
> 
>   Bruce
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 

      reply	other threads:[~2015-07-17 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  3:44 [U-Boot] Trouble with mmc 1 on exynos snow chromebook bruce m beach
2015-07-17 10:38 ` Jaehoon Chung [this message]

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=55A8DB2A.3080503@samsung.com \
    --to=jh80.chung@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 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.