Chapter 1. Target Devices Chapter 2. User's Manuals Chapter 3. Uninstallation Chapter 4. Changes... 5

Transcription

1 R20UT3981EJ0100 Rev.1.00 Contents Chapter 1. Target Devices... 2 Chapter 2. User's Manuals... 3 Chapter 3. Uninstallation... 4 Chapter 4. Changes... 5 Chapter 5. Points for Caution... 9 Chapter 6. Restrictions R20UT3981EJ0100 Rev Page 1 of 19

2 Chapter 1. Target Devices The target devices supported by the CS+ are listed on the Website. Please see this URL. CS+ Product Page R20UT3981EJ0100 Rev Page 2 of 19

3 Chapter 2. User's Manuals Please read the following user s manuals along with this document. Manual Name CS+ V Installer CS+ V Editor CS+ V Python Console CS+ V Updater CS+ V Message CS+ V Project Operation CS+ V Analysis Tool CS+ V RH850 Debug Tool CS+ V RX Debug Tool CS+ V RL78 Debug Tool CS+ V GHS CCRH850 Build Tool Operation Document Number R20UT3094EJ0100 R20UT3625EJ0100 R20UT3932EJ0100 R20UT3942EJ0100 R20UT3952EJ0100 R20UT3928EJ0100 R20UT3461EJ0100 R20UT3941EJ0100 R20UT3940EJ0100 R20UT3939EJ0100 R20UT3829EJ0100 * GHS: Green Hills Software, Inc. R20UT3981EJ0100 Rev Page 3 of 19

4 Chapter 3. Uninstallation There are two ways to uninstall this product. Use the integrated uninstaller from Renesas (uninstalls all CS+ components) Use the Windows uninstaller (only uninstalls this product) To use the Windows uninstaller, select the following from the Control Panel: Programs and Features Then select [CS+ for CC]. R20UT3981EJ0100 Rev Page 4 of 19

5 Chapter 4. Changes This chapter describes changes from V to V Function improvement of CS Support for new emulators CS+ now supports the following new emulators. You can now use these emulators in combination with CS+ to develop programs for the given types of target MCU. E2 emulator (for RH850 devices) E2 emulator Lite (for RX and RL78 devices) Enhanced facility for utilizing existing projects You can use a C source code converter to convert existing projects for the CA78K0R compiler (for the RL78 family and 78K0R group) into projects for the CC-RL compiler (for the RL78 family). The converter will no longer handle any files automatically output by V and later versions of CS+ when projects are created. For this reason, no comments from the converter are output on the first lines of files automatically output by CS Improved login to MyRenesas Logging in to MyRenesas from CS+ from environments with authentication by a proxy is now possible. This means you can use the Smart Browser (for which login to MyRenesas is required) even in such environments Fix of the caution, when using RI850V4 V2 in combination CS+ for CC [RH850] The Following caution has been fixed. RI850V4 V2 does not operate normally. 4.2 Additions to the build tool Support for new versions of compilers Support for the following versions of compilers has been added in V of CS+. CC-RH V CC-RX V CC-RL V Function improvement to the debug tool Addition of the simulation of current drawn by the RL78/G10 [RL78] In addition to the simulation of peripheral modules in the RL78/G10, V supports the simulation of current drawn by the device even when an actual MCU (on a board) is not connected. You can use a Python function to view the results of this simulation Addition of the simulation of peripheral modules in the RL78/G12 [RL78] V supports the simulation of peripheral modules in the RL78/G12. You can thus simulate the operation of the MCU even when an actual MCU (on a board) is not connected. R20UT3981EJ0100 Rev Page 5 of 19

6 4.3.3 Fix of the note on using the P125/KR1/SI01/RESET and P11/ANI17/SI00/RxD0/SDA00 pins of the IECUBE for RL78/G12 group [RL78] The following caution has been fixed. (1) P125/KR1/SI01/RESET pin When the P125/KR1/SI01/RESET pin is used for any of its multiplexed functions, the on-chip pull-up resistor always becomes ineffective. (2) P11/ANI17/SI00/RxD0/SDA00 pin The P11/ANI17/SI00/RxD0/SDA00 pin is not usable for the P11, SI00, RxD0, and SDA00 functions Improvement of trace data output [RL78 IECUBE, Simulator] [RH850 Simulator] Large amount of trace data output processing has been improved. 4.4 Function improvement to the Python console Python functions supporting a new MCU Support for the RL78/G10 by the following Python functions has been added. Function Name debugger.currentconsumption.clear debugger.currentconsumption.disable debugger.currentconsumption.enable debugger.currentconsumption.get debugger.currentconsumption.information Functional Overview Clears data on current drawn that have been acquired. [RL78/G10, RL78/G13] [Simulator] Disables the acquisition of data on current drawn. [RL78/G10, RL78/G13] Enables the acquisition of data on current drawn. [RL78/G10, RL78/G13] [Simulator] Displays the maximum and average values of data on current drawn that have been acquired. [RL78/G13, RL78/G10] [Simulator] Displays data on current drawn that have been acquired. [RL78/G10, RL78/G13] [Simulator] Addition of parameters and return values for Python functions The debugger.debugtool.change function has the following new parameters. Parameter Description DebugTool.E2 E2 Emulator DebugTool.E2Lite E2 Emulator Lite The debugger.debugtool.gettype function has the following new return values. Return value Description E2 E2 Emulator E2Lite E2 Emulator Lite Support by Python functions for a new emulator The following Python functions now support the E2 emulator. Function Name debugger.performance.delete debugger.performance.disable debugger.performance.enable Functional Overview This function deletes a condition of performance measurement. This function disables performance measurement. This function enables performance measurement. R20UT3981EJ0100 Rev Page 6 of 19

