Table of Contents
Advertisement
Quick Links
To our customers,
st
On April 1
, 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.
Issued by: Renesas Electronics Corporation (http://www.renesas.com)
Send any inquiries to http://www.renesas.com/inquiry.
Note that the following URLs in this document are not available:
http://www.necel.com/
http://www2.renesas.com/
Please refer to the following instead:
Development Tools | http://www.renesas.com/tools
Download | http://www.renesas.com/tool_download
For any inquiries or feedback, please contact your region.
http://www.renesas.com/inquiry
Old Company Name in Catalogs and Other Documents
Renesas Electronics website: http://www.renesas.com
st
April 1
, 2010
Renesas Electronics Corporation
Advertisement
Table of Contents
Related Manuals for Renesas MINICUBE QB-MINI2
Summary of Contents for Renesas MINICUBE QB-MINI2
- Page 1 On April 1 , 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.
- Page 2 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”...
- Page 3 User’s Manual ® MINICUBE OCD Checker MINICUBE Utility Target Devlopment Tool QB-MINI2 QB-78K0MINI QB-78K0SKX1MINI Document No. U18591EJ2V0UM00 (2nd edition) Date Published October 2008 NS 2007 Printed in Japan...
- Page 4 [MEMO] User’s Manual U18591EJ2V0UM...
- Page 5 MINICUBE is a registered trademark of NEC Electronics Corporation in Japan and Germany. Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. The names of other companies and products are the registered trademarks or trademarks of their companies. •...
- Page 6 INTRODUCTION Target Readers This manual is intended for users who use the MINICUBE OCD Checker when designing and developing a system using an NEC Electronics on-chip flash memory microcontroller. Purpose This manual is intended to give users an understanding of the basic specifications and correct use of the MINICUBE OCD Checker.
- Page 7 Terminology The meanings of the terms used in this manual are as follows. Term Meaning Emulator General name that means MINICUBE2, 78K0 MINICUBE and 78K0S MINICUBE+ MINICUBE2 Indicates QB-MINI2, an on-chip debug emulator with programming function. 78K0 MINICUBE Indicates 78K0 on-chip debug emulator QB-78K0MINI. 78K0S MINICUBE+ Indicates 78K0S/Kx1+ in-circuit emulator QB-78K0SKX1MINI.
-
Page 8: Table Of Contents
CONTENTS CHAPTER 1 OVERVIEW..........................8 MINICUBE OCD Checker ......................8 Target Emulators and Items to Be Checked................8 Notes Before Using OCD Checker....................9 CHAPTER 2 INSTALLATION AND STARTUP..................10 When NEC Electronics Tool Is Used ..................10 2.1.1 Installation............................10 2.1.2 Startup ............................ - Page 9 CHAPTER 8 OCD CHECK FOR 78K0S MINICUBE+ ................44 Execution of OCD Check......................44 Format of Log File........................46 Error Output..........................47 Action for Error .......................... 48 CHAPTER 9 OCD CHECKER VERSION INDICATION................50 CHAPTER 10 UNINSTALLATION ......................51 APPENDIX A REVISION HISTORY ......................52 Major Revisions in This Edition....................
-
Page 10: Chapter 1 Overview
CHAPTER 1 OVERVIEW MINICUBE OCD Checker MINICUBE OCD Checker (hereinafter referred to as OCD Checker) is a self-check tool for simply detecting problems that may occur when an on-chip debug emulator and target system are connected. The OCD Checker checks if The OCD Checker checks if the communication circuits the communication circuits... -
Page 11: Notes Before Using Ocd Checker
CHAPTER 1 OVERVIEW Notes Before Using OCD Checker Chapters 1 and 2 present an overview and basic specifications of the OCD Checker, and the following sections provide separate description for the target device and the emulator to be used. To utilize this manual effectively, refer to the following table and see the relevant section for your target device and purpose of use. -
Page 12: Chapter 2 Installation And Startup
CHAPTER 2 INSTALLATION AND STARTUP This section explains how to install and start the OCD Checker. When NEC Electronics Tool Is Used 2.1.1 Installation • Select the “Emulator Utilities” check box when installing CubeSuite V1.00 or later. The MINICUBE OCD <R>... -
Page 13: When Tools Manufactured By Partner Companies (Ghs And Iar) Are Used
CHAPTER 2 INSTALLATION AND STARTUP Caution If the debugger, QBP, or MINICUBE2 diagnostic tool is running, terminate it before starting the OCD Checker. Remark When an ID78K0-QB or ID78K0S-QB earlier than V3.00, a link file for startup is created in the [NEC Tools32] and [NEC Electronics Utilities] folders. -
Page 14: Explanation Of Each Area
CHAPTER 2 INSTALLATION AND STARTUP Explanation of Each Area When the OCD Checker is started, the following window appears. (11) (10) (1) Emulator mode select area Select from the drop-down list the emulator mode for which target connection check is to be performed. (2) Target Device Connection area If “MINICUBE2 V850”, “MINICUBE2 78K0S”... - Page 15 CHAPTER 2 INSTALLATION AND STARTUP (4) Clock select area Select with the radio button the clock supplied to the emulator. • internal: When a clock mounted in the emulator is used. • socket: When a clock mounted in the CLK1 socket of the MINICUBE2 78K0-OCD board and a clock mounted in the CLK1 socket of the 78K0 MINICUBE or 78K0S MINICUBE+ are used.
-
Page 16: Chapter 3 Ocd Check For Minicube2 And 78K0 Microcontroller
CHAPTER 3 OCD CHECK FOR MINICUBE2 AND 78K0 MICROCONTROLLER This section describes the method to check the connection between MINICUBE2 and the target system, which uses a 78K0 microcontroller as the target device, using the OCD Checker. Execution of OCD Check Be sure to terminate the debugger, QBP and MINICUBE2 diagnostic tool before executing the OCD Checker. - Page 17 CHAPTER 3 OCD CHECK FOR MINICUBE2 AND 78K0 MICROCONTROLLER (5) When all of the tests are complete, the result dialog box is displayed as shown below. The contents displayed in the log view window are saved in the log file. If an NG is displayed, refer to 3.3 Error Output and 3.4 Action for Error.
-
Page 18: Format Of Log File
CHAPTER 3 OCD CHECK FOR MINICUBE2 AND 78K0 MICROCONTROLLER Format of Log File The following shows an example of the log file when the check results show “OK” statuses. Execution time Execution time tt:mm:ss tt:mm:ss Clock status Clock status Target Clock: 20.00MHz [OK] Target Clock: 20.00MHz [OK] status status... -
Page 19: Error Output
CHAPTER 3 OCD CHECK FOR MINICUBE2 AND 78K0 MICROCONTROLLER Error Output The following describes the operation and display example when an NG is displayed as a result of 3.1 Execution of OCD Check. The message just indicates “NG”, but there are various causes. (1) The result is displayed in the dialog box. -
Page 20: Action For Error
CHAPTER 3 OCD CHECK FOR MINICUBE2 AND 78K0 MICROCONTROLLER Action for Error The errors that may occur during self-testing (such as setting error) and relevant actions for coping with the errors are listed below. If an error other than below is displayed, the cause may be a defect in MINICUBE2. If the same error is displayed even after the relevant action is implemented, the cause may be a defect in MINICUBE2. - Page 21 CHAPTER 3 OCD CHECK FOR MINICUBE2 AND 78K0 MICROCONTROLLER (2/2) Error message and action Incorrect ID code The input ID code is incorrect. → Confirm the ID code written to the target device and re-input the ID code. Log file write error The specified log file cannot be accessed.
-
Page 22: Chapter 4 Ocd Check For Minicube2 And V850 Microcontroller
CHAPTER 4 OCD CHECK FOR MINICUBE2 AND V850 MICROCONTROLLER This section describes the method to check the connection between MINICUBE2 and the target system, which uses a V850 microcontroller as the target device, using the OCD Checker. Execution of OCD Check Be sure to terminate the debugger, QBP and MINICUBE2 diagnostic tool before executing the OCD Checker. - Page 23 CHAPTER 4 OCD CHECK FOR MINICUBE2 AND V850 MICROCONTROLLER (4) Click the [Test] button. If an error occurs during checking, refer to 4.3 Error Output and 4.4 Action for Error. (5) When all of the tests are complete, the result dialog box is displayed as shown below. The contents displayed in the log view window are saved in the log file.
-
Page 24: Format Of Log File
CHAPTER 4 OCD CHECK FOR MINICUBE2 AND V850 MICROCONTROLLER (6) Click the [Exit] button. Format of Log File The following shows an example of the log file when the check results show “OK” statuses. Execution time Execution time tt:mm:ss tt:mm:ss status status Target Power: 3.2V... -
Page 25: Error Output
CHAPTER 4 OCD CHECK FOR MINICUBE2 AND V850 MICROCONTROLLER Remark The version of MINICUBE2 can also be checked with the MINICUBE2 diagnostic tool, debugger and QBP. The latest version of MINICUBE2 firmware can be checked on the following NEC Electronics websites. Japanese version: http://www.necel.com/micro/ods/jpn/index.html English version:... -
Page 26: Action For Error
CHAPTER 4 OCD CHECK FOR MINICUBE2 AND V850 MICROCONTROLLER [Log file] Execution time Execution time tt:mm:ss tt:mm:ss status = OK status = OK Target Power: 3.2V Target Power: 3.2V Reset status = OK Reset status = OK Target Reset: HIGH Target Reset: HIGH Hardware version Hardware version... - Page 27 CHAPTER 4 OCD CHECK FOR MINICUBE2 AND V850 MICROCONTROLLER (2/2) Error message and action Cannot find monitor file Check if an unsupported device or unsupported port is selected. Monitor Command(xxH) Error Communication between the target device and MINICUBE2 has failed. →...
-
Page 28: Chapter 5 Ocd Check For Minicube2 And 78K0S Microcontroller
CHAPTER 5 OCD CHECK FOR MINICUBE2 AND 78K0S MICROCONTROLLER This section describes the method to check the connection between MINICUBE2 and the target system, which uses a 78K0S microcontroller as the target device, using the OCD Checker. Execution of OCD Check Be sure to terminate the debugger, QBP and MINICUBE2 diagnostic tool before executing the OCD Checker. - Page 29 CHAPTER 5 OCD CHECK FOR MINICUBE2 AND 78K0S MICROCONTROLLER (4) Click the [Test] button. If an error occurs during checking, refer to 5.3 Error Output and 5.4 Action for Error. (5) When all of the tests are complete, the result dialog box is displayed as shown below. The contents displayed in the log view window are saved in the log file.
-
Page 30: Format Of Log File
CHAPTER 5 OCD CHECK FOR MINICUBE2 AND 78K0S MICROCONTROLLER (6) Click the [Exit] button. Format of Log File The following shows an example of the log file when the check results show “OK” statuses. Execution time Execution time tt:mm:ss tt:mm:ss Reset status Reset status Target Reset: HIGH... -
Page 31: Error Output
CHAPTER 5 OCD CHECK FOR MINICUBE2 AND 78K0S MICROCONTROLLER Remark The version of MINICUBE2 can also be checked with the MINICUBE2 diagnostic tool, debugger and QBP. The latest version of MINICUBE2 firmware can be checked on the following NEC Electronics websites. -
Page 32: Action For Error
CHAPTER 5 OCD CHECK FOR MINICUBE2 AND 78K0S MICROCONTROLLER [Log file] Execution time Execution time tt:mm:ss tt:mm:ss Reset status = OK Reset status = OK Target Reset: HIGH Target Reset: HIGH Hardware version Hardware version MINICUBE2 4100 x xx.xx MINICUBE2 4100 x xx.xx Error indication Error indication Program Download:NG... - Page 33 CHAPTER 5 OCD CHECK FOR MINICUBE2 AND 78K0S MICROCONTROLLER (2/2) Error message and action Emulator Command(xxH) Error Communication between the host machine and MINICUBE2 has failed. (1) Check the connections between the host machine and the USB cable, and the USB cable and the MINICUBE2.
-
Page 34: Chapter 6 Ocd Check For Minicube2 And 78K0R Microcontroller
CHAPTER 6 OCD CHECK FOR MINICUBE2 AND 78K0R MICROCONTROLLER This section describes the method to check the connection between MINICUBE2 and the target system, which uses a 78K0R microcontroller as the target device, using the OCD Checker. Execution of OCD Check Be sure to terminate the debugger, QBP and MINICUBE2 diagnostic tool before executing the OCD Checker. - Page 35 CHAPTER 6 OCD CHECK FOR MINICUBE2 AND 78K0R MICROCONTROLLER (4) Click the [Test] button. If an error occurs during checking, refer to 6.3 Error Output and 6.4 Action for Error. (5) When all of the tests are complete, the result dialog box is displayed as shown below. The contents displayed in the log view window are saved in the log file.
-
Page 36: Format Of Log File
CHAPTER 6 OCD CHECK FOR MINICUBE2 AND 78K0R MICROCONTROLLER (6) Click the [Exit] button. Format of Log File The following shows an example of the log file when the check results show “OK” statuses. Execution time Execution time tt:mm:ss tt:mm:ss status status Target Power: 3.2V [OK]... -
Page 37: Error Output
CHAPTER 6 OCD CHECK FOR MINICUBE2 AND 78K0R MICROCONTROLLER Remark The version of MINICUBE2 can also be checked with the MINICUBE2 diagnostic tool, debugger and QBP. The latest version of MINICUBE2 firmware can be checked on the following NEC Electronics websites. Japanese version: http://www.necel.com/micro/ods/jpn/index.html English version:... -
Page 38: Action For Error
CHAPTER 6 OCD CHECK FOR MINICUBE2 AND 78K0R MICROCONTROLLER [Log file] Execution time Execution time tt:mm:ss tt:mm:ss tt:mm:ss tt:mm:ss status = OK status = OK Target Power: 3.2V [OK] Target Power: 3.2V [OK] Reset status = OK Reset status = OK Target Reset: HIGH Target Reset: HIGH Hardware version... - Page 39 CHAPTER 6 OCD CHECK FOR MINICUBE2 AND 78K0R MICROCONTROLLER (2/2) Error message and action Log file write error The specified log file cannot be accessed. → Confirm that the folder, path, and file are write-enabled. Monitor Command(xxH) Error Communication between the target device and MINICUBE2 has failed. →...
-
Page 40: Chapter 7 Ocd Check For 78K0 Minicube
CHAPTER 7 OCD CHECK FOR 78K0 MINICUBE This section describes the method to check the connection between the 78K0 MINICUBE and self-check board (accessory), using the OCD Checker. Execution of OCD Check Be sure to terminate the debugger before executing the OCD Checker. Perform the connection check according to the following steps (1) to (4). - Page 41 CHAPTER 7 OCD CHECK FOR 78K0 MINICUBE (4) When all of the tests are complete, the result dialog box is displayed as shown below. The contents displayed in the log view window are saved in the log file. If an NG is displayed, refer to 7.3 Error Output and 7.4 Action for Error.
-
Page 42: Format Of Log File
CHAPTER 7 OCD CHECK FOR 78K0 MINICUBE Format of Log File The following shows an example of the log file. Execution time Execution time tt:mm:ss tt:mm:ss Clock status Clock status Target Clock: 5.00MHz [OK] Target Clock: 5.00MHz [OK] status status Target Power: 4.8V [OK] Target Power: 4.8V [OK] Reset status... -
Page 43: Error Output
CHAPTER 7 OCD CHECK FOR 78K0 MINICUBE Error Output The following describes the operation and display example when an NG is displayed as a result of 7.1 Execution of OCD Check. The message just indicates “NG”, but there are various causes. (1) The result is displayed in the dialog box. - Page 44 CHAPTER 7 OCD CHECK FOR 78K0 MINICUBE Action for Error The errors that may occur during self-testing (such as setting error) and relevant actions for coping with the errors are listed below. If an error other than below is displayed, the cause may be a defect in 78K0 MINICUBE. If the same error is displayed even after the relevant action is implemented, the cause may be a defect in the 78K0 MINICUBE.
-
Page 45: Action For Error
CHAPTER 7 OCD CHECK FOR 78K0 MINICUBE (2/2) Error message and action Log file write error The specified log file cannot be accessed. → Confirm that the folder, path, and file are write-enabled. Test Rom Command(xxH) Error, Monitor Command(xxH) Error Communication between the target device on the self-check board and MINICUBE has failed. -
Page 46: Chapter 8 Ocd Check For 78K0S Minicube
CHAPTER 8 OCD CHECK FOR 78K0S MINICUBE+ This section describes the method to perform a simple test based on checking the connection between the QB- 78K0SMINI and QB-78K0SKX1-DA of the 78K0S MINICUBE+, using the OCD Checker. Execution of OCD Check Be sure to terminate the debugger before executing the OCD Checker. - Page 47 CHAPTER 8 OCD CHECK FOR 78K0S MINICUBE+ (4) When all of the tests are complete, the result dialog box is displayed as shown below. The contents displayed in the log view window are saved in the log file. If an NG is displayed, 8.3 Error Output and 8.4 Action for Error.
-
Page 48: Format Of Log File
CHAPTER 8 OCD CHECK FOR 78K0S MINICUBE+ Format of Log File The following shows an example of the log file when the check results show “OK” statuses. Execution time Execution time tt:mm:ss tt:mm:ss Clock status Clock status Target Clock: 10.00MHz [OK] Target Clock: 10.00MHz [OK] status status... -
Page 49: Error Output
CHAPTER 8 OCD CHECK FOR 78K0S MINICUBE+ Error Output The following describes the operation and display example when an NG is displayed as a result of 8.1 Execution of OCD Check. The message just indicates “NG”, but there are various causes. (1) The result is displayed in the dialog box. -
Page 50: Action For Error
CHAPTER 8 OCD CHECK FOR 78K0S MINICUBE+ Action for Error The errors that may occur during self-testing (such as setting error) and relevant actions for coping with the errors are listed below. If an error other than below is displayed, the cause may be a defect in the 78K0S MINICUBE+. If the same error is displayed even after the relevant action is implemented, the cause may be a defect in the 78K0S MINICUBE+. - Page 51 CHAPTER 8 OCD CHECK FOR 78K0S MINICUBE+ (2/2) Error message and action Log file write error The cause may be: The specified log file cannot be accessed. → Confirm that the folder, path, and file are write-enabled. Test Rom Command(xxH) Error, Monitor Command(xxH) Error Communication between the QB-78K0SKX1-DA and QB-78K0SMINI has failed.
-
Page 52: Chapter 9 Ocd Checker Version Indication
CHAPTER 9 OCD CHECKER VERSION INDICATION This section describes the method to check the version. Click the icon on the title bar or right-click the title bar; the system menu is then displayed. Click “About OCD Checker…” on the system menu; the version information window then appears. User’s Manual U18591EJ2V0UM... -
Page 53: Chapter 10 Uninstallation
CHAPTER 10 UNINSTALLATION This section explains how to uninstall the OCD Checker. Note the following points when uninstalling the OCD Checker. • The MINICUBE2 diagnostic tool is uninstalled at the same time. • The log files are not deleted by uninstalling the OCD Checker. Perform uninstallation according to the following steps (1) to (5). -
Page 54: Appendix A Revision History
<R> APPENDIX A REVISION HISTORY Major Revisions in This Edition Page Description CHAPTER 2 INSTALLATION AND STARTUP p.10 Addition of description in 2.1.1 Installation Addition of description in 2.1.2 Startup APPENDIX A REVISION HISTORY p.52 Addition of APPENDIX A REVISION HISTORY User’s Manual U18591EJ2V0UM... - Page 55 [MEMO] User’s Manual U18591EJ2V0UM...
- Page 56 [MEMO] User’s Manual U18591EJ2V0UM...
- Page 57 [MEMO] User’s Manual U18591EJ2V0UM...
- Page 58 For further information, please contact: NEC Electronics Corporation 1753, Shimonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8668, Japan Tel: 044-435-5111 http://www.necel.com/ [Asia & Oceania] [America] [Europe] NEC Electronics (China) Co., Ltd NEC Electronics America, Inc. NEC Electronics (Europe) GmbH 7th Floor, Quantum Plaza, No. 27 ZhiChunLu Haidian 2880 Scott Blvd.