• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 199 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.

TMS320F28379D: CLB Projects Won't Build

Ed Sanders
Genius 4085 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Greetings,

We are migrating to Windows 11, and I have been able to rebuild my C:\ti folder to the point where most of the projects build.  The exception is the CLB projects.  The output says that it cannot see "c2000ware_software_package v2.0.0.02".  But I can see it in the C:\ti folder as shown below (the first item was an error, and the rest are warnings).  It was installed using the installer.  What else do I need to do to have the tools see it?

Description    Resource    Path    Location    Type
Product c2000ware_software_package v2.0.0.02 is not currently installed and no compatible version is available. Please install this product or a compatible version.    <ProjectName>        <ProjectName>    Problem
Invalid project path: Include path not found (\device_support\f2837xd\common\include).    <ProjectName>        pathentry    Path Entry Problem
Invalid project path: Include path not found (\driverlib\f2837xd\driverlib).    <ProjectName>        pathentry    Path Entry Problem
Invalid project path: Include path not found (\utilities\clb_tool\clb_syscfg\systemc\include).    <ProjectName>        pathentry    Path Entry Problem

Thank you,

Ed

  • 0
    TI__Mastermind 28220 points

    Hi Ed,

    Are you actually using C2000Ware 2? This is an extremely old C2000Ware version. If you are upgrading to windows 11 I would suggest upgrading to the latest C2000Ware version as well.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Genius 4085 points

    Hi Luke,

    How do I know which C2000Ware we are using?

    Thank you,

    Ed

  • 0 in reply to Ed Sanders
    TI__Mastermind 28220 points

    You should be able to see this in your project properties. Are you trying to build a single project, a selection of projects or ALL projects in  your workspace? I'm not sure what you mean when you say you're trying to build your C:/ti folder.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Genius 4085 points

                    Ahhh…  I hadn’t looked at the Products tab.  I can see it now.  It is calling for “C2000Ware [2.0.0.02 -> 3.2.0.00]”.  This must be the version we used many years ago when I first started using the CLB.  Since then, I have developed several projects using the CLB, the most recent being just a few months ago.  The original tools have always worked well, so I haven’t felt a need to change them.

                    At any rate, as shown above, the tools seem to be in the C:\ti folder, so I’m thinking there must be some other setting I’m missing which allows CCS to see them during a build.

                    Towards the building of the C:ti folder…  Instead of “rebuild”, I should have said “recreate”.  I had originally copied my C:\ti folder from my Windows 10 computer to my Windows 11 computer.  That was only partially successful.  So I have been trying to recreate it by going through the installation process.  Most of our projects now build.  The projects which don’t build are all CLB projects, and they all fail in the same way.

    Thank you,

    Ed

  • 0 in reply to Ed Sanders
    TI__Mastermind 28220 points

    Hi Ed,

    Are you able to modify the products tab C2000Ware selection so that it selects 2.0.0.02 instead of pointing to 3.2.0.00?

    You may need to download the installer again for C2000Ware instead of doing a raw copy and paste.

    Are you using the same CCS version as before?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Genius 4085 points

    Hi Luke,

    I was able to figure out how to do change the version it is going to use, and have verified that the resulting output has not changed in any manner which would affect the projects which use those CLBs.

    But I still don't understand why it can't see the older one.  I'm wondering if I might have done something wrong during the installation.

    Thank you,

    Ed

  • 0 in reply to Ed Sanders
    TI__Mastermind 28220 points

    Hi Ed,

    I have not seen this issue before so I cannot provide much insight on this, I have only worked with C2000Ware versions 4.x and later. Hopefully it is acceptable for you to use the newer versions of C2000Ware as they are intended to be backwards compatible with previous versions.

    Thank you,

    Luke