Release Notes for Code Composer Studio v4.1.2

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:

Registration Information

Installation:

  1. Run setup_CCS_4.1.2.xxxxxx.exe
  2. Choose where you want to install
  3. Select the components you wish to install

Activation:

  1. Go to http://tiexpressdsp.com/wiki/index.php?title=Activating_CCS
  2. Follow step-by-step instructions

Managing Your License:

  1. Web interface for managing your licenses:
    www.ti.com/myregisteredsoftware
  2. Use it if you want to see expiry info, or move the license to a different machine

For additional information and support, please go to: http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4


New Features (CCSv4.1 vs. CCSv4.0)

  • Added support for these devices:
                Stellaris devices
	C6472
	OMAP3630
 	TMS570 (LS20216)
	F28035
                AM1808
	C5515
  • Added support for:
MSP430F44x1, MSP430F461x, MSP430F461x1, MSP430F4796, MSP430F4797 and MSP430F471x3
MSP430F5513, MSP430F5514, MSP430F5515, MSP430F5517,         
MSP430F5519, MSP430F5521, MSP430F5522, MSP430F5524,         
MSP430F5525, MSP430F5526, MSP430F5527, MSP430F5528,         
MSP430F5529, MSP430F5438A, MSP430F5436A, MSP430F5419A,      
MSP430F5437A, MSP430F5435A, MSP430F5418A, CC430F6127
Updated header files. 
Updated drivers for USB debug interfaces. Added Windows 7 32- and 64-bit support, and for Windows XP and Vista 64-bit. 
    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.2 installs a number of other products (DSP/BIOS, XDC, IPC, CodeGen).  Check the product installations directory for their release notes.

For additional information and support, please go to: http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4 

Bug Fixes