7 debugger.performance.get debugger.performance.information debugger.performance.set debugger.pseudoerror.clear debugger.pseudoerror.get debugger.pseudoerror.setgo This function references the result of performance measurement. This function displays performance measurement information. This function sets performance measurement. This function clears the error status of all pseudo-errors. This function references ECM error information. This function sets conditions of a pseudo-error and runs a program Python class supporting a new MCU Support for the RL78/G10 by the following Python class has been added. Class Name CurrentConsumptionInfo Class Overview This class holds information on current drawn. [RL78/G10, RL78/G13] [Simulator] Support by Python classes for a new emulator The following Python classes now support the E2 emulator. Class Name Class Overview PerformanceCondition This class creates conditions of performance measurement. PerformanceEventInfo PerformanceInfo PseudoErrorCondition PseudoErrorInfo This class holds performance measurement event information. This class holds performance measurement information. This class creates a pseudo-error condition. This class holds ECM error information Addition of Python properties for debugging tools The following Python properties for debugging tools have been added. Property Name Property Overview debugger.option.accumulatetracetime This property is used to specify whether or not to accumulate trace time tags. [Simulator] debugger.option.tracebranchpc This property is used to specify whether or not to acquire the addresses of instructions at the origins and destinations of branches during program execution. debugger.option.tracedataaccess This property is used to specify whether or not to acquire trace data on events that involve access during program execution Changes to the names of Python properties The names of the following Python properties for debugging tools have been changed. Before After PerformanceItem.IfuFetchRequestHit PerformanceItem.CpuFetchRequestHit PerformanceItem.IfuFetchRequest PerformanceItem.CpuFetchRequest 4.5 Additions to the I/O header generation tool Addition of a facility for separating comments from generated files [RH850] V of CS+ supports the output of IOR List comments, which were formerly always output to files generated by the I/O header generation tool, to separate files. This will reduce the sizes of the actual header files output by the I/O header generation tool. It is possible to enable the facility by adding [-iorlist=off] to [Oher additional options] in [Ohers] R20UT3981EJ0100 Rev Page 7 of 19

8 4.5.2 Addition of a facility for generating a macro for the target MCU [RL78] V of CS+ supports the definition of macro names that correspond to specified device information files for RL78 devices. The macro names are the same as those defined by the CA78K0R C compiler for the RL78 family and 78K0R group. This will reduce the amount of work required for porting source files from CA78K0R to CC-RL. R20UT3981EJ0100 Rev Page 8 of 19

9 Chapter 5. Points for Caution This section describes points for caution regarding CS Points for caution regarding CS+ (general) File names The following rules apply to folder and file names. Folder and file names Do not use folder or file names that cannot be created from Windows Explorer. Source file names, load module file names, and project file names File names consist of the characters a-z, A-Z, 0-9, the period (.), the underscore (_), plus sign (+), and minus sign ( ). File names cannot start or end with a period (.). Filenames cannot start with a plus sign (+) or minus sign ( ). CS+ is not case-sensitive to file names. File names may have up to 259 characters, including the path. Do not use source files with the same file name. Even if they are on different paths, CS+ cannot classify them. File names other than the above File names comply with Windows conventions. Note that the following characters cannot be used in file names. \ / : *? " < > ; File names cannot start or end with a period (.) or space. CS+ is not case-sensitive to file names. File names may have up to 259 characters, including the path. Folder names Folder names comply with Windows conventions. Note that the characters below cannot be used in file names. ( ), = Panel display If your hardware environment does not meet the recommended specifications for CS+, the [Property] panel may appear small and have scrambled contents. If this happens, move the [Property] panel outside the split panel area. Enable [Dockable], and make it a docking panel Enable [Floating], and make it a floating panel User Account Control (UAC) function (Windows Vista, Windows 7) If the UAC function is disabled on Windows Vista or Windows 7, then if a user without administrator privileges creates a project, and no Device Dependence Information is installed, installation of the Device Dependence Information will begin, but the installation will fail. If the UAC function is disabled, create projects after logging in with administrator privileges Problem with a Windows update program Your computer may suffer a "blue screen" error if you apply the KB patch published by Microsoft Corporation. If this error occurs, please apply the patch provided by your computer's manufacturer or another source Renesas Electronics real-time OS If you use the real-time operating system for the RX family provided by Renesas Electronics, install CS+ in a folder and path where the names contain no parentheses. If you install it under the 64-bit version of Windows, it will be installed in the "Program Files (x86)" folder by default, and since the folder path includes parentheses, this will produce an error. R20UT3981EJ0100 Rev Page 9 of 19

