From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot stuck after relocation attempt on MX51 board
Date: Thu, 26 Feb 2015 11:38:21 +0100 [thread overview]
Message-ID: <20150226113821.2e46750f@lilith> (raw)
In-Reply-To: <CA+sos7-WD0Z_DopTOPLAUF3aoRrph5qBu=mS6K7qHRG=BJGLgw@mail.gmail.com>
Hello Beno?t,
On Thu, 26 Feb 2015 00:56:00 +0100, Beno?t Th?baudeau
<benoit.thebaudeau.dev@gmail.com> wrote:
> Dear Dave Kucharczyk,
>
> On Wed, Feb 25, 2015 at 11:08 PM, DaveKucharczyk
> <david.kucharczyk@gmail.com> wrote:
> > Fabio Estevam-2 wrote
> >> Also, you said that your 512MB board version works fine, but the 256MB
> >> fails.
> >>
> >> I suppose you are using two different binaries for each board, right?
> >> You can't have a single binary for the two boards, unless you use the
> >> SPL approach.
> >
> > Fabio, we use one binary. It has runtime memory discovery via gpio's
> > (resistor reads). DRAM size is reported correctly from both boards. It just
> > hangs on the 256MB board.
> >
> > We do not have SPL setup.
>
> You should try with 2015.01 as Fabio suggested.
>
> Also, check the CONFIG_SYS_TEXT_BASE of your board. From your log, I'm
> wondering if it's not set too high, resulting in an overlap of the
> pre- and post-relocation addresses occupied by your binary in the
> 256-MiB case.
/me wonders whether we should not add a test for this situation, with
a conspicuous error message on the console stating that relocation will
probably fail due to overlap.
> Best regards,
> Beno?t
Amicalement,
--
Albert.
next prev parent reply other threads:[~2015-02-26 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 2:19 [U-Boot] U-Boot stuck after relocation attempt on MX51 board DaveKucharczyk
2015-02-25 15:49 ` DaveKucharczyk
2015-02-25 20:40 ` Benoît Thébaudeau
2015-02-25 21:23 ` DaveKucharczyk
2015-02-25 22:05 ` Fabio Estevam
2015-02-25 22:08 ` DaveKucharczyk
2015-02-25 23:56 ` Benoît Thébaudeau
2015-02-26 10:38 ` Albert ARIBAUD [this message]
2015-02-26 21:15 ` Benoît Thébaudeau
2015-02-26 14:19 ` DaveKucharczyk
2015-02-26 22:01 ` Benoît Thébaudeau
2015-02-28 16:00 ` Fabio Estevam
2015-02-26 21:10 ` Benoît Thébaudeau
2015-02-28 15:56 ` Fabio Estevam
2015-03-01 15:30 ` Albert ARIBAUD
2015-03-01 18:01 ` Fabio Estevam
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=20150226113821.2e46750f@lilith \
--to=albert.u.boot@aribaud.net \
--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