ID850QB U17435EJ1V0UM00 U17435EJ1V0UM V850ES U15943E V850E1 U14559E - Datasheet Archive

 

Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology

 

To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. 2. 3. 4. 5. 6. 7. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 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. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 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. When exporting the 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. You should not use Renesas Electronics products or the 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. 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. 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. Renesas Electronics products are classified according to the following three quality grades: "Standard", "High Quality", and "Specific". The recommended applications for each Renesas Electronics product depends on the product's quality grade, as indicated below. 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 categorized as "Specific" without the prior written consent of Renesas Electronics. Further, you may not use any Renesas Electronics product for any application for which it is not intended without the prior written consent of Renesas Electronics. 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 an application categorized as "Specific" or for which the product is not intended where you have failed to obtain the prior written consent of Renesas Electronics. The quality grade of each Renesas Electronics product is "Standard" unless otherwise expressly specified in a Renesas Electronics data sheets or data books, etc. "Standard": 8. 9. 10. 11. 12. Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment; home electronic appliances; machine tools; personal electronic equipment; and industrial robots. "High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems; anticrime systems; safety equipment; and medical equipment not specifically designed for life support. "Specific": Aircraft; aerospace equipment; submersible repeaters; nuclear reactor control systems; medical equipment or systems for life support (e.g. artificial life support devices or systems), surgical implantations, or healthcare intervention (e.g. excision, etc.), and any other applications or purposes that pose a direct threat to human life. 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. 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 system manufactured by you. 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. This document may not be reproduced or duplicated, in any form, in whole or in part, without prior written consent of Renesas Electronics. 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 majorityowned subsidiaries. (Note 2) "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics. User's Manual ID850QB ID850QB Ver. 3.10 Integrated Debugger Operation Target Device V850 Series Document No. U17435EJ1V0UM00 U17435EJ1V0UM00 (1st edition) Date Published April 2005 CP(K) © NEC Electronics Corporation 2005 Printed in Japan [MEMO] 2 User's Manual U17435EJ1V0UM U17435EJ1V0UM Windows, Windows NT, and Windows XP are either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. User's Manual U17435EJ1V0UM U17435EJ1V0UM 3 · The information in this document is current as of April, 2005. The information is subject to change without notice. For actual design-in, refer to the latest publications of NEC Electronics data sheets or data books, etc., for the most up-to-date specifications of NEC Electronics products. Not all products and/or types are available in every country. Please check with an NEC Electronics sales representative for availability and additional information. · No part of this document may be copied or reproduced in any form or by any means without the prior written consent of NEC Electronics. NEC Electronics assumes no responsibility for any errors that may appear in this document. · NEC 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 NEC Electronics products listed in this document or any other liability arising from the use of such products. No license, express, implied or otherwise, is granted under any patents, copyrights or other intellectual property rights of NEC Electronics or others. · Descriptions of circuits, software and other related information in this document are provided for illustrative purposes in semiconductor product operation and application examples. The incorporation of these circuits, software and information in the design of a customer's equipment shall be done under the full responsibility of the customer. NEC Electronics assumes no responsibility for any losses incurred by customers or third parties arising from the use of these circuits, software and information. · While NEC Electronics endeavors to enhance the quality, reliability and safety of NEC Electronics products, customers agree and acknowledge that the possibility of defects thereof cannot be eliminated entirely. To minimize risks of damage to property or injury (including death) to persons arising from defects in NEC Electronics products, customers must incorporate sufficient safety measures in their design, such as redundancy, fire-containment and anti-failure features. · NEC Electronics products are classified into the following three quality grades: "Standard", "Special" and "Specific". The "Specific" quality grade applies only to NEC Electronics products developed based on a customerdesignated "quality assurance program" for a specific application. The recommended applications of an NEC Electronics product depend on its quality grade, as indicated below. Customers must check the quality grade of each NEC Electronics product before using it in a particular application. "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. "Special": Transportation equipment (automobiles, trains, ships, etc.), traffic control systems, anti-disaster systems, anti-crime systems, safety equipment and medical equipment (not specifically designed for life support). "Specific": Aircraft, aerospace equipment, submersible repeaters, nuclear reactor control systems, life support systems and medical equipment for life support, etc. The quality grade of NEC Electronics products is "Standard" unless otherwise expressly specified in NEC Electronics data sheets or data books, etc. If customers wish to use NEC Electronics products in applications not intended by NEC Electronics, they must contact an NEC Electronics sales representative in advance to determine NEC Electronics' willingness to support a given application. (Note) (1) "NEC Electronics" as used in this statement means NEC Electronics Corporation and also includes its majority-owned subsidiaries. (2) "NEC Electronics products" means any product developed or manufactured by or for NEC Electronics (as defined above). M8E 02. 11-1 4 User's Manual U17435EJ1V0UM U17435EJ1V0UM Regional Information Some information contained in this document may vary from country to country. Before using any NEC Electronics product in your application, pIease contact the NEC Electronics office in your country to obtain a list of authorized representatives and distributors. They will verify: · Device availability · Ordering information · Product release schedule · Availability of related technical literature · Development environment specifications (for example, specifications for third-party tools and components, host computers, power plugs, AC supply voltages, and so forth) · Network requirements In addition, trademarks, registered trademarks, export restrictions, and other legal issues may also vary from country to country. [GLOBAL SUPPORT] http://www.necel.com/en/support/support.html NEC Electronics America, Inc. (U.S.) NEC Electronics (Europe) GmbH NEC Electronics Hong Kong Ltd. Santa Clara, California Tel: 408-588-6000 800-366-9782 Duesseldorf, Germany Tel: 0211-65030 Hong Kong Tel: 2886-9318 · Sucursal en España Madrid, Spain Tel: 091-504 27 87 · Succursale Française Vélizy-Villacoublay, France Tel: 01-30-67 58 00 · Filiale Italiana Milano, Italy Tel: 02-66 75 41 · Branch The Netherlands Eindhoven, The Netherlands Tel: 040-244 58 45 · Tyskland Filial NEC Electronics Hong Kong Ltd. Seoul Branch Seoul, Korea Tel: 02-558-3737 NEC Electronics Shanghai Ltd. Shanghai, P.R. China Tel: 021-5888-5400 NEC Electronics Taiwan Ltd. Taipei, Taiwan Tel: 02-2719-2377 NEC Electronics Singapore Pte. Ltd. Novena Square, Singapore Tel: 6253-8311 Taeby, Sweden Tel: 08-63 80 820 · United Kingdom Branch Milton Keynes, UK Tel: 01908-691-133 J04.1 User's Manual U17435EJ1V0UM U17435EJ1V0UM 5 [MEMO] 6 User's Manual U17435EJ1V0UM U17435EJ1V0UM PREFACE Target Readers This manual is intended for user engineers who design and develop application systems of the V850 Series. Purpose This manual is intended for users to understand the functions of the ID850QB ID850QB in the organization below. Organization This manual consists of the following chapters: · OVERVIEW · INSTALLATION · STARTING AND TERMINATING · ASSOCIATION WITH PM+ · DEBUG FUNCTION · WINDOW REFERENCE · COMMAND REFERENCE How to Use This Manual It is assumed that the readers of this manual have general knowledge of electrical engineering, logic circuits, microcontrollers, C language, and assemblers. To understand the functions of the V850 Series Refer to Hardware User's Manual for each product. To understand the instruction functions of the V850 Series Refer to V850ES V850ES Architecture User's Manual (U15943E U15943E) or V850E1 V850E1 Architecture User's Manual (U14559E U14559E). Conventions Data significance: Higher digits on the left and lower digits on the right Note: Footnote for item marked with Note in the text Caution: Information requiring particular attention Remark: Supplementary information Numerical representation: Binary . XXXX or XXXXB Decimal . XXXX Hexadecimal . 0xXXXX Prefix indicating the power of 2 (address space, memory capacity): K (Kilo): 210 = 1024 M (Mega): 220 = 10242 User's Manual U17435EJ1V0UM U17435EJ1V0UM 7 Related Documents Refer to the documents listed below when using this manual. The related documents indicated in this publication may include preliminary versions. However, preliminary versions are not marked as such. Documents related to development tools (User's Manuals) Document Name Document No. IE-V850E1-CD-NW IE-V850E1-CD-NW(PCMCIA Card Type On-Chip Debug Emulator) U16647E U16647E QB-V850ESSX2 QB-V850ESSX2(In-circuit emulator for V850ES/SG2 V850ES/SG2, V850ES/SJ2 V850ES/SJ2) U17091E U17091E QB-V850IA4 QB-V850IA4(In-circuit emulator for V850ES/IK1 V850ES/IK1, V850E/IA3 V850E/IA3, V850E/IA4 V850E/IA4) U17167E U17167E QB-V850ESKX1 QB-V850ESKX1(In-circuit emulator for V850ES/Kx1, V850ES/Kx1+) U17214E U17214E CA850 CA850 Ver. 2.70 C Compiler Package Operation U16932E U16932E C Language U16930E U16930E Assembly Language U16931E U16931E Link Directives U16933E U16933E Operation U17293E U17293E C Language U17291E U17291E Assembly Language U17292E U17292E Link Directives U17294E U17294E CA850 CA850 Ver. 3.00 C Compiler Package PM+ Ver.6.00 Project Manager U17178E U17178E ID850QB ID850QB Ver. 3.10 Integrated Debugger Operation This manual SM+ System Simulator Operation U17246E U17246E User Open Interface U17247E U17247E SM850 SM850 Ver. 2.50 System Simulator Operation U16218E U16218E SM850 SM850 Ver. 2.00 or Later System Simulator External Part User Open Interface U14873E U14873E Specifications RX850 RX850 Ver. 3.20 Real-Time OS Basics Installation U17419E U17419E Technical U13431E U13431E Task Debugger U17420E U17420E Fundamental U13773E U13773E Installation U17421E U17421E Technical U13772E U13772E Task Debugger RX850 RX850 Pro Ver. 3.20 Real-Time OS U13430E U13430E U17422E U17422E AZ850 AZ850 Ver. 3.30 System Performance Analyzer U17423E U17423E PG-FP4 Flash Memory Programmer U15260E U15260E TW850 TW850 Ver.2.00 Performance Analysis Tuning Tool U17241E U17241E 8 User's Manual U17435EJ1V0UM U17435EJ1V0UM CONTENTS CHAPTER 1 OVERVIEW . 18 1.1 Features . 19 1.1.1 New functions, enhanced functions . 19 1.1.2 Other functions . 21 1.2 System Configuration . 22 1.3 Operating Environment . 24 1.3.1 Hardware environment . 24 1.3.2 Software environment . 24 1.4 Cautions During Debugging . 25 1.4.1 When performing source level debugging . 25 1.4.2 Security ID . 25 CHAPTER 2 INSTALLATION . 26 2.1 Installing . 26 2.2 Uninstalling . 26 CHAPTER 3 STARTING AND TERMINATING . 27 3.1 Cautions Before Starting (When N-Wire CARD Or MINICUBE Is Connected) . 27 3.2 Startup Option And Argument Specification . 28 3.2.1 Specification method . 29 3.2.2 Specification format and options . 30 3.3 Starting . 31 3.4 Terminating . 32 3.5 Error Messages At Start Up . 33 3.5.1 When IECUBE is connected . 33 3.5.2 When N-Wire CARD or MINICUBE is connected . 34 CHAPTER 4 ASSOCIATION WITH PM+ . 35 4.1 Setting Build Mode . 36 4.2 Registering Debugger To PM+ Project . 36 4.2.1 Selecting debugger . 36 4.2.2 Downloading multiple load module files . 37 4.3 To Start ID850QB ID850QB From PM+ . 38 4.3.1 Restoring debugging environment . 38 4.4 Auto Load . 39 4.4.1 Auto load by correcting source code . 39 4.4.2 Auto load by starting debugger . 40 CHAPTER 5 DEBUG FUNCTION . 41 5.1 Setting Debugging Environment . 42 5.1.1 Setting operating environment . 43 5.1.2 Setting option . 43 5.1.3 Setting mapping . 44 5.1.4 To change the value of a register required for access of an external memory . 44 5.2 Download Function, Upload Function . 45 5.2.1 Download . 46 5.2.2 Upload . 47 5.3 Source Display, Disassemble Display Function . 48 5.3.1 Source display . 49 5.3.2 Disassemble display . 49 5.3.3 Mixed display mode (Source Window) . 50 5.3.4 Convert symbol (symbol to address) . 51 5.4 Break Function . 52 5.4.1 Break types . 53 5.4.2 Breakpoint setting . 54 5.4.3 Setting breaks to variables . 55 5.4.4 Hardware break and software break . 56 User's Manual U17435EJ1V0UM U17435EJ1V0UM 9 5.4.5 Fail-safe break function . 57 5.5 Program Execution Function . 58 5.6 Watch Function . 60 5.6.1 Displaying and changing data values . 61 5.6.2 Displaying and changing local variable values . 62 5.6.3 Registering and deleting watch data . 62 5.6.4 Changing watch data . 63 5.6.5 Temporarily displaying and changing data values . 63 5.6.6 Callout watch function . 64 5.6.7 Stack trace display function . 64 5.7 Memory Manipulation Function . 65 5.7.1 Displaying and changing memory contents . 66 5.7.2 Filling, copying, and comparing memory contents . 66 5.7.3 Access monitor function (when IECUBE is connected) . 67 5.7.4 Flash memory writing function (when N-Wire CARD, MINICUBE is connected) . 67 5.8 Register Manipulation Function . 68 5.8.1 Displaying and changing register contents . 69 5.8.2 Displaying and changing peripheral I/O registers contents . 69 5.8.3 Displaying and changing I/O port contents . 70 5.9 Timer Function (When IECUBE Is Connected) . 71 5.9.1 Timer event conditions . 72 5.9.2 Run-Break event . 72 5.10 Trace Function (When IECUBE Is Connected) . 73 5.10.1 Trace memory . 74 5.10.2 Setting trace data . 74 5.10.3 Checking Trace Data . 75 5.10.4 Mixed display mode (Trace View Window) . 75 5.10.5 Tracer operation . 76 5.10.6 Setting conditional trace . 77 5.10.7 DMA point trace function . 77 5.11 Coverage Measurement Function (When IECUBE Is Connected) . 78 5.11.1 Coverage mesurement result display . 79 5.11.2 Coverage measurement range . 79 5.11.3 Display of locations for which coverage measurement is executed . 80 5.11.4 RRM function, trace function, and coverage function used on a mutually exclusive basis . 81 5.12 Event Function . 82 5.12.1 Using event function . 83 5.12.2 Creating events . 83 5.12.3 Setting event conditions . 84 5.12.4 Number of enabled events for each event condition . 86 5.12.5 Managing events . 87 5.13 RRM Function . 88 5.13.1 Real-time RAM monitor function . 89 5.13.2 Pseudo real-time RAM monitor function (Break When Readout) . 90 5.14 DMM Function . 91 5.15 Load/Save Function . 92 5.15.1 Debugging environment (project file) . 93 5.15.2 Window display information (view file) . 95 5.15.3 Window setting information (setting file) . 96 5.16 Functions Common to Each Window . 97 5.16.1 Active status and static status . 98 5.16.2 Jump function . 99 5.16.3 Trace Result with Linking Window (when IECUBE is connected) . 101 5.16.4 Drag & drop function . 102 5.16.5 Cautions . 104 CHAPTER 6 WINDOW REFERENCE . 105 6.1 Window List . 106 6.2 Explanation of Windows . 109 Main window . 110 Configuration Dialog Box . 123 Extended Option Dialog Box . 129 Fail-safe Break Dialog Box . 135 10 User's Manual U17435EJ1V0UM U17435EJ1V0UM RRM Setting Dialog Box . 137 Flash Option Dialog Box . 140 Debugger Option Dialog Box . 143 Project File Save Dialog Box . 149 Project File Load Dialog Box . 151 Download Dialog Box . 153 Upload Dialog Box . 156 Load Module List Dialog Box . 158 Source Window . 160 Source Search Dialog Box . 165 Source Text Move Dialog Box . 167 Assemble Window . 169 Assemble Search Dialog Box . 173 Address Move Dialog Box . 175 Symbol To Address Dialog Box . 176 Watch Window . 178 Quick Watch Dialog Box . 183 Add Watch Dialog Box . 185 Change Watch Dialog Box . 188 Local Variable Window . 190 Stack Window . 192 Memory Window . 195 Memory Search Dialog Box . 199 Memory Fill Dialog Box . 201 Memory Copy Dialog Box . 202 Memory Compare Dialog Box . 203 Memory Compare Result Dialog Box . 205 DMM Dialog Box . 206 Register Window . 208 Register Select Dialog Box . 211 IOR Window . 213 IOR Select Dialog Box . 217 Add I/O Port Dialog Box . 219 Timer Dialog Box . 221 Timer Result Dialog Box . 225 Trace View Window . 227 Trace Data Select Dialog Box . 232 Trace Search Dialog Box . 234 Trace Move Dialog Box . 239 Trace Dialog Box . 241 Delay Count Dialog Box . 244 Code Coverage Window . 246 Coverage-Address Dialog Box . 249 Software Break Manager . 251 Event Manager . 253 Event Dialog Box . 258 Event Link Dialog Box . 263 Break Dialog Box . 266 View File Save Dialog Box . 268 View File Load Dialog Box . 270 Environment Setting File Save Dialog Box . 272 Environment Setting File Load Dialog Box . 274 Reset Debugger Dialog Box . 276 Exit Debugger Dialog Box . 277 About Dialog Box . 278 Console Window . 280 Font Dialog Box . 281 Browse Dialog Box . 283 CHAPTER 7 COMMAND REFERENCE . 285 7.1 Command Line Rules . 286 7.2 Command List . 287 7.3 List of Variables . 288 User's Manual U17435EJ1V0UM U17435EJ1V0UM 11 7.4 List of Packages . 289 7.5 Key Bind . 289 7.6 Expansion Window . 289 7.7 Callback Procedure . 290 7.8 Hook Procedure . 291 7.9 Related Files . 292 7.10 Cautions . 292 7.11 Explanation Of Commands . 292 address . 293 assemble . 294 batch . 295 breakpoint . 296 cache . 298 dbgexit . 299 dbgopt . 300 download . 301 erase . 302 extwin . 303 finish . 304 flop . 305 go . 306 help . 307 hook . 308 ie . 309 inspect . 310 jump . 311 map . 312 mdi . 314 memory . 315 module . 316 next . 317 refresh . 318 register . 319 reset . 320 run . 321 step . 322 stop . 323 upload . 324 version . 325 watch . 326 where . 327 wish . 328 xcoverage . 329 xtime . 330 xtrace . 331 7.12 Samples (Calculator Script) . 332 APPENDIX A EXPANSION WINDOW . 333 A.1 Overview . 333 A.2 Sample Window . 333 A.3 Activation . 333 A.4 Explanation of each sample window . 334 A.5 List window . 334 Grep window . 335 RRM window . 336 Hook window . 337 Memory Mapped I/O window . 339 Memory Mapped I/O dialog box . 340 Sym Inspect window . 341 Run Break Timer window . 342 APPENDIX B INPUT CONVENTIONS . 343 B.1 Usable Character Set . 344 12 User's Manual U17435EJ1V0UM U17435EJ1V0UM B.2 Symbols . 345 B.3 Numeric Values . 346 B.4 Expressions and Operators . 347 B.5 File Names . 349 APPENDIX C KEY FUNCTION LIST . 350 APPENDIX D MESSAGES . 353 D.1 Display Format . 353 D.2 Types of Messages . 353 D.3 Message Lists . 354 APPENDIX E INDEX . 376 User's Manual U17435EJ1V0UM U17435EJ1V0UM 13 LIST OF FIGURES Figure No 1-1 1-2 1-3 3-1 3-2 3-3 3-4 3-5 4-1 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 5-15 5-16 5-17 5-18 5-19 5-20 5-21 5-22 5-23 5-24 5-25 5-26 5-27 5-28 6-1 6-2 6-3 6-4 6-5 6-6 6-7 6-8 6-9 6-10 6-11 6-12 6-13 6-14 6-15 6-16 6-17 6-18 14 Title, Page ID850QB ID850QB . 18 Example of ID850QB ID850QB System Configuration (IECUBE) . 22 Example of ID850QB ID850QB System Configuration (N-Wire CARD, MINICUBE) . 23 [Debugger Settings] Dialog Box (PM+) . 28 Startup Option (Example) . 29 Configuration Dialog Box . 31 Main Window (At Startup) . 32 Exit Debugger Dialog Box . 32 Downloading Multiple Files . 37 Breakpoint Setting . 54 Setting Break to Variable . 55 Management of Software Breaks . 56 Fail-safe Break Setting . 57 Execution Button . 58 [Run] Menu . 58 Watch Window . 61 Specification of the Display Format (Debugger Option Dialog Box) . 61 Local Variable Window . 62 Change Watch Dialog Box . 63 Quick Watch Dialog Box . 63 Stack Window . 64 Displaying and Changing Memory Contents . 66 Access Monitor Function (Memory Window) . 67 Absolute Name/Function Name Switching . 69 Displaying IOR Contents . 69 Register I/O Port . 70 Sets and Displays Timer Event (Timer Dialog Box) . 72 Setting trace data . 74 Checking Trace Data . 75 Coverage Mesurement Result Display . 79 View of Locations for Which Coverage Measurement Executed . 80 Setting of Various Event Conditions . 84 Managing Events (the Event Manager) . 87 RRM Setting Dialog Box . 89 Specification of Pseudo Real-Time RAM Monitor Function . 90 DMM Dialog Box . 91 Automatic Save/Automatic Load Setting for Project File . 93 Main Window . 110 Toolbar (Picture Only) . 120 Toolbar (Picture and Text) . 120 Status Bar . 121 Configuration Dialog Box (When IECUBE Is Connected) . 123 Configuration Dialog Box (When N-Wire CARD, MINICUBE is connected) . 124 Extended Option Dialog Box Extended Option Dialog Box . 129 Fail-safe Break dialog box . 135 RRM Setting Dialog Box . 137 Flash Option Dialog Box . 140 Debugger Option Dialog Box . 143 Add Source Path Dialog Box . 144 Project File Save Dialog Box . 149 Project File Load Dialog Box . 151 Download Dialog Box . 153 The Progress of Download . 153 Upload Dialog Box . 156 Load Module List Dialog Box . 158 User's Manual U17435EJ1V0UM U17435EJ1V0UM 6-19 6-20 6-21 6-22 6-23 6-24 6-25 6-26 6-27 6-28 6-29 6-30 6-31 6-32 6-33 6-34 6-35 6-36 6-37 6-38 6-39 6-40 6-41 6-42 6-43 6-44 6-45 6-46 6-47 6-48 6-49 6-50 6-51 6-52 6-53 6-54 6-55 6-56 6-57 6-58 6-59 6-60 6-61 6-62 6-63 6-64 6-65 6-66 6-67 6-68 6-69 6-70 7-1 A-1 A-2 A-3 A-4 A-5 A-6 A-7 A-8 D-1 Source Window . 160 Source Search Dialog Box . 165 Source Text Move Dialog Box . 167 Assemble Window . 169 Assemble Search Dialog Box . 173 Address Move Dialog Box (Example: When Memory Window Is Open) . 175 Symbol To Address Dialog Box . 176 Watch Window . 178 Quick Watch Dialog Box . 183 Add Watch Dialog Box . 185 Change Watch Dialog Box . 188 Local Variable Window . 190 Stack Window . 192 Memory Window . 195 Memory Window (When RRM Function Is Selected) . 195 Memory Search Dialog Box . 199 Memory Fill Dialog Box . 201 Memory Copy Dialog Box . 202 Memory Compare Dialog Box . 203 Memory Compare Result Dialog Box . 205 DMM Dialog Box . 206 Register Window . 208 Register Select Dialog Box . 211 IOR Window . 213 IOR Select Dialog Box . 217 Add I/O Port Dialog Box . 219 Timer Dialog Box . 221 Timer Result Dialog Box . 225 Trace View Window . 227 Trace Data Select Dialog Box . 232 Trace Search Dialog Box . 234 Trace Move Dialog Box . 239 Trace Dialog Box . 241 Delay Count Dialog Box . 244 Code Coverage Window . 246 Coverage-Address dialog box . 249 Software Break Manager . 251 Event Manager (In Detailed Display Mode) . 253 Select Display Information Dialog Box . 257 Event Dialog Box . 258 Event Link Dialog Box . 263 Break Dialog Box . 266 View File Save Dialog Box . 268 View File Load Dialog Box . 270 Environment Setting File Save Dialog Box . 272 Environment Setting File Load Dialog Box . 274 Reset Debugger Dialog Box . 276 Exit Debugger Dialog Box . 277 About Dialog Box . 278 Console Window . 280 Font Dialog Box . 281 Browse Dialog Box . 283 Execution Screen . 332 List Window . 334 Grep Window . 335 RRM Window . 336 Hook Window . 337 Memory Mapped I/O Window . 339 Memory Mapped I/O Dialog Box . 340 Sym Inspect Window . 341 RunBreakTimer Window . 342 Error/Warning Messages . 353 User's Manual U17435EJ1V0UM U17435EJ1V0UM 15 LIST OF TABLES Table No 2-1 3-1 3-2 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 5-15 5-16 5-17 5-18 5-19 5-20 5-21 5-22 5-23 5-24 5-25 6-1 6-2 6-3 6-4 6-5 6-6 6-7 6-8 6-9 6-10 6-11 6-12 6-13 6-14 6-15 6-16 6-17 6-18 6-19 6-20 6-21 6-22 6-23 6-24 7-1 16 Title, Page Install . 26 Startup Options . 30 Error Message Output Pattern (When IECUBE Is Connected) . 33 Debug Function List (Flow of Debugging Operations) . 41 Mapping Attribute . 44 Type of File That Can Be Downloaded . 46 Type of File That Can Be Uploaded . 47 File Type Can Be Displayed . 49 Specifying Symbols . 51 Break Types . 53 The Number of Valid Software Break . 56 Type of Execution . 59 Trace Memory Size . 74 Types of Trace Mode . 76 Types of Tracer Control Mode . 76 Types of Conditional Trace . 77 Code Coverage Measurement Range . 79 Format of View of Locations for Which Coverage Measurement Executed . 80 Various Event Conditions . 83 Number of Enabled Events For Each Event Condition . 86 Event Icon . 87 Real-time RAM Monitor Function . 89 Contents Saved to Project File . 94 Type of the View Files . 95 Type of the Setting Files . 96 Details of Jump Source Address . 100 Details of Drag & Drop Function (Line/Address) . 102 Details of Drag & Drop Function (Character String) . 103 Window List . 106 CPU Status . 121 IE Status . 122 Break Cause . 122 Range and Unit of Internal ROM/RAM Setting (When IECUBE Is Connected) . 125 The Relationship Between the Time Tag Counter Division Ratio and Maximum Measurement Time (Time tag counter (Trace) . 130 Relationship Between Meaning of Trace Data to Be Collected and Trace Collection Mode . 131 The Relationship Between the Timer Count Division Ratio and Maximum Measurement Time (Timer counter (Timer) . 132 Event Setting Status (Event Mark) . 161 Watch Window Display Format (Symbol) . 179 Watch Window Display Format (Data) . 180 Watch Window Input Format . 186 How a Variable Is Handled When a Scope Is Specified . 186 Measurable Values . 223 Settable Range of Address Condition (Trace) . 236 Frame Number Specification Format . 240 Number of Events Settable . 242 Coverage Measurement Range (Detail) . 249 Separator for Displaying Event Details . 254 Status Condition . 259 Settable Range of Address Condition (Event) . 261 Settable Range of Data Condition . 261 The Number of Event Conditions in Event Link Dialog Box . 264 Number of Events Settable in Condition Setting Area . 267 List of Debugger Control Commands . 287 User's Manual U17435EJ1V0UM U17435EJ1V0UM 7-2 7-3 A-1 B-1 B-2 B-3 B-4 B-5 B-6 C-1 D-1 List of Console/Tcl Commands . 288 Message ID . 290 List of Expansion Window (Sample) . 333 List of Character Set . 344 List of Special Characters . 344 Input Format of Numeric Values . 346 List of Operators . 347 Operator Priority . 348 Range of Radixes . 349 Key Function List . 350 Types of Messages . 353 User's Manual U17435EJ1V0UM U17435EJ1V0UM 17 CHAPTER 1 OVERVIEW CHAPTER 1 OVERVIEW The Integrated Debugger ID850QB ID850QB for the V850 Series (hereafter referred to as the ID850QB ID850QB) is a software tool developed for NEC Electronics V850 Series of microcontrollers for embedded control. This software tool is intended to enable efficient debugging of user programs. Figure 1-1 ID850QB ID850QB This chapter explains the following items regarding the ID850QB ID850QB. - Features - System Configuration - Operating Environment - Cautions During Debugging 18 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 1 OVERVIEW 1.1 Features The ID850QB ID850QB has the following features: - New functions, enhanced functions - Other functions 1.1.1 New functions, enhanced functions (1) Enhanced RRM function (when IECUBE is connected) Division setting for the sampling range of the real-time RAM monitor area is now possible (refer to "5.13 RRM Function"). Up to 8 locations can be set in 256-byte units in the 2 KB RRM area of the ID850QB ID850QB. Moreover, in the Memory window, the access status (read, write, read & write) can be displayed in different colors using this function. This can also be used as a simple coverage function. (2) Enhanced timer function (when IECUBE is connected) Using an external clock of 50 MHz, measurement of up to 7 segments + Run-Break time (time from program execution start until break) is possible (refer to "5.9 Timer Function (When IECUBE Is Connected)"). Other than during Run-Break, the maximum time, minimum time, pass count, and average time are displayed. Measured time display during user program execution and time-over break are supported. (3) Fail-safe break support (when IECUBE is connected) In addition to the traditional guarded areas and IOR areas, fail-safe break is also supported for the guarded areas of internal ROM/internal RAM (refer to "5.4.5 Fail-safe break function"). (4) Enhanced command function Script file specification is possible at ID startup (refer to "3.2 Startup Option And Argument Specification"). Testing can be done with 1 click by specifying a project file at the same time as the script file. The Tcl/Tk core was updated to the latest version 8.4. (5) Settings during program execution (when IECUBE is connected) Timer event conditions and trace event conditions can now be set during user program execution. (6) Support of N-Wire CARD, MINICUBE and IECUBE Three emulators (IECUBE, N-Wire CARD, MINICUBE,and MINICUBE) can be connected with 1 debugger (ID850QB ID850QB) (refer to "1.2 System Configuration"). In the case of IECUBE or MINICUBE, USB2.0 is supported. User's Manual U17435EJ1V0UM U17435EJ1V0UM 19 CHAPTER 1 OVERVIEW (7) Trace complementation function (when IECUBE is connected) This function performs complementary display of instructions between branch instructions that cannot be traced by the hardware (refer to "5.10.2 Setting trace data"). Complementation/non-complementation can be selected. In the complementation mode, assemble display in the internal ROM area is possible even during program execution (while the tracer is stopped). (8) Supports extension linear addresses In Intel-HEX-format load-module files, 1 MB or more of addresses (extension linear addresses) can be downloaded. (Refer to "5.2 Download Function, Upload Function".) (9) Supports multiple versions Multiple versions of products can be installed in the same machine. (10) Hardware detailed version display The hardware detailed version is displayed in the About Dialog Box. The version can also be confirmed in the Configuration dialog box prior to startup, and the display information can be copied and pasted. Pasting to support mail is now easy. (11) Supports one-byte spaces Single-byte spaces can now be used for folder names. (12) Support of code coverage measurement (when IECUBE is connected and when memory boards are incorporated) Code coverage measurement (C0 coverage) can now be performed. The code coverage can now be displayed in the Code Coverage Window, and sections for which coverage measurement is executed can now be displayed in the Source Window and Assemble Window (refer to "5.11 Coverage Measurement Function (When IECUBE Is Connected)"). (13) Enhanced DMM function DMM (Dynamic Memory Modification) is now possible with memory, registers, or IORs specified. Real-time writing to the memory can be performed with the DMM function during user program execution (refer to "5.14 DMM Function"). (14) Support of emulation memory (when IECUBE is connected and when memory boards are incorporated) Up to 16 MB emulation memory can be used. (15) Support of flash self programming error emulation (when IECUBE is connected) Flash self programming can now be debugged (refer to " Flash Option Dialog Box"). 20 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 1 OVERVIEW 1.1.2 Other functions (1) Using function of in-circuit emulator By using the event setting function of an in-circuit emulator, break events can be set, the user program can be traced, and time can be measured, and so on (refer to "5.12 Event Function"). (2) Support of on-chip debugging (when N-Wire CARD, MINICUBE connected) A debugging function implemented by the on-chip debug unit of the Nx85ET RCU0+TEU+TRCU , Nx85E901 RCU0 RCU1 is provided. (3) Flash memory writing function (when N-Wire CARD, MINICUBE connected) The internal flash memory can be written and the load module can be downloaded by the same access method as an ordinary memory operation (refer to "5.7.4 Flash memory writing function (when N-Wire CARD, MINICUBE is connected)"). (4) Security function (when N-Wire CARD, MINICUBE is connected) The ID code stored in the internal ROM or internal flash memory of a product with a security unit can be authenticated (refer to " Configuration Dialog Box", "(5) ID Code"). (5) Function expansion through Tcl The batch processing and hook processing, and the creation of original user custom windows are possible using the command line with Tcl/Tk (Tool Command Language) (refer to "CHAPTER 7 COMMAND REFERENCE", "APPENDIX A EXPANSION WINDOW"). (6) Function expansion through TIP or ToolLink By associating with a task debugger (RD) and system performance analyzer (AZ) supporting TIP (Tool Interface Protocol) or ToolLink, the debugging efficiency of the user program using a real-time OS (RX) can be dramatically improved. User's Manual U17435EJ1V0UM U17435EJ1V0UM 21 CHAPTER 1 OVERVIEW 1.2 System Configuration The ID850QB ID850QB can be connected to the following two types of emulators. User programs developed for the V850 Series and a pleasant debugging environment for target systems are provided. (1) IECUBE IECUBE can be manipulated from the ID850QB ID850QB by connected it to the ID850QB ID850QB via a USB cable. Figure 1-2 Example of ID850QB ID850QB System Configuration (IECUBE) Host machine USB 1.1/2.0 IECUBE Target System 22 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 1 OVERVIEW (2) N-Wire CARD, MINICUBE The N-Wire CARD, MINICUBE can provide debugging functions by connecting it to a target system on which the V850ES V850ES incorporating an RCU (Run Control Unit) and the V850E1 V850E1 are mounted. The N-Wire CARD a PC card emulator, can be manipulated from the ID850QB ID850QB by directly inserting it to the host machine. The MINICUBE can be manipulated from the ID850QB ID850QB by connected it to the ID850QB ID850QB via a USB cable. Figure 1-3 Example of ID850QB ID850QB System Configuration (N-Wire CARD, MINICUBE) Host machine N-Wire CARD Target system (on which microcontroller incorporating RCU is mounted) ) Host machine USB1.1/2.0 MINICUBE Target system User's Manual U17435EJ1V0UM U17435EJ1V0UM 23 CHAPTER 1 OVERVIEW 1.3 Operating Environment This section explains the following items regarding the operating environment. - Hardware environment - Software environment 1.3.1 Hardware environment (1) Host machine - The machine by which the target OS operates Caution: When N-Wire CARD is connected, because it is assumed that the IECUBE is used with a notebook PC, the host machine must have a PC card slot (TYPEII). (2) In-circuit emulator - IECUBE (QB-V850Exxxx) - MINICUBE (QB-V850MINI QB-V850MINI) - N-Wire CARD (IE-V850E1-CD-NW IE-V850E1-CD-NW) 1.3.2 Software environment (1) OS (any of the following) - Windows98 - Windows2000 - Windows NT4.0 * - WindowsMe - WindowsXP * Caution: Can be used only when N-Wire CARD is connected. Regardless of which of the OS above is used, we recommend that the latest Service Pack is installed. (2) Device file (Individual acquisition) - The device file of the target device to be used. Remark: This file is available from the following Web site of NEC Electronics (ODS). http://www.necel.com/micro/index_e.html 24 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 1 OVERVIEW (3) Supported tools (manufactured by NEC Electronics) - C compiler package CA850 CA850 (Version 3.00 or later) - Project manager PM+ (Version 6.00 or later) - System performance analyzer AZ850 AZ850 (Version 3.30 or later) - Performance tuning tool TW850 TW850 (Version 2.10 or later) 1.4 Cautions During Debugging The cautions to be observed during debugging are described below. - When performing source level debugging - Security ID 1.4.1 When performing source level debugging The object file for which source level debugging is performed must include symbol information or other information for debugging (debugging information). Therefore, perform the following processing during source file compiling. (1) When using PM+ Specify [Debug Build] when the Build mode is selected. (2) When using CA850 CA850 on standalone basis Add the -g option. 1.4.2 Security ID The object file used when N-Wire CARD, MINICUBE is connected must include the security ID information. For the security ID850QB ID850QB settings, refer to "CA850 CA850 Assembler Package Manipulation". For details about the security ID, refer to the N-Wire CARD, MINICUBE user's manual. The security ID (ID code) from the ID850QB ID850QB is set in the Configuration Dialog Box. User's Manual U17435EJ1V0UM U17435EJ1V0UM 25 CHAPTER 2 INSTALLATION CHAPTER 2 INSTALLATION This chapter explains the following items about installation of ID850QB ID850QB: - Installing - Uninstalling 2.1 Installing The following items must be installed, when the ID850QB ID850QB is used. Table 2-1 Install Item Procedure ID850QB ID850QB system disk Install the contents of this disk according to the automatically executed installer. Used device file Install this file according to the DFINST.exe dedicated startup installer by selecting [Start] menu -> [Program] -> [NEC Electronics Tools] -> [Device File Installer]. Caution: When ID850NWC ID850NWC is already installed, ID850QB ID850QB cannot be installed in the same machine. In this case, uninstall ID850NWC ID850NWC before installing ID850QB ID850QB. 2.2 Uninstalling Perform uninstallation using [Add/Remove Programs] on the Control Panel. 26 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 3 STARTING AND TERMINATING CHAPTER 3 STARTING AND TERMINATING This chapter explains the following items related to the starting and terminating the ID850QB ID850QB: - Cautions Before Starting (When N-Wire CARD Or MINICUBE Is Connected) - Startup Option And Argument Specification - Starting - Terminating - Error Messages At Start Up 3.1 Cautions Before Starting (When N-Wire CARD Or MINICUBE Is Connected) When N-Wire CARD or MINICUBE is connected, start the N-Wire Checker before the starting the ID850QB ID850QB to check that the in-circuit emulator and the target system can be normally debugged. Caution: For the connection between the in-circuit emulator and the target system and the power application sequence, refer to the N-Wire CARD or MINICUBE User's Manual. Incorrect connection may damage the in-circuit emulator and the target system. User's Manual U17435EJ1V0UM U17435EJ1V0UM 27 CHAPTER 3 STARTING AND TERMINATING 3.2 Startup Option And Argument Specification The procedure for specifying the startup options and arguments for the ID850QB ID850QB is described below. By specifying the startup options and arguments, it is possible to specify the script file at startup and the project file. Remark: When starting up the ID850QB ID850QB from PM+, the startup option and argument settings are performed in [Debugger Settings.] in the [Tool] menu of PM+ (refer to "CHAPTER 4 ASSOCIATION WITH PM+"). The debugger startup option can be set to the option column. Figure 3-1 [Debugger Settings] Dialog Box (PM+) 28 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 3 STARTING AND TERMINATING 3.2.1 Specification method 1) Create the ID850QB ID850QB shortcut on the desktop. The ID850QB ID850QB execution file is located in the bin folder in the folder to which the installation was performed. 2) Open the properties of the created shortcut and after the execution file name displayed in [Target:], specify the option and argument (refer to "3.2.2 Specification format and options"). Figure 3-2 Startup Option (Example) User's Manual U17435EJ1V0UM U17435EJ1V0UM 29 CHAPTER 3 STARTING AND TERMINATING 3.2.2 Specification format and options (1) Specification format id850g32.exe ?options? id850g32.exe ?options? project Each option and argument is separated by a space. The case is distinguished in the character string. Arguments enclosed between '?' can be omitted. When a project file is specified, that project file is read at startup. However, during PM+ startup, the project file specification is ignored. When there are spaces in the file names and paths, specify the project file names and script file names enclosed in double quotation marks (" "). (Refer to " Example3) Specification when there are spaces in the path".) (2) Specification options The following options can be specified. Table 3-1 Startup Options Options Meaning /SC Change background color of window to system color. /SCRIPT:script file name Specify the script file to be executed at startup. (3) Specification example Example1) Specification of script file only id850g32.exe /script:c:/work/script.tcl Example2) Specification of script file and project file id850g32.exe /script:c:/work/script.tcl c:/work/project.prj Example3) Specification when there are spaces in the path id850g32.exe /script:"c:/work folder/script.tcl" "c:/work folder/project.prj" 30 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 3 STARTING AND TERMINATING 3.3 Starting 1) Start ID850QB ID850QB from the [Start] menu of PM+ or by clicking the shortcut created on the desktop. Refer to "4.3 To Start ID850QB ID850QB From PM+" when starting from PM+. Start the ID850QB ID850QB, the Configuration Dialog Box will be opened. Caution: In this case, the Configuration Dialog Box should not be displayed, but an error message should be displayed, please cope with it with reference to "3.5 Error Messages At Start Up". Figure 3-3 Configuration Dialog Box 2) Set the items related to the operating environment of the ID850QB ID850QB in the Configuration Dialog Box. After setting each item, click the button in the dialog box. User's Manual U17435EJ1V0UM U17435EJ1V0UM 31 CHAPTER 3 STARTING AND TERMINATING 3) The Main window will be opened and the ID850QB ID850QB can be operated. Mainly use this window for debugging. Figure 3-4 Main Window (At Startup) 3.4 Terminating 1) Select [File] menu -> [Exit] on the Main window. The following the Exit Debugger Dialog Box will be opened: (An execution stop confirmation message is displayed when stop operation is performed during program execution.) Figure 3-5 Exit Debugger Dialog Box 2) To save the current debugging environment to a project file, click the button. If the button is clicked, all the windows are closed the ID850QB ID850QB terminated. 32 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 3 STARTING AND TERMINATING 3.5 Error Messages At Start Up Error messages that may be output when ID850QB ID850QB starts up are listed below (by order of occurrence). When these messages are output, refer to "APPENDIX D MESSAGES". Caution: 3.5.1 If both IECUBE and N-Wire CARD are connected, the USB connection (IECUBE) has priority. When IECUBE is connected The pattern of the output error message differs as follows depending on the connection status with the target and the settings in the Configuration Dialog Box. Table 3-2 Error Message Output Pattern (When IECUBE Is Connected) Error Message [Target] Area in the Configuration Dialog Box Connect Not Connect Target Connect Not Connect Exchange Adapter Used Not Used Target Power Supply ON Ff606: Please check Checked connection with the target board, and power on it. OFF Checked Wf607: Please check connection of the exchange adapter. Checked Ff608: Please disconnect the target board. Checked Ff609: Please power off the target board, and disconnect it. Checked Checked Checked Checked Checked Checked Checked F0100 F0100: Can not communicate with ICE. Please confirm the installation of the device driver for the PC interface board. F0c43: Can not communicate with ICE. Please confirm the power of ICE, connection of the interface cable. F0c70: DCU cannot be accessed. F0c76: Initial state at the time of DCU access start is unusual. F0c77: DCU access is unusuall. Ff606: Please check connection with the target board, and power on it. Wf607: Please check connection of the exchange adapter. Ff608: Please disconnect the target board. A0105 A0105: Failed in reading device file (d3xxx.800). F0ca2: This device file does not include the on-chip debug information. User's Manual U17435EJ1V0UM U17435EJ1V0UM 33 CHAPTER 3 STARTING AND TERMINATING F0ca4: This device file does not include the IECUBE information. F0c71: Reset cannot be performed. F0c72: Monitor memory cannot be accessed. F0c73: Monitor execution cannot be performed. F0c74: CPU register cannot be accessed. F0c23: Bus hold under continuation. A0c01: During access of register, CPU did time out. A0c02: During access of memory, CPU did time out. A0c03: During access of I/O register, CPU did time out. A01a0: No response from the evachip. Please confirm the signal of the CLOCK or RESET WAIT, HLDRQ and so on.(IECUBE) No response from the CPU. Please confirm the signal of the CLOCK or RESET WAIT, HLDRQ and so on.(N-Wire CARD, MINICUBE) 3.5.2 When N-Wire CARD or MINICUBE is connected F0100 F0100: Can not communicate with ICE. Please confirm the installation of the device driver for the PC interface board. F0c43: Can not communicate with ICE. Please confirm the power of ICE, connection of the interface cable. F03a0: Target is not turned on. F0c70: DCU cannot be accessed. F0c76: Initial state at the time of DCU access start is unusual. F0c77: DCU access is unusuall. A0105 A0105: Failed in reading device file (d3xxx.800). F0ca2: This device file does not include the on-chip debug information. F0ca3: Unsupported information is included in the on-chip debug information in the device file. F0c24: It cannot shift to debug mode. F0c72: Monitor memory cannot be accessed. F0c73: Monitor execution cannot be performed. F0c74: CPU register cannot be accessed. F0c23: Bus hold under continuation. A0c01: During access of register, CPU did time out. A0c02: During access of memory, CPU did time out. A0c03: During access of I/O register, CPU did time out. A01a0: No response from the evachip. Please confirm the signal of the CLOCK or RESET WAIT, HLDRQ and so on.(IECUBE) No response from the CPU. Please confirm the signal of the CLOCK or RESET WAIT, HLDRQ and so on.(N-Wire CARD, MINICUBE) 34 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 4 ASSOCIATION WITH PM+ CHAPTER 4 ASSOCIATION WITH PM+ The ID850QB ID850QB can automatically perform a series of operations in development processes, such as creating source files -> compiling -> debugging -> correcting source files, in association with the PM+. This chapter explains the following items related to association with the PM+. For details of the PM+ functions, refer to the PM+ User's Manual. - Setting Build Mode - Registering Debugger To PM+ Project - To Start ID850QB ID850QB From PM+ - Auto Load Caution: If a load module file is created by using the Windows command prompt, the function to associate the ID850QB ID850QB with the PM+ cannot be used. User's Manual U17435EJ1V0UM U17435EJ1V0UM 35 CHAPTER 4 ASSOCIATION WITH PM+ 4.1 Setting Build Mode To debug the load module file created by the PM+ on the ID850QB ID850QB at the source level, build to output symbol information for debugging must be performed to create a load module file. This setting can be performed by selecting [Debug Build] on the PM+. 4.2 Registering Debugger To PM+ Project The debugger to be used or the load module files to be downloaded can be specified for each project in the PM+. 4.2.1 Selecting debugger The procedure for selecting the debugger is as follows: The ID850QB ID850QB is registered as the debugger of the active project. The ID850QB ID850QB icon is displayed on the tool bar of the PM+. (1) Creating a new workspace 1) Select [File] menu -> [New Workspace.] on the PM+. -> This opens the dialog box to create a new workspace using the wizard format. 2) Creating the necessary settings for the workspace with the wizard, the [Select Debugger] dialog box will be opened. Specify ID850QB ID850QB in this dialog box. For details of the setting, refer to the User's manual. (2) Using an existing workspace 1) Select [Tool] menu -> [Debugger Settings.] on the PM+. -> The [Debugger Settings] dialog box will be opened. 2) Specify ID850QB ID850QB and click the button in this dialog box. For details of the setting, refer to the User's manual. 36 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 4 ASSOCIATION WITH PM+ 4.2.2 Downloading multiple load module files Load module files in the same project group can be downloaded when using ID850QB ID850QB. Download multiple load module files by specifying items in the [Debugger Settings] dialog box of PM+. Figure 4-1 Downloading Multiple Files For details of the project group, refer to the "User's manual". Remark: Multiple load module files that are being downloaded can be checked in the Load Module List Dialog Box of the ID850QB ID850QB. Caution: If [Execute symbol reset after download] in the [Debugger Settings] dialog box of the product with a internal flash memory is checked, the contents of the internal flash memory are erased before downloading (when N-Wire CARD, MINICUBE is connected) User's Manual U17435EJ1V0UM U17435EJ1V0UM 37 CHAPTER 4 ASSOCIATION WITH PM+ 4.3 To Start ID850QB ID850QB From PM+ The ID850QB ID850QB can be started from the PM+ as follows: - Click the ID850QB ID850QB starting button on the tool bar of the PM+. - Select the [Build] menu -> [Debug] on the PM+. - Select the [Build] menu -> [Build and Debug] on the PM+. - Select the [Build] menu -> [Rebuild and Debug] on the PM+. If the debugging environment of the ID850QB ID850QB is saved to a project file currently being used by the PM+, it will be started in the debugging environment saved in the project file. If the debugging environment of the ID850QB ID850QB is not saved to a project file being used by the PM+, the Configuration Dialog Box is opened. At this time, the device type (chip name) cannot be changed. 4.3.1 Restoring debugging environment The previous debugging environment can be restored by the following procedure when the ID850QB ID850QB is started from the PM+: 1) Create a new workspace (project file: e.g., sample.prj) on the PM+Note. 2) Start the ID850QB ID850QB from the PM+. Because a new project file is created, set items other than the device type (chip name) in the Configuration Dialog Box in the same manner as when only the ID850QB ID850QB is started. 3) Download the load module file to be debugged with the Download Dialog Box of the ID850QB ID850QB. 4) Debug the load module file on the ID850QB ID850QB. 5) Click the button on the Exit Debugger Dialog Box when the ID850QB ID850QB is terminated. -> The debugging environment will be saved to the project file (sample.prj) for the PM+ when the ID850QB ID850QB is terminated (the debug environment can also be saved to the sample.prj file by overwriting the project file at times other than the completion of ID850QB ID850QB debugging). 6) When the ID850QB ID850QB is next started up after the sample.prj file is read by PM+, the debug environment at the point when the project file was saved is automatically restored. Note: In the ID850QB ID850QB and PM+, the environment information is saved to a project file and referenced. The extension of the project file that can be used by the ID850QB ID850QB and PM+ is "prj". For the information that is saved or restored by the project file, refer to the "User's manual" of each product. 38 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 4 ASSOCIATION WITH PM+ 4.4 Auto Load If a bug is found while the load module file is being debugged by the ID850QB ID850QB, correct the source file using the following procedure. Compiling and re-downloading the file can be automatically executed. (Refer to "4.4.1 Auto load by correcting source code".) The load module is downloaded again to the ID850QB ID850QB by compiling and linking the file on the PM+ with the activated ID850QB ID850QB. (Refer to "4.4.2 Auto load by starting debugger".) Caution: This processing cannot be performed if it is selected that the standard editor (idea-L) is used with the PM+. 4.4.1 Auto load by correcting source code Correct the source file for auto load as follows: 1) Open the source file to be corrected in the Source Window. Select [File] menu -> [Open] and specify the file to be corrected on the ID850QB ID850QB (if the file is already open in the Source Window, that window is displayed in the forefront). -> The specified file will be opened in the Source Window. 2) Select [Edit] menu -> [Edit Source] on the ID850QB ID850QB. -> An editor will be opened and the specified source file will be read. 3) Correct the source file on the editor. 4) Terminate the editor. Caution: The CPU reset is not performed when the load module file is automatically downloaded. The debug window that was opened when the editor was called, and each event setting will be restored. If the previously used line or symbol has been deleted as a result of correcting the source file, the following happens: - A variable that was displayed is dimmed. - The event mark of an event condition is displayed in yellow. - A software break point may be deleted. 5) Select [Build] menu -> [Build and Debug], or [Build] menu -> [Rebuild and Debug] on the PM+. User's Manual U17435EJ1V0UM U17435EJ1V0UM 39 CHAPTER 4 ASSOCIATION WITH PM+ 4.4.2 Auto load by starting debugger If the following operation is performed on the PM+ with the ID850QB ID850QB started, the load module will be automatically downloaded to the ID850QB ID850QB. - Selecting the [Build] menu -> [Build and Debug] on the PM+. - Selecting the [Build] menu -> [Rebuild and Debug] on the PM+. Remark: Specify whether to use a CPU reset after downloading from [Debugger Settings.] on the [Tool] menu of PM+ (a CPU reset is performed by default). 40 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION CHAPTER 5 DEBUG FUNCTION This chapter explains about debug function of ID850QB ID850QB. Table 5-1 Debug Function List (Flow of Debugging Operations) Function Refer To To set the debugging environment 5.1 Setting Debugging Environment To download the load module 5.2 Download Function, Upload Function To display the source file and the disassemble result 5.3 Source Display, Disassemble Display Function To set a break point 5.4 Break Function To execute the user program 5.5 Program Execution Function To check the variable value 5.6 Watch Function To check and edit the memory contents 5.7 Memory Manipulation Function To check and change the register variable 5.8 Register Manipulation Function To check the execution time 5.9 Timer Function (When IECUBE Is Connected) To check the trace data 5.10 Trace Function (When IECUBE Is Connected) To check the code coverage measurement results 5.11 Coverage Measurement Function (When IECUBE Is Connected) To manage the events 5.12 Event Function RRM function 5.13 RRM Function DMM function 5.14 DMM Function To save the debug environment and window status 5.15 Load/Save Function Jump function, linking window and cautions 5.16 Functions Common to Each Window User's Manual U17435EJ1V0UM U17435EJ1V0UM 41 CHAPTER 5 DEBUG FUNCTION 5.1 Setting Debugging Environment This section explains the following items related to the setting debugging environment: - Setting operating environment - Setting option - Setting mapping - To change the value of a register required for access of an external memory 42 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.1.1 Setting operating environment The in-circuit emulator operating environment settings are performed in the Configuration Dialog Box that is automatically displayed when ID850QB ID850QB starts up. If a project file already exists, the debugging environment can be restored by clicking the button. (Refer to "5.15.1 Debugging environment (project file)".) 5.1.2 Setting option Perform setting related to the debugger or in-circuit emulator in the following setting dialog boxes. - Configuration Dialog Box - Extended Option Dialog Box - Fail-safe Break Dialog Box - RRM Setting Dialog Box - Flash Option Dialog Box - Debugger Option Dialog Box User's Manual U17435EJ1V0UM U17435EJ1V0UM 43 CHAPTER 5 DEBUG FUNCTION 5.1.3 Setting mapping The mapping settings are performed in the Configuration Dialog Box. The following types of mapping attributes are available: Table 5-2 Mapping Attribute Attribute Meaning Internal ROM Internal RAM(When IECUBE is connected, with memory board) A memory area specified as the internal ROM is equivalent to the internal ROM of the target device (core).If the target device attempts writing to this memory area, a write protect break occurs. Internal RAM Internal RAM(When IECUBE is connected, with memory board) A memory area specified as the internal RAM is equivalent to the internal RAM of the target device. The actual memory configuration depends on the target system. Target User area mapping The memory area specified for user area mapping becomes the area to accesses the memory in the target system or memory incorporated in the CPU. Target ROM Target ROM (When IECUBE is connected) Areas specified as target ROM are subject to write protect for fail-safe break (refer to " Fail-safe Break Dialog Box"). I/O Protect I/O protect area An I/O Protect area can be set in the area specified for the "target". The I/O protect area is displayed in the same manner as an area that is not mapped (display symbol: ?), on the Memory Window. By mapping an area with this attribute, data cannot be read or written from/to this area by the Memory Window, on the area can therefore be protected from an illegal access.To read or write the value of the area mapped with this attribute, register the value in the IOR Window or Watch Window. 5.1.4 To change the value of a register required for access of an external memory When mapping has been performed for external memory, must change the values of the registers required for accessing external memory prior to downloading, using the IOR Window or the hook procedure. For how to change register values using the hook procedure, refer to "7.8 Hook Procedure". For the registers to be changed, refer to the hardware manual of the CPU that is used. 44 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.2 Download Function, Upload Function ID850QB ID850QB allows downloading and uploading of object files in the formats listed in the following table: Table 5-3, Table 5-4. This section explains the following items: - Download - Upload Remark: When N-Wire CARD, MINICUBE is connected, the internal flash memory can be written and the load module can be downloaded (refer to "5.7.4 Flash memory writing function (when N-Wire CARD, MINICUBE is connected)"). User's Manual U17435EJ1V0UM U17435EJ1V0UM 45 CHAPTER 5 DEBUG FUNCTION 5.2.1 Download Object files are downloaded in the Download Dialog Box. The corresponding source text file (Source Window) is displayed by downloading load module files with debug information. Remark: Multiple load module files can be downloaded. Loaded files can be checked in the Load Module List Dialog Box that is opened by selecting [File] menu -> [Load Module]. (1) Format of file that can be downloaded Format of file that can be downloaded is as follows: Table 5-3 Type of File That Can Be Downloaded Format Extension Load module (ELF(.out) Load Module (*.out) Intel Hex format Note1 (Standard, extension, and extension linear) Hex Format (*.hex)Note2 Motorola Hex format S type Extended Tektronix Hex format (S0, S3, S7) Binary data Binary Data (*.bin) Coverage result Coverage (*.cvb) Note1: Addresses of 1 MB or more can be uploaded. Note2: Automatic format detection 46 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.2.2 Upload Uploading of memory contents, etc., is performed in the Upload Dialog Box. The saving range can be set. (1) Format of file that can be uploaded Format of file that can be uploaded is as follows: Table 5-4 Type of File That Can Be Uploaded Format Intel Hex format Note1 Extension Hex Format (*.hex)Note2 Motorola Hex format S type (S0, S3, S7 - 32 bit-address) Extended Tektronix Hex format Binary data Binary Data (*.bin) Coverage results (when IECUBE is connected) Coverage (*.cvb) Note1: Standard (16-bit addresses), extension (20-bit addresses), and extension linear (32-bit addresses) Addresses of 1 MB or more can be uploaded. Note2: Specify saving format User's Manual U17435EJ1V0UM U17435EJ1V0UM 47 CHAPTER 5 DEBUG FUNCTION 5.3 Source Display, Disassemble Display Function Source file display is performed in the Source Window. Disassemble display and online assembly are per- formed in the Assemble Window. This section explains the following items: - Source display - Disassemble display - Mixed display mode (Source Window) - Convert symbol (symbol to address) Remark: The locations for which coverage measurement is executed in the user program are displayed in the Source Window and Assemble Window (refer to "5.11.3 Display of locations for which coverage measurement is executed"). 48 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.3.1 Source display The corresponding text file is displayed in the Source Window by downloading a load module file having debug information. The display start position can be changed in the Source Text Move Dialog Box displayed by selecting [View] menu -> [Move.]. Specifications related to the tab size, display font, etc., and specification of the source path are made in the Debugger Option Dialog Box. Specify a searching method in the Source Search Dialog Box opened by clicking the button. The search result is highlighted in the Source Window. Table 5-5 File Type Can Be Displayed File Type (Extension) Meaning Source (*.c, *.s) Source file (The extension can be changed in the Debugger Option Dialog Box.) Text (*.txt) Text file All (*.*) All files 5.3.2 Disassemble display Disassemble display is performed in the Assemble Window. The display start position can be changed in the Address Move Dialog Box opened by selecting [View] menu -> [Move.]. Offset display and register name display are specified in the Debugger Option Dialog Box. Specify a searching method in the Assemble Search Dialog Box opened by clicking the button. The search result is highlighted in the Assemble Window. User's Manual U17435EJ1V0UM U17435EJ1V0UM 49 CHAPTER 5 DEBUG FUNCTION 5.3.3 Mixed display mode (Source Window) Programs can be disassembled and displayed combined with the source file by selecting [View] menu -> [Mix] in the Source Window. The contents displayed in the mixed display mode can be saved as a view file. Normal display mode In the normal display mode, general text files can be displayed as well as source files. Mixed display mode If a program code corresponds to the line of the displayed source file, the disassembly line is displayed next to the source line. The label of the address, code data, and disassembled mnemonic are displayed (the display start position of the mnemonic is adjusted by the set value of the tab size). Caution: The mixed display mode is valid only when the load module is downloaded and the symbol information is read, and the corresponding source file is displayed. Remark: When scrolling is performed using the cursor keys in the Mixed display mode, excessive scrolling may occur. Also, scrolling down to the last line may not be possible using the cursor keys. 50 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.3.4 Convert symbol (symbol to address) In the Symbol To Address Dialog Box, can be displayed the address of the specified variable or function, or the value of the specified symbol. Convert symbol is performed by selecting the character string to be converted in the Source Window or Assemble Window, and then selecting context menu -> [Symbol.]. The Specification symbols is indicated below. Table 5-6 Specifying Symbols Conversion Target Specification Method Variable var file#var(to specify a static variable with file name) func#var(to specify a static variable with function name) file#func#var(to specify a static variable with file name and function name) Function func file#func (to specify a static function with file name) Label label file#label(to specify a local label with file name) Line number of source file file#no prog$file#no I/O port name portname I/O register name I/O regname Register name regname PSW flag name pswname Remarks1: Separator "#" "#" is used as a separator for file names, variables, function names, and line numbers. If a specified symbol is not found in the scope, all symbols (static variables, static functions, local labels) are searched. Remarks2: Separator "$" To specify a load module name when two or more load modules are read, use "$" as a separator to delimit the load module name from a file name, variable, function name, or symbol name. In the default status, a symbol name takes precedence. To temporarily change the priority, prefixing "$" to a symbol gives the priority to a register name. User's Manual U17435EJ1V0UM U17435EJ1V0UM 51 CHAPTER 5 DEBUG FUNCTION 5.4 Break Function The break function is used to stop execution of the user program by the CPU and operation of the tracer. This section explains the following items: - Break types - Breakpoint setting - Setting breaks to variables - Hardware break and software break - Fail-safe break function 52 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.4.1 Break types The ID850QB ID850QB has the following break functions. Table 5-7 Break Types Item Contents Hardware break Note1 (Event detection break) Function to stop user program execution upon detection of the set break event condition. -> Refer to "5.4.2 Breakpoint setting". Software break Note1 Function to replace the instruction at the specified address software break instruction and stop the user program executed (refer to "5.4.4 Hardware break and software break"). -> Refer to "5.4.2 Breakpoint setting". [Come Here] break Note2 (Simple break) Function to stop user program execution selected by selecting [Run] menu -> [Come Here] upon detection of address specified in the Source Window or Assemble Window. Break on satisfaction of condition of step execution Function to stop execution upon satisfaction of the stop condition of each command ([Step In], [Next Over], [Return Out], [Slowmotion]). Forced break Function to forcibly stop execution by selecting [Run] menu -> [Stop], or selecting the STOP button. It is valid for all the execution commands. Fail-safe break Function to forcibly stop execution when the user program performs an illegal operation in relation to the memory or registers (refer to "5.4.5 Fail-safe break function"). -> Refer to " Fail-safe Break Dialog Box". Time-out break Function to stop user program execution when the measurement time exceeds the specified time-out time (refer to " Timer Dialog Box"). Note1: This break is valid for [Go], [Go & GO], [Come Here] and [Restart]. Note2: After user program execution has been stopped, the breakpoint by this function is eliminated. During execution of a user program by this function, break events set before the cursor position does not occur. User's Manual U17435EJ1V0UM U17435EJ1V0UM 53 CHAPTER 5 DEBUG FUNCTION 5.4.2 Breakpoint setting Breakpoints can simply be set to the desired location by clicking in the Source Window or Assemble Window. Since breakpoints are set as break event conditions and managed using the Event Function, restrictions apply to the number of breakpoints that can be set. (Refer to "5.12.4 Number of enabled events for each event condition".) (1) Breakpoint setting method Breakpoints are executed by clicking lines in which " * " is displayed (lines where program code exists). In the default setting, software breakpoint (B) is set, but if [Breakpoint] is selected in the context menu, hardware breakpoint (B, or B) is set. If a breakpoint is set on a line on which an event breakpoint has already been set, "A" indicating that multiple events have been set is marked (refer to "Table 6-9 Event Setting Status (Event Mark)"). Caution: A software breakpoint cannot be set/delete in an externally mapped ROM area. Remark: Breaks set by default can also be changed in the Extended Option Dialog Box. Figure 5-1 Breakpoint Setting (2) Deleting a breakpoint method Click the position at which the breakpoint to be deleted is set. At the same time as setting is performed, in the default setting, software breakpoint (B) is deleted, but if [Breakpoint] is selected in the context menu, hardware breakpoint (B, or B) is deleted. As a result of deletion, If another event remains, however, the mark of that event is displayed. 54 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.4.3 Setting breaks to variables Access breaks can easily be set to variables from the context menu in the Source Window or Watch Window. Figure 5-2 Setting Break to Variable User's Manual U17435EJ1V0UM U17435EJ1V0UM 55 CHAPTER 5 DEBUG FUNCTION 5.4.4 Hardware break and software break (1) Hardware break Hardware breaks are breaks that are set using one hardware resource per event condition. Therefore, in the ID850QB ID850QB, they are managed using "5.12 Event Function" as break event conditions. The number of valid break points varies depending on the device (refer to "5.12.4 Number of enabled events for each event condition"). (2) Software break Software breaks are breaks that are set by rewriting instructions of specified addresses to software break instructions. Therefore, the number of software breaks that can be set is not limited, but settings to external ROM, stopping at variable access timing, etc., cannot be specified. Table 5-8 The Number of Valid Software Break Connected IE Valid Number IECUBE 2000 N-Wire CARD, MINICUBE 2000 Note: Software breaks in relation to internal ROM and internal flash memory are automatically set by the ROM collection function. The maximum number of software breaks that can be set with the ROM collection function depends on the product (0, 4, or 8). Moreover, the software breaks set with the ROM collection function are temporarily disabled by target reset or internal reset, but they are enabled when a break occurs. Software break is managed by the Software Break Manager. Figure 5-3 Management of Software Breaks 56 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.4.5 Fail-safe break function The fail-safe break settings are performed in the Fail-safe Break Dialog Box. Individual settings are possible by selecting check boxes. Remark: However, the protect setting for the internal RAM area is performed through verify processing by software, and therefore a warning is displayed during breaks. During IOR Illegal and internal RAM verify checks, the address is displayed on the status bar. Figure 5-4 Fail-safe Break Setting User's Manual U17435EJ1V0UM U17435EJ1V0UM 57 CHAPTER 5 DEBUG FUNCTION 5.5 Program Execution Function The program execution function is used to start/stop execution of the user program by the CPU and operation of the tracer. Through user program execution, the program counter (PC) advances until the set breakpoint or forced break. (Refer to "5.4 Break Function".) Remark: While the user program is being executed, trace event condition and timer event condition can be set. (Refer to " Trace Dialog Box", " Timer Dialog Box".) The following types of ID850QB ID850QB execution functions are provided. buttons on the tool bar , or from the [Run] menu. Figure 5-5 Execution Button Figure 5-6 [Run] Menu 58 User's Manual U17435EJ1V0UM U17435EJ1V0UM They are operated using the execution CHAPTER 5 DEBUG FUNCTION Table 5-9 Type of Execution Items Contents [Restart] The CPU is reset and the user program is executed starting from address 0. This is the same operation as "resetting the CPU before execution of the user program and executing [Go]". [Go] The user program is executed starting from the address indicated by the current PC register and is stopped if a set break event condition is satisfied. [Ignore break points and Go] The user program is executed starting from the address indicated by the current PC register Execution of the user program continues, ignoring set breakpoints. [Return Out] The user program is executed until execution returns to the calling function described in C language. [Step In] In the source mode, step execution of one line of the source text is performed starting from the current PC register value and the contents of each window are updated. In the instruction mode, one instruction is executed from the current PC register value and the contents of each window are updated. [Next Over] jarl instruction: Next step execution is performed, assuming the function or subroutine called by the jarl instruction as one step (step execution continues until the nesting level becomes the same as when the jarl instruction was executed). Instruction other than jarl: The same processing as [Step In] is performed. [Start From Here] This command executes the user program starting from the specified address. Execution of the user program is stopped when a set break event condition is satisfied. [Come Here] The user program is executed from the address indicated by the current PC register to the address selected in the line/address display area of the Source Window or Assemble Window, and then a break occurs. While the user program is being executed, the break event currently set does not occur. [Go & Go] The user program is executed starting from the address indicated by the current PC register and stopped if a set break event condition is satisfied. The contents of each window are updated, and execution of the user program is resumed from the address at which the program was stopped. This operation is repeated until the user executes [Stop]. [Slowmotion] Step execution of one line is performed from the address indicated by the current PC register value in the source mode. In the instruction mode, step execution of one instruction is performed. The contents of each window are updated each time step execution is performed. This operation is repeated until the user executes [Stop]. [Stop] Forcibly stops program execution. User's Manual U17435EJ1V0UM U17435EJ1V0UM 59 CHAPTER 5 DEBUG FUNCTION 5.6 Watch Function This section explains the following items related to the watch function: - Displaying and changing data values - Displaying and changing local variable values - Registering and deleting watch data - Changing watch data - Temporarily displaying and changing data values - Callout watch function - Stack trace display function 60 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.6.1 Displaying and changing data values Data values are displayed and changed in the Watch Window. Shifts in data values can be checked by registering watch data. The display format is specified in the Debugger Option Dialog Box. Figure 5-7 Watch Window Figure 5-8 Specification of the Display Format (Debugger Option Dialog Box) User's Manual U17435EJ1V0UM U17435EJ1V0UM 61 CHAPTER 5 DEBUG FUNCTION 5.6.2 Displaying and changing local variable values Local variables are displayed and changed in the Local Variable Window. Local variables within the current function are automatically displayed in this window. (Variable addition/deletion is not possible.) Figure 5-9 Local Variable Window 5.6.3 Registering and deleting watch data Data can be registered to the Watch Window from the Source Window or Assemble Window. This is simply done by selecting the variable or symbol name in the respective window, and then clicking the button. Registration is also possible with the following method. - Drag and drop the selected variable or symbol name directly on the Watch Window. (Refer to "5.16.4 Drag & drop function".) - Click the button in the Quick Watch Dialog Box or Add Watch Dialog Box. To delete watch data, click the variable name or symbol name (multiple selections can also be made using the Shift key or Ctrl key), and then click the button. However, lines with an expanded hierarchy, such as elements of an array, and members of structures and unions, cannot be deleted. 62 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.6.4 Changing watch data Watch data is changed in the Change Watch Dialog Box. Note that the symbol name can be changed even if it results in duplication of a name already in use with existing data. Figure 5-10 Change Watch Dialog Box 5.6.5 Temporarily displaying and changing data values Data values are temporarily displayed and changed in the Quick Watch Dialog Box. Select the desired variable or symbol name in the Source Window or Assemble Window and click the button to perform watch data registration. The display radix, display size, and display number can be changed in this window. Figure 5-11 Quick Watch Dialog Box User's Manual U17435EJ1V0UM U17435EJ1V0UM 63 CHAPTER 5 DEBUG FUNCTION 5.6.6 Callout watch function The corresponding variable value pops up when the mouse cursor is placed over a selected variable in the Source Window or Assemble Window. 5.6.7 Stack trace display function This function displays the stack contents of the current user program in the Stack Window. Figure 5-12 Stack Window 64 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.7 Memory Manipulation Function This section explains the following items related to the memory manipulation: Verify check, etc., is specified in the Extended Option Dialog Box. - Displaying and changing memory contents - Filling, copying, and comparing memory contents - Access monitor function (when IECUBE is connected) - Flash memory writing function (when N-Wire CARD, MINICUBE is connected) User's Manual U17435EJ1V0UM U17435EJ1V0UM 65 CHAPTER 5 DEBUG FUNCTION 5.7.1 Displaying and changing memory contents In the Memory Window, the memory contents can be displayed or changed by using mnemonic codes, hexadecimal codes, and ASCII codes. Searching is done in the Memory Search Dialog Box displayed by clicking the button. The results of search is highlighted in the Memory Window. The display start position can be changed in the Address Move Dialog Box displayed by selecting [View] menu > [Move.]. The variables and data allocated to the sampling range can be displayed in real time even during program execution. (Refer to "5.13 RRM Function".) Figure 5-13 Displaying and Changing Memory Contents 5.7.2 Filling, copying, and comparing memory contents Memory contents are Filled, copied, and compared in the Memory Fill Dialog Box, Memory Copy Dialog Box, and Memory Compare Dialog Box displayed by selecting [Edit] menu -> [Memory] -> [Fill./Copy./Compare.]. The comparison results are displayed in the Memory Compare Result Dialog Box. 66 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.7.3 Access monitor function (when IECUBE is connected) The access monitor function displays the access status (read, write, read & write) for the sampling range of the The RRM Function using different colors in the Memory Window. The access monitor color-marking function is executed only during byte display. Colors are not displayed in the ASCII display area. Cumulative display setting and access status display can be cleared by selecting [View] menu -> [Access Monitoring]. Cautions1: The value of memory rewritten via DMA during program execution, and the value of memory rewritten from the debugger cannot be displayed on the access monitor. Cautions2: This function is enabled only when [Option] menu -> [RRM Function] is selected. Figure 5-14 Access Monitor Function (Memory Window) 5.7.4 Flash memory writing function (when N-Wire CARD, MINICUBE is connected) With the ID850QB ID850QB, the internal flash memory can be written and the load module can be downloaded by the same access method as an ordinary memory operation. The data on the internal flash memory can be changed from the Memory Window, Assemble Window, Watch Window, Memory Fill Dialog Box and Memory Copy Dialog Box, without having to be aware that the data is that of the internal flash memory. The load module can also be downloaded to the internal flash memory by using the flash self-programming function (refer to " Flash Option Dialog Box"). Caution: No data can be written to the internal flash memory during user program execution. Remark: With the ID850QB ID850QB, the remaining area contents after the load module was downloaded to the internal flash memory are erased. User's Manual U17435EJ1V0UM U17435EJ1V0UM 67 CHAPTER 5 DEBUG FUNCTION 5.8 Register Manipulation Function This section explains the following items related to the register manipulation function. - Displaying and changing register contents - Displaying and changing peripheral I/O registers contents - Displaying and changing I/O port contents 68 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.8.1 Displaying and changing register contents Register contents can be displayed and changed in the Register Window. Register name display switching (absolute name/function name) can be done in the Debugger Option Dialog Box. Remark: The display register is selected in the Register Select Dialog Box. Figure 5-15 Absolute Name/Function Name Switching 5.8.2 Displaying and changing peripheral I/O registers contents The peripheral I/O registers contents can be displayed and changed in the IOR Window. The display start position can be changed in the Address Move Dialog Box displayed by selecting [View] menu > [Move.]. The display register is selected in the IOR Select Dialog Box. Figure 5-16 Displaying IOR Contents User's Manual U17435EJ1V0UM U17435EJ1V0UM 69 CHAPTER 5 DEBUG FUNCTION 5.8.3 Displaying and changing I/O port contents User-defined I/O ports can be displayed and changed in the IOR Window once they have been registered in the Add I/O Port Dialog Box. In the case of products that support programmable I/O registers, programmable I/O register contents can be displayed and changed by setting programmable I/O area use in the Configuration Dialog Box. Figure 5-17 Register I/O Port 70 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.9 Timer Function (When IECUBE Is Connected) The timer function measures the execution time (run-break time) from the start of user program execution until a break, or the execution time in a specific user program interval using timer events. The ID850QB ID850QB timer function performs measurements using an external clock. Therefore, the measurable time differs based on the setting in "Table 6-8 The Relationship Between the Timer Count Division Ratio and Maximum Measurement Time (Timer counter (Timer)" (when IECUBE is connected). The Run-Break time is also displayed in the status bar in the Main window. This section explains the following items: - Timer event conditions - Run-Break event Remarks1: Timer event condition setting/enable/disable/delete operations are possible even during user program execution. Remarks2: When N-Wire CARD, MINICUBE is connected, there is no timer event setting function and only Run-Break time measurement is possible. The Run-Break measurement result is displayed in the status bar of the Main window. User's Manual U17435EJ1V0UM U17435EJ1V0UM 71 CHAPTER 5 DEBUG FUNCTION 5.9.1 Timer event conditions A timer event condition specifies the trigger by which time measurement is started or stopped. Timer event conditions are set in the Timer Dialog Box. (Refer to "5.12 Event Function".) In the ID850QB ID850QB, timeout break settings can be performed in the Time Out Break area. Figure 5-18 Sets and Displays Timer Event (Timer Dialog Box) Continuous display in the Timer Result Dialog Box can be selected by clicking the button. Timer manipulations during program execution are performed by selecting [Run] -> [Timer Start/Timer Stop]. 5.9.2 Run-Break event Run-Break event is a timer event name given to a timer event condition that measures the execution time from execution to break. Run-break events are registered in advance and the run-break time can be displayed through specification in the Timer Dialog Box. The Run-Break time is also displayed in the status bar in the Main window. Since Run-Break events are included in the number of timer events that can be simultaneously enabled (refer to "5.12.4 Number of enabled events for each event condition"), they can be used added to the number of valid timer event conditions. 72 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.10 Trace Function (When IECUBE Is Connected) The trace function is used to save the history of the data indicating the execution process of the user program to the trace memory. The DMA (Direct Memory Access) start point and end point are traced regardless of the trace condition. (Refer to "5.10.7 DMA point trace function".) This section explains the following items: - Trace memory - Setting trace data - Checking Trace Data - Mixed display mode (Trace View Window) - Tracer operation - Setting conditional trace - DMA point trace function Caution: RRM Function, Trace Function (When IECUBE Is Connected) and Coverage Measurement Function (When IECUBE Is Connected) are functions that are used on a mutually exclusive basis (refer to "5.11.4 RRM function, trace function, and coverage function used on a mutually exclusive basis"). To switch between the three functions, go to the [Option] menu. Remark: Trace event condition setting/enable/disable/delete operations are possible even during user program execution. In this case, the tracer operation is momentarily stopped during manipulation. User's Manual U17435EJ1V0UM U17435EJ1V0UM 73 CHAPTER 5 DEBUG FUNCTION 5.10.1 Trace memory ID850QB ID850QB has trace memory with a ring structure. Size specification is done in the Extended Option Dialog Box. The maximum trace memory capacity is as follows. Table 5-10 Trace Memory Size Connected IE IECUBE 5.10.2 Maximum Value 256 KB Setting trace data The detailed settings for the collected traced data are done in the Extended Option Dialog Box. Complement display of instructions between branch instructions that cannot be traced by hardware is possible in the complement mode (enabled by selecting the Complement Data area checkbox). When the complement mode is enabled, assemble display of the internal ROM area is possible during user program execution (while the tracer is stopped). Figure 5-19 Setting trace data 74 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.10.3 Checking Trace Data The trace data saved to the trace memory can be checked in the Trace View Window. Trace data can be searched in the Trace Search Dialog Box displayed by clicking the < Search.> button. The display start position can be changed in the Trace Move Dialog Box displayed by selecting [View] -> [Move]. The display items in the Trace View Window can be selected in the Trace Data Select Dialog Box. Figure 5-20 Checking Trace Data 5.10.4 Mixed display mode (Trace View Window) Source file display combined with trace results can be done by selecting [View] -> [Mix] in the Trace View Window (mixed display mode). If a program code corresponds on the program fetch address to be displayed, a source file line is displayed before the line indicating the result of tracing that program fetch address. The source file line is displayed, emphasized in green. Caution: The mixed display mode is valid only when the load module has been downloaded and symbol information is read, and when a fetch address, fetch data, fetch status, or result of disassembly is displayed. User's Manual U17435EJ1V0UM U17435EJ1V0UM 75 CHAPTER 5 DEBUG FUNCTION 5.10.5 Tracer operation The trace operation differs as follows according to the user program execution format and the tracer control mode. Tracer manipulations during program execution are performed by selecting [Run] -> [Tracer Start/Tracer Stop]. (1) Operation during execution The tracer operation differs as follows according to [Run] -> [Cond. Trace ON/Cond. Trace ON] selection. Table 5-11 Types of Trace Mode Item Contents Unconditional trace Trace is started when execution of user program, and ends when a break occurs. At this time, the set trace event conditions are ignored. Conditional trace Trace is started or stopped by the condition set in the Trace Dialog Box (refer to "5.10.6 Setting conditional trace"). If a break occurs while a trace is being executed, however, trace is stopped immediately. (2) Operation during Step In execution The tracer operates every step execution, and trace data of one step is successively added to the trace memory. (3) Operation during Next Over execution The operation of the tracer differs depending on the instruction to which Next Over is to be executed. (a) jarl disp22, [lp] instruction The jarl instruction and the subroutine that was called are traced. (b) Other instructions The same operation as that during Step In execution is performed. (4) Tracer control mode There are the following types of trace control mode. These trace mode settings are performed from the [Run] menu. Table 5-12 Types of Tracer Control Mode Mode Contents Non Stop Goes around the trace memory and overwrites data from the oldest frame (default). Full Stop Goes around the trace memory and then stops the tracer. Full Break Goes around the trace memory and then stops the tracer and program execution Delay Trigger Stop Traces data by the number of delay count frames and stops the tracer when a delay trigger event has occurred. 76 User's Manual U17435EJ1V0UM U17435EJ1V0UM CHAPTER 5 DEBUG FUNCTION 5.10.6 Setting conditional trace A trace event condition triggers starting/stopping trace execution when a conditional trace is set. By setting a trace event condition in the Trace Dialog Box, the conditional trace can be set (refer to "5.12 Event Function"). There are the following types of conditional trace. Table 5-13 Types of Conditional Trace Item Contents, Setting Method Section trace Executes a trace between two specified conditions (in a specific zone). A section trace can be executed by setting a trace start event and trace end event in the Trace Dialog Box and selecting [Run] -> [Cond. Trace ON]. Qualify trace Executes a trace only when a condition is satisfied. If two or more events are set as qualify trace events, a qualify trace can be executed by executing a conditional trace. A qualify trace can be executed by setting a qualify trace event in the Trace Dialog Box and selecting [Run] -> [Cond. Trace ON]. Delay trigger trace Executes a trace by the number of delay counts after a condition has been satisfied. A delay trigger trace can be executed by setting a delay trigger event in the Trace Dialog Box, setting a delay count in the Delay Count Dialog Box and selecting [Run] -> [Cond. Trace ON]. 5.10.7 DMA point trace function The DMA point trace (Direct Memory Access Trace) function is performed prior to normal trace functions. For frames to be accessed using the DMA point trace function, the "M" mark is displayed in the Trace View Window. Below are th