Importing the StellarisWare Driver Libraries - "Error loading Managed Make project information for project driver-libXXXX"

Hello Thomas,

What version of CCS are you using?  I just imported the driverlib project using CCS5.1 and did not see that message. 

If you are just wanting to run example code and develop your own projects you won't need to add this project as it is used to create a driverlib library.  All of the source files are provided with the Stellarisware download though and most example projects will provide the include paths to find those files when compiling when you do the import of the project.  When you create your own project you can use one of the existing examples as a starting point or you can direct the tools to point to the Stellarisware directories yourself.

Hope that helps.

Regards,

Craig

Hello Craig:

I'm using a licensed version of CCS 4.2.4.00033, but that really shouldn't matter, right? I've been using it for MSP430 development. This is the first time I'm using it for Stellaris development. I'm using the EKS-LM3S1968 evaluation kit as the source for project examples.

Also, I have further problems that look related to this. I have imported all the example projects for the kit, and I get the following message for each project. It appears everytime I start CCS.

"The Managed Make project file could not be read because fo the following error: Error loading Managed Make project information for project ProjectName. The tool definition used to create the project is not available. Managed Make functionality will not be available for this project."

Also, this other problem could be related. I can't debug the example "hello" project, nor any of the other example Stellaris projects. When I try to rebuild the active project, a dialog box appears for only a fraction of a second, so I can't read what it says. Perhaps the FTDI driver was not installed correctly. The driver only appears on the Ports Device Manager when I physically connect the board to the host computer; when disonnected, it disappears. I was wondering if the driver should appear also when there is no physical connection. Below is an image of the driver in the Ports Device Manager.

This additional information might also help. An image of the target configuration configuration for the projects is shown below. Would this configuration have anything to do with my problem.

Here is an image of the contents of the "hello" project. Perhaps this might give you some insight to the problem.

It seems that I don't have my tools configured properly to begin my work. Have you any advice?

Hello Thomas,

That version of CCS is able to support both families, but they can be selected during the install.  I installed ccs 4.2.4 and am able to import the projects and build them.  I am wondering if there was something to do with your install (were all devices selected when you installed ccs?).  Each family can be deselected.  Maybe upgrade to v5.1 since that is the latest and there are quite a few improvements.  During the install make sure all of the product families are selected.

As far as the drivers are concerned you should also see two more entries in Device manager.  They will show up in their own hierarchy as "Stellaris In-Circuit Debug Interface" and below that are the "Stellaris ICDI DFU Device" and the "Stellaris ICDI JTAG/SWD Interface."

Also, when you create the workspace and are adding projects try having CCS copy the project to the working directory.  You may have already done that, but it was not selected by default and in v5.1 it appears to be the default.

Hope this helps.

Regards,

Craig

Craig:

I hope you are still available for help, because I'm still stuck. I can now build the project, but I can't debug it. Can you  help, or do you suggest I look elsewhere?

By the way, none of the documentation for the EKS-LM3S1968 covers CCSv5, and the GUI has changed so many of the commands are no longer in the menus.

I have done the following.

1. Installed CCS v5.
2. Imported the driver libraries, driverlib-cm3 and driverlib-cm4. What is the difference here?
3. Built the example "Hello" project.
4. Re-installed the FTDI drivers.

The Device Manager has the following:

1. one port named "Stellaris Virtual COM Port(COM12)"
2. one USB controller named "Stellaris Evaluation Board A"
3. one USB controller named "Stellaris Evaluation Board B"
4. one USB "Texas Instruments XDS560 PCI JTAG Emulator' that in inoperative because it will not start.

The Device Manager has no entry for "Stellaris In-Circuit Debug Interface."

Hello Thomas,

Sorry for the delay.  Sounds like you have been making progress in getting the tools to build the project.  What error messages are you receiving from the tools?  Your settings sound like they are correct (the driver designations I provided earlier are for the newer debug).

Regards,

Craig

Hello Thomas,

One other thing...right click the Hello project and go to Build Configurations -> Set Active and make sure Debug is selected.  Also, make sure the optimizations are set to 0 so that you can debug effectively.

Regards,

Craig