??? 06/18/08 05:45 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#155990 - Explanation Responding to: ???'s previous message |
Amit Mittal said:
i can't understand why have you given this type of reply? Well, you gave a good description of how you could cause this message to appear, and how to make it go away again - and reading the message should made it obvious what was happening. Maybe this is just a problem with the message being in English, and English not being your native language? I have wondered about this before - so I'd be interested to know if it is, indeed, the case. Obviously, the first step in resolving any error or warning has to be to understand what the message is actually telling you. So, let's look at it ste-by step: Amit Mittal said:
whenever i increase the size of any array and try to build the target (KEIL UV2), following message is displayed: ****ERROR 107: ADDRESS SPACE OVERFLOW SPACE: DATA The message is telling you about an "overflow" - so, clearly, the first thing to understand is what does the word "overflow" mean? Well, "overflow" is what happens when you try to put more stuff into a place than it can hold. Clearly, there are two possible ways to overcome this: but this message is not displayed, if the arrays are limited to smaller size So, you reduce the amount of stuff, and the message goes away - that should be entirely as expected. The next question is, then, what is overflowing? Again, the message tells you this explicitly: ****ERROR 107: ADDRESS SPACE OVERFLOW SPACE: DATAIt's telling you that an ADDRESS SPACE is overflowing, and it specifically identifies that the particular address space is DATA In other words, you are trying to fit more stuff into the DATA space than the DATA space can hold. The size of the DATA space is fixed by the chip (in fact, by the 8051 architecture) - so you can't change that. Therefore your only options are: Please note that this is exactly the process that you need to adopt when resovling any error or warning message from any tool: Look at the message, read it literally, and think about what it actually means |
Topic | Author | Date |
P89C51RD2BN MEMORY MODEL | 01/01/70 00:00 | |
look up the "code" keyword in the manual | 01/01/70 00:00 | |
look up the "xdata" keyword in the manual | 01/01/70 00:00 | |
the whole manual might be worth reading... ;-) | 01/01/70 00:00 | |
look up the word "overflow" in a dictionary | 01/01/70 00:00 | |
??????????????? | 01/01/70 00:00 | |
Explanation | 01/01/70 00:00 | |
about the size of data memory | 01/01/70 00:00 | |
Arrays | 01/01/70 00:00 | |
is this caused by the model? | 01/01/70 00:00 | |
Re: Little more information | 01/01/70 00:00 | |
Problem Solved | 01/01/70 00:00 | |
IDATA - beware | 01/01/70 00:00 | |
why not XDATA | 01/01/70 00:00 | |
external memory?????? | 01/01/70 00:00 | |
yes, you are | 01/01/70 00:00 | |
more confusing terminology...![]() | 01/01/70 00:00 |