10 5.1.6 Changing microcontrollers Note the following points for caution when changing the microcontroller. The microcontroller can only be changed to another within the same family, since this will correspond to the same build tool (RH850, RX and RL78). When changing the microcontroller, do so while the debugger is not connected. Save the project before changing the microcontroller. Information on pin layout (design tool), code generation (design tool), and debugging (except for watch registration information) are not carried over after the microcontroller has been changed Plug-in Manager function We recommend that the checkbox for the plug-in for the microcontroller that is the target for development is not deselected on the [Basic Function] tabbed page of the [Plug-in Manager] dialog box. Deselect the checkboxes for the build tool and debugging tool plug-ins that are for microcontrollers that are not the target for development. For example, if only the plug-in for the build tool is deselected, the file to be downloaded by the debugging tool will not be found and an error will occur [Editor] panel The [Page Setup] dialog box is not available. Although there is a [Copy] button on the [Print Preview] toolbar, it does not work. When a variable or label is selected and the Jump to Function feature is used from the context menu, execution does not jump to the variable or label. The Jump to Function feature will not jump to a static function defined in another file. The following notes apply to the editor, when source files with the same name but from different folders are registered with a main project and a sub project, and load modules from both the main project and sub project are downloaded. The address of the main project is displayed on the file. At jumping to a source file from disassembled code, the file registered with the main project is opened. If the file is opened from either project, only one file will be opened. The smart edit function does not work correctly for a structure that does not have a name. If the arguments of a function include a function call, incorrect information will be displayed in the tooltip. Names of member variables and functions are not correctly supplemented by the smart edit function in arrays of classes and of pointers to classes. Supplementation does not produce appropriate strings even if a part of a member name is entered and 'ctrl + (space)' is also entered. Outlining (collapse/expand) only works with files that have been registered with the project. Any files that have not been registered with the project will not be outlined in the [Editor] panel of CS+. On Windows 8.1, the display may become unclear due to anti-aliasing. In mixed display mode, if a line number is specified for a jump, the disassembled code is inserted and displayed, so the specified line may not be displayed on the screen. If a structure is nested, the smart edit function does not work on the third and subsequent stages. In addition, information is not displayed in the tooltip. For the first line of code immediately after #ifdef - #endif, the smart edit function does not show candidate members. In addition, no tooltip is displayed. For the first variable in #ifdef - #endif, the smart edit function does not show candidate members for the code after #endif. In addition, no tooltip is displayed. When a file not included in a project is opened, a bookmark is set, the project is closed, the setting for the bookmark in the file is changed, the project is opened again, and the [Bookmarks] dialog box is opened, the dialog box will display the bookmark with the setting when the project was closed while the source window displays the bookmark with the new setting that was made after the project was closed. That is, different settings are displayed for the bookmark in the dialog box and source window. In such cases, close the file and then open it again. The display of the bookmark in the [Bookmarks] dialog box will then reflect the display in the source window. When the rectangular selection tool (obtained by holding the Alt key down and then using the mouse to select an area) is used and the selected area is pasted to add lines in and after the last line, the selected area is pasted from the beginning of the line after last regardless of the location specified for pasting. Insert spaces after pasting as required. When saving a file in the [Save As] dialog box, the extension listed at the top of the [Save as type] drop-down list is automatically added unless another extension is specified. Note however, that an extension is not added when a file name is input with an extension that is selected in the [Save as type] drop-down list or with an extension that is registered with Windows. When an automatically added extension is not as expected, modify the name of the file by using, for example, Explorer. When inputting to [file type] combo box of the [Find and Replace] dialog directly, input only a wildcard of R20UT3981EJ0100 Rev Page 10 of 19

