SPARC linker command files
sebastian.huber at embedded-brains.de
Tue Dec 3 10:29:40 UTC 2013
On 2013-12-03 10:13, Jiri Gaisler wrote:
> On 12/03/2013 08:46 AM, Sebastian Huber wrote:
>> >On 2013-12-02 23:06, Jiri Gaisler wrote:
>>> >>On 11/30/2013 02:31 AM, Gedare Bloom 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 boot loader (or gdb debug monitor) supplies the top-of-stack
>>> >>address in %sp when the RTEMS binary is called. The area between
>>> >>the start address and %sp indicates the size of RAM to be used.
>>> >>In this way only one bsp is needed.
>> >Ok, good to know. Then this symbols should probably go away. Is the boot loader always the same?
> The most common loader is generated by the mkprom2 PROM builder. The loader
> sets up system specific things like memory controllers, timers and UARTs.
> It the calls the RTEMS (or other eg. linux) binary with the top-of-RAM
> in %sp.
> The simulator (TSIM) and grmon debug monitor does the same thing as
> the loader before launching the binary.
The startup code also assumes a valid stack pointer for CPU0. So what is the
purpose of the global symbols? Why not use the boot loader provided values we
already rely on?
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.
More information about the devel