For up-to-date status information, go to:
https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO-Web&contextid=SDOWP&rmsessionid=019e2b0b-3586-450f-8905-c0a8f08f4205

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
SDSCM00035162 ALL Debug Server S2 - Major SD 510 USB and 510 USB LC configurations crash on launch if the emulator is not present
SDSCM00035609 ALL DVT Data Processors S1 - Critical Trace Analyzer disassembly incorrect when working with more than one tdf and/or live trace
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
SDSCM00033413 ALL Eclipse IDE S2 - Major minor dialog change to RTSC project wizard to help stear customer (remove Finish from 2nd-to-last page)
SDSCM00033473 ALL Eclipse IDE S2 - Major IDE uses stale pointer when accessing TPI info
SDSCM00033516 ALL Eclipse IDE S2 - Major Extra target IO being performed by register view
SDSCM00033672 ALL Eclipse IDE S2 - Major Set breakpoints do not appear in the editor margin of source file (source lookup issue)
SDSCM00033698 ALL Eclipse IDE S2 - Major CCSv4 legacy project import wizard does not handle multiple projects in the same folder
SDSCM00033779 ALL Eclipse IDE S2 - Major Use milliseconds for the continuous refresh rate preference option
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
SDSCM00033843 ALL Eclipse IDE S2 - Major Command line project create/import do not set a .ccxml file that is part of the project as default
SDSCM00033863 ALL Eclipse IDE S2 - Major Load GEL dialog should not use windows current directory as default location
SDSCM00033870 ALL Eclipse IDE S2 - Major BIOS cmd files need to be included in link order
SDSCM00033909 ALL Eclipse IDE S2 - Major Build or make target dialogs losing "" when they are opened. Paths with spaces
SDSCM00033925 ALL Eclipse IDE S2 - Major Need to update the description text for "Use Free Limited License"
SDSCM00034182 ALL Eclipse IDE S2 - Major Would like a scripting console command to set an active project
SDSCM00034183 ALL Eclipse IDE S2 - Major Would like a scripting console command to set a default .ccxml file
SDSCM00034184 ALL Eclipse IDE S2 - Major Would like multiple levels in scripting menu hierarchy
SDSCM00034185 ALL Eclipse IDE S2 - Major Would like an MRU listing of loaded .js files that would persist between CCS sessions
SDSCM00034205 ALL Eclipse IDE S2 - Major Command line standard make project creation adds extra options to make command that break some make commands
SDSCM00034231 ALL Eclipse IDE S2 - Major Build selected file corrupts .pp file causing successive builds to fail
SDSCM00034360 ALL Eclipse IDE S2 - Major Load Program progress bar shows up twice
SDSCM00034373 ALL Eclipse IDE S2 - Major PJT migration: linked-files whose path contains spaces arent migrated properly
SDSCM00034434 ALL Eclipse IDE S2 - Major Watch window performance issue when large program files with many symbols are used
SDSCM00034618 ALL Eclipse IDE S2 - Major Changes to BIOS tcf file causes rebuild of entire project when incremental build is expected
SDSCM00034880 ALL Eclipse IDE S2 - Major CCS is not finding source files from an included library
SDSCM00035292 ALL Eclipse IDE S2 - Major Watch window does not update array element pointing to a different structure
SDSCM00035396 ALL Eclipse IDE S2 - Major CCS reports wrong state when setting breakpoint for run to main fails
SDSCM00033192 ALL Eclipse IDE S3 - Minor CCSv4 - Memory Map View - Spelling Mistake
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
SDSCM00035084 ALL Eclipse IDE S3 - Minor Program Load dialog should remember last selected file extension
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
SDSCM00034893 ALL Installation S2 - Major Installer should warn users if running as non-admin that they need to installer somewhere other than program files
SDSCM00035228 ALL Installation S2 - Major Scripting option should not install Eclipse IDE
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
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
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 --float_support option is missing from ARM 4.4.x build options plug-in
SDSCM00034360 ARM Eclipse IDE S2 - Major Load Program progress bar shows up twice
SDSCM00033760 C2000 Debug Server S1 - Critical CCSv4 crashes when starting a debug session for a C28346 (Delfino)
SDSCM00034902 C2000 Debug Server S1 - Critical F28035 Flash DLL does not allow programming to start addresses of flash
SDSCM00035397 C2000 Debug Server S2 - Major CCS gets confused between the F28x and CLA on F28035 causing a crash
SDSCM00033874 C2000 Eclipse IDE S1 - Critical Wrong silicon version selected for C2000 devices
SDSCM00033908 C2000 Eclipse IDE S2 - Major Projects imported from CCS 3.3 to CCS 4 do not allow selection of a different version of code generation tools
SDSCM00034641 C2000 Eclipse IDE S2 - Major Memory leak with breakpoints leads to crash
SDSCM00033237 C2000 Emulation - Config Files S1 - Critical Cannot use realtime mode on F28 devices on xds100 or xds510 emulators
SDSCM00033882 C2000 Emulation - TPI S2 - Major CLA opcode not disassembled properly
SDSCM00034484 C2000 Installation S1 - Critical 4.1 Beta MCU Core does not install compilers
SDSCM00033270 C6000 C6000 Sim-Features S2 - Major load program using forward slashes in path crashes the simulator
SDSCM00034652 C6000 C6000 Sim-Internal Components S1 - Critical debug server crashes on shutdown with c6474 simulators
SDSCM00033597 C6000 Eclipse IDE S2 - Major XDCtools properties dialog should allow users to specify special compiler options
SDSCM00034965 C6000 Eclipse IDE S2 - Major Conversion Wizard creates bad search paths
SDSCM00035256 C6000 Eclipse IDE S3 - Minor Editing Q31 variables in Watch Window gives incorrect result
SDSCM00035406 MSP430 Debug Server S1 - Critical MSP430 Debugger Options is blank
SDSCM00033488 MSP430 Debug Server S2 - Major 'Run to line' and 'Set PC to Cursor' doesn't work for functions that contain inlined code
SDSCM00034706 MSP430 Debug Server S2 - Major Watch window displays array of pointers incorrectly
SDSCM00035402 MSP430 Debug Server S2 - Major Disable interrupts while stepping option is greyed out in Debug view
SDSCM00034619 MSP430 Eclipse IDE S1 - Critical CCS4 starts deleting all files on the computer after selecting Project-->Build Active Project
SDSCM00033281 MSP430 Eclipse IDE S2 - Major Unable to display 0xfffe in disassembly window
SDSCM00033519 MSP430 Eclipse IDE S2 - Major Tooltips for external memory view on second screen are shown on first screen (where CCS runs)
SDSCM00033879 MSP430 Emulation - Drivers S2 - Major Header files for the MSP430F55xx device series contain wrong definitions
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
SDSCM00033270 OMAP C6000 Sim-Features S2 - Major load program using forward slashes in path crashes the simulator
SDSCM00034978 SOC DVT Solution S1 - Critical CCS4 crashes when loading a .tdf file
SDSCM00033292 SOC DVT Solution S2 - Major Timestamp coulumn name is the Trace Analyzer is not appropriate

 


