• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 21 subscribers
  • Views 1079 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

INVALID ABSOLUTE BASE/OFFS VALUE

Anshul Data

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
  • 0 in reply to Anshul Data

    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

Reply
  • 0 in reply to Anshul Data

    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

Children
No data