| Version 2.1 (R2006b) Link for Code Composer Studio Development Tools Release Notes | |
This table summarizes what's new in V2.1 (R2006b):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| Yes Details below | Yes—Details labeled as Compatibility Considerations, below. See also Summary. | Bug
Reports | Printable Release Notes: PDF |
New features and changes introduced in this version are described here.
Added CCS 3.2 for the C64x+ and C67x+ processor families
Continuing support for CCS 3.1 (C6000, C5000, C2000, Rxx, OMAP processor families)
Additional or continuing compatibility considerations are listed in Compatibility Considerations.
To complement the function objects and createobj in the product, this release includes a new demo that introduces a demonstration function call block — "Comparing Simulation And Target Implementation Through Function Call." You use the block in a Simulink model to identify and run a function on your target. The ability to communicate between Simulink and your target lets you run models that exercise functions and algorithms that reside on your target, and move data back and forth between MATLAB, your Simulink model, and your target-based process. Refer to the demos for Link for Code Composer Studio in MATLAB to find and run the new demo.
A Simulink-based demo featuring the Debug component that shows how you use the debug methods to work with targets.
C64x+ and C67x+ processor families supported by all demos.
The compatibility considerations from the Version 2.0 release (R2006a+) remain applicable as shown here.
The following issues reflect changes to the support provided by Embedded IDE Link CC:
The product no longer supports the RTDX-based demos on the C54x simulator and on C6701 processor-based hardware. These include
Real Time Data Exchange Tutorial
LMS Adaptive Filtering
Transferring Data Between Simulink and a Target Application
When you use the C54x simulator, the disp method does not display the correct processor type for your target. The property revfamily is set to an improper processor revision.
When you use the C6713 Device Cycle simulator, the disp method does not display the correct processor subfamily identifier. The property subfamily is set to an improper processor subfamily value of 100 instead of 103.
If you use the C6713 processor with a USB connection, RTDX communications does not work when you launch Code Composer Studio from Embedded IDE Link CC. To work around this problem, launch CCS manually from Microsoft Windows.
With the C2808 processor as your target, you cannot enable more than one RTDX read channel from the host-side application. In some cases, enabling one channel from the host disables a previously enabled channel. To work around this problem, enable the RTDX channels programmatically in the C2808 application code.
The product no longer support the Debugging a Target Application demo (ccsdebugdemo) on TMS470R2x hardware.
When you launch CCS by issuing the command cc=ccsdsp at the MATLAB prompt, and then you use any DSP/BIOS plug-in or the profile function, you encounter an error that says vbd.dll could not be loaded. Work around this by opening CCS manually before you use ccsdsp.
When you use open to open a project in a CCS IDE window and the project is already open in another CCS IDE window, Embedded IDE Link CC returns a time-out error in MATLAB. You can avoid this error by
Opening the project in a new CCS IDE window manually.
Closing the existing project in the other IDE before you open the new instance of your project.
| Version 3.0 (R2007a) Link for Code Composer Studio | Version 2.0 (R2006a+) Link for Code Composer Studio Development Tools | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |