These release notes contain valuable information which may not be included in other product documentation. This information will assist you in the use of Code Composer Studio™. The release notes are divided into four sections:
Installation:
Activation:
Managing Your License:
CCSv4.1:
Added support for new devices:
Luminary Stellaris devices
MSP430F5513,MSP430F5514,MSP430F5515,MSP430F5517,MSP430F5519,MSP430F5521,MSP430F5522,MSP430F5524,MSP430F5525,MSP430F5526,MSP430F5527,MSP430F5528,MSP430F5529,MSP430F5438A,MSP430F5436A,MSP430F5419A,MSP430F5437A,MSP430F5435A,MSP430F5418A,CC430F6127
C6472
OMAP3630
TMS570 (LS20216)
F28035
Added support for XDS100 Version 2 on applicable targets (see Wiki page for details).
Added support for eZ430-Chronos emulator.
Minor updates in header support files.
Updated Documentation.
Added support for MSP430F44x1, MSP430F461x, MSP430F461x1, MSP430F4796, MSP430F4797 and MSP430F471x3
Updated header files. Now every MSP430 derivative has its own header file, instead of generic ones. The old, generic header files are still included for legacy projectsFixed issue with MSP430F5527 in linker command file and MSP430.DLLFixed issue which caused MSP430F541x memory write failureFixed several MSP430F5xx related debug issuesUpdated drivers for USB debug interfaces. Added Windows 7 32- and 64-bit support. Windows XP and Vista 64-bit support was added. Important Note: Windows Vista operating systems may require a reboot as a new Microsoft Driver package is required. Therefore Windows may install three updates upon rebooting.Updated Documentation
Note: Code Composer Studio v4.1.0 installs a number of other products (DSP/BIOS, XDC, IPC, CodeGen). Check the product installations directory for their release notes.
Identifier | Target | Component | Severity | Headline |
SDSCM00034500 | ALL | Debug Server | S1 - Critical | 90day eval license extension does not work with 4.1 beta |
SDSCM00033752 | ALL | Debug Server | S2 - Major | GEL function execution should not halt when a deprecated function is encountered |
SDSCM00033803 | ALL | Eclipse IDE | S1 - Critical | Allow multi-target operations to execute on some of the targets even some of targets cannot execute it right now. |
SDSCM00034043 | ALL | Eclipse IDE | S1 - Critical | Mixed mode display hangs CCSv4 |
SDSCM00033473 | ALL | Eclipse IDE | S2 - Major | IDE uses stale pointer when accessing TPI info |
SDSCM00033817 | ALL | Eclipse IDE | S2 - Major | CCS Help topic does not point to anything valid |
SDSCM00033831 | ALL | Eclipse IDE | S2 - Major | Problems view does not show assembly errors in linked asm source files |
SDSCM00033154 | ALL | Eclipse IDE | S2 - Major | Unable to discover BIOS/RTSC tools if CCSv4 installed in root of C drive |
SDSCM00033516 | ALL | Eclipse IDE | S2 - Major | Extra target IO being performed by register view |
SDSCM00033779 | ALL | Eclipse IDE | S2 - Major | Use milliseconds for the continuous refresh rate preference option |
SDSCM00033863 | ALL | Eclipse IDE | S2 - Major | Load GEL dialog should not use windows current directory as default location |
SDSCM00033963 | ALL | Eclipse IDE | S3 - Minor | Options to load/reload/remove GEL files in the GEL view should be disabled if the proper context is not selected |
SDSCM00033336 | ALL | Installation | S2 - Major | Remove "core" options from Product Configuration Screen in the platinum installer |
SDSCM00033641 | ALL | Installation | S2 - Major | TI XDS560 32bit driver - device is not automatically found and drivers installed on some machines |
SDSCM00033643 | ALL | Installation | S2 - Major | Support patch installation with UAC on |
SDSCM00033826 | ALL | Installation | S2 - Major | Detect Default Browser |
SDSCM00033278 | ALL | Scripting | S3 - Minor | DSS Perl example missing target connect call |
SDSCM00033297 | ALL | Scripting | S3 - Minor | Remove obsolete 'API' folder in scripting docs folder. |
SDSCM00033694 | ARM | Debug Server | S2 - Major | GEL OnHalt() callback being called before target connection has been completed |
SDSCM00033760 | C2000 | Debug Server | S1 - Critical | CCSv4 crashes when starting a debug session for a C28346 (Delfino) |
SDSCM00034641 | C2000 | Eclipse IDE | S2 - Major | Memory leak with breakpoints leads to crash |
SDSCM00034484 | C2000 | Installation | S1 - Critical | 4.1 Beta MCU Core does not install compilers |
SDSCM00033950 | C6000 | Debug Server | S3 - Minor | Profile clock defualt configuration is blank for c6416 |
SDSCM00033488 | MSP430 | Debug Server | S2 - Major | 'Run to line' and 'Set PC to Cursor' doesn't work for functions that contain inlined code |
SDSCM00033281 | MSP430 | Eclipse IDE | S2 - Major | Unable to display 0xfffe in disassembly window |
SDSCM00033233 | MSP430 | Installation | S1 - Critical | MSP430 CGT with v4 Platinum install is code size limited |
SDSCM00034484 | MSP430 | Installation | S1 - Critical | 4.1 Beta MCU Core does not install compilers |
Identifier | Target | Component | Severity | Headline |
SDSCM00033391 | ALL | Debug Server | S2 - Major |
90 day eval extension is not presented at end of 30 day eval. Workaround: Refer to the mediawiki for instructions on how to get the extension license. |
SDSCM00033798 | ALL | DVT Platform | S2 - Major |
Request to have multiple printf windows open. Similar to how one can
have multiple memory windows. Use case is that customer has multiple threads running each with their own logs and would like to see these side by side. With the single window they can see them interleaved or use the filter option to pick one at a time. But not quite what's needed. |
SDSCM00033832 | ALL | DVT Platform | S2 - Major |
Need to show FileName in function Profiler. Also need to display the filename where the function is called from in Function-level CPU Cycles Profile view. It would be very helpful to easily identify the module in a big project. |
SDSCM00033413 | ALL | Eclipse IDE | S2 - Major | Minor dialog change to RTSC project wizard to help stear customer; remove the "finish" button from this dialog. |
SDSCM00033207 | ALL | Eclipse IDE | S2 - Major | Halt On Reset CCSv4 target menu feature is grayed out until the target is connected |
SDSCM00033386 | ALL | Eclipse IDE | S2 - Major |
On the help menu we should have a menu item that links to the CCSv4
Mediawiki site. The name of the menu should be: CCSv4 Developer Site It should be located below the Welcome item The link is: http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4 |
SDSCM00033416 | ALL | Eclipse IDE | S2 - Major |
CCS allows a project import even when it wouldn't be able to handle
project. You will only get an error message when launching the debugger,
however, it should bring up an error message already when Examples: - Importing an MSP430 project that uses the LPT interface on a CCSv4 version that does not have support for this interface (e.g. user did not select "install LPT tool support" during setup) causes problems without telling the user what's wrong. By opening the ccxml file you will only see XML code instead of the GUI. Need to have dialog already during project import saying: You're trying to import a project that uses the LPT interface. LPT support is currenlty not installed, please add feature by relaunching the installer" or similar. - Importing projects based on devices that do not exist in the IDE works fine - the only message that was shown is locked in the problems view and refers to the XML file - customers overlook this message or do not know what do do. Instead we should have a pop-up box saying: Device not supported by IDE. Please ensure check for updates or install support package for pre-release devices. |
SDSCM00033482 | ALL | Eclipse IDE | S2 - Major | When I reight-click a definition and select "open definition" nothing happens. Please fix. |
SDSCM00033644 | ALL | Eclipse IDE | S2 - Major | When a user checks for updates from within CCS we need to detect if they have installed in program files and UAC is on. Since if UAC is on then the updates will download but they will not get saved. The user will be unable to update CCS. We need to detect that UAC is on and warn the user to turn it off like we do in the main CCS installer. |
SDSCM00033672 | ALL | Eclipse IDE | S2 - Major |
Set breakpoints do not show up in the editor margin (breakpoint icon
missing) of the associated source file, even if the breakpoint was
successfully set by double-clicking in the editor margin. The breakpoint
icon appears in the disassembly view and is listed in the breakpoints
view however. This is a source lookup issue that can occur when using linked resources. |
SDSCM00033692 | ALL | Eclipse IDE | S2 - Major | PJT migration: non-buildable source-files cause unneccessary error messages |
SDSCM00033698 | ALL | Eclipse IDE | S2 - Major |
Various project files of specific names are generated when importing
legacy CCS 3.x projects into CCS 4.x. If the "Copy projects into
workspace" folder is not selected, it will place these generated files
in the same location as the CCS 3.x project file. If there are multiple
CCS 3.x project files in the same directory, and they are all being
imported, the generated project files of the previously imported CCS 3.x
project will be overwritten with the last one. Workaround: Either enable the "Copy projects into workspace" option during the import to copy everything into their workspace folder or place the legacy project files in separate folder prior to importing them. |
SDSCM00033843 | ALL | Eclipse IDE | S2 - Major | If a standard make project is created on a command line and a .ccxml file is added to that project, then it does not automatically become active/default when workspace is opened. When the same project is manually imported (File -> Import -> Existing Project), then .ccxml file is set to be active/default. |
SDSCM00033870 | ALL | Eclipse IDE | S2 - Major |
In the past users would exclude the BIOS installer from their build and
have their owner linker command file include the BIOS linker command
file at the end so that they could control the link order. User need to
be able to control the link order. Having the BIOS generated cmd file show up in the link order tab would help users control their complete link order. |
SDSCM00033909 | ALL | Eclipse IDE | S2 - Major | Build or make target dialogs losing "" when they are opened. |
SDSCM00033925 | ALL | Eclipse IDE | S2 - Major | We have had a number of issues where customers have been trying to use eZ430 usbsticks with the Free limited license in CCS as they see that it supports eZdsp kits and boards with onboard emulation so they assume that it will work with MSP430. Thus we need to add a note to the description that says it does not work with eZ430. |
SDSCM00034182 | ALL | Eclipse IDE | S2 - Major | Scripting console command should set an active project |
SDSCM00034183 | ALL | Eclipse IDE | S2 - Major | Scripting console command should set a default .ccxml file for use when launching ti debugger |
SDSCM00034184 | ALL | Eclipse IDE | S2 - Major | There is a need for scripting menu creation api's that can create multiple menu levels. |
SDSCM00034185 | ALL | Eclipse IDE | S2 - Major | We need a Most Recently Used (MRU) listing of loaded .js files that would persist between CCS sessions |
SDSCM00034205 | ALL | Eclipse IDE | S2 - Major | When creating a standard make project build command can be overwritten. However, -k -f options are preserved. Presence of this option causes problems for some make utilities causing build failures. Would like to have the option or default behaviour be such that build command is completely overwritten by what is specified in project create |
SDSCM00034231 | ALL | Eclipse IDE | S2 - Major |
Open a project, right-click on source file within the project and select
"Build Selected File". This builds the file but seems to generate
incorrect .pp file. Sometimes a Clean Selected FIle is needed before
Build Selected File to generate the error. Next time selecting "Build Selected File" again causes this error: C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake msp430x54x_adc12_10_original.obj C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** No rule to make target `C:/Program', needed by `msp430x54x_adc12_10_original.obj'. Stop. Build complete for project msp430x54x_adc12_10 The problem seems to be due to missing #FIXED in 1st line of .pp file. Doing a "Rebuild Active Project" regenerates the correct .pp file though and build completes. See also forum post: http://e2e.ti.com/forums/p/12543/48993.aspx#48993 |
SDSCM00034360 | ALL | Eclipse IDE | S2 - Major | When you load a program you see two progress tasks in the progress dialog called "Loading". Both report that they are loading the program. Many messages show up twice. This also happens with the erase message for flash. |
SDSCM00034373 | ALL | Eclipse IDE | S2 - Major | PJT migration: linked-files whose path contains spaces arent migrated properly |
SDSCM00034618 | ALL | Eclipse IDE | S2 - Major | Changes to BIOS tcf file causes rebuild of entire project when incremental build is expected |
SDSCM00034720 | ALL | Eclipse IDE | S2 - Major | When a RTSC project is imported that contains two .cfg files then both .cfg files are excluded from the build. This occurs only when project is left in its original location during import. When a project is copied into workspace then this issue does not occur. |
SDSCM00034721 | ALL | Eclipse IDE | S2 - Major | RTSC projects that contain two .cfg files (where both were excluded at some point in time from the build, e.g. when experimenting between two different .cfg files), will be fully rebuilt between CCS restarts. |
SDSCM00034583 | ALL | Eclipse IDE | S3 - Minor |
Scripts' menu is greyed out when switching back to the C/C++ perspective
from the Debug perspective. When starting a debug session from the C/C++ perspective by using a hotmenu from the 'Scripts' menu (added by loading a JS DSS file (loadJSFile) ) , a debug session will start and CCS will flip to the Debug perspective. When the debug session is shut down manually, CCS will flip back to the C/C++ perspective. When it does so, the 'Scripts' menu is greyed out. Switching perspectives and coming back again will make the 'Scripts' menu available again. Workaround: Toggle between perspectives to have the 'Scripts' menu available again |
SDSCM00033192 | ALL | Eclipse IDE | S3 - Minor | Description text in the "Memory Map" view has a spelling mistake. It should read "specify". |
SDSCM00033265 | ALL | Eclipse IDE | S3 - Minor | License activation dialog option to Use Free Limited License should also mention simulators in the description |
SDSCM00033293 | ALL | Eclipse IDE | S3 - Minor |
When exporting a project using "File->Export...->General->Archive File"
and not using the "Browse" button to specify a directory, the archive
file gets stored in "C:\Program Files\Texas
Instruments\ccsv4\emulation\analysis\bin". The expected behavior would be that the file gets stored into the folder that is shown when clicking the "Browse" button. Otherwise, the file basically "disappears" in the file system with no easy way to find it (since the directory shown when clicking the "Browse" button doesn't match the default directory that is actually used). |
SDSCM00033444 | ALL | Eclipse IDE | S3 - Minor |
In CCSv4, on the 'Project' menu, the incremental build selection is
named "Build All". This has confused some customers, as they think it
is a full build. The full build selection is called "Rebuild All". In CCS v3, incremental build was called "Build" and the full build "Rebuild All". I guess the "All' appendage in "Build All" in CCSv4 is what confused my customer. Personally, I think "Incremental Build" and "Full Build" are the best descriptions. Perhaps we should consider changing the menu names. It would be a small change, and might help future users. |
SDSCM00033632 | ALL | Eclipse IDE | S3 - Minor |
Need a way to get to global symbols when adding a new breakpoint. Functions names are aften very long. In the case of BIOS 6.x we have function names like _ti_sdo_ipc_heaps_HeapMemMP_Module_startup__E Typing in such a long name is very error prone and leads to a lot of frustration. It would be very useful if we could access global symbols in breakpoint window or some kind of auto-complete feature. |
SDSCM00034332 | ALL | Eclipse IDE | S3 - Minor | When I press 'ALT', there is no underscore for an letter under the 'Scripts' menu. I would like to be able to get to items under the 'Scripts' menu via keystroke |
SDSCM00034197 | ALL | Installation | S2 - Major |
The Platinum installer on the mediawiki and the auto update patch seem
to be of the different type. When downloading and installing the 4.0.2 full installer from the mediawiki will trigger another 4.0.2 update when launching it for the first time. The reason seem to be that the full installer is of version 4.0.2.01001 whilst the patch is 4.0.2.01003. |
SDSCM00033467 | ALL | Installation | S3 - Minor | DebugServer directory will not be created in Linux BUILD_ARTIFACTS for CCS4.0.2, 4.1, 4.2 and 5.0 as there's nothing that's to be installed by the main installer in that directory now. |
SDSCM00034042 | ALL | Installation | S3 - Minor | On the screen where you get the checkboxes showing what has been installed, i.e. it checks boxes as things complete, the XDAIS box does not match the order it gets installed. It is listed last but actually gets installed before MSP430. Minor issue but looks odd when you see it as you think that maybe some of the items were missed. |
SDSCM00033414 | ALL | Licensing | S2 - Major | CCSv4 Core Edition can't be used on PCs without internet access. |
SDSCM00033897 | ALL | Scripting | S2 - Major |
There are no publicly available DSS equivalent APIs similar to GEL
callback functions such as OnTargetConnect(). Workaround: All the existing GEL callback functions are still supported in CCSv4. |
SDSCM00034418 | ALL | Scripting | S2 - Major | Request to add a DSS API that will return all available session names for a target configuration. This will help avoid using hard-coded names in DSS scripts for opening a debug session. |
SDSCM00034331 | ARM | AET | S2 - Major |
The Breakpoint Manager for CORTEX M3 shows the message below when the
maximum number of hardware breakpoints is reached: "Breakpoint Manager: Error programming AET Job: There is no AET resource to support this job." Workaround: Either reduce/disable the number of active HW breakpoints or avoid stepping through your code (using F5 or F6). |
SDSCM00034642 | ARM | Debug Server | S2 - Major | Button "Remember My Settings" in Stellaris Flash does not work for Address Range |
SDSCM00033678 | ARM | Eclipse IDE | S2 - Major | In the build options for the 4.4.x compiler the --float_support option is missing in the runtime options. This is an important option for CortexR4. The option is present in the 4.5.x build options dialog. |
SDSCM00033881 | ARM | Eclipse IDE | S2 - Major |
When debugging multiple targets in CCS it becomes difficult to
differentiate tabs/windows from each other when they have names like
'Memory (1)' and 'Memory (2)'. Workarounds: Either: - Select, highlight and modify the text 'Memory (1)' in the top of the tab/window. - Allow the user to right click on the text and choose 'Rename'. Then give the user a pop-up box that would allow them to rename the tab/window. |
SDSCM00034360 | ARM | Eclipse IDE | S2 - Major | When you load a program you see two progress tasks in the progress dialog called "Loading". Both report that they are loading the program. Many messages show up twice. This also happens with the erase message for flash. |
SDSCM00034635 | ARM | Emulation - Config Files | S3 - Minor | GEL_WatchAdd should not be in CortexM3_util.gel |
SDSCM00034736 | ARM | DVT | S2 - Major |
Stop Mode RTA is not gathering substantial amount of data for ARM9
target. After successfully building and loading a BIOS6 RTA project onto the ARM9 core of the OMAPL137 target. I ran the target for just under 20 seconds and found inconsistencies in the amount of data collected between the views. I was expecting the stop mode RTA to be very similar to that of the continuous RTA on the DSP's; except of course that I would be expected to manually halt the target to gather data. According to the RAW Logs view data is collected for "xdc.runtime.LoggerBuf" for the whole run, while "RTASystemLog" has < 1second worth of data and "RTALoadLog" has roughly 3 seconds worth of data. I am not sure if this is behaving correctly. |
SDSCM00033908 | C2000 | Eclipse IDE | S2 - Major |
When a C2000 CCS 3.3 project is imported into CCS v4, the project builds
ok as-is. However, if the version of codegen tools is changed, it is
unable to save the changes, it gives an error and reverts back to the
original version of codegen tools. This seems to be related to Project Build Settings->Device Variant being set to "C2000 Custom Device". If this is changed to "Generic C28xx Device" then the version of codegen tools can be modified without problem. Tested with a C6000 example project shipped with CCS 3.3 as well and the same issue occurs. User should be able to directly modify/update the build properties of the converted project without having to make further changes to the device variant. |
SDSCM00034641 | C2000 | Eclipse IDE | S2 - Major |
Sometimes when using CCS for a long period of time it will run out of
JVM heap space and then crash. Workaround: Open eclipse.ini in \ccsv4\eclipse Adjust the “-Xmx256m“ argument, i.e. bump up to 512m. This will not fix the problem but it will take longer for the heap to be used up. |
SDSCM00033237 | C2000 | Emulation - Config Files | S1 - Critical | Cannot use realtime mode on F28 devices on xds100 or xds510 emulators |
SDSCM00034620 | C2000 | Emulation - Drivers | S2 - Major | CCS v4.0x allows user to set only 1 hardware breakpoint when debugging BIOS programs in Flash |
SDSCM00034673 | C2000 | Scripting | S2 - Major | CCS v4.0x allows user to set only 1 hardware breakpoint when debugging BIOS programs in Flash |
SDSCM00034652 | C6000 | C6000 Simulation | S2 - Major |
Invoking C6474, C6487 or C6488 simulator multiple times can lead to a
crash Temporary Workaround: Restarting CCSv4 every time while using any of above simulator configuration should resolve the issue. |
SDSCM00034580 | C6000 | C6000 Sim-Features | S2 - Major | CCS crashes during a function profiling run if profile resume and pause points are used is certain scenarios. In this particular case, the issue occurred when setting a profile resume point inside the beginning of a called function (beginning bracket) and a pause point inside the end of the called function (closing bracket). |
SDSCM00034560 | C6000 | C6000 Sim-Source Components | S2 - Major | VCP2_statRun() CSL API doesn't initialize the VCP2 model on simulator. |
SDSCM00033292 | C6000 | DVT Platform | S2 - Major | The naming of the timestamp column in STM is confusing. "Cycles" in the name "Timestamp (cycles)" is not appropriate for STM. |
SDSCM00033597 | C6000 | Eclipse IDE | S2 - Major |
The user should be provided an option in the XDCtools properties dialog
to specify special compiler options. It is suggested that a text box be provided in the "Advanced Options" section with the title "Additional Compiler Options (--compileOptions)". An appropriate API should be provided in the 'IProjectPropertyProvider' interface for the XDCtools integration plugin. This option should be visible for XDCtools release 3.16 and higher. |
SDSCM00033119 | MSP430 | Documentation | S2 - Major | No link to MSP430 specific help docs from the IDE or Windows start menu. |
SDSCM00033230 | MSP430 | Eclipse IDE | S1 - Critical |
Importing projects (given the usage of build configurations that use
different libraries) does not work when projects are created with CCE3.x
- see example 1 (attachements). The 104 error message (!) do not provide
enough information to address the issue unless you have good knowledge
about the project. Project import from CCSv4 to CCSv4 works only if the libs that are not used are manually excluded. Build configurations are not supported in that case (at least when predefined symbols are used - see example 2). It's still possibel to manually exclude libs, but this needs to happen in multiple places in the code. Without project knowledge it's very difficult for (new) customers getting. |
SDSCM00033421 | MSP430 | Eclipse IDE | S2 - Major |
I can't always successfully create new project (from scratch) in CCSv4
all the time. Sometimes everything works fine, sometimes I get strange
error messages related to a CMD file that can't be found by the CGT -
pls see screenshot. The missing CMD file is present in the "msp430\include" directory, the project properties contain the correct path (at least it shows the correct one). When I copy the file to the "tools\compiler\msp430\include" directory everything works fine - but it should work also with the cmd file being present in "msp430\include\". ERROR MESSAGE: <Linking> error: cannot find file "msp430x54x.cmd" undefined first referenced >> Compilation failure symbol in file --------- ---------------- PADIR_L ./msp430x2xx_fet_1.obj PAOUT_L ./msp430x2xx_fet_1.obj TA1R ./msp430x2xx_fet_1.obj WDTCTL ./msp430x2xx_fet_1.obj error: unresolved symbols remain error: errors encountered during linking; "5438_test1.out" not built C:\Program Files\Texas Instruments_test_lnk\ccsv4\utils\gmake\gmake: *** [5438_test1.out] Error 1 C:\Program Files\Texas Instruments_test_lnk\ccsv4\utils\gmake\gmake: Target `all' not remade because of errors. Build complete for project 5438_test1 |
SDSCM00033518 | MSP430 | Eclipse IDE | S2 - Major | Using a second screen with a big external memory view is not possible, as the bigger you make the view, the longer it takes for one single step. On an about half full 1280x1024 screen, it already takes 3-5 secs per single assembly step. |
SDSCM00033519 | MSP430 | Eclipse IDE | S2 - Major | When having CCS run on the first screen, and having an external memory view on the second screen, the tooltips for the memory view are shown on the edge of the first screen. This can be really annoying when having a large memory view open (watching stacks of different tasks in an os, for example) |
SDSCM00033861 | MSP430 | Eclipse IDE | S2 - Major |
When a variable is declared as long, then the Watch window and also the
Local window views only the lower Byte of the variable, with unsigned
int as data type. But this error only occurs with the new MSP430F6638 as target. With an older one, like the MSPF5438A, it works. |
SDSCM00033419 | MSP430 | Eclipse IDE | S2 - Major |
I have a working CCS4 project for a CC430F6137. Building works fine
after installing CCS4, but after a restart of windows I get the
following error message while trying to rebuild my project: "This project was created for a device-variant that is not currently recognized: CC430F6137. Please install the device-variant descriptor, or migrate the project to one of the supported device-variants." When I try to create a new CCS project (MSP430) I get the following error message: "No Code Generation tools are currently installed for this project type. Please install Code Generation tools before creating a project of this " After closing and restarting CCS4 (without restarting windows) everything works fine again. |
SDSCM00033501 | MSP430 | Eclipse IDE | S2 - Major |
The Outline View can be very useful for bigger projects, but then it
should also work correctly for them. In bigger projects there is often a configuration header-file, which might define a lot of things for conditional compiles or other defines. The Problem is: When you have for example a file main.c and include a file xyz.h, and if there is a conditional compile in the main.c depending on for example "foo", and "foo" is defined in xyz.h. Then the Outline View does not show the correct things, and assumes "foo" is NOT set, so things the other part would be "active". |
SDSCM00033879 | MSP430 | Emulation - Drivers | S2 - Major |
The MSP430F5527 linker command file contains a wrong definition for the
RAM length. Workaround: When using this device please change the length to “0x1800”. |
SDSCM00033777 | MSP430 | Installation | S3 - Minor | When trying to overwrite an old but updated CCS Core Edition Installation with CCS Platinum, the wrong version is shown. |
SDSCM00034660 | TMS470 | Eclipse IDE | S3 - Minor | CCS4.1 build doesnt execute if you forget a dependent library |
Windows, Windows XP, Windows Vista, Windows
7, Visual SourceSafe, Visual Basic, and Visual C++ are all trademarks and/or registered trademarks of Microsoft Corporation.
C2000, C5000, C54x, C55x, C6000, C6x, OMAP, TMS320, TMS320C54x,TMS470, MSP430,
Stellaris, Code Composer Studio, Code Composer Essential, DSP/BIOS, eXpressDSP, XDS560, XDS510,
and XD100 are trademarks of Texas Instruments.