From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] SAMA5D2 xplained SD/eMMC boot
Date: Thu, 21 Apr 2016 04:58:45 +0200 [thread overview]
Message-ID: <571841E5.8010602@denx.de> (raw)
In-Reply-To: <B256D81BAE5131468A838E5D7A243641D6478138@penmbx01>
On 04/21/2016 04:46 AM, Yang, Wenyou wrote:
> Hi,
Hi!
[...]
pile of unnecessary email headers redacted.
[...]
>>>>>>>> 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-at
>>>>>>> 91
>>>>>>
>>>>>> 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 ?
>>>
>>> In this SoC, there is not register to list the current boot device.
>>
>> And thus, it is not possible to detect at runtime from which device the SoC booted
>> and thus load u-boot.img from the same device. Correct ?
>
> Yes,
Ha, thanks for confirming.
[...]
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-04-21 2:58 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
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 [this message]
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=571841E5.8010602@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