SPARC linker command files

[Sebastian Huber]

On 2013-11-30 02:44, Joel Sherrill wrote:
> -DXXX on the linker command line overrides the defaults

The problem with this approach is that the linker has no ability to detect 
region overflows.

>
> On Nov 29, 2013 7:30 PM, Gedare Bloom <gedare at rtems.org> wrote:
> Does the NGMP allow for variant sizes of ROM and RAM? If so will we
> provide separate BSP variants for all possibilities, or how does the
> user select the right size for their board?

The user has to provide an application specific linker command file, e.g.

LDFLAGS += -qnolinkcmds -T linkcmds.app

linkcmds.app:

MEMORY {
   ram : ORIGIN = 0x00000000, LENGTH = 12345678M
}

INCLUDE linkcmds.base


>
> On Fri, Nov 29, 2013 at 8:20 AM, Sebastian Huber
> <sebastian.huber at embedded-brains.de> wrote:
>  > Hello,
>  >
>  > most SPARC BSPs use current the following linker provided symbols to specify
>  > the memory layout:
>  >
>  > _PROM_SIZE = DEFINED (_PROM_SIZE) ? _PROM_SIZE : 2M;
>  > _PROM_START = DEFINED (_PROM_START) ? _PROM_START : 0x00000000;
>  >
>  > _RAM_SIZE = DEFINED (_RAM_SIZE) ? _RAM_SIZE : 4M;
>  > _RAM_START = DEFINED (_RAM_START) ? _RAM_START : 0x40000000;
>  >
>  > So it is possible to define them as command line parameters.  There are two
>  > problems with this approach.


-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.