Renesas CS+ V8.03.00 User Manual

User’s Manual

CS+ V8.03.00

Integrated Development Environment

User’s Manual: RX Debug Tool

Target Device RX Family

All information contained in these materials, including products and product specification s, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com).

www.renesas.com

Rev.1.00 2019.11

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 or any other use of the circuits, software, and information in the design of your product or system. Renesas Electronics disclaims any and all liability for any losses and damages incurred by you or third part ies arising from the use of these circuits, software, or information.

2. Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other claims involving patent s, copyright s, 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, including but not limited to, the product data, drawings, charts, programs, algorithms, and application examples.

3. No license, express, implied or otherwise, is granted hereby under any patents, copyright s or other intellectual property rights of Renesas Electronics or others.

4. You shall not alter, modify, copy, or reverse engineer any Renesas Electronics produ ct, whether in whole or in part. Renesas Electronics disclaims any and all liability for any losses or damages incurred by you or third parties arising from such alteration, modification, copying or reverse engineering.

5. Renesas Electronics products are classified according to th e following two quality grades: "St andard" and "High Quality". The intended 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

"High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control (traff ic lights); large-scale communication equipment; key

Unless expressly designated as a high reliability product or a product for harsh environments in a Renesas Electronics data sheet or other Renesas Electronics document, Renesas Electronics products are not intended or 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 damage (space system; undersea repeaters; nuclear power control systems; aircraft control systems; key plant systems; military equipment; etc.). Renesas Electronics disclaims any and all liability for any damages or losses incurred by you or any third parties arising from the use of any Renesas Electronics product that is inconsistent with any Renesas Electronics data sheet, user's manual or other Renesas Electronics document.

