[U-Boot] [PATCH v11 0/3] Adds support for Exynos5422 odroid xu3 board

[Hyungwon Hwang]

Dear Suriyan,

On Tue, 09 Dec 2014 18:29:56 -0800
Suriyan Ramasami <suriyan.r at gmail.com> wrote:

> Hello Hyungwon Hwang,
> 
> On Tue, Dec 9, 2014 at 4:58 PM, Hyungwon Hwang
> <human.hwang at samsung.com> wrote:
> > Dear Kevin,
> >
> > On Tue, 09 Dec 2014 15:36:00 -0800
> > Kevin Hilman <khilman at kernel.org> wrote:
> >
> >> Hyungwon Hwang <human.hwang at samsung.com> writes:
> >>
> >> > This is v11 of the patchset adding support Odroud XU3 board.
> >>
> >> I finally got around to testing this on top of v2015.01-rc3 on my
> >> XU3.
> >>
> >> As I mentioned earlier, I had to enable the USB and networking
> >> options so I could dhcp/tftp but after that it works for me.
> >>
> >> Feel free to add:
> >>
> >> Tested-by: Kevin Hilman <khilman at linaro.org>
> >
> > Thanks for yout review. Sjoerd is waiting for his patch merged
> > (title: Exynos: Move down common USB
> > configuration). So the features related USB and networking will be
> > enabled after this patchset and his patch are merged.
> >
> >>
> >> [...]
> >>
> >> > Note: If you use micro SD card for your test you have to apply
> >> > the below patch additionally. This patch is needed, because
> >> > micro sd card is recognized as MMC1 instead of MMC0. Additional
> >> > work is needed to make it work regardless of device id.
> >>
> >> FYI, with or without your MMC ID patch, I wasn't able to save the
> >> environment to the SD card I'm booting from:
> >>
> >> ODROID-XU3 # saveenv
> >> Saving Environment to MMC...
> >> dwmci_send_cmd: Timeout.
> >> MMC init failed
> >>
> >
> > Actually I just tested it again. But it works for me.
> >
> > Saving Environment to MMC...
> > Writing to MMC(1)... done
> >
> > I applied my patchset and MMC ID patch to commit
> > 38cd8c4253013ccdd4052ee021f6066fe9a52551 in
> > http://git.denx.de/u-boot-samsung.git (branch: master).
> >
> > I don't know why it does't work for you. Please feel free to need my
> > help for this, if you need.
> >
> 
> Just like Kevin, I have to say that mmc is erratic.
> For example, if you let the boot process go all along (and not
> interrupt it), and let it fail in the pxe load commands. Then if you
> do a, ls mmc 1:1 / it will give a timeout error (Assuming you do have
> a valid 1st partition)
> But, if you interrupt the boot during the count down, and issue the
> same, it will work.
> I had mentioned this before, that if you enable *MMC_TRACE, it again
> stops working.
> 
> Also, I found if you do a couple of mmc 1:1 commands, and do some
> other commands (say mmc rescan etc), and retry it will fail.

I tested all sinarios that you told me. But in all cases, it works for
me. That's awkward. You are using Micro SD card. Right?

> 
> Regards
> - Suriyan
> 
> 
> >> Kevin
> >
> > Best regards,
> > Hyungwon Hwang
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot

Best regards,
Hyungwon Hwang