• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 3226 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.

Imported example project with broken links, wrong paths

Don McCune
Intellectual 385 points

Other Parts Discussed in Thread: CONTROLSUITE

When I import the Blinky project from controlSUITE, the file links are broken.  Any attempt to build results in several "No rules for " errors.

I am attempting to run my first simple example program on my new controlCard F28m35H52C1.  I import the blinky project from C:\TI\controlSUITE\device_support\f28m35x\v110\F28M35x_examples_Control.  I am using CCS 5.1 installed in C:\TI\ccs5.

I import the project but do not copy it to the workspace.  The immediate problem is that none of the file links are correct -- if I double click on any of the source files, it just displays an error.  I solved this problem by following a suggestion found elsewhere in this forum.  In the macro.ini file I found these two lines:

INSTALLROOT_F28M35X_V110 = ../../../../

INSTALLROOT_FPU_FASTRTS_V100 = ../../../../../../../libs/math/FPUfastRTS/V100

In CCS, I go to Window|Preferences|General|Workspace|Linked Resources.  I understand that these two entries in macro.ini should have been inserted into Linked Resources during the import, but I found the page blank.  So I added the two manually.  This restored the links to the source files (I forget if I needed to restart CCS or reload the project).

The next problem was the include files.  Under Includes in the Project Explorer, the include paths were abreviated and showed no files when you click the little error by each line.  I solved this problem by right clicking the project, selecting Build Options|Build|C2000 Compiler|Include Options.  Here I edited each of the include paths, changing the variable name in the ${} syntax to a hardcoded path in each instance.  This seemed to satisfy the includes.

However, there are still problems.  The generated make file has an abbreviated path where it is looking for "F28M35x_generic_C28_FLASH.cmd"  Since this make file is generated, it does no good to edit it to hard code the path.  If I knew how it is generated, I could change the path.  Can someone help with that?

But it seems like I am going to a lot of work to fix a single underlying problem.  Why are the paths messed up?  I have un-installed and re-installed controlSUITE, but it did not change anything.  Moving the project into the workspace during Import does not help.  The problem exists for all sample projects.

  • 0
    TI__Guru*** 130875 points

    Hi Don,

    please import the project selecting "copy project into workspace".  I just verified this works and give no build errors.  Please keep us informed.

    Best Regards,

    Lisa

  • 0 in reply to Lisa TI
    Intellectual 385 points

    Here is some detail of what happens when I try your suggestion:

    The last time I re-installed controlSuite, I made a back up copy of the original.  I deleted the existing files from C:\TI\controlSUITE\device_support\f28m35x\v110 and copied the original files into the folder.

    I started CCS5 and selected a new workspace that did not yet exist.

    File | Import | General | Existing Projects Into Workspace | Select root directory (check Copy projects into workspace) | Browse to C:\TI\controlSUITE\device_support\f28m35x\v110\F28M35x_examples_Control\blinky

    Would you like to convert to 4.0.0?  Yes

    blinky_c28[Active-Flash] is now in the Project Explorer along with Includes, Flash, multiple source files, and macros.ini

    Double click blinky_c28.c

    Could not open the editor: Must specify a URI scheme:INSTALLROOT_F28M35X_V110/F28M35x_examples_Control/blinky/c28/blinky_c28.c

    The same happens on all of the source files.

    Problems window:
    Three warnings:
    Invalid project path: Include path not found (\F28M35x_common\include).
    Invalid project path: Include path not found (\F28M35x_headers\include).
    Invalid project path: Include path not found (\include).

    Try to build:
    10 errors, 9 warnings
    Build variable 'INSTALLROOT_F28M35X_V110' cannot be resolved.
    Build variable 'INSTALLROOT_F28M35X_V110' cannot be resolved.
    Build variable 'INSTALLROOT_FPU_FASTRTS_V100' cannot be resolved.
    This project contains unresolved buildable linked resources. It might not build as expected.

    Check various settings:

    Windows | Preferences | General | Workspace | linked Resources was empty.

    Macros.ini
    INSTALLROOT_F28M35X_V110 = ../../../../
    INSTALLROOT_FPU_FASTRTS_V100 = ../../../../../../../libs/math/FPUfastRTS/V100

    Right Click project blinky_28|Properties|Build|C2000 Compiler|Include Options
    "${CG_TOOL_ROOT}/include"
    "${INSTALLROOT_F28M35X_V110}/F28M35x_common/include"
    "${INSTALLROOT_F28M35X_V110}/F28M35x_headers/include"
    "${INSTALLROOT_FPU_FASTRTS_V100}/include"

    Right Click project blinky_28|Properties|Build|Build Variables (check Show System Variables) shows many entries, including
    PROJECT_ROOT Directory C:/Projects/Sandbox5_workspace_v5_1/blinky_c28

    I believe that this works on your system, but how do I make it work on mine?  Re-installing controlSUITE did not help.  Re-installing CCS5.1 did not help.  I am guessing that the error "Build variable 'INSTALLROOT_F28M35X_V110' cannot be resolved." is a key to the problem, but even after I hand enter it in Windows | Preferences | General | Workspace | linked Resources and re-import the project, it does not resolve all of the problems.

     

  • 0 in reply to Don McCune
    TI__Guru*** 130875 points

    Hi Don,

    odd, but I am wondering whether the manual suffling of the control suite files may be breaking a path or link somewhere. 

    I was able to browse to an example and import it no problem.  Can you confirm you imported it as a CCS Project?   You need "Import Existing CCS/Eclipse Project" rather than a generic import.

    Did you select to automatically import referenced projects?  I my case this did not bring in any further projects so should not be necessary.

    Please keep me informed on the above.

    Best Regards,

    LIsa

  • 0 in reply to Don McCune
    Intellectual 385 points

    The problem was in the way that I imported the project.  Instead of

    File | Import | General | Existing Projects Into Workspace | Select root directory (check Copy projects into workspace) | Browse

    I needed to use

    File | Import | Code Composer Studio | Existing CCS/CCE Eclipse Projects | Select search directory (check Copy projects into workspace) | Browse etc. 

    When I import that way, everything works as I would expect.

    Now I just have to figure out why it is not turning the led on and off.

  • 0 in reply to Don McCune
    TI__Guru*** 130875 points

    Hi Don,

    glad that worked.  All the best with development.

    Best Regards,
    Lisa