11 the file name. (For example) *.c; *.inc; *.asm CS+ searches or replaces for a specified character string as the file name. (For example) Source files(*.c; *.inc; *.asm) It is recognized as the file name including "Source files(". Printing the contents of the Editor panel is not possible in an environment with.net Framework 4.6 installed. To do so in that case, use an editor other than that of CS Conversion from PM+ to CS+ projects CS+ cannot read CA850 projects made by PM+ V6.00/V6.10/V6.11 then the Build Mode has been newly added. Handling by CS+ is as follows. (1) When [Debug Build] or [Release Build] is specified, information on the added Build Mode cannot be read. (2) When the added Build Mode is specified, it leads to an error. [Workaround] Use V6.20 or a later version of PM+ to read the project, save it, then read the project into CS Debugging tool settings during project appropriation When you create a project by appropriate settings from another project, only the settings for the default debugging tool will be imported. In the RX family, however, internal processing is common to the emulator and simulator, so the settings are imported regardless of which debugging tool is selected Help If you close the help while the Search tab is being displayed and you then open the help again and display the [Contents] tab, the Compiler and Build Tool Operation sections may disappear. If this happens, close the help while the [Contents] tab is being displayed, and then open the online again Changing the target device during the process of converting a project When the target device is changed in the [Project Convert Setting] dialog box while it is open for conversion of a project created by using the High-performance Embedded Workshop, PM+, or an earlier version of CubeSuite, the value chosen in [Kind of project] is returned to the default value (top type in the combo box). For example: The setting for [Kind of project] changes to the default type (for example, [Application]) when the device selection is changed Converting CA78K0R projects for use with CC-RL In converting projects created by using CA78K0R to projects for use with CC-RL, conversion will not proceed if the destination folder already contains files with the same names as those of the files to be output. Check that there are no such files in the destination folder before using the converter Converting High-performance Embedded Workshop projects Attempting to load a High-performance Embedded Workshop project into the CS+ under certain conditions may not be possible, or may lead to an error during conversion or building of the project. (1) Converting a High-performance Embedded Workshop project to make it compatible with the CS+ fails when any of the following conditions is satisfied. No toolchain from Renesas Electronics Corp. is selected for the project. The project contains no tps file for use in setting up the High-performance Embedded Workshop environment (the tps file is automatically created when the project is opened through the High-performance Embedded Workshop). To avoid this problem, you should open the project through the High-performance Embedded Workshop once before starting conversion. The project contains multiple CFG files, each of which is used to set up a realtime OS from Renesas Electronics Corp. (2) Converting a High-performance Embedded Workshop project to make it compatible with the CS+ succeeds but building of the project leads to an error when any of the following conditions is satisfied. Placeholder $(TCINSTALL) is used in the project. (TCINSTALL) remains in the project even after conversion but the CS+ does not recognize R20UT3981EJ0100 Rev Page 11 of 19

12 $(TCINSTALL). Placeholder $(TCINSTALL) that has been used as a parameter for [Options] in the High-performance Embedded Workshop is simply passed to the CS+ and may cause an unintended result (e.g. an error) upon building of the project. For this reason, you should manually change $(TCINSTALL) after converting the project. Placeholder $(WORKSPDIR) is used in the project. If you select a HEW project file (with extension hwp) in the CS+, this is automatically converted to %ProjectDir%\.. (the directory above the project directory). An error may occur during building of the project if the workspace does not exist in the directory indicated by %ProjectDir%\... For this reason, you should manually change %ProjectDir%\.. after converting the project. A custom build phase is used in the project. Since all custom phases are deleted upon conversion, an error may occur during building of a project that involved a file output created for a custom build phase in the High-performance Embedded Workshop. After converting the project, register the custom build-phase command with the CS+ as a command to be executed before or after each phase as required. A custom placeholder is used in the project. Custom placeholders are not converted because the CS+ does not recognize them. Any custom placeholder that has been used as a parameter for [Options] in the High-performance Embedded Workshop is simply passed to the CS+ and may cause an unintended result (e.g. an error) upon building of the project. For this reason, you should manually change the custom placeholders after converting the project. (3) Other (a) $(FILEDIR) is converted to %FileDir%. Leaving %FileDir% as it is when the pathname is edited in the [Path Edit] dialog box will lead to the following error: The specified path contains a non-existent folder. (W ) Edit the pathnames and replace %FileDir% with another placeholder or directory name. (b) $(WINDIR) is converted to %WinDir%. (c) The order in which folders are displayed in CS+ may differ from that in the High-performance Embedded Workshop. (d) If a High-performance Embedded Workshop project for which downloaded files have been specified is loaded into CS+, CS+ will show these files as the second and subsequent items in the list of downloaded files for each debugging tool. (e) The compiler option -output=src is converted to output=obj (default). (f) If you load a library project that has been linked to the standard library into CS+, the linkage setting will be discarded (this is indicated in the log information that is output as a result of loading the project). (g) If [Use an existing library file] has been selected for the library generator in the High-performance Embedded Workshop, the setting is changed to [Do not add a library file] in CS+. For this reason, linking with the specified library will not proceed (this is indicated in the log information that is output as a result of loading the project). (h) Option settings that were made on the [Toolchain Option] tabbed page of the High-performance Embedded Workshop are not converted but discarded (i.e. they are not moved across to CS+). (i) If a sub-command file has been selected for the linkage editor in the High-performance Embedded Workshop, the [Use external subcommand file] setting is discarded when the project is loaded into CS+. The linkage editor options will have their default settings. (j) Any files specified with the -library, -input, or -binary option will not be listed in the [Link Order] dialog box. The result is that the order of linkage for these files will not be selectable. (k) RTOS configuration files will not be displayed under the [Configuration file] category node after the project is loaded into CS+. (l) RTOS option settings that were made in the High-performance Embedded Workshop are discarded. RTOS options will have their default settings in CS+. (m) The build mode for RTOS projects will be "DefaultBuild" after the project is loaded into CS+. You will need to change the build mode as required. (n) The order of linkage of the assembly output files (ritbl.obj) for an RTOS project will differ from that in the High-performance Embedded Workshop Creating new projects Applies to: RX If a new project is created by selecting [Empty Application[CC-RX]] under the environment for the RX, building the project may lead to the following errors. ** L2132 (E) Cannot find "D" specified in option "rom" ** L2132 (E) Cannot find "D_1" specified in option "rom" ** L2132 (E) Cannot find "D_2" specified in option "rom" If you encounter these errors, change the setting of [ROM to RAM mapped section] on the [Link Options] sheet in CS+. R20UT3981EJ0100 Rev Page 12 of 19

