From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] mx35: Fix boot ROM hang in internal boot mode
Date: Fri, 13 Aug 2010 10:58:26 +0200 [thread overview]
Message-ID: <4C650932.7090209@eukrea.com> (raw)
In-Reply-To: <20100813081720.GA23898@pengutronix.de>
Hi Uwe,
Le 13/08/2010 10:17, Uwe Kleine-K?nig a ?crit :
> On Thu, Aug 12, 2010 at 02:15:04PM +0200, Hans J. Koch wrote:
>> As a sidenote, it should be clear that this patch is a workaround for
>> a serious chip bug of the MX35.
>> From the things you wrote up to now it's possible that this is a
> bootloader issue, isn't it.
>
> I don't know exactly what "internal boot mode" means, but assuming the
> ROM code doesn't make any output to UART1 at least this clock smells
> like a bootloader problem.
internal bootmode is the mode where the CPU boots on the internal rom
code which samples some GPIO to set the fuses and select which boot
media to use. So ROM code is executed before loading the bootloader
(barebox in my case) and that's where the CPU hangs.
I think we have the exact same problem using i.MX35 (and maybe also on
i.MX51), but I need to find time to do more tests to confirm this.
Eric
next prev parent reply other threads:[~2010-08-13 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 23:37 [PATCH v2] mx35: Fix boot ROM hang in internal boot mode Hans J. Koch
2010-08-12 5:57 ` Uwe Kleine-König
2010-08-12 11:29 ` Hans J. Koch
2010-08-12 12:15 ` Hans J. Koch
2010-08-13 8:17 ` Uwe Kleine-König
2010-08-13 8:58 ` Eric Bénard [this message]
2010-08-13 10:04 ` Hans J. Koch
2010-08-13 10:25 ` Uwe Kleine-König
-- strict thread matches above, loose matches on Subject: below --
2010-09-24 8:13 John Ogness
2010-09-24 10:10 ` Hans J. Koch
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=4C650932.7090209@eukrea.com \
--to=eric@eukrea.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).