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

INVALID ABSOLUTE BASE/OFFS VALUE

Hi,
I am using uvision version 8.16

I am getting
error A80: INVALID ABSOLUTE BASE/OFFS VALUE.
line at which it points out error is

"SEGMENT EDATA AT (07F0000h+RESERVED_START)"

My code was working fine few days ago but now it starts complaining about this error. I compared the address at address given in previously correctly working code {which is also giving same compilation error} and both are same.

As I mentioned my previously stable code also throws out this compilation error.

Any idea what could be the problem.

Thank You,

Regards,
Anshul

Parents
  • So, in summary:

    1. It was "stable"
    2. You made some change(s)
    3. Now you get this error.

    In the trade, we have a technical term for this: we say that you have broken your code!

    Clearly, you need to retrace your steps back to the stable version, then carefully examine the changes that you made to see which one caused it to break.

Reply
  • So, in summary:

    1. It was "stable"
    2. You made some change(s)
    3. Now you get this error.

    In the trade, we have a technical term for this: we say that you have broken your code!

    Clearly, you need to retrace your steps back to the stable version, then carefully examine the changes that you made to see which one caused it to break.

Children
  • Hi,

    No I meant,

    the code which I compiled and ran successfully is throwing compilation error now. {without any change}

    I didn't make any changes in address.

    In fact at my workplace we have two uvision licenses and same code successfully compiles and run on my teammates machine but I am getting this error.

    I haven't made any changes in addresses.

    Any idea what should I do?

    Thanks,

    Anshul

  • we work here with various varsions of Keil (some update religously, some do not) and there ARE differences between releases, they come in two groups:
    1) and most important We have found that some 'stable' code, produced an error when built with another release. This 'new' error proved that the 'stability' was an illusion and the problem was fixed and now the code builds with both releases.
    2) rarely have we found that there was an actual bug in the compiler which did not exist in another release (I recall one)

    My guess is that the error one release produces is significant, and, instead of crying wolf, find out what is wrong (I'll bet you dollars to doughnuts that your code, not the compiler/linker has a problem)

    Erik

  • Look carefully for the differences between his installation and yours.

    Are you using exactly the same project files?