CRITICAL: Do NOT use Compiler 6.2.0 - 6.2.2

Update, we have found a project build incompatability in CCSv5.5 and a bug in compiler 6.2.x

We are fixing the project build issue in how we define our projects in the next release of MotorWare (early November _1_01_00_10 )

We are workign on a fix for the compiler, so for now please use 6.1.5

Hello Chris,

could you already give more details about the cause within MotorWare? We're thinking about a move from CCS5.2.1 to 5.5 and don't want to get into similar problems (although we are not using MotorWave...).

Thank you,

Ralph

Ralph,

There are a couple of issues.

1. Has to do with the order of linking in a project. This only seems to effect our MotorWare projects as we have specific libraries that need to be linked in and instead CCSv5.5 is overwriting with the default RTS lib.  This is fixed by having the project settings command a specific order of linking instead of leaving it to the compiler.

2. There is a bug in 6.2.x Optimizer’s prototype for __IQsat.  It’s treating the final argument as an int instead of a long.  This is being investigated further to see if there are other similar issues.

The compiler has been fixed for issue #2, it is rev'd to 6.2.3 and is available through CCS updates now.

We are updating our project settings for issue #1, will be updated in MotorWare _10 which releases on November 7, 2013.

Thanks for the update, we will check the new compiler.

Regards,

Ralph

In the meantime before MotorWare 1_01_00_10 is released (November 7th), if you are using a floating point project with CCSv5.5 you need to go to Properties --> Build --> Link Order tab; and insure that the rts .lib is before the ROM symbols file.

To the Top, and note that there is also a new compiler update to 6.2.4

You can use compiler 6.2.3 or 6.2.4 for MotorWare

Do NOT use previouse 6.2.x versions, InstaSPIN 100% WILL NOT work correctly.

Hi Chris,

I believe that I upgraded both CCS and Motorware and additionally ran CCS check for updates. Nonetheless, I question if my upgrades are all updated. The revisions are less than I've seen elsewhere in the forum, but perhaps I am looking in the wrong places. In short:

1) How do I tell if my CCS rev is up to date?

2) How do I get the latest CCS rev?

3) Same questions for Motorware and the compiler.

4) Finally, rather than relying on autoupdate, is there one site that shows latest revs?

Thanks,

Bill

Hi, Bill.

1. Help --> About Code Composer Studio

Please make sure you are on 5.5.x;
5.4.x is ok also

2. You can download new installs of CCS from the wiki

3.

You can download MotorWare from the tool folder. The revision is included on the tool folder, and it is versioned in the installation, ex: C:\ti\motorware\motorware_1_01_00_11

For the compiler:
The best way to see ALL versions of the compiler you have installed with a given instance of CCS is to look in the /tool folder of the installation directory.  For example, with my installation of CCS5.5 I can look at:

C:\ti\ccsv5p5\ccsv5\tools\compiler   (you won't have the ccsv5p5 folder if you did a standad install; I do this so I can install versions next to each other, like 5p3, 5p4, etc.)

Compilers can be added from:

Help --> Check for updates

or you can download and install to the /tool folder from the wiki

HOWEVER, this is just what compilers are installed for that instance of the CCS version.  To see which version is being used with a project

Righ click on the project --> Properties --> General
look at the Compiler version, and more importantly look at the effective compiler version if it's present (this is used if the compiler specificed doesn't exist).

Make sure this is 6.1.5 or prefferably 6.2.3+

4. For updates to the compiler the only reliable thing I've found (just yesterday) is to subscribe to the post (under Options on the upper left hand side) to the e2e thread where they post the update

Thanks Chris. I'm working through this. One of my issues was I thought the CCS update would rev it to 5.5.

>4. For updates to the compiler the only reliable thing I've found (just yesterday) is to subscribe to the post (under Options on the upper left hand side) to the e2e thread where they post the update

The link appears to be dead. I found this one: http://e2e.ti.com/support/development_tools/compiler/f/343/t/279320.aspx

Sorry, my original link was for a TI INTERNAL posting of the compiler update. I couldn't find the external posting. I'll see if the compiler team has a suggestion for us.

pushing to the top as I've seen some more people recently get burned by 6.2.0-6.2.2 compiler.

You MUST use 6.2.3+ (preferred) or 6.1.5- with MotorWare projects.

Chris,

Can i use new CCS6 for motorware (TMS320F28069F)?

Thanks,

Suprit

Should be fine. CCSv6 ships with good compiler and I haven't seen any issues in my limited testing. 

Dear chris,

When we will expected motorware version 13?

-Suprit

Suprit,

MotorWare _13 will release on June 19th along with a new announcement.

Hi,

I am still on CSS4.

the newest compiler CSS4 did find is 6.2.0

I had a problem with _IQsat what calls __IQsat. The Min, a 32Bit variable is cutted to 16Bit.

what to do?

Thanks, Thomas

Thomas,

You must roll-back to 6.1.x or forward to 6.2.3+

You can download any compiler package necessary though

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

Hey Chris, 

I tried using the 6.4.12 compiler version but it did not let me go in the reverse direction when i specify a negative speed. 

When I use 6.1.5 it works in both directions. 

Reading the thread it seems that the bug was fixed after 6.2.x but i may be mistaken ?

Is it necessary for me to use the newest compiler version. I am using ccs v5.5. 

which is the optimal compiler I should use with this version?

Regards,

Rajan Joshi

unfortunately we don't get to test each compiler release with MotorWare.

the last one I have been using regularly is 6.2.11

I'll see if someone can take a look at 6.4.12

but in the meantime I'd suggest starting with a fresh project just to make sure it isn't some other setting. If the link order gets switched with the libraries it can cause this problem as well.