Get Started with the New Code Composer Essentials Version 3!

Reply

Brandon Posted: 16 May 2008 3:47 PM

rated by 0 users

Hello Everyone! Below is a step-by-step process on how to create a new project with CCE. Please feel free to post any questions for this process.

1. Open Code Composer Essentials.  Under the “File” menu, choose New -> Managed Make C/ASM Project.

2. Then, when prompted, please name your project. Please be careful to use different names for different projects as one workspace is shared for all CCE projects. After naming click “Next.”

3. (Should be correct as default) Please make sure that the Project Type is set to “MSP430 Executable” and that both Debug and Release configurations are checked.

4. (Should be correct as default) Please make sure no C/C++ Projects are referenced under the Projects tab. The C/C++ Indexer tab should reflect “Full C/C++ Indexer (slow but accurate)” as the indexers available. Once this is verified click “Next.”

 5. On the Device Selection Page, please choose the appropriate MSP430 under “Device Variant.” Once chosen the correct Linker Command File should automatically appear. If you are planning on making an assembly-code project, please check the box “Configure as an assembly only project.”  If you are going to program in C/C++ leave this box unchecked. Click “Finish.”

6.   Now the project should appear at the left-hand side of the application under the C/C++ Projects tab. Right-click on your project and choose “Properties.”

7. (Should be correct as default - if USB) Please choose the TI Debug Settings category and choose the Setup tab. Pick the appropriate connection using the drop-down box as shown below.

Note: The JTAG protocol should be configured automatically, so only the connection needs to be specified.

 Click “OK” once these changes are made.

 8. Now we are ready to add our code (of file type “.c” or “.asm”) to our project. Right-click on your project once more and choose “Add files to project.” Note: CCE V3 has default settings that are compatible with IAR syntax. To use the Version 2 CCE syntax please follow the steps located in section 2.1.3 in SLAU157: http://www.ti.com/litv/pdf/slau157f

9. Once this file is added, double click on it under the project tree to view the code in the main window of the C/C++ perspective.  When you are ready to load your code onto the MSP430, choose “Debug Active Project” under the “Run” menu. Alternatively you can choose the Debug Active Project button at the upper-left side of the screen, as shown below.

10. Once your code successfully builds and loads onto your device, Code Composer will change the view to the debug perspective. At this point the code is completely loaded onto your device and is ready to run. To run this code, press F8 or choose run under the “Run” menu. Alternatively you can click the run button on the upper-left side of the screen as shown below.

Further Reading:

CCE FET User’s Guide: http://www.ti.com/litv/pdf/slau157g

Reply

Chakra replied on 2 Jun 2008 6:21 AM

rated by 0 users

I have developed a project using CCE 2.0,now I am trying to run that
project in CCE 3.0 and I am getting the following error.

------------ --------- --------- --------- --------- --------- -
The Managed Make project file could not be read because of the
following error:
project type com.ti.ccsstudio. managebuild. ui.programTarget ID not found

Managed Make functionality will not be available for this project.
------------ --------- --------- --------- --------- --------- -

Can you please help me to sovle this error.

Thankyou........... 

Reply

Brandon replied on 3 Jun 2008 3:56 PM

rated by 0 users

Chakra,

What files are you importing into V3? I am not 100% sure how you are porting over your project files, but the best recommendation I have is to take only the source files (not the whole project, just the .c or .asm files) and create a new project per those above steps.

If you do this do you see the same error? If so, when do you see this error? Is it at compile time, link time, or at debug time?

Also useful is SLAU157. Section 2.1.3 on page 17 discusses how to import a CCE V2 project. This is another way to attack this problem: http://focus.ti.com/lit/ug/slau157f/slau157f.pdf

~Brandon

Reply

Chakra replied on 4 Jun 2008 9:02 PM

rated by 0 users

 Thankyou for the kind reply,I imported only the source file (.c file) and made some modification in .h header file according to the details provided in SLAU157  (2.1.3 Using an Existing CCE 2.x Project).

The problem was solved and I could debug the project (created in CCE 2.0) in CCE3.0.

Thankyou once again........ 

Reply

Chakra replied on 23 Jun 2008 4:51 AM

rated by 0 users

Hi,

Where do I change the JTAG protocol(4 Wire JATG/Spi-Bi- Wire) in CCE 3.0.
In CCE 2.0 there was an option in Debug Properties.

