• State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 22 subscribers
  • Views 4356 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

When I compile Make a mistake Seek to answer THX!

Jia Zong

Because when compiling. The following information appears...
MAIN.C(1351): error C249: 'DATA': SEGMENT TOO LARGE
Change the small:variables in DATA into the Large:variables in XDATA.
While compiling again. The following information will appear....
Could you tell me what kind of situation it is.
How to solve？？ Help to answer it. THX！

*** ERROR L102: EXTERNAL ATTRIBUTE MISMATCH
SYMBOL: DDS_DATA_TEMP
MODULE: tranCode.obj (TRANCODE)

*** ERROR L102: EXTERNAL ATTRIBUTE MISMATCH
SYMBOL: DDS_DATA
MODULE: DDS_value.obj (DDS_value)

*** ERROR L102: EXTERNAL ATTRIBUTE MISMATCH
SYMBOL: LATCH_COUNTERvalue
MODULE: Counter.obj (COUNTER)

*** WARNING L16: UNCALLED SEGMENT, IGNORED FOR OVERLAY PROCESS
SEGMENT: ?PR?ONUSBSUSPEND?MAIN

*** WARNING L16: UNCALLED SEGMENT, IGNORED FOR OVERLAY PROCESS
SEGMENT: ?PR?MAIN1?MAIN

*** WARNING L16: UNCALLED SEGMENT, IGNORED FOR OVERLAY PROCESS
SEGMENT: ?PR?_TRANSMITDATAEPX?UPSD_USB

*** WARNING L1: UNRESOLVED EXTERNAL SYMBOL
SYMBOL: TIMEINT2
MODULE: initial.obj (INITIAL)

*** WARNING L1: UNRESOLVED EXTERNAL SYMBOL
SYMBOL: SAVEANDRECALL
MODULE: initial.obj (INITIAL)

*** WARNING L2: REFERENCE MADE TO UNRESOLVED EXTERNAL
BL51 BANKED LINKER/LOCATER V5.12 09/07/2005 11:41:29 PAGE 161


SYMBOL: TIMEINT2
MODULE: initial.obj (INITIAL)
ADDRESS: 848AH
.
.
.
.
.
*** ERROR L118: REFERENCE MADE TO ERRONEOUS EXTERNAL
SYMBOL: LATCH_COUNTERvalue
MODULE: Counter.obj (COUNTER)
ADDRESS: B612H

*** WARNING L1: UNRESOLVED EXTERNAL SYMBOL
SYMBOL: CUSCL_value
MODULE: upsd_usb.obj (UPSD_USB)

*** WARNING L2: REFERENCE MADE TO UNRESOLVED EXTERNAL
SYMBOL: CUSCL_value
MODULE: upsd_usb.obj (UPSD_USB)
ADDRESS: B8E3H

Program Size: data=174.0 xdata=613 code=47389
LINK/LOCATE RUN COMPLETE. 11 WARNING(S), 131 ERROR(S)

Parents
  • 0 in reply to erik malund

    "I would - for general purposes - go as far as 'Once you've fixed the 1st error some, if not all, of the rest will probably also disappear'"

    Yes, that would be a very good generalisation.

    "If there is no clear picture of whether an error is/could be the result of a previous, do one at a time."

    Yes.

    In this particular case, it is obvious to me that there are 3 distinct "root" errors - so I would fix the 3 and then rebuild.
    As your method suggests, even with the above observation, I wouldn't bother trawling through all the other messages to try and spot any more unrelated ones - just fix the 3, then address any that are left.

    But, in general, "fix the first one first" stands.

Reply
  • 0 in reply to erik malund

    "I would - for general purposes - go as far as 'Once you've fixed the 1st error some, if not all, of the rest will probably also disappear'"

    Yes, that would be a very good generalisation.

    "If there is no clear picture of whether an error is/could be the result of a previous, do one at a time."

    Yes.

    In this particular case, it is obvious to me that there are 3 distinct "root" errors - so I would fix the 3 and then rebuild.
    As your method suggests, even with the above observation, I wouldn't bother trawling through all the other messages to try and spot any more unrelated ones - just fix the 3, then address any that are left.

    But, in general, "fix the first one first" stands.

Children