The next version of our MSP430 Code Composer development tools are in beta and we’d like to give you an opportunity to give try them out and provide feedback. The new version is called Code Composer Studio v4. Starting with version 4, we will change the name from Code Composer Essentials to Code Composer Studio and will now support our MCU and DSP families with the same product.
Code Composer Studio v4 includes many improvements for MSP430 including build option usability, reduced runtime support library size (which improves code size) and automatic updating.
Feel free to visit our CCSv4 website (http://tiexpressdsp.com/wiki/index.php?title=Category:Code_Composer_Studio_v4) to learn more about this release and to download the beta.
If you have any comments or run into any problems, please post them on this forum thread.
Regards,
John
John Stevenson
CCS Product Manager
Hi,
Great news.
How about License upgrade if we own CCE Professional?Do we have to buy this new version again?
regards,
Gregor
Gregor,
If you purchased CCE Pro within 12 months of the release of CCSv4 then you will receive the new version for free. There are more details here:
http://tiexpressdsp.com/index.php?title=Licensing
John,
Interesting news indeed. What about Vista support? IIRC, the USB driver was the only problem under Vista. Any update?
Kind regards,
Mike
Mike - like CCE v3, CCS v4 will support Vista. however, the msp430 driver (msp430.dll) that communicates between the IDE and the FET is currently only supported under 32-bit systems. we're working on 64-bit support and we'll hopefully get it out soon.
Any information on license pricing?
We will continue to have a MSP430 code size limited verison that is free. The equivalent of the current CCE Pro MSP430 would be the CCSv4 Microcontroller version, the node locked (single machine) license for this will be 495 which is consistent with the CCE pricing. There will also be floating license versions available a well, pricing for those are not finalized.
Hello John
I have just converted one of my MSP430F2272 projects to CCS V4. Worked perfectly right out of the box.
Congratulations.
One small issue (more an annoyance than anything). After rebuilding the project there was a warning stating that the project was originally built for version 3.0 of the CG tools. Version 3.0 of the CG tools is not installed. So there is no choice. In CCS build settings the properties rightly indicate that the project should build with version 3.2 of the CG tools. However in the C/C++ build tab it indicates that the CG tools version is 3.0.1. It cannot be changed because it is greyed out. Therefore I cannot get rid of the warning it seems...
Regards
Bruno
Normal 0
I just tried the CCSv4 on a project I have been using with CCE. The CCSv4 tools wanted to update the firmware in my FET430UIF, which I allowed it to do. I was having trouble with halting the target and seeing memory contents, local variables, etc. and I figured I would put it aside and try again when I had more time to play with it.
I went back to the CCE tools in an effort to get some work done, but now CCE will not recognize the existence of the FET430UIF. I cannot get CCSv4 to properly show the machine state when the target is halted which I REALLY need to do, and I cannot go back to CCE because the FET430UIF no longer works with it. Is there any way to force a reload of the old firmware in the FET430UIF?
Dave
Dave,
Back up the msp430.dll in your CCE install then copy the one from CCSv4 into it. That should enable you to work wih CCE again.
JohnS:Back up the msp430.dll in your CCE install then copy the one from CCSv4 into it.
Thanks John, that worked great! It's nice to know that I can go back to CCE if I have to.
I've been using the new tool for a little while now and I am finding that it works pretty well. I have a couple suggestions since it is still in Beta phase:
1) CCE allows the user to pick from a drop-down list of all global variables and check or uncheck which variables are to appear in the watch window. CCSv4 does not have this feature and it sure would be nice.
2) The IAR tools offer a shortcut to enable or disable the GIE flag and I find that particularly useful. When the target is paused and single stepping is required, the debugger perpetually steps into the various ISR events that are still being triggered by external events unless the GIE bit is cleared. It requires many steps and clicks to get to and from the GIE bit to set and clear it and I spend a lot of time doing that. A shortcut button to toggle that particular bit would be nice to have.
3) I still cannot always get the watch window to update or see where the target is paused in the source code when the Halt button is clicked. It only works about 10% of the time, and this is showstopper for the debugger.
I'm having a little trouble with keeping the target connected to the tool through the FET430UIF, but I have not determined what causes the breakdown just yet. Other that that it's working great so far!
Thanks -
1) We actually had the option to browse and add global variables in early beta builds. I believe we lost it when we replaced the view with a new one. It should be added back in before the final release.
2) If we had a way that you could automatically clear GIE on a halt would that help? I guess the problem there would be that we would also need to automatically set it on Run as well which would cause problems while stepping. I guess what we could do is show how to white a short little GEL script that adds a couple of menu items under the scripts menu that would set and clear the bit. If the script is generic across all MSP devices maybe we could even have it setup by default.
3) Not updating on halt would be a big problem. Is there a particular devices this is happening on?
Bruno I will import a couple projects on Monday to see if I can reproduce this. In theory you should be able to select build properties from the right context menu of the project and then select build settings and switch it to the 3.2 compiler (but it seems like that is already indicating 3.2, but the build options being displayed are for 3.0.1).
Bruno Paillard:One small issue (more an annoyance than anything). After rebuilding the project there was a warning stating that the project was originally built for version 3.0 of the CG tools. Version 3.0 of the CG tools is not installed. So there is no choice. In CCS build settings the properties rightly indicate that the project should build with version 3.2 of the CG tools. However in the C/C++ build tab it indicates that the CG tools version is 3.0.1. It cannot be changed because it is greyed out. Therefore I cannot get rid of the warning it seems...
when importing old projects, i've run into the same problem and i haven't figured out how to fix it. it's not a showstopper but a workaround would be greatly appreciated.
JohnS:2) If we had a way that you could automatically clear GIE on a halt would that help? I guess the problem there would be that we would also need to automatically set it on Run as well which would cause problems while stepping. I guess what we could do is show how to white a short little GEL script that adds a couple of menu items under the scripts menu that would set and clear the bit. If the script is generic across all MSP devices maybe we could even have it setup by default.
I'm not sure it would be a good idea to automatically set or clear the GIE as not all pro9grams would require it to be set the same way. If there were an option button that would toggle the current state of the GIE bit, whatever it currently is, then that would be ideal. I find myself spending a lot of time and breaking a lot of concentration having to go in there and set/clear that particular bit because it's buried fairly deep and far away from everything else I'm usually looking at, and modifying its value it is quite necessary for single stepping.
JohnS:3) Not updating on halt would be a big problem. Is there a particular devices this is happening on?
The MSP du jour is the MSP430F2132. I have many other projects I can (and eventually will) try it with. It's fairly consistent in its Normal 0 behavior with the project I am currently working on and that's why I had to go back to the CCE tool. Is there any other info that would be helpful? I'm assuming I am the lucky one and it's not happening with anyone else.
ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". TI AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY TI. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM TI.
Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.