6. When using Renesas Electronics products, refer to the latest product information (data sheets, user's manuals, application notes, "General Notes for Handling and Using Semiconductor Devices" in the reliability handbook, etc.), and ensure that usage conditions are within the ranges specified by Renesas Electronics with respect to maximum ratings, operating power supply voltage rang e, heat dissipation characteristics, installation, etc. Renesas Electronics disclaims any and all liability for any malfunctions, failure or accident arising out of the use of Renesas Electronics products outside of such specified ranges.

7. Although Renesas Electronics endeavors to improve the quality and reliability of Renesas Electronics product s , semiconductor products have specific characteristics, such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Unless designated as a high reliability product or a product for harsh environment s in a Renesas Electron ics dat a sheet or other Rene sas E lectronics document, Renesas Electronics product s are not subject to radiation resistance design. You are responsible for implementing safety measures to guard against the possibility of bodily injury , injury or damage caused by fire, and/or danger to the public in the event of a failure or malfunct i on of Renesas Electronics products, such as safety design for hardware and software, including but not limited to redundan cy, fire control and malfunction prevention, appropriate treatment fo r aging degradation or any other appropriate measures. Because the evaluation of microcomput er software alone is very difficult and imp responsible for evaluating 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. You are responsible for carefully and sufficiently investi gating applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive, and using Renesas Electronics products in compliance with all these applicable laws and regulations. Renesas Electronics disclaims any and all liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations.

9. Renesas Electronics products and technologies shall not be used for or i ncorporated into any products or systems whose manufacture, use, or sale is prohibited under any applicable domestic or foreign laws or regulations. You shall comply with any applicable export control l a ws and regula tions promulgated and administered by the governments of any countries assertin g jurisdiction over the parties or transactions.

10. It is the responsibility of the buyer or distributor of Renesas Ele ctronics products, or any other party who distributes, disposes of, or otherwise sells or transfers the product to a third party, to notify such third party in advance of the contents and conditions set forth in this document.

11. This document shall not be reprinted, reproduced or duplicated in any form, in whole or in part, withou t 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.

(Note1) "Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its directly or indirectly controlled

subsidiaries.

(Note2) "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics.

electronic appliances; machine tools; personal electronic equipment; industrial robots; etc.

financial terminal systems; safety control equipment; etc.

ractical, you are

Corporate Headquarters Contact Information

TOYOSU FORESIA, 3-2-24 Toyosu, Koto-ku, Tokyo 135-0061, Japan

www.renesas.com

For further information on a product, technology, the most up-to-date version of a document, or your nearest sales office, please visit:

www.renesas.com/contact/

Trademarks

Renesas and the Renesas logo are trademarks of Renesas Electronics Corporation. All trademarks and registered trademarks are the property of their respective owners.

(Rev.4.0-1 November 2017)

How to Use This Manual

This manual describes the role of the CS+ integrated development environment for developing applications and sys-

tems for RX family, and provides an outline of its features.

CS+ is an integrated development environment (IDE) for RX family, integrating the necessary tools for the development

phase of software (e.g. design, implementation, and debugging) into a single platform.

By providing an integrated environment, it is possible to perform all development using just this product, without the

need to use many different tools separately.

Readers This manual is intended for users who wish to understand the functions of the CS+ and

design software and hardware application systems.

Purpose This manual is intended to give users an understanding of the functions of the CS+ to use

for reference in developing the hardware or software of systems using these devices.

Organization This manual can be broadly divided into the following units.

1.GENERAL

2.FUNCTIONS A.WINDOW REFERENCE B.I/O FUNCTIONS

How to Read This Manual It is assumed that the readers of this manual have general knowledge of electricity, logic

circuits, and microcontrollers.

Conventions Data significance: Higher digits on the left and lower digits on the right

Active low representation: XXX Note: Footnote for item marked with Note in the text Caution: Information re quiring particular attention Remarks: Supplementary information Numeric representation: Decimal ... XXXX

(overscore over pin or signal name)

Hexadecimal ... 0xXXXX

TABLE OF CONTENTS

1. GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.1 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2. FUNCTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Preparation before Debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2.1 Confirm the connection to a host machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2.1.1 [E1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2.1.2 [E20] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2.1.3 [EZ Emulator]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2.1.4 [Simulator] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3 Configuration of Operating Environment of the Debug Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.3.1 Select the debug tool to use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.3.2 [E1]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.3.2.1 [Connect Settings] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.3.2.2 [De bug Tool Settings] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.3.2.3 [Download File Settings] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.3.2.4 [Hook Transaction Settings] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.3.3 [E20]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.3.3.1 [Connect Settings] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.3.3.2 [De bug Tool Settings] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.3.3.3 [Download File Settings] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2.3.3.4 [Hook Transaction Settings] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2.3.4 [EZ Emulator] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2.3.4.1 [Connect Settings] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2.3.4.2 [De bug Tool Settings] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

2.3.4.3 [Download File Settings] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

2.3.4.4 [Hook Transaction Settings] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

2.3.5 [Simulator]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

2.3.5.1 [Connect Settings] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

2.3.5.2 [De bug Tool Settings] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2.3.5.3 [Download File Settings] tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2.3.5.4 [Hook Transaction Settings] tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2.4 Connect to/Disconnect from the Debug Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

2.4.1 Connect the debug tool to CS+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

2.4.2 Disconnect the debug tool from CS+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

2.4.3 Connect the debug tool to CS+ using hot plug-in [E1(JTAG)] [E20(JTAG)] . . . . . . . . . . . . . . . . . . . . . . . 63

2.5 Download and Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

2.5.1 Execute downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

2.5.2 An applied method of download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

2.5.2.1 Changing the download conditions for load module files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

2.5.2.2 Addin g a download file (*.hex, *.mot, or *.bin). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

2.5.2.3 Downloading multiple load module files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

2.5.2.4 Performing source-level debug with hex format, Motorola S format, or binary data format files. . . . 74

2.5.2.5 Downloading files to external flash memory [E1] [E20]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

2.5.3 Executing an upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

2.6 Displaying and Changing Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

2.6.1 Displaying source files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

2.6.2 Displaying the disassembled result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

2.6.2.1 Changing the display mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

2.6.2.2 Changing the display form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

2.6.2.3 Moving to a specified address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

2.6.2.4 Moving to a symbol definition part. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

2.6.2.5 Sa ving the displayed contents of disassembled results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

2.6.3 Executing a build in parallel with other processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

2.6.4 Performing line assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

2.6.4.1 Editing instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

2.6.4.2 Editing instruction code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

2.7 Usage of PIC/PID Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

2.7.1 Changing the allocation of a load module using the PIC/PID function . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

2.8 Setting Overlay Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

2.8.1 Selecting the priority section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

2.9 Execute Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

2.9.1 Reset microcontroller (CPU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

2.9.2 Execute programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

2.9.2.1 Execute after resetting microcontroller (CPU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

2.9.2.2 Execute from the current address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

2.9.2.3 Execute after changing PC value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

2.9.3 Execute programs in steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

2.9.3.1 Step into the function (Step In execution) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

2.9.3.2 Step over the function (Step Over execution) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

2.9.3.3 Execute until return is completed (Return Out execution). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

2.9.4 Execute a specified routine [E1] [E20] [EZ Emulator]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

2.10 Stop Programs (Break) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

2.10.1 Stop the program manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

2.10.2 Stop the program at the arbitrary position (breakpoint) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

2.10.2.1 Set the type of breakpoints/break timing to use [E1] [E20] [EZ Emulator]. . . . . . . . . . . . . . . . . . . . . 99

2.10.2.2 Set a breakpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

2.10.2.3 Edit a hardware breakpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

2.10.2.4 Delete a breakpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

2.10.3 Stop the program at the arbitrary position (break event) [E1] [E20] [EZ Emulator]. . . . . . . . . . . . . . . . . 101

2.10.3.1 Set a beak event (execution-related). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

2.10.3.2 Edit a break event (execution-related). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

2.10.3.3 Delete a break event (execution-related) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

2.10.4 Stop the program with the access to variables/I/O registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

2.10.4.1 Set a break event (access-related) to a variable/I/O register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

2.10.4.2 Edit a break event (access-related) to a variab le / IO register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

2.10.4.3 Delete a break event (access-related) to a variable/IO register . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

2.10.5 Set multiple break events in combination (Combination break) [E1] [E20] [EZ Emulator] . . . . . . . . . . . 107

2.10.6 Other break factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

2.11 Displaying and Changing Memory, Registers, and Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

2.11.1 Displaying and changing memory contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

2.11.1.1 Specifying the display position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

2.11.1.2 Changing the display form of values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

2.11.1.3 Changing memory contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

2.11.1.4 Displaying and changing memory contents during program execution. . . . . . . . . . . . . . . . . . . . . . 113

2.11.1.5 Searching for memory contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

2.11.1.6 Collectively changing (initializing) memory contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

2.11.1.7 Saving displayed memory contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

2.11.2 Displaying and changing the CPU registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

2.11.2.1 Changing the form in which values are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

2.11.2.2 Changing the CPU register contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

2.11.2.3 Saving the displayed CPU register contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

2.11.3 Displaying and changing the I/O registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

2.11.3.1 Searching I/O register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

2.11.3.2 Putting the I/O registers in order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

2.11.3.3 Changing the form in which values are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

2.11.3.4 Changing the contents of I/O registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

2.11.3.5 Displaying and changing I/O register contents during program execution . . . . . . . . . . . . . . . . . . . 124

2.11.3.6 Saving the displayed I/O register contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

2.11.4 Displaying and changing global and static variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

2.11.5 Displaying and changing local variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

2.11.5.1 Changing the form in which values are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

2.11.5.2 Changing the contents of local variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

2.11.5.3 Saving the displayed contents of local variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

2.11.6 Displaying and changing watch-expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

2.11.6.1 Registering watch-expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

2.11.6.2 Putting the registered watch-expressions in order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

2.11.6.3 Editing the registered watch-expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

2.11.6.4 Removing watch-expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.11.6.5 Changing the form in which values are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

. . . . . . . 130

2.11.6.6 Changing the contents of watch-expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

2.11.6.7 Displaying and changing the contents of watch-expressions during program execution . . . . . . . . 131

2.11.6.8 Exporting/importing watch-expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

2.11.6.9 Saving the displayed contents of watch-expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

2.12 Display Function Call Information from the Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

2.12.1 Display call stack information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

2.12.1.1 Changing the form in which values are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

2.12.1.2 Jumping to the source line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

2.12.1.3 Displaying local variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

2.12.1.4 Saving the displayed contents of call stack information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

2.13 Collecting an Execution History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

2.13.1 Setting up a trace operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

2.13.1.1 For [E1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

2.13.1.2 For [E20] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

2.13.1.3 For [EZ Emulator] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

2.13.1.4 For [Simulator]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

2.13.2 Collecting an execution history up to a halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

2.13.3 Collecting an execution history in a section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

2.13.3.1 Setting a trace start event and a trace end event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

2.13.3.2 Combining multiple events [E1] [E20] [EZ Emulator]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

2.13.3.3 Executing the program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

2.13.3.4 Editing trace start and trace end events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

2.13.3.5 Deleting a trace start or trace end event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

2.13.4 Collecting an execution history only when conditions are met . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

2.13.5 Stopping/Restarting Collection of Execution History [E20] [Simulator]. . . . . . . . . . . . . . . . . . . . . . . . . . 148

2.13.5.1 To temporarily stop collection of execution history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

2.13.5.2 To restart collection of execution history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

2.13.6 Displaying an execution history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

2.13.6.1 Changing the display mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

2.13.6.2 Changing the form in which values are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

2.13.6.3 Getting linked to other panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

2.13.7 Clearing the trace memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

2.13.8 Searching for trace data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

2.13.8.1 Searching at the instruction level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

2.13.8.2 Searching at the source level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

2.13.9 Saving the displayed content of an execution history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

2.14 Measuring the Execution Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

2.14.1 Setting the timer measurement operation [E1] [E20] [EZ Emulator]. . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

2.14.2 Measuring execution time from start to stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

2.14.2.1 Checking the status bar for confirmation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

2.14.2.2 Checking the Events panel for confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

2.14.3 Measuring execution time in a section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

2.14.3.1 Setting the timer start event and timer end event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

2.14.3.2 Execute the program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

2.14.3.3 Editing a timer measurement event [E1] [E20] [EZ Emulator]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

2.14.3.4 Editing timer start and timer end events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

2.14.3.5 Deleting a timer start event or timer end event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

2.14.4 Range of measurable time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

2.15 Measure Coverage [Simulator] [E20 [RX71M, RX66x, RX65x, RX64M, RX66T, RX72T, RX72M, and RX72N Groups]]169

2.15.1 Configure the coverage measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

2.15.2 Display coverage measurement results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

2.16 Set an Action into Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

2.16.1 Insert printf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

2.16.1.1 Set a Printf event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

2.16.1.2 Execute the program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

2.16.1.3 Check the output result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

2.16.1.4 Edit Printf event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

2.16.2 Insert an interrupt event [Simulator] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

2.16.2.1 Set an interrupt event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

2.16.2.2 Execute the program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

2.16.2.3 Edit interrupt event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

2.17 Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

2.17.1 Changing states of setting (Enabled/Disabled). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

2.17.2 Displaying only a specific type of event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

2.17.3 Jump to an event address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

2.17.4 Editing detailed settings of events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

2.17.4.1 Editing execution-related events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

2.17.4.2 Editing access-related events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

2.17.4.3 Editing combination conditio ns of events [E1] [E20] [EZ Emulator]. . . . . . . . . . . . . . . . . . . . . . . . . 183

2.17.5 Deleting events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

2.17.6 Entering comments for events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

2.17.7 Points to note regarding event setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

2.17.7.1 Allowable number of valid events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

2.17.7.2 Types of events that can be set or removed during execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

2.17.7.3 Other precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

2.18 Setting Up the Hook Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

2.19 Measuring Current Consumption [E2] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

2.20 Using the Debug Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

2.21 About Input Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

2.21.1 Input rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

2.21.2 Symbol name completion function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

2.21.3 Icons for invalid input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

2.22 Differences between the Microcontroller and the Emulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

2.23 Other Notes on Usage [E1] [E20] [EZ Emulator]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

A. WINDOW REFERENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

A.1 Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

B. I/O FUNCTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

B.1 Standard I/O and File I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

Revision Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C - 1

CS+ V8.03.00 1. GENERAL

1. GENERAL

CS+ is an integrated developing environment platform for RH850 family, RX family, V850 family, RL78 family, 78K0R

microcontroller and 78K0 microcontroller.

CS+ comprehensively supports the operations required for program development such as designing, coding, building,

debugging, and flash programming.

In this manual, the debugging is explained out of those operations needed for the program development.

Caution When the E2 emulator Lite (abbreviated name: E2 Lite) is used, please read references to "E1" in this

manual as also meaning "E2 Lite". When the E2 emulator (abbreviated name: E2) is used, please read references to "E1" in this manual as also meaning "E2".

Among them, this manual focuses on the description of debugging the outline of which is provided in this chap ter.

1.1 Summary

You can efficiently debug the program developed for the RX family, using the debugger provided by CS+.

1.2 Features

The following are the features of the debugger provided by CS+.

- Connectable to various debugging tools Usable in combination with the on-chip debugging emulator (E1/E20/EZ Emulator) and the simulator, it provides improved efficiency in program development.

- Mixed display of C/C++ source text and disassembled text The C/C++ source text and the disassembled text can be displayed together on the same panel.

- Source level debugging and instruction level debugging C/C++ source program can be debugged either at the source or the instruction level.

- Data flash memory programming When the selected microcontroller is provided with a data flash memory, you can display or edit the contents of the data flash memory using the same access method as in other normal memory operations (not including the simulator).

- Real-time display updating function The values of memory, registers and variables are automatically updated not only when the program is stopped, but also in execution.

- Saving/restoring the debugging environment The debugging environment such as breakpoints, event configurati on information, file download information, display condition/position of the panel, etc. can be saved.

R20UT4588EJ0100 Rev.1.00 Page 10 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

2. FUNCTIONS

This chapter describes the debugging process using CS+ as well as main debugging functions.

2.1 Overview

Following shows the basic sequence of program debugging using CS+. (1) Start CS+

Launch CS+ from the [Start] menu of Windows. Remark For details on "Start CS+", see "CS+ Integrated Development Environment User's Manual: Project

Operation".

(2) Set a project

Create a new project, or load the existing one. Remark For details on "Set a project", see "CS+ Integrated Development Environment User's Manual: Proj-

ect Operation".

(3) Create a load module

Once you are finished with the setting of the active project and the build, execute the build to create a load module.

Remark For details on "Create a load module" with CC-RX, see "CS+ Integrated Development Environment

User's Manual: CC-RX Build Tool Operation".

(4) Confirm the connection to a host machine

Connect the debug tool (E1, E20, EZ Emulator or Simulator) to be used to a host machine.

(5) Select the debug tool to use

Select the debug tool to be used in a project. Remark The selectable debug tool differs depending on the microcontroller type to be used in a project.

(6) Configure the operating environment for the debug tool

Configure the operating environment for the debug tool selected in step (5).

- [E1]

- [E20]

- [EZ Emul ator]

- [Simulator]

(7) Connect the debug tool to CS+

Connect the debug tool to CS+ to start communication.

(8) Execute downloading

Download the load module created in step (3) to the debug tool.

(9) Displaying source files

Display the contents of the downloaded load module (source files) on the Editor panel or Disassemble panel.

(10) Execute programs

Execute the program using the operation method that matches your purpose. If you wish to stop the program at the arbitrary position, set a breakpoint/break event gram (see "2.10.2 Stop the program at the arbitrary position (breakpoint)"/"2.10.3 Stop the program at the arbi-

trary position (break event) [E1] [E20] [EZ Emulator]").

Note These functions are implemented by setting events to the debug tool used.

See "2.17.7 Points to note regarding event setting", when you use events.

(11) Stop the program manually

Stop the program currently being executed. Note that if a breakpoint/break event has been set in steps (10), the program execution will be stopped automatically when the condition of the breakpoint/break event is met.

(12) Check the result of the program execution

Check the following information that the debug tool acquired by the program execution.

- Displaying and Changing Memory, Registers, and Variables

Note

before executing the pro-

R20UT4588EJ0100 Rev.1.00 Page 11 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

- Display Function Call Information from the Stack

- Collecting an Execution History

- Measuring the Execution T i me

- Measure Coverage [Simulator] [E20 [RX71M, RX66x, RX65x, RX64M, RX66T, RX72T, RX72M, and RX72N

Groups]]

Note These functions are implemented by setting events to the debug tool used.

See "2.17.7 Points to note regarding event setting", when you use events.

Debug the program, repeating steps (9) to (12) as required. Note that if the program is modified during debugging, steps (3) and (8) also should be repeated.

Remark 1. Other than the above, you can also check the result of the program execution by using the following

functions.

- Set an Action into Programs

- Setting Up the Hook Process

- Using the Debug Console

Remark 2. The acquired information can be saved to a file.

- Saving the displayed contents of disassembled results

- Saving displayed memory contents

- Saving the displayed CPU register co ntents

- Saving the displayed I/O register contents

- Saving the displayed contents of local variables

- Saving the displayed contents of watch-expressions

- Saving the displayed contents of call stack information

- Saving the displayed content of an execution history

(13) Execu ting an upload

Save the program (the memory contents) to a file in the arbitrary format (e.g. Intel hex format, binary data format, etc.), as required.

(14) Disconnect the debug tool from CS+

Disconnect the debug tool from CS+ to terminate communication.

(15) Save the project file

Save the setting information of the project to the project file. Remark For details on "Save the project file", see "CS+ Integrated Development Environment User's Man-

ual: Project Operation".

Note

R20UT4588EJ0100 Rev.1.00 Page 12 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

2.2 Preparation before Debugging

This section describes the preparation to start debugging the created program.

2.2.1 Confirm the connection to a host machine

Connection examples for each debug tool are shown. Note that the relationship between the microcontroller selected in the project and the connectable debug tools is as the

following table.

Remark "(Serial)"/"(JTAG)" in the table below means that E1/E20 is used with FINE communications or JTAG

communications.

Table 2.1 Relationship between Typ es of Microcon troller and Connectable Debug Tools

Microcontroller Debug Tool

E1(Serial) E1(JTAG) E20(Serial) E20(JTAG) EZ Emulator Simulator

RX610, RX621, RX62N, RX62T, and RX62G Groups

RX630, RX631, RX63N, and RX634 Groups

RX63T Group RX110, RX111, RX113,

RX210, and RX220 Groups

RX21A, RX211, RX231, RX23W, RX23T, RX24T, RX24U, RX130, RX13T and RX23E-A Groups

RX71M, RX66x, RX64M, RX65N, RX651, RX65N2M, RX651-2M, RX72T, RX72M and RX72N Groups

2.2.1.1 [E1]

2.2.1.2 [E20]

2.2.1.3 [EZ Emulator]

2.2.1.4 [Simulator]

---

2.2.1.1 [E1]

Connect a host machine and E1. If required, connect a target board, too. You can make a choice between FINE communications [E1(Serial)] and JTAG communications [E1(JTAG)] as the com-

munication method to the target system (see "2.3.1 Select the debug tool to use").

See E1 User's Manual for details on the connection method.

R20UT4588EJ0100 Rev.1.00 Page 13 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

Target system

USB interface cable

CS+

Host machine

Dedicated probe

Target system

E20

USB interface cable

CS+

Host machine

Dedicated probe 38-pin

Target system

E20

USB interface cable

CS+

Host machine

Dedicated probe

38-pin to 14-pin conversion adapter

Note

Figure 2.1 Connection Example [E1]

2.2.1.2 [E20]

Connect a host machine and E20. If required, connect a target board, too. You can make a choice between FINE communications [E20(Serial)] and JTAG communications [E20(JTAG)] as the

communication method to the target system (see "2.3.1 Select the debug tool to use").

See E20 User's Manual for details on the connection method. Figure 2.2 Connection Example [E20(JTAG)]

R20UT4588EJ0100 Rev.1.00 Page 14 of 423 Nov 01, 2019

Figure 2.3 Connection Example [E20(Serial)]

Note Use a 38-pin to 14-pin conversion adapter attached to the E20 emulator if you have selected FINE [E20

(Serial)] as the method of communication with the target system. For more details on the connection using a 38-pin to 14-pin conversion adapter, see E20 User's Manual

2.2.1.3 [EZ Emulator]

Connect a host machine and EZ Emulator. If required, connect a target board, too. See EZ Emulator User's Manual for details on the connection method.

CS+ V8.03.00 2. FUNCTIONS

EZ Emulator

USB interface cable

CS+

Host machine

CS+

Host machine

Figure 2.4 Connection Example [EZ Emulator]

2.2.1.4 [Simulator]

A host machine is only needed for debugging (emulators are not needed). Figure 2.5 Connection Example [Simulator]

R20UT4588EJ0100 Rev.1.00 Page 15 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

2.3 Configuration of Operating Environment of the Debug Tool

This section describes the configuration of the operating environment for each debug tool.

2.3.1 Select the debug tool to use

You can configure the operating environment in the Property panel corresponding to the debug tool to use. Therefore, first, select the debug tool to be used in a project (the debug tool to be used can be specified in the individual

projects).

To select or switch the debug tool, use the context menu shown by right clicking on the [Microcontroller type Debug tool

name (Debug Tool)] node on the Project Tree panel.

Figure 2.6 Select/Switch Debug Tool to Use

Caution The context menu items displayed differ depending on the microcontroller selected in the project (see

"Table 2.1 Relationship between Types of Microcontroller and Connectable Debug Tools").

Remark 1. [E1] [E20]

Select [Microcontroller type E1(Serial)]/[Microcontroller type E20(Serial)] to perform FINE communications between E1/E20 and the target system. Select [Microcontroller type E1(JTAG)]/[Microcontroller type E20(JTAG)] to perform JTAG communications between E1/E20 and the target system.

Remark 2. [EZ Emulator]

Only FINE is supported for communication between the EZ Emulator and the target system.

If the Property panel is already open, click the [Microcontroller type Debug tool name (Debug Tool)] node again. The

view switches to the Property panel of the selected debug tool.

If the Property panel is not open, double-click the above mentioned node to open the corresponding Property panel.

R20UT4588EJ0100 Rev.1.00 Page 16 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

2.3.2 [E1]

Configure the operating environment on the Property panel below when using E1. Note that the contents of the Property panel differ depending on the communication method (FINE communications

[E1(Serial)] or JTAG communications [E1(JTAG)]) between E1 and the target system.

Figure 2.7 Property Panel [E1(Serial)]

R20UT4588EJ0100 Rev.1.00 Page 17 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

Figure 2.8 Property Panel [E1(JTAG)]

Follow the steps below by selecting the corresponding tab on the Property panel.

2.3.2.1 [Connect Settings] tab

2.3.2.2 [Debug Tool Settings] tab

2.3.2.3 [Download File Settings] tab

2.3.2.4 [Hook Transaction Settings] tab

2.3.2.1 [Connect Settings] tab

In the [Connect Settings] tab, you configure the connection with the debug tool for each one of the following categories.

(1) [Internal ROM/RAM] (2) [Clock] (3) [Connection with Emulator] (4) [Connection with Target Board] (5) [E2 Expansion Interface] [E2] (6) [Flash] (7) [Operating Modes of CPU] (8) [External Flash]

(1) [Internal ROM/RAM]

The configuration of internal ROM/RAM is displayed in this category. Figure 2.9 [Internal ROM/RAM] Category

(a) [Size of internal ROM[KBytes]

The internal ROM size to emulate is displayed (unit: Kbytes).

R20UT4588EJ0100 Rev.1.00 Page 18 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

You cannot change the value of this property.

(b) [Size of internal RAM[Bytes]]

The internal RAM size to emulate is displayed (unit: bytes). You cannot change the value of this property.

The data flash memory size is displayed (unit: Kbytes). If the currently selected microcontroller does not incorporate the data flash, [0] is displayed. You cannot change the value of this property.

(2) [Clock]

You can configure the clock in this category. Caution You cannot change the property in this category while connected to E1.

Figure 2.10 [Clock] Category [HOCO]

Figure 2.11 [Clock] Category [EXTAL]

(a) [Main clock source]

Select EXTAL frequency or internal HOCO as the main clock source. [EXTAL] will be displayed for microcontrollers with no internal HOCO.

(b) [Main clock frequency [MHz]]

Specify the main clock frequency (before multiplier). Specify EXTAL frequency by directly entering a number between 0.0001 and 99.9999 (MHz). The entered value will be truncated to 4 decimal places. If the value is out of the specifiable range, it will be rounded to 0.0001 (when 0 or below) or to 99.9999 (when 100 or above). This property is displayed only when you have selected [EXTAL] in the [Main clock source] property.

Specify the Operating frequency (ICLK) by directly entering a number between 0.0001 and 999.999 (MHz). If the value is out of the specifiable range, it will be rounded to 0.0001 (if 0 or negative) or to 999.999 (if 1000 or greater).

(d) [Allow changing of the clock source on writing internal flash memory]

Specify whether to allow a debugger to operate the clock while the internal flash memory is being rewritten. Caution [E1]

When [Y es] is selected, if internal flash ROM is rewritten by the debugger while the FlashIF clock (FCLK) of the microcontroller is outside of the guaranteed operating range (that is, while operating with LOCO or subclock), the E1 will switch the clock source. After rewriting to the internal flash ROM is completed, the clock will be restored to the previous clock source. Note that the operating frequency of the peripheral clock will change during internal flash memory rewriting because the clock source is switched. The clock manipulation enabling setting takes effect when the internal flash ROM is rewritten after program execution or step execution. Note that the clock source is forcibly switched regardless of the clock manipulation enabling setting if FCLK is outside of the guaranteed operating range immediately after the debug tool is activated or when the [CPU Reset] button is clicked.

(3) [Connection with Emulator]

You can configure the connection between E1 and the host machine in this category. Caution You cannot change the property in this category while connected to E1.

R20UT4588EJ0100 Rev.1.00 Page 19 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

Figure 2.12 [Connection with Emulator] Category

(a) [Emulator serial No.]

Serial numbers of all connected E1 emulators are displayed in the drop-down list. Select the one to be connected to the target system. The drop-down list is updated every time it is used.

(4) [Connection with Target Board]

You can configure the connection between E1 and the target board in this category. Figure 2.13 [Connection with Target Board] Category [E1(Serial)]

Figure 2.14 [Connection with Target Board] Category [E1(JTAG)]

(a) [Power target from the emulator. (MAX 200mA)]

Specify whether to supply power to the target system from E1. Select [Yes] to supply power to the target system ([No] is selected by default).

Caution This property cannot be changed while connected to E1.

(b) [Interface for supplying the power] [E2]

This property appears only when the [Power target from the emulator. (MAX 200mA)] property is set to [Yes]. Select the interface for supplying the power to the target board from the emulator (default: [USER I/F]).

Specify the power voltage supplied to the target system from the following drop-down list. This property appears only when the [Power target from the emulator. (MAX 200mA)] property is set to [Yes]. The voltage value that can be specified differs depending on the type of the microcontroller.

Caution [E1]

This property cannot be changed while connected to E1. [E2 Lite] This property cannot be changed.

(d) [Communications method]

Displays the method of communication used by the E1 emulator for communicating with the microcontroller on the target system. Specifying [RX E1(Serial)] for a debug tool in the Project Tree panel will display [FINE] in this property, and specifying [RX E1(JTAG)] will display [JTAG]. You cannot change the value of this property when specifying E1. When specifying [RX E2 Lite] or [RX E2], whether this property can be changed differs with the type of the selected microcontroller and the communication method. See "2.2.1 Confirm the connection to a host machine" for the relationship between types of the microcontroller and the communication method. For the details of debug tool selection, see "2.3.1 Select the debug tool to use".

(e) [JTAG clock[MHz]]

From the drop-down list, select the baud rate (JTAG clock) to be used by the E1 emulator for communicating with the microcontroller on the target system. This property is displayed only when [JTAG] is selected in the [Communications method] property. The following baud rate is displayed in the drop-down list.

- 16.5 (default), 12.38, 6.188, 3.094, 1.547 [E1]

- 6.00 (default), 3.00, 1.50 [E2 Lite]

- 16.5 (default), 12.5, 6.25, 3.125, 1.562 [E2]

R20UT4588EJ0100 Rev.1.00 Page 20 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

Caution 1. This property cannot be changed while connected to E1. Caution 2. Depending on the length or the method of JTAG signal wiring on the target system, it may not be

possible to communicate using the selected JTAG clock. In such a case, reducing the JTAG clock may achieve successful communication.

(f) [FINE baud rate[bps]]

From the drop-down list, select the baud rate (FINE baud rate) to be used by the E1 emulator for communicating with the microcontroller on the target system. This property is displayed only when [FINE] is selected in the [Communications method] property. The following baud rate is displayed in the drop-down list.

- 2000000 (default), 750000, 500000, 250000 [E1][E2]

- 1500000 (default), 750000, 500000, 250000 [E2 Lite]

Caution 1. This property cannot be changed while connected to E1. Caution 2. Depending on the length or the method of FINE signal wiring on the target system, it may not be

possible to communicate using the selected FINE baud rate. In such a case, reducing the FINE baud rate achieve successful communication.

(5) [E2 Expansion Interface] [E2]

You can configure the E2 expansion interface. Figure 2.15 [E2 Expansion Interface] Category [E2]

(a) [Interface for supplying the power]

Select whether to use the E2 expansion interface. If you want to use the E2 expansion interface, select the power used by the E2 expansion interface.

(6) [Flash]

You can configure the flash memory rewriting in this category. Caution This property cannot be changed while connected to E1.

Figure 2.16 [Flash] Category

(a) [Input Mode of ID code]

Specify a mode for the input of ID code. Caution This property cannot be changed while connected to E1.

(b) [ID code]

Enter the ID code to release the flash memory from the protected state. If you have selected [Specify the ID code as a 32-digit hexadecimal] in the [Input Mode of ID code] property, enter the ID code in a 32-digit hexadecimal number. If you have selected [Specify the ID code as an ASCII code within 16 characters], enter the ID code using maximum 16 ASCII characters.

Caution 1. This property cannot be changed while connected to E1. Caution 2. To enter the ID code as a 32-digit hexadecimal value, arrange it as a sequence of 32-bit units of

data. Byte order of the ID code of the flash programmer can be different from that of CS+. Please confirm the specification about ID code of the flash programmer you’re using.

Caution 3. If the ID code entered in ASCII characters is shorter than 16 characters, the unused space will be

padded with 0.

Caution 4. Even if you have downloaded a program that contains an ID code, that ID code is replaced with

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF.

R20UT4588EJ0100 Rev.1.00 Page 21 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

Specify the location address of the work RAM to be used by the debugger. Specify an address value that is a multiple of four bytes. If the entered value is not a multiple of four bytes, the value is automatically corrected. The amount of memory indicated by the [Work RAM size[bytes] property beginning with this address is to be used by the debugger firmware.

Caution 1. This property cannot be changed while connected to E1. Caution 2. The work RAM area can also be used by the user program because the emulator saves and

restores data in this area. Note, however, that the work RAM area is not specifiable as: the destination or origin of a DMA or DTC transfer, an address where a DTC vector table or transfer information is to be allocated, or the interrupt vector for a DMAC or DTC activation source.

(d) [Work RAM size[bytes]

Displays the size of the work RAM to be used by the debugger.

(7) [Operating Modes of CPU]

In this category, you configure the operating mode of the microcontroller to be emulated. Caution This property cannot be changed while connected to E1.

Figure 2.17 [Operating Modes of CPU] Category

(a) [Mode pins setting]

Specify the operating mode set by the mode pin of the microcontroller.

(b) [Allow erasing the USB boot program]

Select whether to erase the USB boot program in the user boot area when you are starting up the emulator in the user boot mode by using a microcontroller in which the USB boot program is stored. This property is displayed only when [User boot mode] is selected for the [Mode pins setting] property. Note that this is not displayed for an microcontroller in which the USB boot program in the user boot area does not need to be erased when you are starting up the emulator.

Specify the operating mode to be set by the register. The operating mode that can be speci fi e d d epends on the type of the microcontroller.

(d) [Endian]

Display the project endian. Acquires endian information from the project and displays its value. Can be selected only when the debug tool is disconnected.

(e) [Change the start bank][RX651-2M, RX65N-2M, RX72M, RX66N, and RX72N Groups]

Specify whether to change the start bank before connecting to the debug tool. Select [Yes] to change the start bank before connecting to the debug tool ([No] is selected by default).

(f) [Start bank][RX651-2M, RX65N-2M, RX72M, RX66N, and RX72N Groups]

Specify the start bank to be changed before connecting to the debug tool. This property is displayed only when [Yes] is selected for the [Change the start bank][RX651-2M, RX65N-2M,

RX72M, RX66N, and RX72N Groups] property.

(8) [External Flash]

In this category, you can configure external flash. The settings in this category are required when downloading to an external flash memory . For more details regarding property setting, see "2.5.2.5 Downloading files to external flash memory [E1] [E20]“.

Caution You cannot change the property in this category while connected to E1.

R20UT4588EJ0100 Rev.1.00 Page 22 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

2.3.2.2 [Debug Tool Settings] tab

In the [Debug Tool Settings] tab, you configure the basic settings of the debug tool for each one of the following catego-

ries.

(1) [Memory] (2) [Access Memory While Running] (3) [Register] (4) [E2 Expansion Interface] [E2] (5) [Break] (6) [System] (7) [Trace] (8) [Timer] [RX600, RX700 series]

(1) [Memory]

You can configure the memory in this category. Figure 2.18 [Memory] Category

(a) [Memory mappings]

Current memory mapping status is displayed for each type of memory area. It is not possible to change mapping on this panel. To add or delete an I/O protection area, select the [Memory mappings] property and click on the [...] button that appears on the right to open the Memory Mapping dialog box. For details on how to change settings, refer to the section of the Memory Mapping dialog box. This property displays only the number of memory areas. Expanding the [Memory mappings] property will display the following sub-items.

R20UT4588EJ0100 Rev.1.00 Page 23 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

- [Memory type] Indicates the memory type of the corresponding area. Each memory type corresponds to the following areas.

On-chip ROM area Program ROM On-chip RAM area On-chip RAM

Note 1

and data flash

Note 4

I/O registers area Peripheral I/O register

Divided into areas with different endians for display

External area(CS7/CS6/.../CS0) External address space

CS0 to CS7 are displayed separa te ly

Other memory area FCU-RAM

Note 3

, FCU firmware Reserved area Areas other than those listed above I/O protection area Address range in an external area that is not read by the

debugger. Register this area in the Memory Mapping dialog

box.

Note 1. If data in the on-chip flash ROM area is changed by means other than downloading (e.g. by

manipulating it via the Memory panel or line assembling), the flash ROM reflects this change next time the user program is run.

Note 2. If an attempt is made to reference data in erased data flash ROM, only undefined values are

displayed due to the specifications of the microcontroller. If the debugger is used to write to the data flash ROM, on the othe r h an d , data is written in 256-byte units. Written areas do not hold undefined values.

Note 3. Do not use the debugger to write to FCU-RAM. The FCU firmware area also cannot be written

by the debugger.

Note 4. The area including the option setting memory areas listed below is displayed as an on-chip

RAM area. Note that values cannot be specified in this area through the memory panel.

Note 3

Note 2

, user boot

[RX71M, RX66x, RX65x, RX64M, and RX72T Groups]

- S PCC Serial Programmer Command Control Reg.

- OSIS OCD/Serial Programmer ID Setting Reg.

- E ndian select registers (MDE)

- Option function select register 0 (OFS0)

- Option function select register 1 (OFS1)

[RX65N-2M, RX651-2M, RX72M, RX66N, and RX72N]

- S PCC Serial Programmer Command Control Reg.

- OSIS OCD/Serial Programmer ID Setting Reg.

- E ndian select registers (MDE)

- Option function select register 0 (OFS0)

- Option function select register 1 (OFS1)

- Bank Select Register (BANKSEL)

- Flash Access Window Setting Register (F AW)

- [Start address] Displays the starting address of the corresponding area.

- [End address] Displays the ending address of the corresponding area.

- [Access width[bits]] Displays the access width of the corresponding area.

R20UT4588EJ0100 Rev.1.00 Page 24 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

When [Memory type] is an external area, the access width can only be changed when the debug tool is disconnected.

- [Endian] Displays the endians of the external area and the I/O register area. When [Memory type] is an external area, the endian can only be changed when the debug tool is disconnected.

Caution Connecting to a debug tool (see "2.4.1 Connect the debug tool to CS+") will display details for

each memory type.

(b) [Verify on writing to memory]

Specify whether to perform a verify check when the memory value is initialized from the drop-down list. Select [Yes] to perform verification after download or when values are changed in the Watch panel/ Memory

panel.

(2) [Access Memory While Running]

You can configure the memory access while executing a program in this category. The settings of this category are required when using the real-time display update function. See "2.1 1.1.4 Display-

ing and changing memory contents during program execution" for details on the real-time display update function.

Figure 2.19 [Access Memory While Running] Category

(a) [Access by stopping execution]

Specify from the drop-down list whether to allow access to the memory area while executing a program. Select [Yes] to allow access ([No] is sele cted by default).

(b) [Update the display during execution]

Specify whether to update the display in the Watch panel/Memory panel while executing a program. Select [Yes] to update the display (default).

Caution You cannot change this property while the program is in execution.

This property is displayed only when the [Update the display during execution] property is set to [Yes]. Specify the interval in 100ms unit to update the contents in the Watch panel/Memory panel display while execut- ing a program. Directly enter the Integer number between 100 and 65500 (rounding up the fractions less than 100ms) ([500] is specified by default). Note that if you've changed the specified value of the [Update the display during execution] property from [No] to [Yes], the previous set value is displayed in this property.

Caution You cannot change this property while the program is in execution.

(3) [Register]

In this category, make settings related to PC display in the Status bar during program execution. Figure 2.20 [Register] Category

(a) [PC display during the execution]

This property specifies whether the PC value is displayed in the Status bar during program execution. When you select [No], the Status bar under execution will show "Running."

Caution 1. You cannot change this property while the program is in execution. Caution 2. [RX100 Series]

This property is hidden because these microcontrollers do not support display of the PC value in the status bar during program execution.

Caution 3. While current consumption is being measured, this property is fixed to [No].

(b) [Display update interval for PC[ms]]

R20UT4588EJ0100 Rev.1.00 Page 25 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

This property is displayed only when you've selected [Yes] in the [PC display during the execution] property. During program execution, specify a PC display updating interval in the Status bar in 100 ms units. Enter an integer directly in the range 100 to 65500 (with fractions below 100 ms rounded up). (By default, [500] is specified.) Note that if you've changed the specified value of the [PC display during the execution] property fro m [No] to [Yes], the previous set value is displayed in this property.

Caution You cannot change this property while the program is in execution.

(4) [E2 Expansion Interface] [E2]

You can configure the E2 Expansion Interface. Figure 2.21 [E2 Expansion Interface] Category

(a) [External trigger input]

Set the settings related to the external trigger input. You can select different actions for each channel.

<1> Channel number

The channel number is displayed.

<2> Use

Specify whether to use the external trigger input for this channel number.

<3> Input signal

Specify the input signal.

<4> Action when inputting the external trigger

The action when inputting the external trigger is displayed.

(b) [External trigger output]

Set the settings related to the external trigger output. You can select different actions for each channel.

<1> Channel number

The channel number is displayed.

<2> Use

Specify whether to use the external trigger output for this channel number.

<3> Output timing

The output timing is displayed.

R20UT4588EJ0100 Rev.1.00 Page 26 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

<4> Output signal

The output signal displayed.

<5> Pulse width [us]

Specify the pulse width.

(5) [Break]

You can configure the break function in this category. Figure 2.22 [Break] Category

(a) [Type of breakpoints to be preferentially used]

Specify from the following drop-down list the type of preferential breakpoint to be used with a single click of the mouse in the Editor panel/Disassemble panel. When setting a break point after the preferential break point type has been used up, the other break point type will be automatically selected. See "2.10.2 Stop the program at the arbitrary position (breakpoint)" for details on breakpoints.

Software break Sets software breakpoint preferentially. Hardware break Sets hardware breakpoint preferentially (default).

(6) [System]

You can configure the emulation system in this category. For more information regarding the execution of a specified routine before the execution and after the break of a program, see "2.9.4 Execute a specified routine [E1] [E20] [EZ Emulator]".

Figure 2.23 [System] Category

(a) [Debug the program re-writing the on-chip PROGRAM ROM]

Specify whether to debug programs that rewrite on-chip program ROM area, such as those that use ROM P/E mode.

Caution You cannot change this property while connected to E1.

(b) [Debug the program re-writing the on-chip DATA FLASH]

Specify whether to debug programs that rewrite on-chip data flash area, such as those that use data flash P/E mode.

Caution You cannot change this property while connected to E1.

Specify whether to execute a specified routine before executing the user program. Caution You cannot change this property while the program is in execution.

(d) [Routine to run immediately before execution starts]

Specify the address to be executed immediately before the user program execution. This property is displayed only when [Execute the specified routine immediately before execution of the user program] property is set to [Yes].

Caution You cannot change this property while the program is in execution.

(e) [Execute the specified routine immediately after the user program stops]

Specify whether to execute a specified routine after the user program break. Caution You cannot change this property while the program is in execution.

R20UT4588EJ0100 Rev.1.00 Page 27 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

(f) [Routine to run immediately after execution stops]

Specify the address to be executed immediately after the user program break. This property is displayed only when [Execute the specified routine immediately after the user program stops] property is set to [Yes].

Caution You cannot change this property while the program is in execution.

(g) [Work RAM start address for executing a specified routine]

Specify the address where the work RAM for use in execution of the specified routine starts. Specify an address value that is a multiple of four bytes. If the entered value is not a multiple of four bytes, the value is automatically corrected. The amount of memory indicated by the [Work RAM size [bytes] for executing a specified routine] property beginning with this address is to be used by the debugger firmware. This property is displayed only when you have selected [Yes] either for the [Execute the specified routine imme-

diately before execution of the user program] or [Execute the specified routine immediately after the user program stops] property.

Caution 1. You cannot change this property while the program is in execution. Caution 2. Specify the range of memory that is not used by the user program.

(h) [Work RAM size [bytes] for executing a specified routine]

Indicates the size of the work RAM for use in execution of the specified routine. This property is displayed only when you have selected [Yes] either for the [Execute the specified routine imme-

diately before execution of the user program] or [Execute the specified routine immediately after the user program stops] property.

(7) [Trace]

You can configure the trace function in this category. Figure 2.24 [Trace] Category

(a) [Usage of trace function]

[Trace] is displayed as the usage of trace function. You cannot change the value of this property.

(b) [Operation after trace memory is full]

Select the trace acquisition mode from the following drop-down list.

Overwrite trace memory and continue execution

Stop trace Stops writing the trace data after the trace memory is full. Stop Breaks after the trace memory is full.

Select the type of data for which trace is to be acquired from the drop-down list. The type of data that can be selected differs depending on the series of the microcontroller. Following data types are displayed in the drop-down list.

- [RX600, RX700 Series] Branch, Branch + Data access, Data access

- [RX100, RX200 Series] Branch, Data access

(d) [Bus master of data access][RX71M, RX66x, RX65x, RX64M, RX72M, RX72N, and RX72T Groups]

This property is displayed only when [Branch + Data access] or [Data access] is specified in the [Trace data

type] property.

Select the Bus master of data access from the drop-down list. The following bus masters are displayed in the drop-down list.

Continues overwriting the older trace data after the trace memory is full.

R20UT4588EJ0100 Rev.1.00 Page 28 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

- CPU (default), DMAC/DTC

For data access tracing, only the trace results of data access from the specified bus master are displayed on the trace panel.

Caution 1. This property setting cannot be changed during program execution. Caution 2. For an microcontroller that does not have the function for selecting the Bus master of data

access, the [Bus master of data access][RX71M, RX66x, RX65x, RX64M, RX72M, RX72N, and

RX72T Groups] property is not displayed. In this case, the bus master is fixed to [CPU].

(e) [Output timestamp]

Specify whether timestamp information is added to the trace data to be collected. The change options in this property vary depending on the microcontroller series and the specified value of

[Trace data type] property, as follows:

Microcontroller Data type Change options

RX600, RX700 Series

RX200 Series Branch Not changeable.

RX100 Series Branch, Data access Not changeable.

(f) [Trace clock count source[MHz]]

This property is displayed only when you've specified [Yes] in the [Output timestamp] property. Enter a count source with which a timestamp value is calculated from a count value. To specify this, enter a value directly in the range 0.0001 to 999.999. Note that if this property is blank, the set value of the [Operating frequency [MHz]] property in the [Clock] category of a [Connect Settings] tab is used in place of the count source.

Caution 1. You cannot change this property while the program is in execution. Caution 2. The property's set value is not reflected in the trace data that has already been collected. The

property you've set is reflected beginning with the trace data that is collected after it is set.

(g) [Division ratio of trace clock count source][RX71M, RX66x, RX65x, and RX64M Groups]

This property is displayed only when [Yes] is selected in the [Output timestamp] property. Select the frequency division ratio for the timestamp count source from the drop-down list. The following frequency division ratios are displayed in the drop-down list.

- 1/1 (default), 1/16, 1/256, 1/4096

Branch, Branch + Data access, Data access

Data access Changeable only when program is halted.

Changeable only when program is halted.

[No] is always displayed.

The frequency specified in the [Trace clock count source[MHz]] property is divided by the specified value (the frequency is multiplied by 1/n) and one cycle of the obtained frequency is used as the unit for timestamp count (the frequency for count value 1).

Caution 1. This property setting cannot be changed during program execution. Caution 2. For an microcontroller that does not have the function for dividing the timestamp frequency for

tracing, the [Division ratio of trace clock count source][RX71M, RX66x, RX65x, and RX64M

Groups] property is not displayed. In this case, the division ratio is fixed to [1/1].

(8) [Timer] [RX600, RX700 series]

You can configure the timer function in this category. Figure 2.25 [Timer] Category

(a) [Use 64bit counter]

Specify whether to use two 32-bit counters or one 64-bit counter.

R20UT4588EJ0100 Rev.1.00 Page 29 of 423 Nov 01, 2019

CS+ V8.03.00 2. FUNCTIONS

2.3.2.3 [Download File Settings] tab

You can configure downloading to the debug tool in [Download File Settings] tab. For the details of settings in each cat-

egory, see "2.5.1 Execute downloading".

2.3.2.4 [Hook Transaction Settings] tab

In the [Hook Transaction Settings] tab, you can configure hook transaction for the debug tool. See "2.18 Setting Up the Hook Process" for details on hook transaction and the settings in each category.

R20UT4588EJ0100 Rev.1.00 Page 30 of 423 Nov 01, 2019

+ 393 hidden pages

Renesas CS+ V8.03.00 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

1. GENERAL

1.1 Summary

1.2 Features

2. FUNCTIONS

2.1 Overview

2.2 Preparation before Debugging

2.2.1 Confirm the connection to a host machine

2.2.1.1 [E1]

2.2.1.2 [E20]

2.2.1.3 [EZ Emulator]

2.2.1.4 [Simulator]

2.3 Configuration of Operating Environment of the Debug Tool

2.3.1 Select the debug tool to use

2.3.2 [E1]

2.3.2.1 [Connect Settings] tab

2.3.2.2 [Debug Tool Settings] tab

2.3.2.3 [Download File Settings] tab

2.3.2.4 [Hook Transaction Settings] tab