Known Issues

For up-to-date status information, go to:
https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO-Web&contextid=SDOWP&rmsessionid=019e2b0b-3586-450f-8905-c0a8f08f4205

Identifier Target Component Severity Headline
SDSCM00035342 ALL Debug Server S2 - Major GEL_TargetTextOut() does not respect newline (0x0A) characters. It ignores it and continues output on the same line. Earlier versions of CCS (4.0.2) respected the newline character.
SDSCM00035566 ALL Debug Server S2 - Major Unable to load a program with unicode characters in the filename
SDSCM00035681 ALL Debug Server S2 - Major If another product installs a dll named logger.dll into windows/system, CCS may fail to launch a debug session with the message:
Could not createInstance(@ti.com//DebugServer1;1.{bfab7a88-14c8-48be-8729-f7701e4e0f35}) The function "createInstanceByContractID" returned an error condition (0x80004051) (0x80004005)
Workaround:
  There should be a logger.dll located in <install>\ccsv4\common\bin.  By copying that file to <install>\ccsv4\common\bin\logger.dll to <install>\ccsv4\eclipse\jre\bin\ CCS should begin working again
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.
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.
SDSCM00033692 ALL Eclipse IDE S2 - Major PJT migration: non-buildable source-files cause unneccessary error messages
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. 
SDSCM00034927 ALL Eclipse IDE S2 - Major Control panel view currently uses an unordered Map to contribute to Tools menu item.  As a result, in some cases the menu items appear in inconsistent order.  
SDSCM00035127 ALL Eclipse IDE S2 - Major setDefaultTargetConfig Scripting Console Command does not properly handle relative paths to the ccxml file. The issue is related to problems with the regular expression parsing.
Workaround:
  To specify a ccxml file in a subfolder (ex: subfolder\file.ccxml)  try:
   setDefaultTargetConfig "subfolder.*/<regexp>.*file.ccxml"
SDSCM00034393 ALL Eclipse IDE S2 - Major Certain projects that include header files through compiler's include search paths are not indexed propertly. Source files are treated as external files and are not indexed. Hence, source navigation (i.e. F3) does not do anything. 
SDSCM00034742 ALL Eclipse IDE S2 - Major Headless projectCreate: add macros.ini file processing:
Implement automatic macros.ini file processing for the headless projectCreate commands.  Currently this is only implemented for project-importing, but there is no reason not to do it for projectCreate, if a macros.ini file is present after project creation (for both projectCreate and projectCreate_stdMake).
SDSCM00035187 ALL Eclipse IDE S2 - Major Request for ability to use -@ option for archiver
SDSCM00035196 ALL Eclipse IDE S2 - Major If you have a large project where your object files are placed outside of the standard directory (i.e. not in \Debug) it is possible to get an error when running the clean command complaining that the input line is too long.  Essentially the command generated by Eclipse could exceed the length supported by windows.
Workaround:
  Do not override the default object file location.
SDSCM00035255 ALL Eclipse IDE S2 - Major Need scripting console function to set active build configuration
SDSCM00035339 ALL Eclipse IDE S2 - Major When CCSv4 Update Manager detects a new CCS update, there are very little details about what is actually contained in the update. At the very least, CCS should open up the release notes somewhere (there are all posted on external servers).
Workaround:
  Release notes are posted externally: http://tiexpressdsp.com/index.php/Download_CCS
SDSCM00035358 ALL Eclipse IDE S2 - Major Need ability to specify a startup JavaScript file that will execute on startup of CCS itself
SDSCM00035411 ALL Eclipse IDE S2 - Major Standard make project does not load .out file.
Workaround:
  Click on the load program or reload program buttons.
SDSCM00035448 ALL Eclipse IDE S2 - Major NPE in TargetConfigurationUtils during headless project creation
SDSCM00035451 ALL Eclipse IDE S2 - Major Headless proj-create: add support for pre-pending to list-type build-options
SDSCM00035474 ALL Eclipse IDE S2 - Major Project clean will delete entire folder contents of the active build configuration folder.
SDSCM00035490 ALL Eclipse IDE S2 - Major Build error during build when custom build steps are used.
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
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
SDSCM00034930 ALL Eclipse IDE S3 - Minor When the build-configuration in master project is switched, the currently active build-configuration in a dependent project is built first, then the referenced build-configuration is built.  The active build-configuration in the dependent project is built unnecessarily.
SDSCM00034999 ALL Eclipse IDE S3 - Minor The help documentation for the Scripting Console "saveRaw" command is missing information on one parameter.
Workaround:
  Below is the correct list of parameters for the "saveRaw" command:
  Parameters:
    address - is the first address in the block.
    page - the memory page. Use one of Memory.Page enumeration.
    filename - specifies the name of the file that will store the target data.
    length - the number of values to save.
    typeSize - specifies the type size of the data. Affects how data is byte-swapped to account for differences in host and target endianess. For example: if the target is big endian (the host is always little endian) and you specify nTypeSize = 16 then the upper and lower bytes are swapped after reading the data from memory - but before writing to disk.
    byteSwap - Force a byte-swap of the data before saving to the file. If Host and Target are difference endianess - this will effectively disable the automatic endianess conversion. 
SDSCM00035129 ALL Eclipse IDE S3 - Minor setDefaultTargetConfig Scripting Console command does not handle parentheses or bracket characters in the ccxml file name.
Ex: The below will fail because of the brackets in the file name
js:> setDefaultTargetConfig(64xpsim[LE].ccxml)
Workaround:
  Do not use parentheses or bracket characters in the file name
SDSCM00035142 ALL Eclipse IDE S3 - Minor If a ccxml file is copied, using a tool external to CCS, into the Target Configurations folder, CCS is not aware of this until the Target Configurations view is refreshed. Hence the setDefaultTargetConfig will fail if it is trying to access a ccxml file just copied into the folder and a refresh is not done.
It would be a good idea if setDefaultTargetConfig automatically refreshes the view before trying to access the file to avoid such any errors.
SDSCM00035010 ALL Eclipse IDE S3 - Minor Request to add keyboard shortcuts for assembly stepping.
SDSCM00035232 ALL Eclipse IDE S3 - Minor CCSv4 will generate some intermediate files like *.opt and *.mk and put it in the active configuration subfolder. This location is fixed.  The option to control the location of where these files are generated is desired.
SDSCM00035243 ALL Eclipse IDE S3 - Minor Would like an option in Target Configuration view's context menu to create a New Target Configuration
SDSCM00035313 ALL Eclipse IDE S3 - Minor Headless project-create: allow specifying multiple files with the copyFile and linkFile flags
SDSCM00035496 ALL Emulation - Drivers S2 - Major Enabling the profile clock claims a breakpoint resource. The issue is that this is not notified to the user and in instances where all HW breakpoint resources are used, it can silently disable one of the HW breakpoints, but the IDE does not reflect this (breakpoint appears to still be set). This can cause a lot of confusion. Disabling the clock also does not release the breakpoint resource in use. The debug session must be terminated.
SDSCM00034753 ALL Emulation - Drivers S3 - Minor When launching becomes unresponsive, dump all thread stacks and other information to a log file
SDSCM00035249 ALL Emulation - Hardware S1 - Critical When seeing errors with the LogicPD (EVM) OMAPL137 board and the XDS100v2 emulator, try enabling the Adaptive clocking mode.  In the Advanced setup tab of the Target Configuraiton, click on the emulator in the configuration tree, and choose "Adaptive with user specified limit" for the JTAG TCLK setting.  This mode helps resolve timing issues between the OMAP137 board and the XDS100v2 emulator. 
SDSCM00035492 ALL Installation S1 - Critical OMAPL138 Fails to connect after updating to CCS 4.1.1.  Works fine in CCS 4.0.
SDSCM00034832 ALL Installation S2 - Major Upon uninstalling CCSv4.1, I get prompted with a message that some files could not be deleted, and the uninstaller asks me whether I want to have these files removed.  If I select yes, it follows up with a message that uninstallation successfully completed.  However, the files were not removed; the program link under Program Files is also not removed.
Workaround:
  In order to fully complete the uninstallation, one has to:
   1. manually delete these ipc and xdais folders under Program Files \ Texas Instruments;
   2. remove CCSv4 installation through Add/Remove Programs;
   3. remove CCSv4 folder from C:\Documents and Settings\<my username>\Start Menu\Programs\Texas Instruments
SDSCM00034833 ALL Installation S2 - Major I installed a version of CCSv4.1.0, uninstalled it, then tried to install an earlier version.
The installer complained that I already had an existing version of CCSv4 and asked me to select another folder for installation.
There were no other versions of CCSv4 and all folders related to CCSv4 were removed (including removal through Add/Remove Programs).
Workaround:
  Two options:
  #1. Select a different folder than CCSv4 to install an earlier version.
  #2. Delete the InstallJammer registry (if not used by non-CCS programs) under Program Files; the installation will then proceed and complete properly.
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.
SDSCM00034172 ALL Installation S3 - Minor Windows driver locations are not consistent for XDS100 and XDS560.
Sometimes you have to manually locate the windows drivers to get an emulator like the XDS100 to install.  However the XDS100 driver location is not consistent with other drivers.  Essentially you have to do a search for *.sys and then hope that you know it is the FTDI driver.  It should be located in the same location as the XDS560 driver, i.e. under emulation and not buried in the common folder.
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. 
SDSCM00035581 ALL Trace Software S3 - Minor Trace Decoder cannot open .tdf files with swedish characters
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).
SDSCM00035487 ARM Debug Server S2 - Major Running LM Flash during a debug session can lead to a crash
Workaround:
  Terminate the debug session prior to launching LM Flash.
