From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Peter Kuennemann@Crane-Soft" <pkue@crane-soft.de>
Cc: barebox@lists.infradead.org
Subject: Re: Failed to launch barebox from flash memory on i.MX35
Date: Wed, 2 Nov 2011 15:49:32 +0100 [thread overview]
Message-ID: <20111102144932.GM23421@pengutronix.de> (raw)
In-Reply-To: <4EB14DEA.2030901@crane-soft.de>
On Wed, Nov 02, 2011 at 03:04:26PM +0100, Peter Kuennemann@Crane-Soft wrote:
>
> Am 02.11.2011 11:16, schrieb Sascha Hauer:
> >>
> >> I am completly stuck. What went wrong?
> >> Any help will be very much appreciated.
> > There seems to be a bug in the pcm043_defconfig. It is configured for
> > internal bootmode, which means that the board has to specify a header
> > of size 0x2000 before the actual image. The pcm043 does not specify this
> > header as it uses the external bootmode.
> > Please disable CONFIG_ARCH_IMX_INTERNAL_BOOT in your config, that should
> > do it. If it works I'll commit a corresponding patch.
> >
> > Sascha
> >
> Thanks, that did the trick. I changed the option "support internal boot mode" to
> "support external boot mode" (What ever that means) and the relocation works
> pretty well now.
It's described in the i.MX datasheet. Internal bootmode means that after
reset the internal ROM is executed which parses a header in flash or on
a SD Card. The header describes how to setup memory, where to load the
image and so on. In external bootmode the i.MX simply executes the code
in NOR flash after reset.
>
> Nevertheless, next problem appears right after relocation. The console displays the
> welcome messages: "barebox 2011.10.0 (Nov 2 2011 - 14:40:11)" and
> "Board: Phytec phyCORE-i.MX35" but then loops in mmu.c at function mmu_init
> in the for () loop at line 237 .. forever!
Strange. I just flashed a pcm043 with v2011.10.0 pcm043_defconfig +
external bootmode and it works for me. As you have printf available can
you put something like this into the loop?
printf("0x%08x 0x%08x\n", mem->start, mem->size)
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-11-02 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 17:43 Peter
2011-11-02 10:16 ` Sascha Hauer
2011-11-02 12:03 ` Issue when building Barebox with ARM EABI 4.4.3 Loc Nguyen
2011-11-02 14:04 ` Failed to launch barebox from flash memory on i.MX35 Peter Kuennemann@Crane-Soft
2011-11-02 14:49 ` Sascha Hauer [this message]
2011-11-02 14:58 ` Peter Kuennemann@Crane-Soft
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=20111102144932.GM23421@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=pkue@crane-soft.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