Hi Tom,

On Tue, Oct 30, 2012 at 1:08 PM, Tom Rini trini@ti.com wrote:

On Tue, Oct 30, 2012 at 01:00:06PM -0500, Joe Hershberger wrote:

...

Hi Marek,

Not sure if you were already aware of this, but I ran across these errors with MAKEALL on PPC.

alpr: powerpc-linux-gnu-ld: section .bootpg loaded at [00000000fffff000,00000000fffff27f] overlaps section .u_boot_list loaded at [00000000ffffee8c,00000000fffff3cb] powerpc-linux-gnu-ld: u-boot: section .bootpg lma 0xfffff000 adjusted to 0xfffff3cc

P2020DS_36BIT: powerpc-linux-gnu-ld: section .bootpg loaded at [00000000effff000,00000000effff4c3] overlaps section .u_boot_list loaded at [00000000efffef60,00000000effff7fb] powerpc-linux-gnu-ld: u-boot: section .bootpg lma 0xeffff000 adjusted to 0xeffff7fc

P2020DS_SDCARD: powerpc-linux-gnu-ld: section .bootpg loaded at [00000000f8fff000,00000000f8fff4b3] overlaps section .u_boot_list loaded at [00000000f8ffe874,00000000f8fff10f] powerpc-linux-gnu-ld: u-boot: section .bootpg lma 0xf8fff000 adjusted to 0xf8fff110

P2020DS_SPIFLASH: powerpc-linux-gnu-ld: section .bootpg loaded at [00000000f8fff000,00000000f8fff4b3] overlaps section .u_boot_list loaded at [00000000f8ffe778,00000000f8fff013] powerpc-linux-gnu-ld: u-boot: section .bootpg lma 0xf8fff000 adjusted to 0xf8fff014

What toolchain are you using? I don't see that with ELDK 5.2.

powerpc-linux-gnu-gcc (Sourcery G++ Lite 2010.09-55) 4.5.1

I may just be that there is barely enough space and my added 14 bytes or so to the .u_boot_list section is pushing it over.

...

Tom,

There are also several boards that fail due to missing CONFIG_SYS_MPC85xx_DDR2_ADDR

MPC8641HPCN_36BIT, MPC8641HPCN, xpedite517x.

Andy is aware of these and has a patch he'll be pushing my way shortly.

Thanks, -Joe

On Tue, Oct 30, 2012 at 1:37 PM, Joe Hershberger joe.hershberger@gmail.com wrote:

Hi Andy,

On Tue, Oct 30, 2012 at 1:00 PM, Joe Hershberger joe.hershberger@gmail.com wrote:

...

Hi Marek,

Not sure if you were already aware of this, but I ran across these errors with MAKEALL on PPC.

alpr: powerpc-linux-gnu-ld: section .bootpg loaded at [00000000fffff000,00000000fffff27f] overlaps section .u_boot_list loaded at [00000000ffffee8c,00000000fffff3cb] powerpc-linux-gnu-ld: u-boot: section .bootpg lma 0xfffff000 adjusted to 0xfffff3cc

P2020DS_36BIT: powerpc-linux-gnu-ld: section .bootpg loaded at [00000000effff000,00000000effff4c3] overlaps section .u_boot_list loaded at [00000000efffef60,00000000effff7fb] powerpc-linux-gnu-ld: u-boot: section .bootpg lma 0xeffff000 adjusted to 0xeffff7fc

P2020DS_SDCARD: powerpc-linux-gnu-ld: section .bootpg loaded at [00000000f8fff000,00000000f8fff4b3] overlaps section .u_boot_list loaded at [00000000f8ffe874,00000000f8fff10f] powerpc-linux-gnu-ld: u-boot: section .bootpg lma 0xf8fff000 adjusted to 0xf8fff110

P2020DS_SPIFLASH: powerpc-linux-gnu-ld: section .bootpg loaded at [00000000f8fff000,00000000f8fff4b3] overlaps section .u_boot_list loaded at [00000000f8ffe778,00000000f8fff013] powerpc-linux-gnu-ld: u-boot: section .bootpg lma 0xf8fff000 adjusted to 0xf8fff014

These appear to simply be because my env changes make the u-boot build a bit too big. What are the memory areas on these 2 boards that can be used?

We put u-boot in the last 512k of memory...ish. Theoretically it can grow or shrink, but we hard-code the start to make it somewhat more comprehensible. I haven't had a chance to really look at this yet, but 512k is the simple answer (0xfff80000 - 0xffffffff)