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.

error: unresolved symbols remain

Other Parts Discussed in Thread: CONTROLSUITE

hello:

somebody can help me cancel this problem please?

  • Hi Kuo,

    normally this error is caused by a broken or missing or incorrect path to a library.  I have below posted a useful wiki on this topic.  Are you trying to work with an example?  Is this imported code?  If so how have you imported?  What exact CCS version do you use? 

    http://processors.wiki.ti.com/index.php/Include_paths_and_options

    Please keep us informed.

    Best Regards,

    Lisa

  • dear Lisa :

    my CCS Version is 5.2.0.00029. ( compiler version TI V6.1.0)

    I just imported  example project  of  HVPM_Sensorless.  I's can't Work.

    I'm sure the include  path and link path  was set  right  in my  CCS.

    I guess the LINKER is not compatible with the sample program.

    The New  ControlSuite  example code not  math in  CCS 5.2    ?? 

    Best Regards

    Dowsheng.

  • Hi Kuo,

    control suite examples are built into CCS in the resource explorer.  Have you tried importing it that way?  How did you import?  Did you have a look at the wiki and double check the include paths? 

    Best Regards,
    Lisa

  • dear Lisa:

    Please check my  files. Thanks 

    Best Regards

    Dowsheng.

  • Dowsheng,

    I just followed your same procedure for the same project (with the exception that when importing the project, I checked the box for "copy proejct into workspace". I was able to build without errors. Since you are getting a compiler error, are you sure that none of the files in the project (source files/header files) have been modified? You can check the dates on the files to confirm if any changes were made. Since you did not copy the project to workspace, it will keep all files in its original location and build it in its original location, so if any changes are made to the files in the HVPM_Sensorless folder, they will be used for successive builds.

    Also please make sure you are using the latest version of ControlSuite.

    If you have checked the above points, I would then also try using a new workspace, and this time copy the project into workspace during import and see if that makes a difference.

     

  • Hi Dowsheng,

    just wanted to check whether there was an update to your enquriy.  Were the tips able to get you past the issue?

    Best Regards,
    Lisa