• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 369 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F280049C: Compiler Output Format Linking Error

Ajay S
Expert 1280 points
Part Number: TMS320F280049C
Other Parts Discussed in Thread: C2000WARE

 I'm need to built program in EABI format. Because some #pragma attributes supports only in EABI.  However, I'm getting an unresolved symbol linking error for the F28x_usDelay, and I don't know what I'm missing here.

 I'm getting this error in bitfield library only, for driver library everything works fine. here i mentioned build errors for your references.

" unresolved symbol F28x_usDelay, first referenced in ./SRC/f28004x_sysctrl.obj
gmake[1]: *** [Motor_Drive.out] Error 1
gmake: *** [all] Error 2
<a href="file:/C:/ti/ccs1250/ccs/tools/compiler/dmed/HTML/10234.html">#10234-D</a> unresolved symbols remain
#10010 errors encountered during linking; "Motor_Drive.out" not built "

Best Regards,

Sathish P

  • 0
    TI__Mastermind 30185 points

    Hello Sathish,

    Are you using an example from C2000Ware or your own project? Have you verified that the proper file paths for header files and libraries are set up in the project properties? This error comes about when CCS is not able to find the function based on the included files and libraries within the project. For this reason, we typically recommend customers to use C2000Ware examples as the basis for their projects, so the basic required files are already set up to be used.

    Also, if you're building the project for an EABI format verify that any libraries you include are also built for EABI format. This mainly applies if you're using driverlib, but please double-check this.

  • 0 in reply to Omer Amir
    Expert 1280 points

    Hello omer,

      Yes, I'm using example project from c2000ware and all supporting files were included. This project build successfully in coff format. I get this error only in EABI format.

      I'm using c2000ware 5.03 version and i imported project from device_support examples. How do i verify that libraries are built for EABI format?

    Thanks,

    Sathish 

  • +1 in reply to Ajay S
    TI__Mastermind 30185 points

    If you're using the bitfield example(s), then the library issue may not apply. It seems that your problem is mainly isolated to the F28x_usDelay. What you can do is replace the .def _F28x_usDelay line with the following:

           ;.def _F28x_usDelay
       .asg F28x_usDelay, _F28x_usDelay
       .global _F28x_usDelay

    I tested this on an example from the device_support folder for F28004x and after modifying the linker command file for more space, the project built with only warnings. You can refer to this page for more info on how to address other migration changes.