• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 341 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.

unresolved symbol problems with C2000 piccolo launchpad

Mário Silva
Intellectual 340 points

Other Parts Discussed in Thread: CONTROLSUITE, CCSTUDIO

I am trying to build a project in C2000 piccolo launchpad, without success so far... 

I'm using ccs_v5.4 running under Debian Wheezy x64.

I'm getting errors like : "unresolved symbol _GPIO_init", "unresolved symbol _CLK_init" and "unresolved symbol _CPU_init".

Can anyone help me with a solution to this?

Thanks in advance,

Mário Silva

 

  • 0
    Guru 20525 points

    Hi, Mário.

    1) Perhaps you didn't add to your project the file F2802x_GlobalVariableDefs.c from:

    C:\ti\controlSUITE\development_kits\C2000_LaunchPad\f2802x_headers\source\.

    2) Also check please "Include options" of Project's Properties (Properties->Build->C2000 Compiler->Include options):

    C:\ti\controlSUITE\development_kits\C2000_LaunchPad\

    C:\ti\controlSUITE\development_kits\C2000_LaunchPad\f2802x_headers\include\

    C:\ti\controlSUITE\development_kits\C2000_LaunchPad\f2802x_common\include\

    Regards,

    Igor

  • 0 in reply to Igor Gorbachev
    Intellectual 340 points

    Hi Igor,

    thanks a lot for the answer. I think I'm facing some extra problems by using CCstudio with my  OS distribution, Debian Wheezy x64. Even the examples that comes with the installation for linux for this launchpad seems to be quite poor.

    Nevertheless, reading another posts I was able to solve this problem. It seems that I have to add a bunch of *.c files to my project like GPIO.c, CLK.c and other... Every include file *.h that I use in my project I must add manualy its *.c correspondent file.

    After solving this I came across another error, <<"Uint16" has already been declared in the current scope>>. I've found the answer on this post

    http://e2e.ti.com/support/embedded/tirtos/f/355/p/193381/691349.aspx

    do you have any idea why do I have to add that "xdc__strict" command to the compiler options in every project?

    Thanks in advance.

     

    Regards,

    Mário Silva

     

  • 0 in reply to Mário Silva
    Guru 20525 points

    Hi, Mário,

    Mário Silva said:

    do you have any idea why do I have to add that "xdc__strict" command to the compiler options in every project?


    the short explanation there is at this link http://processors.wiki.ti.com/index.php/SYS/BIOS_and_controlSUITE_ADC_Example#Warning:_.23303-D_typedef_name_has_already_been_declared_.28with_same_type.29

    Regards,

    Igor