From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Beagleboard xM boot broken due to FIT enable
Date: Mon, 2 Oct 2017 11:58:26 -0400 [thread overview]
Message-ID: <20171002155826.GF13147@bill-the-cat> (raw)
In-Reply-To: <b334a89a-3164-36b2-0729-cffddaafecc9@free.fr>
On Mon, Oct 02, 2017 at 05:55:27PM +0200, Guillaume Gardet wrote:
>
>
> Le 02/10/2017 à 15:53, Tom Rini a écrit :
> >On Mon, Oct 02, 2017 at 03:24:01PM +0200, Guillaume Gardet wrote:
> >>Hi,
> >>
> >>commit 46f9ef18461609064a1ffbc3f61dc027ec76b3ff
> >>Author: Andrew F. Davis <afd@ti.com>
> >>Date: Fri Apr 21 10:01:28 2017 -0500
> >>
> >> Kconfig: Enable FIT support by default for TI platforms
> >>
> >> Almost all TI defconfigs enable this already, add this as a default
> >> and remove the explicit assignment.
> >>
> >> Signed-off-by: Andrew F. Davis <afd@ti.com>
> >> Reviewed-by: Tom Rini <trini@konsulko.com>
> >>
> >>broke boot on Beagleboard xM. I mean the board hangs after:
> >> OMAP3630/3730-GP ES1.1, CPU-OPP2, L3-200MHz, Max CPU Clock 800 MHz
> >> OMAP3 Beagle board + LPDDR/NAND
> >> I2C: ready
> >> DRAM: 512 MiB
> >>
> >>
> >>To get back the board booting, I need to manually disable FIT (CONFIG_FIT) _and_ disable SHA256 hash support (CONFIG_SHA256).
> >>
> >>If I enable FIT without sha256 : it breaks boot.
> >>If I enable sha256 without FIT : it breaks boot.
> >>
> >>Any idea what could cause this?
> >>
> >>As a workaround we could disable it in the omap3_beagle_defconfig but I guess it would be better to fix it instead of workaround it, since other boards may also be affected.
> >Which Beagleboard xM rev do you have? And how are you booting (FAT or
> >raw) ? Mine, FAT booting, is working currently and is part of my
> >automated test farm, thanks!
>
> This is a Beagleboard xM rev. B.
> We use raw booting (instead of default FAT booting).
OK. Can you test FAT booting? Both should work, but I have an idea at
least on RAW, but I'd like to rule out anything else other than size
changes. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171002/20172dfb/attachment.sig>
next prev parent reply other threads:[~2017-10-02 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 13:24 [U-Boot] Beagleboard xM boot broken due to FIT enable Guillaume Gardet
2017-10-02 13:53 ` Tom Rini
2017-10-02 15:55 ` Guillaume Gardet
2017-10-02 15:58 ` Tom Rini [this message]
2017-10-02 16:14 ` Guillaume Gardet
2017-10-04 7:39 ` Guillaume Gardet
2017-10-04 11:46 ` Tom Rini
2017-10-04 11:59 ` Guillaume Gardet
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=20171002155826.GF13147@bill-the-cat \
--to=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.