13 Microsoft IME If you are using Microsoft Office IME 2010, which is included in Office 2010 from Microsoft Corporation, CS+ may output error E Since Microsoft Office IME 2010 may have caused this problem, replace it with Microsoft s standard IME or install the KB module provided by Microsoft Corporation to fix Microsoft Office IME Tutorials The Code Generator Plug-in, Pin Configurator Plug-in and Program Analyzer Plug-in are used in tutorials. Enable them through the [Plug-in Manager] dialog box Starting multiple instances of CS+ Two or more instances of CS+ can be started on the same host machine, but if you do so, take note of the points listed below. When two or more instances of CS+ are started, the most recent information to have been written is saved in the information file for each user s own PC. When two or more instances of CS+ are started, the most recent information to have been written is saved in the information file for the stack analysis tools (including CallWalker). When the same project file is used in two or more instances of CS+, the most recent information to have been written is saved. When the same project file is used in two or more instances of CS+, do not attempt building from more than one instance at the same time since the names of the output files will be identical Smart Browser Applies to: RH850 When an RH850 project is opened, Smart Browser does not display the contents of user's manuals and sample code in some cases Loading projects by using earlier versions of CS+ If the version of CS+ being used to load a project is earlier than the CS+ version with which the project was created, some settings may be cleared since the earlier versions of CS+ do not recognize them Mentions of R8C in user s manuals and online help R8C is mentioned in the user s manuals and online help, but CS+ does not support the R8C family. 5.2 Points for caution regarding design tools Changing packages If you change the package name in the pin layout properties, the data input in the device top view and device pin list will be cleared Saving projects If you save a project that has sub-projects while the [Device Top View] or [Device Pin List] panel is open, then the device top view and device pin list of the last sub-project in the Project Tree will always appear. 5.3 Points for caution regarding debugging tools The abbreviations listed below collectively denote the corresponding tools in this section. OCD (serial): E1 Emulator (serial), E20 Emulator (serial) OCD (JTAG): E1 Emulator (JTAG), E20 Emulator (JTAG) Low-power consumption modes When a forced break occurs in a low-power consumption mode (e.g. sleep, stop, or standby) or an instruction that makes the CPU enter a low-power consumption mode is executed during stepped execution, the behavior of the simulator and the emulator will differ as follows. Emulator: The forced break leads to release of the CPU from the low-power consumption mode. Furthermore, the CPU will enter the low-power consumption mode during stepped execution. Simulator: Transitions to low-power consumption modes (e.g. by a register setting) are not supported. Executing a WAIT instruction causes a break, with the PC placed at the address of the next R20UT3981EJ0100 Rev Page 13 of 19

14 instruction. During stepped execution, the CPU does not enter the low-power consumption mode and the PC is placed at the address of the next instruction Traces over desired intervals Applies to: Simulator for all devices If you perform a trace from a trace start event until a trace end event, the simulator will not include the trace end event in the results of the trace. For this reason, if you are using a simulator, set the trace end event one line below the range for which you require display of the trace data Adding sub-projects Applies to: Common to all debugging tools and devices If you add a sub-project while a debugging tool is connected, downloading and so on may fail. Only add sub-projects while the debugging tool is disconnected Breakpoints and other settings becoming invalid Applies to: Common to all debugging tools and devices If you use leading underscores to differentiate function or variable names, the debugger may recognize them incorrectly and change the symbols or invalidate breakpoint settings. This applies in cases such as when you have two functions, one named _reset and the other named reset Two or more variables having the same name When two or more variables are defined with the same name in unnamed name spaces of different source files, the [Watch] panel only shows the information on the first variable to be found Member-variable pointers After the member-variable pointer "mp1" defined in the program below is registered with the [Watch] and [Local Variables] panels, the type of the pointer is indicated as "int *", not "int Foo::*". class Foo { int m1; }; int Foo::*mp1 = &Foo::m1; Assigning unions to registers When a union is assigned to a register, it is assumed that the members of the union are assigned to the lower-order bytes of the register. For this reason, the values of the members will be incorrect when displayed as big endian Functions with the same name and char-type parameters When three functions with char-type parameters are defined as shown below, the address of "Func(signed char)" will not be displayed (i.e. the address of "Func(char)" will be displayed instead). void Func(char); void Func(signed char); void Func(unsigned char); Char-type one-dimensional arrays When a char-type one-dimensional array is assigned to multiple locations in registers or memory as shown below, no character string will be displayed in the value column of the [Watch] or [Local Variables] panel even after the array "array" has been registered with the panel. char array[5] = "ABCD"; Changing the priority section among overlaid sections Changing the priority section among overlaid sections is not immediately reflected in debugger operations. To update the display of addresses in the editor, for example, you need to close the file and open it again. To update the display of variables in the [Watch] panel, execute a single step of the program. R20UT3981EJ0100 Rev Page 14 of 19

