Group Actions
Engagement
  • Author Author: jomoenginer
  • Date Created: Date Created
  • Views 765 views
  • Likes 6 likes
  • Comments 5 comments
Related
Recommended

Safe and Sound Wearables- Code Composer Studio Woes

jomoenginer

So, lately I have been running into a series of issues with Code Composer Studio and I thought I would share these with other folks in case the may be helpful.

 

1. After a recent TI Update, or rather Upbreak, when attempting to import a project through the TI Resource Explorer in CCS 7.0.0.x, the following error is seen:

 

Error importing project. Location cannot be resolved: "c:/ti/tirtos_msp43x_2_20_00_06resources/msp_exp432P401RLaunchpad/driverExamples/tiDriverExamples/emptyExamples/com_ti_rtsc_tirtosmsp430_example_100.projectspec"!

 

NOTE: The tirtos_msp43x and resources directories are collapsed and a '/' is used instead of '\' to separate the folders. This is on Windows

 

Issue logged with TI:

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/582313/2138715#2138715http://

 

At this time, there is no resolution for this in CCS 7.0.0.x and it is suggested to use the latest CCS, well at least as of 03202017, CCS 7.1.0.x.

http://processors.wiki.ti.com/index.php/Download_CCS#Download_the_latest_CCS

 

2. The other issue has been seen in CCS 6.x as well as 7.0.0.x where, at least in my case, if the .cfg file is left open in the Editor window when CCS is closed, once CCS is started again, the following error is seen:

 

Error Report

 

Sorry, I'm having problems creating this editor. An unexpected exception was thrown.

 

org.eclipse.rtsc.xdctools.INVALID_CODEGEN_LOCATION: Invalid codegen location "

 

In my case, if I close the file and then reopen it the issue goes away.

 

This issue has also been seen by others when just opening a .cfg file.

 

Issue filed with TI:

https://e2e.ti.com/support/embedded/tirtos/f/355/t/544313

 

3. Another issue was when I attempted to add C++ Style Classes to my project.  When I initially added a C++ Class, I ran into the following error:

 

"warning #10247-D: creating output section "HEAP_CACHE" without a SECTIONS"

 

To resolve this, I removed the 'iostream' and namespace entries in the file. Also, since I have both 'C' and 'CPP', I have found it is best to add the following in the header file:

#ifdef __cplusplus

extern "C" {

#endif

 

// Standard "C" code here

 

#ifdef __cplusplus

}

#endif

 

I found the following link to be helpful:

C++ Support in TI Compilers - Texas Instruments Wiki

 

Also, in TI-RTOS for MSP43x, there is an C++ example that shows an implementation of C++ in TI-RTOS.

This is located:

   TI-RTOS for MSP43x - v2.20.00.06

     Documents->Development Tools->MSP-EXP432P401R->Kernel Examples->C++ Example (bigtime)

 

Using this example, I set the following in the .cfg file:

     System (Hwi and Swi) stack size - 768

     Heap Size - 2048

     Enable Assets - False (Unchecked)

     Enable Logs - False (Unchecked)

 

4. One bright side, with the release of Code Compose Studio 7.x, the now provide the Full License for CCS 6.x.  This means no more limitations in CCS for time, code size, debug probe or target used.

    

     See the Licensing - CCSv6 Wiki for more info:

         http://processors.wiki.ti.com/index.php/Licensing_-_CCSv6

 

Hopefully this is helpful to someone.

  • in reply to DAB

    Yeah, the real pain is when attempting to add C++ into the mix especially when trying to use modules that were written in "C" like the Graphics libs since they use the standard variable types such as int8_t for strings rather than ints.  Out of the box, TI ARM Compiler used C89 so it's best to change this to C99. However, the C++ compiler only supports up to C03 thus does not support the standard types and will cause compiler errors. I ended up creating a new project but using the GNU C++ compiler which supports up to C11 with the added build option "-std=c++11". It still has issue, so I ended up putting the Graphic calls into a separate ".c" file and reference it from the ".cpp" files. I'm still trying to iron this out.

  • in reply to Jan Cumps

    Jan,

     

    The fun part is that with CCS 7.1 the download location for Resource Explorer changed from C:\ti\tirex-content to C:\ti so if you download a new package from Resource Explorer in CCS 7.0.0 it will install to C:\ti\tirex-content but when trying to import a project it will look under C:\ti.  This was supposed to be corrected in CCS7.1.  However, one thing to note is that if you update to CCS7.1 it will over write CCS7.0.0 and you will not have CCS 7.0.0 anymore.  I still have CCS 6.1 and 6.2 running for backward compatibility so I am not sure why CCS 7.1 over wrote CCS7.0.0.  Also, with CCS 7.1 you will only see 2 folders in Resource Explorer "Development Tools" and "Software". Also, if you install the latest SimpleLink packages outside of Resource Explorer, they will not show within Resource Explorer since they install at C:\ti\tirex-content.  Fun huh?

  • Good that you filed / updated the support issues.

     

    For #1, the ti\tirex-content; vs \ti change created issues when I was migrating from 6.X to 6.2 (the intro of the new Resource Explorer). Several projects (code examples from TI and other downloadable projects) that had their dependency path relative to $TI_HOME needed manual fixes for include and link settings. I've seen that this is now changed back to \ti - but I don't know yet what that means for me, now that I have all packages and RTOS versions in ti\tirex

  • Wasn't there was a song about that called "A total Eclipse of with your code."

  • Seeing someone else's pain is always useful to anyone considering the use of a product.

     

    One person's "intuitively obvious" is another person's "obtuse" software.

     

    DAB