• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 745 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.

Broken paths on Starterware example project

Walter Snafu
Genius 3450 points
Other Parts Discussed in Thread: OMAP-L138, OMAPL138, CCSTUDIO

I keep getting build errors due to broken paths, using the OMAP-L138 Starterware example USB device bulk project. 

I did the correct thing, that is, I imported the project into CCSv5 without copying the files. 

Also, I tried re-installing the Starterware several times (and also a complete re-install of CCS and all the packages).  I installed Starterware into the default location, that is, at C:\ti\OMAPL138_StarterWare_1_10_03_03

It always results in numerous broken path names, for the compiler, and for the linker. 

Here is what the compiler reports when I try to build. Notice the highlighted items have something missing.  For example, the first one on the list should read "C:/ti/OMAPL138_StarterWare_1_10_03_03/examples/....." The part highlighted in blue in missing from all the following paths. 

Description Resource Path Location Type

gmake: *** No rule to make target `C:/examples/evmOMAPL138/usb_dev_bulk/usb_bulk_structs.c', needed by `usb_bulk_structs.obj'. usb_dev_bulk_armv5_omapl138_evmOMAPL138  Unknown C/C++ Problem

gmake: *** No rule to make target `C:/examples/evmOMAPL138/usb_dev_bulk/usb_dev_bulk.c',  needed by `usb_dev_bulk.obj'.  usb_dev_bulk_armv5_omapl138_evmOMAPL138  Unknown C/C++ Problem

gmake: *** No rule to make target `C:/examples/evmOMAPL138/usb_dev_bulk/ustdlib.c',   needed by `ustdlib.obj'.  usb_dev_bulk_armv5_omapl138_evmOMAPL138  Unknown C/C++ Problem

Invalid project path: Include path not found (C:\grlib\include).  usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\usblib\include).  usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\ipclite\include).  usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\nandlib\include).  usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\include\armv5\omapl138). usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\include\armv5).  usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\include\hw).   usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\include).   usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\examples\evmOMAPL138\usb_dev_bulk).  usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

Invalid project path: Include path not found (C:\examples\evmOMAPL138\usb_dev_bulk).  usb_dev_bulk_armv5_omapl138_evmOMAPL138  pathentry Path Entry Problem

This project contains unresolved buildable linked resources. It might not build as expected. usb_dev_bulk_armv5_omapl138_evmOMAPL138  project Problems

  • 0
    TI__Prodigy 480 points

    Hello Walter,

    I suggest you to go through the Getting Started Guide once again to see any deviation from the procedure to import the CCS projects.

    Could you please let us know the following details?

    • CCS Version
    • ARM CGT version
    • Steps to import the CCS project.

    Alternatively, Could you try the following eclipse command for importing the project?

    "<CCS_Install_Directory>\ccsv5\eclipse\eclipsec.exe" -nosplash -data <Workspace> -application com.ti.ccstudio.apps.projectImport -ccs.location "<Starterware_Install_Directory>\build\armv5\cgt_ccs\omapl138\evmOMAPL138\usb_dev_bulk"

    Please let me know if this post answers your problem.

    Regards,

    Vinay

  • 0 in reply to Vinay Kumar42
    Genius 3450 points

    Something isn't making sense. 

    I went to the "Getting Started Guide version 2.00", and it referred me to a webpage for instructions on how to import.  That webpage shows a contradiction.  That is, the text (correctly) says to use the command,  "Code Composer Studio -> Existing CCS/CCE Eclipse Projects".  But the illustration indicates to use the "General -> Existing projects into Workplace" command -- which is the wrong command.  This is FYI.

    Anyway, I figured it out, and used the correct command.  And the project imported and built easily.  Great. 

    But for some reason it would not run correctly on the target.  I figured it must be caused by some junk left in my project folder from my previous attempts.  So I deleted the project from my project explorer window (without deleting the project contents on the disk). I then went to re-import the original project from the Starterware package.  But the import no longer worked.  (Ugh!)  So I uninstalled the Starterware package, and deleted the remaining Starterware leftovers from the disk, and re-installed it anew.  When I went to import the project, (using the same approach as the previous time that worked), this time it wouldn't import the project -- it couldn't even find the project.  I repeatedly browsed down into the correct Starterware directory, but CCS could not 'see' the project there. I tried it many times. 

    So I tried the Resource Explorer.  The Resource Explorer discovered all the projects, and listed them all, and I neatly selected the one I wanted (usb_dev_bulk), and it imported using the click-button on the resource explorer.  Then I built the project.  And this time the compiler gave a stream of errors, the same exact ones I listed in my opening post.  Lots of broken path names.

    As I said, something isn't making sense. 

    I'm using:  

    CCS Version: 5.4.0.00091

    ARM Compiler Tools 5.0.5 com.ti.cgt.tms470.5.0.win32.feature.group Texas Instruments

    GCC ARM Compiler Tools 4.7.2012.12 

    Thanks for your help.

    -- Walter

     

  • 0 in reply to Walter Snafu
    Genius 3450 points

    P.S.  I tried that command line you gave me (with the proper directories plugged in).  But I didn't know where to feed that command line.  The best I could figure was to feed it to the Scripting Console.  It came back with the following response: 

    missing ) after argument list


    P.P.S.  So I looked up how to run command lines on eclipse.  First I shut down CCS.  Then I use the DOS command line window in Windows7.  Then I change directory to the eclipse directory.  Then I give it the command line you gave me.  ...  And it worked.  It imported properly.  At least the include paths look correct.  And it compiled/linked/built without any complaining from the compiler. 

    Mysterious....

  • 0 in reply to Walter Snafu
    TI__Prodigy 480 points

    Hello Walter,

    Please do refer the Getting Started Guide for OMAPL138 starterware for details.
    http://processors.wiki.ti.com/index.php/StarterWare_Getting_Started_01.10.XX.XX

    I suggest you start with fresh workspace and starterware installation to avoid any confusion.

    Since you are using ARM CGT v 5.0.5, you will have issues with building the application.

    The issue is related to support of GCC variable attributes.

    To resolve this issue, enable GCC variable attribute support.

    1. Right click on project menu and select properties.
    2. Go to Build > TMS470 Compiler >Language Options.
    3. Check the box for Enable support for GCC Extensions (--gcc)

    You should be able to build the project with this modification.

    However, this modification should be applied to USB library project as well.

    You could import the project for usb library at:
    <Starterware_Install_directory>\build\armv5\cgt_ccs\omapl138\usblib

    Regards,
    Vinay