Thankyou....

Reply

Brandon replied on 23 Jun 2008 9:28 AM

rated by 0 users

Chakra,

You actually do not need to specify the JTAG protocol as the tool will automatically detect which you are using. This can be shown in a simple test in which you make a project with one protocol (say, blink the LED) then disconnect and try the other protocol.

Reply

Mischa Jovic replied on 23 Jun 2008 1:42 PM

rated by 0 users

 When I get to the New Project section, I have no options to pick a Device Variant. The drop down menu is completely void of options. Any idea why this is?

Reply

Brandon replied on 23 Jun 2008 1:57 PM

rated by 0 users

This error could be related to the tool not being referenced to its proper source files. This can be due to an incomplete or corrupt installation. I recommend that you uninstall and reinstall to a slightly different directory. This way none of your corrupt settings have a chance at "reappearing".

Reply

Chakra replied on 23 Jun 2008 8:12 PM

rated by 0 users

Brandon,

Thankyou for the reply,where do I find the details about this?

Regards.... 

Reply

Mischa Jovic replied on 24 Jun 2008 10:51 AM

rated by 0 users

 Interesting. Well, I'll have to try that. I was very tempted to scrap CCE and go with the IAR IDE till I saw this post. I'll have to give it another try. Free up to 16KB is tempting.  

Reply

Al replied on 10 Jul 2008 11:38 AM

rated by 0 users

 at step 5 I get :

No Code Generation tools are currently installed for this project type. Please install Code Generation tools before creating a  ...

I cant select anthing.

I had Eclispe installed on my PC before installing CCE, could this be the problem. I did not find any uninstallers for eclipse and it was absent from the add/remove programs.

Reply

Brandon replied on 10 Jul 2008 12:04 PM

rated by 0 users

Al,

 Personally I have never seen this message before, but it is almost certainly due to an incomplete installation. Did you perform a custom install or typical? If possible I highly recommend that you uninstall Eclipse, delete any CCE directories, and reinstall the tool. It seems there can be some sort of conflict with the CCE installer that yields a partial installation. This should clear up your issue, but let me know if it does not. In the meantime I will flag this thread as feedback to the appropriate folks.

 Thanks.

Reply

Kai replied on 14 Jul 2008 11:14 PM

rated by 0 users

Did anyone had any weird problems before? Currently I tried entering an invalid function call (eg. gfdgfgdfg() ) and compile. Weird thing is there is no error with the compilation. Test with all the 4 rebuilds.

Did I forget activating something in the compiler flag?

Reply

Brandon replied on 15 Jul 2008 10:40 AM

rated by 0 users

Kai,

I would like to clarify that you are simply making a function call to a function that is not defined? 

I tested this. With the default Project Property settings I did receive an error for such an erroneous function call. There are many settings in the build options that can suppress error messages for errors and warnings. Because of this, I recommend the following to resolve this issue.

• In CCE, choose File -> Switch Workspace (and set a new workspace directory, different from your default workspace you were previously using). Then create a new project (something simple, like flashing the LED). See this link: http://focus.ti.com/mcu/docs/mcuflashtools.tsp?sectionId=95&tabId=1538&familyId=342
• Compile and run the example as-is. Verify that the project is built, loads, and runs properly.
• Return the the example code and add an erroneous function call, then rebuild all. This should produce a link error, since the function is not defined.

If you DO recieve the error at that point, then something changed in your other workspace's build settings. If you still receive the error, there is more to explore. It is helpful to search the help documentation, which explains many of these settings, however I advise against suppressing the error or warning messages in any capacity as you are simply removing information that will be important to your project.

Reply

Al replied on 15 Jul 2008 3:33 PM

rated by 0 users

Hi Brandon,

I am porting a project written in C and some asm sections from mspgcc to code composer. I added the -gcc extension support for my project but the assembly section dont link.

Here is two examples of an asm section I have to port:

__asm__ __volatile__("br %0"::"g" (gDownloaderPtrStruct_t.mainPtr));

Void_t __inline__ Wait(register Word2_t n){
  __asm__ __volatile__(
           "1: \n"
           " dec %[n] \n"
           "jne 1b \n"
           : [n] "+r"(n));
}

I am not  too familiar with asembly I cant find enought information in the manuals. The commands are not listed.

Do you have any advice

Thanks