public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] SAMA5D2 xplained SD/eMMC boot
Date: Wed, 20 Apr 2016 11:36:32 +0200	[thread overview]
Message-ID: <57174DA0.3040401@denx.de> (raw)
In-Reply-To: <B256D81BAE5131468A838E5D7A243641D647784A@penmbx01>

On 04/20/2016 03:17 AM, Yang, Wenyou wrote:
> Hi Marek,
> 
>> -----Original Message-----
>> From: Marek Vasut [mailto:marex at denx.de]
>> Sent: 2016?4?20? 0:34
>> To: Yang, Wenyou <Wenyou.Yang@atmel.com>
>> Cc: u-boot at lists.denx.de
>> Subject: Re: SAMA5D2 xplained SD/eMMC boot
>>
>> On 04/19/2016 05:22 AM, Yang, Wenyou wrote:
>>> Hi Marek,
>>>
>>>> -----Original Message-----
>>>> From: Marek Vasut [mailto:marek.vasut at gmail.com]
>>>> Sent: 2016?4?18? 23:30
>>>> To: Yang, Wenyou <Wenyou.Yang@atmel.com>
>>>> Cc: u-boot at lists.denx.de
>>>> Subject: SAMA5D2 xplained SD/eMMC boot
>>>>
>>>> Hi!
>>>>
>>>> I've been playing around with latest mainline u-boot on sama5d2
>>>> xplained ultra. I noticed that if I want to boot the board from SD
>>>> card (SDHCI1), the board will indeed load the SPL from it, but SPL
>>>> will try to load u-boot.img from eMMC
>>>> (SDHCI0) and fail, as my eMMC is blank.
>>>
>>> Yes, there is some issue to load u-boot.img. I found there is something to do on
>> sdhci.c.
>>>
>>> You can try this branch, it should works.
>>>
>>> https://github.com/linux4sam/u-boot-at91/commits/u-boot-2016.03-at91
>>
>> I am not interested in using non-mainline stuff. Do you have any particular
>> patch/commit which I can refer to ? I do not think this has anything to do with
>> sdhci.c driver at all, it has to do with detecting the boot device from which SPL
>> was started and loading u-boot.img from the same boot device instead of always
>> using SDHCI0.
> 
> I will test the mainline code. I will let you know when I get something.

OK.

Does the SoC have any sort of register which lists the current boot device ?

> Thank you.
> 
>>
>>>> This is a result of hard-coding boot
>>>> device to
>>>> BOOT_DEVICE_MMC1 in arch/arm/mach-at91/spl.c spl_boot_device() I think.
>>>>
>>>> Is there any way to discern from which SDHCI the board booted to
>>>> continue loading u-boot.img from the correct one ? This would let us
>>>> implement
>>>> board_boot_order() and boot from correct SDHCI.
>>>>
>>>> --
>>>> Best regards,
>>>> Marek Vasut
>>>
>>>
>>> Best Regards,
>>> Wenyou Yang
>>>
>>
>>
>> --
>> Best regards,
>> Marek Vasut
> 
> 
> Best Regards,
> Wenyou Yang
> 


-- 
Best regards,
Marek Vasut

  reply	other threads:[~2016-04-20  9:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 15:30 [U-Boot] SAMA5D2 xplained SD/eMMC boot Marek Vasut
2016-04-18 16:54 ` Andreas Bießmann
2016-04-18 22:48   ` James Chargin
2016-04-19  3:22 ` Yang, Wenyou
2016-04-19 16:34   ` Marek Vasut
2016-04-20  1:17     ` Yang, Wenyou
2016-04-20  9:36       ` Marek Vasut [this message]
2016-04-21  2:30         ` Yang, Wenyou
2016-04-21  2:41           ` Marek Vasut
2016-04-21  2:46             ` Yang, Wenyou
2016-04-21  2:58               ` Marek Vasut
2016-04-22  0:54                 ` Yang, Wenyou
2016-04-22 12:17                   ` Marek Vasut
2016-04-25  0:55                     ` Yang, Wenyou
2016-04-25 10:30                       ` Marek Vasut
2016-04-26  1:47                         ` Yang, Wenyou
2016-04-26 12:42                           ` Marek Vasut

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=57174DA0.3040401@denx.de \
    --to=marex@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox