From: Derald D. Woods <woods.technical@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] spl_mmc: allow to load raw image
Date: Sun, 1 May 2016 21:17:45 -0500 [thread overview]
Message-ID: <ceb84b3e-7190-3c70-2c30-e6a6fdcc2c4e@gmail.com> (raw)
In-Reply-To: <20160502015758.GI7884@bill-the-cat>
On 05/01/2016 08:57 PM, Tom Rini wrote:
> On Sun, May 01, 2016 at 08:32:48PM -0500, Derald D. Woods wrote:
>> On 05/01/2016 03:37 AM, Masahiro Yamada wrote:
>>> Hi Adam,
>>>
>>>
>>> 2016-04-30 3:06 GMT+09:00 Adam Ford <aford173@gmail.com>:
>>>> On Fri, Apr 29, 2016 at 12:53 PM, Tom Rini <trini@konsulko.com> wrote:
>>>>> On Fri, Apr 29, 2016 at 09:59:00AM -0500, Adam Ford wrote:
>>>>>
>>>>>> Does anyone with an OMAP3 board have any issues with this patch? I
>>>>>> will admit I haven't stayed on top of stuff due to moving, and other
>>>>>> issues at home, but I pulled down the master to reviews some on
>>>>>> related stuff, and found that master doesn't boot. I used git bisect
>>>>>> this morning and it narrowed down a problem with booting to this
>>>>>> patch.
>>>>>>
>>>>>> With the patch, I get:
>>>>>>
>>>>>> U-Boot SPL 2016.03-00378-g4976f48 (Apr 29 2016 - 09:25:27)
>>>>>> Trying to boot from MMC
>>>>> OK. Do you have u-boot.bin or u-boot.img (which?) written to the raw
>>>>> offset in MMC or from filesystem? Based on the log it looks like
>>>>> filesystem.
>>>> I have u-boot.img copied to the fatfs on the card, but I didn't put it
>>>> in a specific location.
>>>>
>>>> I never used to have to do that. Is this a new behavior and is it
>>>> documented somewhere?
>>>>
>>>> adam
>>> You are expecting to boot it from FAT,
>>> but I think spl_boot_mode() on your board returns MMCSD_MODE_RAW.
>>>
>>> Can you fix the function to return MMCSD_MODE_FS?
>>>
>>>
>>>
>>> This commit changed to allow to load raw U-Boot image,
>>> so MMCSD_MODE_RAW never fails.
>>>
>>> So, you can no longer rely on the former behavior
>>> "try MMCSD_MODE_RAW first, and fallback to MMCSD_MODE_FS".
>>>
>> So everyone loading MLO from the FAT filesystem is now wrong? I am
>> trying to understand how this came into being the default.
> ... yes, we can't break the case of SPL+U-Boot being on FS on MMC1. I
> wonder if:
> commit 22d90d560a2b01c47f180e196e6c6485eb8e65db
> Author: Alexander Graf <agraf@suse.de>
> Date: Tue Mar 1 09:56:34 2016 +0100
>
> omap3: Use raw SPL by default for mmc1
>
> Isn't part of what's going wrong now.
>
Reverting that commit worked for me!
---8<----------------------------------------------
U-Boot SPL 2016.05-rc3-00012-gfccdb28-dirty (May 01 2016 - 21:10:05)
Trying to boot from MMC1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img
U-Boot 2016.05-rc3-00012-gfccdb28-dirty (May 01 2016 - 21:10:05 -0500)
OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
Logic DM37x/OMAP35x reference board + LPDDR/NAND
---8<----------------------------------------------
Derald
next prev parent reply other threads:[~2016-05-02 2:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 11:31 [U-Boot] [PATCH] spl_mmc: allow to load raw image Masahiro Yamada
2016-03-01 1:58 ` Tom Rini
2016-03-15 19:23 ` [U-Boot] " Tom Rini
2016-03-16 3:10 ` Masahiro Yamada
2016-03-17 2:04 ` Tom Rini
2016-03-17 16:07 ` Masahiro Yamada
2016-03-17 16:12 ` Tom Rini
2016-04-29 14:59 ` Adam Ford
2016-04-29 17:53 ` Tom Rini
2016-04-29 18:06 ` Adam Ford
2016-04-29 18:06 ` Tom Rini
2016-05-01 8:37 ` Masahiro Yamada
2016-05-01 13:46 ` Tom Rini
2016-05-02 1:32 ` Derald D. Woods
2016-05-02 1:57 ` Tom Rini
2016-05-02 2:04 ` Masahiro Yamada
2016-05-02 2:17 ` Derald D. Woods [this message]
2016-05-02 2:29 ` Derald D. Woods
2016-05-02 7:08 ` Alexander Graf
2016-05-02 12:44 ` Tom Rini
2016-05-02 7:35 ` Alexander Graf
2016-05-02 8:58 ` Guillaume Gardet
2016-05-02 9:12 ` Alexander Graf
2016-05-02 9:45 ` Guillaume Gardet
2016-05-02 11:21 ` Alexander Graf
2016-05-02 16:14 ` Tom Rini
2016-05-02 21:19 ` Alexander Graf
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=ceb84b3e-7190-3c70-2c30-e6a6fdcc2c4e@gmail.com \
--to=woods.technical@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox