[U-Boot] U-Boot stuck after relocation attempt on MX51 board

[Benoît Thébaudeau]

Hi Albert,

On Thu, Feb 26, 2015 at 11:38 AM, Albert ARIBAUD
<albert.u.boot at aribaud.net> wrote:
> Hello Benoît,
>
> On Thu, 26 Feb 2015 00:56:00 +0100, Benoît Thébaudeau
> <benoit.thebaudeau.dev at gmail.com> wrote:
>> Dear Dave Kucharczyk,
>>
>> On Wed, Feb 25, 2015 at 11:08 PM, DaveKucharczyk
>> <david.kucharczyk at 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.

Yes, that would be very helpful in such a case, which must occur very
often for new boards being ported to U-Boot. Besides that, it would be
great if CONFIG_SYS_TEXT_BASE could be automatically set to a sensible
value for most boards, from the configured internal/external RAM base
addresses.

Best regards,
Benoît