SDSCM00034736 ARM DVT Data Source 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.
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)'.
Workaround:
  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.
SDSCM00034635 ARM Emulation - Config Files S3 - Minor GEL_WatchAdd should not be in CortexM3_util.gel
SDSCM00033211 C2000 AET S2 - Major Breakpoint manager missing watchpoint option
View -> Target Config is setup for a blackhawk C2000 USB emulator, the board is configured for F28035.  (I also tried F2812)
View-> breakpoints:  Only has options for software, hardware, and profile control point. 
I do not see an option to set a data watchpoint - i.e. setup the analysis unit to watch for a data read/write to a particular address or to watch for a particular value written to a particular address. 
SDSCM00035811 C2000 DVT Data Source S2 - Major BIOS6 RTA project run interrupts unexpectedly while running on ezDSP F28335 w/ SD510 onboard emulator.

When you run an RTA project on the 28335 while it is connected via the onboard SD 510 emulator the program is unexpectedly stops, disconnects and an error shows up in the console:
C28xx: Error: Error 0xA0012080/-1250 Error during: Target Communication, Control, RTDX,  Device driver: Lost USB connection to emulator. You should ABORT and restart to re-establish the USB link. 
SDSCM00035813 C2000 DVT Solution S2 - Major RTA Specific Buttons not working correctly, toggling the buttons then resetting target causes CCS to Hang.

