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@lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
