• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 3152 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

Aduc702x.s Compiling error

Nicky Peh
Note: This was originally posted on 14th March 2011 at http://forums.arm.com

: Error: L6218E: Undefined symbol DAbt_Handler (referred from aduc702x.o)
Can somebody help with this kind of error? How to resolve it? The thing is i didnt call "aduc702x.o" extension file. Does it relate to somewhere else?
PS: There is no error upon the compilation of my coding.
  • Note: This was originally posted on 15th March 2011 at http://forums.arm.com

    Thanks for the information.
    Regarding to the sources. This Dabt_Handler is coming from the initializations from the aduc702x.s

    Here is the codes inside the aduc702x.s :
    EXTERN Undef_Handler
    EXTERN SWI_Handler
    EXTERN PAbt_Handler
    EXTERN DAbt_Handler

    Then the error after compiling error is this:
    Error: L6218E: Undefined symbol DAbt_Handler (referred from aduc702x.o).
    : Error: L6218E: Undefined symbol PAbt_Handler (referred from aduc702x.o).
    Error: L6218E: Undefined symbol SWI_Handler (referred from aduc702x.o).
    Error: L6218E: Undefined symbol Undef_Handler (referred from aduc702x.o).
    The header and the .c files of mine are all free of error which means theoretically i can compile the program but due to this i dont really know what is happenning. The aduc702x.s is generated when a new project is created and based on the target device it will configure a initialization file. Hence the Dabt_Handler is an exception of vector inside the coding explained from the comments.

    Don't really know the meaning of the vectors? Can please help to elaborate or just to explain what is the use of Dabt_Handler in the initialization coding?

    Thanks a lot for sharing. Looking forward to get the reply.
  • Arm Employee Badge
    Note: This was originally posted on 14th March 2011 at http://forums.arm.com

    aduc702x.o is an object file, most likely generated from aduc702x.c or aduc702x.s.  If this is one of your source files then it is being passed directly to the linker.  If not, then it comes from one of the libraries your project is using.  (A library is basically just a packaged bundle of .o files).

    This object is referencing a label called "DAbt_Handler", which none of the objects or libraries in your project define.

    So the first step is to work out where aduc702x.o comes from.  Is it one of your sources or from a library.  If a library, then check with however provided the library.
  • Arm Employee Badge
    Note: This was originally posted on 21st March 2011 at http://forums.arm.com

    These are linker errors.


    You have a set of labels which point to exception handling routines  - so they will typically be functions - which the linker cannot find when linking your program. I'd guess that [color=#222222][font=Arial, Verdana, Tahoma, sans-serif]aduc702x.s defines the vector table, and calls external functions which implement each of the exception handlers. Y[/font][/color][size=2][color=#222222][font=Arial, Verdana, Tahoma, sans-serif]ou should have a set of functions defined somewhere with the name of each of the labels (e.g., [/font][/color][color=#222222][font=Arial, Verdana, Tahoma, sans-serif]Undef_Handler); these need to be compiled and passed in as one of the objects when linking aduc702x.o.[/font][/color][/size]
    [size=2][color=#222222][font=Arial, Verdana, Tahoma, sans-serif]
    [/font][/color][/size]
    [size=2][color=#222222][font=Arial, Verdana, Tahoma, sans-serif]Iso[/font][/color][/size]