Can't compile after last pull

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

Dario Lombardo dario.lombardo at libero.it
Fri Feb 10 09:06:19 UTC 2012


I've tried this:

MEMORY
{
    /* compal-loaded binary: our text, initialized data */
    LRAM (rw) : ORIGIN = 0x00800000, LENGTH = 0x00015000
    /* compal-loaded binary: our unitialized data, stacks, heap */
    IRAM (rw) : ORIGIN = 0x00815000, LENGTH = 0x0000c000
}

but

  LD     board/compal_e88/rssi.compalram.elf
  OBJ    board/compal_e88/rssi.compalram.bin
  LD     board/compal_e86/rssi.compalram.elf
  OBJ    board/compal_e86/rssi.compalram.bin
  LD     board/compal_e86/rssi.highram.elf
arm-elf-ld: region LRAM is full (board/compal_e86/rssi.highram.elf section
.data)
arm-elf-ld: section .got [00820000 -> 00820013] overlaps section
.text.start [00820000 -> 0082006b]
make: *** [board/compal_e86/rssi.highram.elf] Error 1

I have the same behaviour also with other values of length/origin.
Any other suggestion?

On Thu, Feb 9, 2012 at 1:44 PM, Steve Markgraf <steve at steve-m.de> wrote:

> Hi,
>
> On 09.02.2012 07:41, User wrote:
>
> >> Anyone experiencing the same issue?
>
> It seems your toolchain produces a binary larger than 80 kBytes
> (0x14000), which is the current limit for compalram images.
>
> What we need is a setting in the Makefile to blacklist certain apps
> from being built for certain environments, but what you can do for now
> is increase the LRAM length and adjust the IRAM ORIGIN in firmware/board
> /compal/ram.lds.
>
> Regards,
> Steve
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20120210/5aee28ef/attachment.htm>


More information about the baseband-devel mailing list