• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 786 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Absolute placement of stack

Tamiryan Michael

Hello,
I'm using an LPC2478. Can you refer me to the place in the documentation of RealView where absolute location of the stack is demonstrated? I have found some references but they all require to re-implement "__user_initial_stackheap", something I don't want to do. All I want is to place my stack in a predefined, arbitrary location. Can I even choose such a location? I could not find limits in the documentation...

Thanks in advance

  • 0

    I don't know anything about this, and not sure if the below link will be useful to you, but maybe it will help you.

    http://www.keil.com/support/man/docs/armlink/armlink_chdcgbjd.htm

    Using scatter-loading description files

    If you are using scatter-loading, the description file names all the execution regions in the image, and provides their load and execution addresses.

    If the description file defines both stack and heap, the linker also generates special stack and heap symbols.

    Example 4.1. Placing the stack and heap above the ZI region

  • 0 in reply to John Linq

    thanks for the link. a colleague of mine came up with a clever idea that solves both problems (sharing internal RAM by 2 binaries that run in parallel and data abort due to R13 accessing outside of its restricted internal memory region): both binaries can access all of the internal RAM but (here comes the trick) they define (and place using the scatter file) a large array in the memory region of the other binary so that all its RAM variables are mapped implicitly into a restricted zone. the other binary does the same, but "mirror imaged".