By default the only button that is enabled for the 28335 target is the "Stream RTA Data" button. When you run the program and then halt, "Enable RTA Continuous Refresh" button appears to be enabled. However, this doesn't actually correspond to the tooltips for this button. If the button is enabled the tooltips should read 'Disable RTA Continuous Refresh" if you want to negate the newly enabled option. When you toggle this button twice and then the tooltips works appears to coincide. If you disable the "RTA Continuous Refresh", only sometimes does it work where data will not stream into the view. Then once it is disabled it can never be enabled again; it always works as disabled and data will not be continually refreshed in the view. When the debug session is in that state if you press reset button in the debug view CCS hangs.
SDSCM00035825 C2000 DVT Solution S2 - Major CCS hangs on terminate after halting an RTA Program that has been running for a long time.
After collecting a large amount of data and then halting and terminating the debug session the IDE hangs for a couple of minutes.  From the users perspective it appears that the IDE has hung, only after a few minutes have elapsed does the IDE return to the C perspective.
SDSCM00035427 C2000 Eclipse IDE S2 - Major CCS gets confused between the F28x and CLA on F28035.
Workaround:
  Open your target configuration
  Click on advanced at the bottom
  Select the CLA
  Check the box to bypass
  Save the target configuration file
SDSCM00035500 C2000 Eclipse IDE S2 - Major Add time calculation to profile clock display
SDSCM00035502 C2000 Eclipse IDE S2 - Major Persist Auto/Manual setting for profile clock
SDSCM00035555 C2000 Eclipse IDE S2 - Major Double clicking on a global variable in the modules view results in an error on multi-page device
Workaround:
  Remove the "@Data" after the address in the memory view.