15 Variables assigned to registers When the selection for [Scope] in the [Local Variables] panel is not [Current], the values of variables assigned to registers are not displayed correctly. Editing these values is also not possible Locations to which variables are assigned When a defined variable satisfies both of the conditions given below, the [Watch] and [Local Variables] panels indicate the location of the entire variable rather than the location of its member variables. Conditions: (1) The variable is assigned to two or more addresses or registers (i.e. two or more addresses or registers are displayed in the address column). (2) A structure-, class-, array-, or union-type member is defined in the variable. Example: struct Mem { long m_base; }; struct Sample { long m_a; struct Mem m_b; <- Condition (2) }; main () { struct Sample obj; } Display in the [Watch] and [Local Variables] panels: "obj" - { R1:REG, R2:REG } (struct Sample) L m_a 0x { R1:REG } (long) L m_b - { R1:REG, R2:REG } (struct Base) L m_base 0x { R2:REG } (long) Casting variables When a variable is cast to another type in the [Watch] panel, casting of the variable is C-style. For this reason, the result of casting a class using virtual inheritance to its base class is not the same as the result of the cast within the program class AAA [ int m_aaa; } obja; class BBB : public AAA { // BBB inherits AAA. int m_bbb; } objb; class CCC { // CCC does not inherit AAA. int m_ccc; } objc class AAA* pa = obja; class BBB* pb = objb; class CCC* pc = objc; "(AAA*)pa" Usable "(BBB*)pb" Usable "(AAA*)pb" Usable "(CCC*)pc" Usable "(AAA*)pc" Not usable because pc is considered to point to the top address of AAA. Image of the cast in a program: (AAA*)((void*)pc) PC entering the sleep state Applies to: OCD (JTAG) and OCD (serial) for RX When a PC running Windows Vista or Windows 7 enters the sleep state, debugging by CS+ cannot be R20UT3981EJ0100 Rev Page 15 of 19

16 continued after the PC reawakes. Please set up the PC so that it does not enter the sleep state Stopping and restarting tracing during program execution When trace start events and end events have been set, stopping and restarting tracing during program execution is not possible Timestamps of trace information Applies to: OCD (JTAG) and OCD (serial) for RX The timestamps of trace information will not indicate the right times if the time between frames exceeds that corresponding to the trace counter (20 bits) or when trace output is lost Linkage options of CC-RX CC-RX does not support the -sdebug linkage option. Please set [Outputs debugging information] in the [output] category of the [Link Options] tabbed page to '-debug' Return-out command execution Executing a return-out command from a recursive function may lead to execution stopping at the address of the return instruction in the called function instead of the correct line in the calling function Startup program protection Applies to: OCD (serial) for RX100 Executing a CPU reset after one of the following operations during the execution of a user program will lead to a discrepancy between the contents of ROM as displayed by the debugger and the contents of the actual ROM of the MCU. In this case, the contents will match after re-executing then stopping the user program. Calling the R_FCL_ChangeSwapFlag function to immediately swap boot areas Controlling the flash initial setting register (FISR) to immediately swap boot areas Coverage measurement function Applies to: E20 emulator (JTAG) for RX64M (1) If you connect the emulator by using hot plug-in, the coverage measurement function is not available. If you use hot plug-in to connect the emulator, please select [No] for [Use code coverage measurement function] in the [Coverage] category of the debugging tool properties. (2) When the error message "The system was reset." is displayed during program execution, coverage from the start of the program to the system reset will not have been measured Breakpoints in for statements or inline-expanded functions If a line of C source code includes any of the functions or statements listed below, the instruction is placed at two or more addresses. However, the editor panel shows only one of the addresses. In cases where a breakpoint is set on this line, the program stops only when the instruction at the address being displayed on the editor panel is executed. 1. Inline-expanded function (*) 2. Template function 3. First line of a for or do-while statement * Includes those inline-expanded by optimization Trace setting for DMAC/DTC Applies to: E20 emulator (JTSG) for RX64M When [DTAC/DTC] is selected for [Bus Master of data access] in the [Trace] category on the [Debug Tool Settings] tabbed page of the Property panel, select [CPU execution] or [Do not output] for [External trace output] in the [Trace] category. If you select [Trace output] for [External trace output], the trace function may not work correctly. R20UT3981EJ0100 Rev Page 16 of 19

17 Main clock source setting when PLL is selected as clock source Applies to: OCD(JTAG),OCD(Serial),RX64M Please set up the following, when PLL is selected as clock source. Set the [Main clock source] of the [Clock] category of the [Connection settings] tab of a debug tool property as [EXTAL]. When EXTAL is selected as PLL clock source, set the frequency of EXTAL to [Main clock frequency]. When HOCO is selected as PLL clock source, set the frequency of HOCO to [Main clock frequency] DMA display of trace panel Applies to: IECUBE for RL78 and 78K0R When there is access to SFR/ memory by DMA, character string of "DMA" is not displayed in the trace panel. ("Address" and "Data" of the access to SFR/memory by DMA are displayed correctly.) Debug Tool Property panel Applies to: All debugging tools for RH850 The [Use virtual machine and thread] from the [Connect Settings] tabbed page of the property panel, do not change it from "No." Pseudo-error debugging Applies to: All debugging tool excluding simulator for RH850 To cause an RH850/P1x-series MCU to be internally reset by a pseudo-error, set up an ECM pseudo-error trigger register from the user program. A special instruction sequence is required for writing to this register since it is protected. For details, refer to the section of write-protected registers in User s Manual: Hardware for the MCU in use. Do not set a breakpoint at the current PC address in pseudo-error debugging. When it is set, interrupts and internal reset will not occur. If you wish to set another breakpoint via a source editor or the disassemble panel at the address where a breakpoint has been set for pseudo-error debugging, designate it as a hardware breakpoint. Setting a software breakpoint in this case will lead to an error when pseudo-error debugging is started. 5.4 Points for caution regarding analysis tools [Analysis Chart] panel When the emulator does not support the time tags of the internal trace, the [Analysis Chart] panel cannot be used (E1/E20 for RX). When a simulator is specified as the debugging tool in a graph of transitions in values, realtime sampling of IORsis not supported. The results on an [Execution Time(Percentage) Chart] may not be exact. This is because the counter for time-lag measurement of the trace is small and may overflow. Please check whether it has overflowed by checking the timestamp of the [Trace] panel (E1/E20 for RX). 5.5 Points for caution regarding the Python Console Japanese input The Japanese input facility cannot be activated from the Python Console. To enter Japanese text, write it in an external editor etc., copy it, and paste it into the console Display of the prompt The Python Console prompt >>> may be displayed more than once, as in >>>>>>, results may be displayed after the >>>, or the caret may appear without a preceding >>> prompt. Entering functions is still possible in these situations Paths to folders and files IronPython recognizes the backslash character (\) as a control character. For example, if a folder or file name starts with a t, then the sequence \t will be recognized as a tab character. Please use r + "path_name" to avoid this. Example: r"c:\test\test.py" A forward slash (/) can be used instead of a backslash (\). R20UT3981EJ0100 Rev Page 17 of 19

18 5.5.4 Executing scripts for projects that do not have load modules If a script is specified in the startup options for use with a project that does not have a load module file, or if project_file.py is placed in the same folder as the project file, then although the script would have been executed automatically after normal loading of the project, it will not be executed if there is no load module file Forced termination The following actions while a script such as an infinite loop is running may lead to the results of function execution being in error because the actions forcibly terminate the execution of functions. 1. Forcible termination by selecting Forcibly terminate from the context menu or pressing Ctrl+D in the Python Console 2. Changing the active project in a project with multiple projects Forced stopping Executing Abort from the context menu will forcibly stop an executing script or function, but hook and callback functions that had not started at the time the Abort was executed will still be executed in order after that Executing Python commands during building Do not issue Python commands while building is in progress. 5.6 Points for caution regarding licenses Updating CC-RX V and CC-RH V The CC-RX V and CC-RH V compiler have the following two editions. standard edition professional edition Start a License Manager to enable the license of "RX License Pack 2 Professional(CC-RX)" and " RH850 License Pack 1 Professional(CC-RH)" registered at present. R20UT3981EJ0100 Rev Page 18 of 19

19 Chapter 6. Restrictions This section describes restrictions on CS Restrictions imposed by debugging tools The abbreviations listed below collectively denote the corresponding tools in this section. OCD (serial): E1 Emulator (serial), E20 Emulator (serial) OCD (JTAG): E1 Emulator (JTAG), E20 Emulator (JTAG) List of restrictions imposed by debugging tools No. Target tool Target device Description Remarks 1 OCD (serial) RX64M Restriction on ID code authentication OCD (JTAG) due to an error Details of restrictions imposed by debugging tools No.1 Condition leading to errors in ID code authentication Applies to: OCD (serial) and OCD (JTAG) for RX64M Description: When both of the following conditions are met, an error will occur in ID code authentication making it impossible to continue with debugging. [Conditions] 1. A device having an ID code setting other than all FF is being debugged in user boot mode. 2. After downloading a program that includes data for the option-setting memory, the CPU is reset by a RESET command, RES# pin reset, or an internal reset. Workaround: There is no workaround. All trademarks and registered trademarks are the property of their respective owners. R20UT3981EJ0100 Rev Page 19 of 19

20 Notice 1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples. You are fully responsible for the incorporation of these circuits, software, and information in the design of your equipment. Renesas Electronics assumes no responsibility for any losses incurred by you or third parties arising from the use of these circuits, software, or information. 2. Renesas Electronics has used reasonable care in preparing the information included in this document, but Renesas Electronics does not warrant that such information is error free. Renesas Electronics assumes no liability whatsoever for any damages incurred by you resulting from errors in or omissions from the information included herein. 3. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 4. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. Renesas Electronics assumes no responsibility for any losses incurred by you or third parties arising from such alteration, modification, copy or otherwise misappropriation of Renesas Electronics product. 5. Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The recommended applications for each Renesas Electronics product depends on the product's quality grade, as indicated below. "Standard": Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment; home electronic appliances; machine tools; personal electronic equipment; and industrial robots etc. "High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems; anti-crime systems; and safety equipment etc. Renesas Electronics products are neither intended nor authorized for use in products or systems that may pose a direct threat to human life or bodily injury (artificial life support devices or systems, surgical implantations etc.), or may cause serious property damages (nuclear reactor control systems, military equipment etc.). You must check the quality grade of each Renesas Electronics product before using it in a particular application. You may not use any Renesas Electronics product for any application for which it is not intended. Renesas Electronics shall not be in any way liable for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for which the product is not intended by Renesas Electronics. 6. You should use the Renesas Electronics products described in this document within the range specified by Renesas Electronics, especially with respect to the maximum rating, operating supply voltage range, movement power voltage range, heat radiation characteristics, installation and other product characteristics. Renesas Electronics shall have no liability for malfunctions or damages arising out of the use of Renesas Electronics products beyond such specified ranges. 7. Although Renesas Electronics endeavors to improve the quality and reliability of its products, semiconductor products have specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Further, Renesas Electronics products are not subject to radiation resistance design. Please be sure to implement safety measures to guard them against the possibility of physical injury, and injury or damage caused by fire in the event of the failure of a Renesas Electronics product, such as safety design for hardware and software including but not limited to redundancy, fire control and malfunction prevention, appropriate treatment for aging degradation or any other appropriate measures. Because the evaluation of microcomputer software alone is very difficult, please evaluate the safety of the final products or systems manufactured by you. 8. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas Electronics product. Please use Renesas Electronics products in compliance with all applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive. Renesas Electronics assumes no liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations. 9. Renesas Electronics products and technology may not be used for or incorporated into any products or systems whose manufacture, use, or sale is prohibited under any applicable domestic or foreign laws or regulations. You should not use Renesas Electronics products or technology described in this document for any purpose relating to military applications or use by the military, including but not limited to the development of weapons of mass destruction. When exporting the Renesas Electronics products or technology described in this document, you should comply with the applicable export control laws and regulations and follow the procedures required by such laws and regulations. 10. It is the responsibility of the buyer or distributor of Renesas Electronics products, who distributes, disposes of, or otherwise places the product with a third party, to notify such third party in advance of the contents and conditions set forth in this document, Renesas Electronics assumes no responsibility for any losses incurred by you or third parties as a result of unauthorized use of Renesas Electronics products. 11. This document may not be reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas Electronics. 12. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas Electronics products, or if you have any other inquiries. (Note 1) "Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its majority-owned subsidiaries. (Note 2) "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics. SALES OFFICES Refer to " for the latest and detailed information. Renesas Electronics America Inc Scott Boulevard Santa Clara, CA , U.S.A. Tel: , Fax: Renesas Electronics Canada Limited 9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3 Tel: Renesas Electronics Europe Limited Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K Tel: , Fax: Renesas Electronics Europe GmbH Arcadiastrasse 10, Düsseldorf, Germany Tel: , Fax: Renesas Electronics (China) Co., Ltd. Room 1709, Quantum Plaza, No.27 ZhiChunLu Haidian District, Beijing , P.R.China Tel: , Fax: Renesas Electronics (Shanghai) Co., Ltd. Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, P. R. China Tel: , Fax: Renesas Electronics Hong Kong Limited Unit , 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong Tel: , Fax: Renesas Electronics Taiwan Co., Ltd. 13F, No. 363, Fu Shing North Road, Taipei 10543, Taiwan Tel: , Fax: Renesas Electronics Singapore Pte. Ltd. 80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore Tel: , Fax: Renesas Electronics Malaysia Sdn.Bhd. Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, Petaling Jaya, Selangor Darul Ehsan, Malaysia Tel: , Fax: Renesas Electronics India Pvt. Ltd. No.777C, 100 Feet Road, HALII Stage, Indiranagar, Bangalore, India Tel: , Fax: Renesas Electronics Korea Co., Ltd. 12F., 234 Teheran-ro, Gangnam-Gu, Seoul, , Korea Tel: , Fax: Renesas Electronics Corporation. All rights reserved. Colophon 5.0