• Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 474 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.

New install CCS 5.3 & CtlSuite 3.1.3, ePWM Timer Ex.prj. build errors

BadMonkey
Expert 2090 points

Other Parts Discussed in Thread: CONTROLSUITE

I recently installed CCS Version: 5.3.0.00090 and install ControlSUITE 3.1.3 today. I am running Windows 7 64-bit, i5, 2.6GHz,8GB RAM.

I copied the Delfino F2833x, "ePWM Timer Interrupt" "Example Project" from CSuite (using the built-in copy utility) to a folder on my desktop. Then I imported it with CCS5.3 selecting to copy to

the workspace folder as part of the import. The workspace folder is: C:\tiwkspc_PwmEx. CCS and CSuite were all installed into their default directories. This PC had a version of CCS 4.x that was

removed before the installation of 5.3.

I am getting buid errors for this demo project.

One of the errors is "Could not open source" for the following line:
#include "DSP28x_Project.h"     // Device Headerfile and Examples Include File

I am able to fix that by adding the path:
C:\ti\controlSUITE\device_support\f2833x\v133\DSP2833x_common\include
to the project. But, I thought the idea for the examples was that everything would be ready to go.

There are 12 errors for "gmake: No rule to make target" Oddly though the path shown for these errors is rooted in my Windows "User" path although I never configured anything as such as far as I know. Perhaps left over from CCS4.x? I avoid "User" paths for in general, for development, because they are not consistent from PC to PC with different logins.


I have 5 warnings for "Invalid project path" 2 of those are again rooted in the "User" directory.

I looked in the CSuite under Devices->Delfino F2833x->Utilities->Header Files for F2833x. The header file "DSP28x_Project.h" is not there but others are. However, there is no installer or README

that tells me what the TI default path for these should be. So, I don't know where to put them. I found them in the directory:
C:\ti\controlSUITE\device_support\f2833x\v132\DSP2833x_common\include

I did find "DSP28x_Project.h" for the 2833x in these 2 directories:
C:\ti\controlSUITE\device_support\f2833x\v132\DSP2833x_common\include
C:\ti\controlSUITE\device_support\f2833x\v133\DSP2833x_common\include

However, my board is revision 1.0 but these directories indicate 1.32 & 1.33, so I am not sure they are compatible.

Additionally, I cannot open the file:
controlSUITE_DSP2833x_HeaderFiles_Quickstart_Readme.pdf.

I thought the main idea for the "Example Projects" was that they would be "canned" and ready to run for rudimentary testing & learning. Have I missed something? Did I not install something?

I have attached screen shots. The forum would only let me attach one file so I put the screenshots in a zip file.

Any help will be appreciated.

Regards,
Jim Cook

Example Prj screen shots.zip
  • TI__Guru*** 130875 points

    Hi Jim,

    I agree better documentation would be appropriate and helpful.

    Here are some comments/tips

    1 - it may or may not be the best idea to copy and example and start that way.   Typically I would recommend two steps for users gaining familiarity with the tools/examples.   The first to import and example direct from the ControlSuite installation.   You can do this through the resource explorer or project->import existing ccs/eclipse project.   The next step is to create a new project of your own and add dependencies on the controlSuite libraries used as per these wikis

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

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

    2- if you are using the default workspace path when CCS launches, this is likely where the user references are coming from.  ALso note the desktop has this.  This means these need to be part of the paths used in the project as it is where your project is and hence the user in the path.

    3 - It is fortunate or not, known that typically the include paths and variables need to be checked/correct for imported projects

    4 - you may want to consider adding a path/build variable to you control suite directory

    5 - the version numbers you refer to I believe are software versions, and there should be no need to match those to your hardware revision

    Hope this helps and please keep us informed.

    Best Regards,

    Lisa

  • in reply to Lisa TI
    Expert 2090 points

    Hi Lisa,

    I had already read this wiki page before my post; That is how I knew to fix one of the errors by adding a path:

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

    ---------------------------------------------------------------------------------------------------------------

    >> 1 - it may or may not be the best idea to copy and example and start that way.

    I can answer that question for you.

    It is definitely NOT best to copy the project. I deleted my project and just did an "in-place" import of the project and it compiled and ran. The path errors were due to the project being relocated.

    This lends credence to my inclination that the Examples should be canned projects that are simple and ready for experimentation and learning.

    ---------------------------------------------------------------------------------------------------------------
    >>3 - It is fortunate or not, known that typically the include paths and variables need to be checked/correct for imported projects

    I can answer that question for you.

    It is NOT fortunate. Luckily however, if the projects are imported in place, all of the paths work as expected.

    Again, this lends credence to my inclination that the Examples should be canned projects that are simple and ready for experimentation and learning.

    ---------------------------------------------------------------------------------------------------------------
    The main reason that I went the route of copying the Example Projects was that I did not want to edit or otherwise alter the virgin installation. That is, editing, experimenting, etc. It turns out that these questions are answered in the "controlSUITE_DSP2833x_HeaderFiles_Quickstart_Readme.pdf". However, because I had copied the project to a new location, using the CtlSt copy project option, the link to the "controlSUITE_DSP2833x_HeaderFiles_Quickstart_Readme.pdf" was broken (which I had mentioned). In this document, v1.31, pg.7, it states "Do NOT check the box to copy projects into the workspace. The projects will NOT work properly if this box is checked." Well, that solves the non-working projects mystery. As far as preserving the virgin installation, that is addressed in said document on pg.12, section 9, where it states, "If you wish to modify the examples...create a backup of the original files first".

    ---------------------------------------------------------------------------------------------------------------
    >>5 - the version numbers you refer to I believe are software versions, and there should be no need to match those to your hardware revision

    You are correct. This was also addressed in said document, on page 3, section 1.1, titled "Revision History." That title is appropriate ;-)

    ---------------------------------------------------------------------------------------------------------------
    So, my questions were answered in the document "controlSUITE_DSP2833x_HeaderFiles_Quickstart_Readme.pdf". It was just a Catch-22 because the file shows up as a link inside the project (an included file) but because I had copied the project, the link to the file was broken. But, I did stumble across it an now things are working.

    Regards,
    Jim