SDSCM00035593 C2000 Eclipse IDE S2 - Major Want to be able to pin context of disassembly view
Workaround:
  It is possible to open multiple top level CCS windows.  1 for each core.  In the debug view right click on one of the cores and select "Debug in new window".
SDSCM00035637 C2000 Eclipse IDE S2 - Major Update rate of variables in watch window is too slow
SDSCM00035689 C2000 Eclipse IDE S2 - Major The memory window does not allow formatting the value display in Q formats higher than Q15.
This is particularly useful to display lookup tables stored in ROM memory and typically available in the C2000 family, but can potentially be useful in other device families.
Workaround:
  There is no practical workaround available.
  Although the Watch window can display any Q value, it is not practical to access the ROM tables on the C2000 devices. 
SDSCM00035113 C2000 Eclipse IDE S3 - Minor CCS project build not tracking file dependencies correctly in specific use case
CCS is not tracking file dependencies when doing an incremental build properly when files have been conditionally included into the source file using #ifdef.  Here is the situation:
***FILE: MyInclude.h
#define FOO
***FILE: main.c
#ifdef FOO
  #include "file1.c"
#else
  #include "file2.c"
#endif
The first thing that happens is that only MyInclude.h and file2.c appear in the project window in CCS.  File1.c does not appear.  The bigger problem is that changes to file.c do not cause main.c to get rebuilt if an incremental build is performed.
The problem seems to be the #ifdef.  If you define FOO with a value (e.g., #define FOO 1) and then do #if FOO == 1 in the main.c, the project manager lists all three include files (MyInclude.h, file1.c, file2.c) and everything works correctly with incremental build.
Workaround:
  Workaround is to use #if instead of #ifdef.
