• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 22 subscribers
  • Views 1403 views
  • Users 0 members are here
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

Address Space Overflow-89C52

Ranjith Nair

Hi,
I have a made a code for testing a hardware board.The code on compilation generates an error code of L107 Address space overflow.After searching through the KEIL forum I came to know that once you define XDATA for all variables (including global variables),this error can be avoided.How to define XDATA and where?Please mail me & thanks in advance.

Parents
  • 0 in reply to Ranjith Nair

    So you are doing trial-and-error development?

    You throw in some new keyword just to see if it makes a difference. When it does (the linker doesn't complain) then you start looking for next trial-and-error change.

    1 - are you sure that you need all your variables?
    2 - are you sure that you need to move all variables to XDATA?
    3 - are you sure that you do have actual memory for the XDATA variables?
    4 - are you sure that you have selected the "best" variables to move to XDATA, since access time and code size does differ?

Reply
  • 0 in reply to Ranjith Nair

    So you are doing trial-and-error development?

    You throw in some new keyword just to see if it makes a difference. When it does (the linker doesn't complain) then you start looking for next trial-and-error change.

    1 - are you sure that you need all your variables?
    2 - are you sure that you need to move all variables to XDATA?
    3 - are you sure that you do have actual memory for the XDATA variables?
    4 - are you sure that you have selected the "best" variables to move to XDATA, since access time and code size does differ?

Children
No data