- Important information
- New features
- Known problems
- Program corrections
- User guide corrections
- Miscellaneous
- Release history
Important information
-
Assume a debug scenario where the device is put into low power (sleep) mode, be aware that the debugger will then loose the communication with hardware thus making the debugging error-prone. To avoid this, make sure to deactivate code which puts the device into sleep mode before you debug it.
New features
- None
Known Problems
-
EW18593
It is not possible to set breakpoints when using preprocessed C source code with #line statements unless you write the absolute path for the file e.g: #line 3 "c:\\path\\file.c"
Program Corrections
- None
User guide corrections
- None
Miscellaneous
- Nothing
Release history
8.20.1, Oct 2012
New features
- None
Program corrections
EW23069
If stopped at a breakpoint, the driver will now always execute a step instruction before continuing execution to ensure that the driver does not immediately gets stuck at the same breakpoint again.
8.11.1, Feb 2012
New features
- None
Program corrections
- None
8.10.4, Dec 2011
New features
- None
Program corrections
- None
8.10.3, Sep 2011
New features
- None
Program corrections
EW22582
You could not specify ranges of pages for the "Retain flash pages option".EW22645
The debugger whatch window displays incorrect values for variables in PDATA/XDATA memory.EW22649
The debugger memory window displays incorrect values for memory cells in PDATA/XDATA memory.
8.10.1, May 2011
New features
-
Support has been added for the CC2540 device family.
Program corrections
EW22134
Attempting to view memory mapped SFR registers in C-SPY for certain devices would result in lost communication with the hardware. This has been corrected.EW22157
The default bank mask value was not correct for certain TI/CC devices; this has been corrected.EW22278
It is now possible to specify a flash page number greater than 64.
V7.60.4, August 2010
EW21926
Support for handling --ks_version reenabled.
V7.60.1, June 2010
Support has been added for the CC25xx device family. The options dialog for this driver has also been modify to accomodate for the different mechanism used for protecting flash memory for these devices. Flash pages that are to be protected should be specifies as a string of decimal caracters, according to the example provided in the options dialog.
V7.51A, March 2009
No changes.
V7.50A, June 2008
No changes.
V7.40A, Feb 2008
The driver was renamed from "Chipcon" to "Texas Instruments" in all IDE dialog boxes.
V7.30B, September 2007
-
An error was corrected that could cause a page being written to flash to partially overwrite a previously written page with garbage data.
7.21A, May 2007
-
Flash protection (boot block, debug inteface and page) added.
-
Retain memory pages added. Pages to be retined should be entered on the form 1,2,3,4....62,63. To retain IEEE address "IEEE" can be entered.
-
Mapping SFRs and XDATA to CODE memory when using unified memory access could sometimes cause inadvertent reads of registers that use hardware clearing.
7.20H, Nov 2007
-
Better support for the latest revision of CC2430.
-
The driver has been updated in order to improve overall stability.
-
The Chipcon driver dialog window has been updated with improved logic to handle checkbox options.
7.20D, May 2006
-
A new menu option, Leave target running, has been added in the Chipcon debug menu. Selecting this option will leave the target system running when the debug session is closed.
-
The FMAP register was erroneously overwritten when execution was stopped. This could cause problems if execution was stopped while running in an interrupt or library routine.
7.20C, January 2006
-
Smaller update of the debuggers has been done for this release. Most updates have been done to improve the stability and speed of the various debuggers.
7.20A, October 2005
Initial release.