SDSCM00034620 C2000 Emulation - Drivers S2 - Major CCS v4.0x allows user to set only 1 hardware breakpoint when debugging BIOS programs in Flash
SDSCM00035554 C2000 Licensing S2 - Major To use the on-board parallel port emulation on the eZdsp F2812, you need to use the "Spectrum Digital XDS510 Parallel Port-PCI Emulator" connection type. However, that connection type is not covered with the bundled license.
SDSCM00034673 C2000 Scripting S2 - Major CCS v4.0x allows user to set only 1 hardware breakpoint when debugging BIOS programs in Flash
SDSCM00035643 C5000 Eclipse IDE S1 - Critical Register window A and B don't work properly for 54x devices
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).
SDSCM00035279 C6000 C6000 Sim-Features S2 - Major Port Connect to McBSP is not supported on C64x+ device simulators. Affected simulators - C6424, C6421, C6455, C6454, C6474, c6487, c6488, dm6437, c6484, dm6446 & dm64443.
SDSCM00034560 C6000 C6000 Sim-Source Components S2 - Major VCP2_statRun() CSL API doesn't initialize the VCP2 model on simulator.
SDSCM00035452 C6000 Debug Server S2 - Major If you right-click on variable in the Local or Watch views and choose "Open Memory View at this Object's Address", it will sign extend the value to a 64-bit value before evaluating. This will be a problem if the most significant bit of the variable is set (ex. address >=  0x80000000 on 32-bit int).  Ex: 0x80000000 turns into 0xFFFFFFFF80000000
Workaround:
  Delete the leading F's from the address from the Address Text in the Memory view.
SDSCM00035008 C6000 DVT Solution S1 - Critical When the Trace Analyzer is opened and viewing a trace file that CCS crashes when re-loading a program on the target.
The .out file appeared to be 170 MB in size. 
The crash would not occur if the Trace Analyzer was not opened.  The customer attempted a 10 program re-loads via the GUI and ~45 via DSS without issue.  For that reason, it's thought that the issue may lie within the realm of the Trace Solution.
SDSCM00035169 C6000 DVT Solution S3 - Minor Trace Analyzer cannot open .tdf files with swedish characters
SDSCM00034625 MSP430 Debug Server S3 - Minor Need ability to erase/program each information memory segment on MSP430 independently. 
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.
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.
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
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".
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.
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.
SDSCM00035143 MSP430 Eclipse IDE S2 - Major Start a CCS terminal window and open a terminal connection using the EXP board using the attached code example, the MSP-EXP430F5438 and a USB <> mini-USB cable. Then unplug the cable. CCSv4 crashes.
Workaround:
  Do not unplug the cable while CCS is running. 
SDSCM00035534 MSP430 Eclipse IDE S2 - Major Can't save CCXML configuration
SDSCM00033899 MSP430 Emulation - Drivers S2 - Major When trying to connect to a running target, the "Launch TI Debugger" menu item in CCS v4 always resets the target even if the settings "Reset the target on connect" and "Reset the target on program load or restart" are unchecked.  This works when using "Debug Active Project" but not when using "Launch TI Debugger".
The following are the Debug Properties set under Project->Debug Properties->Target Tab->Generic Debugger Options:
  Run to : remove main
  Uncheck: "Reset the target on connect"
  Uncheck: "Reset the target on program load or restart".
This should allow you to run the program, optionally halt, terminate session, do "Debug Active Project" and re-connect 
SDSCM00033937 MSP430 Emulation - Drivers S3 - Minor Register xml files are missing some MSP430 module registers.
Using the USCI_A0 in SPI mode, the CCE register view does not show the registers UCA0IE, UCA0IFG, and UCA0IV listed under USCI_A0_SPI mode for MSP430F5437 . This is true for UCA1 AND UCA2 as well. Only the UCBx registers show those 3 registers. But these registers do show up under USCI_A0_UART_Mode.
However since USCI_A0 can be used in either UART or SPI mode, the registers should be visible in both modes.
In IAR toolset, they show up under both modes.
Please refer to files USCI_A0__SPI_Mode_2.xml and USCI_A0__UART_Mode_2.xml in C:\Program Files\Texas Instruments
Workaround:
  Manually add this to the xml file.
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.
SDSCM00035633 OMAP Debug Server S2 - Major If a system reset is issued from a core where any target under the same router as that core, including itself, is not connected, the debugger will not be able to accurately detect status changes on any core in the system.  This may manifest as the target not halting at a breakpoint where it would be expected to halt, but then being at that breakpoint when the user later hits halt.
Workaround:
  This can be worked around by bypassing targets that will not be used in the setup ccxml file, or by connecting every target
SDSCM00034660 TMS470 Eclipse IDE S3 - Minor CCS4.1 build does not 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.