it was me wohl started the thread "for what purpose is start.asm ?"
last friday and I guess now I have found a problem in start.asm which has caused the trouble i was in:
the stack apparently gets initialised before the call to _hw_initialise, but in the function hw_initialise the external RAM gets initialised, wherein the stack is located according to the linkerscripts.
If I call the _hw_initialise before this line:
then everything works fine with external RAM.
So: why is _hw_initialise called after this line at all ? Shouldn’t the hardware gets initialised first at all ?
And do I introduce any bug when calling _hw_initialise right upon
the overall entrypoint as I do now ?