RTEMS stack + TSIM-LEON2 weird behaviour

[Aitor.Viana.Sanchez at esa.int]

This comment just remind me that this should be like Jiri say, also to 
clearly separate the bootstrap code from the application code.

thanks a lot

Aitor


> The SPARC BSP start-up is discussed in this Wiki article:

> http://www.rtems.com/wiki/index.php/SparcBSPStartup

> In particulary, see the first paragraph:

> "The SPARC port of RTEMS generates binaries that do not perform any 
> board initialisation, and that
> are linked to the beginning of the RAM. The idea behind this is to 
> avoid having a separate bsp for
> every possible board around. Instead, a boot-prom builder (mkprom) 
> is used to create a
> self-extracting prom image that initialises all board registers, 
> loads the application to ram, and
> the starts it. The parameters to mkprom defines memory sizes, 
> waitstates, frequency, stack pointer
> and so on."

> When running a RAM image in TSIM, the simulator will recognize that 
> no initialization
> has been done, and automatically set the stack pointer, %psr and 
> some other registers
> to sane values. I do not see any reason why this should be changed. 
> If you want a bsp
> that does the initialization and start-up, I suggest that you create
> a new bsp rather
> that modify the existing one. However, note that a SPARC V8 
> processor starts at address
> 0 (in PROM), so you will need to load some code in PROM as well to 
> be able to jump to
> the RAM image.

> Jiri.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20080506/a92f9e97/attachment.html>