M30220TF-PRB Pod Probe for M30220 and M30221 Group MCUs User's Manual Rev.1.
• NQPACK, YQPACK and YQ-GUIDE are products of Tokyo Eletech Corporation. Keep safety first in your circuit designs! • Renesas Technology Corporation and Renesas Solutions Corporation put the maximum effort into making semiconductor products better and more reliable, but there is always the possibility that trouble may occur with them. Trouble with semiconductors may lead to personal injury, fire or property damage.
Preface The M30220TF-PRB is a pod probe for flash memory rewrite mode debug of the M30220 and M30221 Group of Renesas 16-bit MCUs. The M30220TF-PRB is used by connecting to a PC4701 emulator main unit and the M30200T-RPD-E emulation pod main unit. This product can debug the CPU rewrite mode. CPU rewrite mode debug is a function for debugging rewrites of internal flash memory using your application software.
Contents Terminology ........................................................................................................................... 6 Chapter 1. Precautions for Safety ........................................................................................... 7 1.1 Safety Symbols and Meanings .............................................................................. 8 Chapter 2. Preparation .....................................................................................................
Chapter 6. Troubleshooting .................................................................................................. 45 6.1 When the Emulator Debugger Does Not Start Up Properly ............................... 46 (1) When the LED Display of PC4701 is Abnormal ..................................... 46 (2) Errors Occur When Starting Up the Emulator Debugger (When the target system is connected) ....................................
Terminology Some specific words used in this user's manual are defined as follows: Emulator system This means an emulator system built around the PC4701 emulator. The PC4701 emulator system is configured with an emulator main unit, emulation pod, pod probe, host machine and emulator debugger. Emulator main unit (Hereafter PC4701) This means the generic name for emulators for 8 and 16-bit MCUs. For details on specific models of PC4701, visit Renesas Tools Homepage at http://www.renesas.
Chapter 1. Precautions for Safety This chapter describes precautions for using this product safely and properly. For precautions for the emulator main unit, the emulation pod main unit and the emulator debugger, refer to each user's manual included with your product. 1.1 Safety Symbols and Meanings ..................................................................................................... 8 IMPORTANT Note on Final Evaluation ......................................................................
Chapter 1. Precautions for Safety In both the user's manual and on the product itself, several icons are used to insure proper handling of this product and also to prevent injuries to you or other persons, or damage to your properties. This chapter describes the precautions which should be taken in order to use this product safely and properly. Be sure to read this chapter before using this product. 1.
IMPORTANT Note on Final Evaluation: • Be sure to evaluate your system and make final confirmation with an CS (Commercial Sample) version MCU. Note on Differences between Actual MCU and Emulator: • Operations of the emulator system differ from those of actual MCUs as listed below. (1) Initial values of internal resource data at power-on (2) Internal memories (ROM and RAM) capacities, etc.
IMPORTANT Note on Clock Supply to the MCU: • Clock can be supplied to the evaluation MCU in one of the following two ways. This is determined by emulator debugger clock selection. (1) When "Internal" is selected: The clock generated by the oscillation circuit in the emulation pod is supplied to the evaluation MCU. The clock is continually supplied to the evaluation MCU regardless of "the state of target system clock" and "the state of target program execution".
IMPORTANT Notes on Referencing and Setting the Work Area: • When using this product, set a start address of the work area to "2C00h" at the time of starting up the emulator debugger (set by "F/W and Work Area" tab*1 of Init dialog). In this case, the emulator system uses the area below as a work area. 02C00h - 02C0Fh: Work area *1 Supported by M3T-PD30 Ver.4.00 or later • When using the custom command "fmcr1set" (see "4.
MEMO ( 12 / 54 )
Chapter 2. Preparation This chapter describes the package components, the system configuration and the preparation for using this product for the first time. 2.1 Package Components.................................................................................................................. 14 2.2 Other Tool Products Required for Development........................................................................ 14 2.3 System Configuration ...............................................................
Chapter 2. Preparation 2.1 Package Components This product consists of the following items. When unpacking, check to see if your product package contains all of these items. Table 2.
2.3 System Configuration Figure 2.1 System configuration Product (1) shown in Figure 2.1 is this product. Get (2) to (4) separately. (1) Pod probe (M30220TF-PRB) This pod probe is for flash memory rewrite mode debug of M30220 and M30221 Group MCUs. The evaluation MCUs M30220GP-EVA and M30220GP-PORT are mounted on it. (2) Pitch converter board for 144-pin 0.5-mm-pitch LQFP (FLX-144NSD) This is a pitch converter board (separately available) to be mounted on the foot pattern for 144pin 0.
MEMO ( 16 / 54 )
Chapter 3. Setting Up This chapter describes switch settings required for using this product and how to connect this product to the PC4701 and the target system. 3.1 Switch Settings ........................................................................................................................... 18 3.2 A-D Conversion Bypass Capacitor ............................................................................................ 20 3.3 Connecting the M30200T-RPD-E ....................................
Chapter 3. Setting Up With this product, it is necessary to set the following according to your target system. • CNVSS pin to the target system • XCIN/XCOUT pin to the target system • Mounting the A-D conversion bypass capacitor 3.1 Switch Settings It is necessary to set the switches of the M30220TF-PRB and FLX64-PRB for debugging according to the target system. Figure 3.1 shows the positions of the switches of the M30220TF-PRB and FLX64-PRB, and Table 3.1 shows the switch settings. Figure 3.
Table 3.1 Switch settings of the M30220TF-PRB and FLX64-PRB Board Switch No. Switch setting Function VDD M30220TF-PRB JP1 JP1 CNVSS XCIN CNVSS CNVSS When connecting CNVSS to the target system (Factory-setting) Applies the VCC voltage to CNVSS. When not connecting the target, applies 5 V. The M30220TF-PRB does not use this switch. XCIN is always selected in any setting.
3.2 A-D Conversion Bypass Capacitor This product has foot patterns on the board for mounting a bypass capacitor for the A-D converter circuit. Mount a suitable bypass capacitor as occasion demands. Figure 3.2 shows the position of the bypass capacitor. Figure 3.
3.3 Connecting the M30200T-RPD-E The emulation pod for flash memory rewrite mode debug of the M30220 and M30221 Group MCUs consists of the two products, the M30200T-RPD-E emulation pod main unit and the M30220TF-PRB pod probe. Figures 3.3 and 3.4 show how to connect the M30220TF-PRB and how to remove it, respectively. (1) Connect the J1 and J2 connectors of the M30220TFPRB to the J3 and J4 connectors of the FLX64-PRB. (2) Fix the FLX64-PRB by the two screws. Figure 3.
3.4 Connecting the Target System There are three ways available to connect this product to target system as shown in Figure 3.5. Figure 3.
Figures 3.6, 3.7 and 3.8 show how to connect the pitch converter board FLX-144NSD for 144-pin 0.5-mm-pitch package, how to connect the pitch converter board FLX-144NSE for 144-pin 0.4-mmpitch package and how to connect the pitch converter board FLX-120NSE for 120-pin 0.4-mm-pitch package, respectively. (1) Mount the NQPACK144SD included in the FLX144NSD (separately available) to the target system. (2) Connect the YQPACK144SD included in the FLX144NSD to the NQPACK144SD.
(1) Mount the NQPACK144SE included in the FLX144NSE (separately available) to the target system. (2) Connect the YQPACK144SE included in the FLX144NSE to the NQPACK144SE. Secure the YQPACK144SE using the YQ-GUIDE's. (3) Connect the FLX-144NSE to the M30220TF-PRB. (4) Connect the FLX-144NSE to the YQPACK144SE. Figure 3.7 Connecting the pitch converter board FLX-144NSE for 144-pin 0.
(1) Mount the NQPACK120SE included in the FLX120NSE (separately available) to the target system. (2) Connect the YQPACK120SE included in the FLX120NSE to the NQPACK120SE. Secure the YQPACK120SE using the YQ-GUIDE's. (3) Connect the FLX-120NSE to the M30220TF-PRB. (4) Connect the FLX-120NSE to the YQPACK120SE. Figure 3.8 Connecting the pitch converter board FLX-120NSE for 120-pin 0.
3.5 Procedure for Making an MCU File for M3T-PD30 It is necessary to change the contents of the MCU file according to the MCU to be developed. Make the MCU file M30220.MCU for M30220 Group and M30221.MCU for M30221 Group and store it in the "mcufiles" folder in the folder where emulator debugger M3T-PD30 is stored. For M3T-PD30 Ver.4.10 or earlier, store the MCU file in the same folder as emulator debugger M3T-PD30 is stored in.
Chapter 4. Debugging Procedure for CPU Rewrite Mode This chapter describes procedure for debugging the control program for CPU rewrite mode and restrictions. 4.1 Outline of Debugging Procedure ................................................................................................ 28 4.2 Using Custom Commands dbg_reset and fmcr1set.................................................................... 29 (1) Custom Command dbg_reset ....................................................................
Chapter 4. Debugging Procedure for CPU Rewrite Mode 4.1 Outline of Debugging Procedure You can use the flash memory in the evaluation MCU on the M30220TF-PRB to debug the control program for CPU rewrite mode. Figure 4.1 shows a flow chart of the process. Start M3T-PD30. Register custom commands dbg_reset and fmcr1set. Execute custom command dbg_reset. <- Once registered in the M3T-PD30, there is no need to register again. (See section 4.2.) <- This command must be executed once at M3T-PD30 startup.
4.2 Using Custom Commands dbg_reset and fmcr1set The custom commands dbg_reset and fmcr1set must be used when debugging in CPU rewrite mode. The custom command program file is provided on the attached floppy disk. (1) Custom Command dbg_reset When debugging in CPU rewrite mode, you must execute custom command dbg_reset to initialize tool control. To use custom command dbg_reset, use the following procedure to register dbg_reset in the M3TPD30.
(2) Custom Command fmcr1set When setting "1" in the CPU rewrite mode select bit (FMCR1) (bit 1 of the flash memory control register (address 3B4h), you must write "0" followed consecutively by "1". Because of the interval between the execution of two normal script commands, it is not possible using these normal script commands to write "0" followed consecutively by "1". You can set "1" by using the custom command fmcr1set, which consecutively writes "0", "1" to the CPU rewrite mode select bit (FMCR1).
Custom command fmcr1set specifications Input format: fmcr1set Function: fmcr1set writes the instruction to write "0" and the instruction to write "1" to the CPU rewrite mode select bit (FMCR1) at addresses 2C10h to 2C1Ah, executes them, then sets back the program counter (PC). The program window display starts at the address set in the program counter (PC). (Notes) • The fmcr1set command can set "1" in the CPU rewrite mode select bit (FMCR1).
4.3 Debugging Procedure (1) Debugging Procedure for CPU Rewrite Mode (Microcomputer Mode) Here following describe the debugging procedure in microcomputer mode. Figure 4.2 shows the memory map when debugging. 00000h 00400h SFR area Unused RAM area (3) (4) DE000h (2) Boot ROM area E0000h (5) User ROM area (1) Inside of MCU (MAP: "EXT") Emulation memory (MAP: "INT") FFFFFh Figure 4.
Table 4.1 lists how to set breakpoints for procedures 1 and 3. Table 4.1 How to set breakpoints for procedures 1 and 3 Procedure Description • Examples 1 and 2 show how to set breakpoints to have the result shown below. "Stop after jumping to the RAM area, and before setting the CPU rewrite mode select bit to "1"." Example 1: 1 Example 2: Set a software break at the instruction to jump to the RAM area.
(2) Debugging Procedure for CPU Rewrite Mode (Boot Mode) Here following describe the debugging procedure in boot mode. Figure 4.3 shows the memory map when debugging. 00000h 00400h SFR area Unused RAM area (3) (4) DE000h (2) (1) Boot ROM area E0000h (5) User ROM area FFFFFh Inside of MCU (MAP: "EXT") Emulation memory (MAP: "INT") Figure 4.
Table 4.3 lists how to set breakpoints for procedures 1 and 3. Table 4.3 How to set breakpoints for procedures 1 and 3 Procedure Description • Examples 1 and 2 show how to set breakpoints to have the result shown below. "Stop after jumping to the RAM area, and before setting the CPU rewrite mode select bit to "1"." Example 1: 1 Example 2: Set a software break at the instruction to jump to the RAM area.
4.4 How to Access Flash Memory Area When flash memory is enabled (MAP setting for addresses E0000h to FFFDFh is "EXT" and CPU rewrite mode select bit is "1"), you must invoke software commands to access flash memory area. The following shows how to access the flash memory area using script commands, the dump window, and the RAM monitor window. (1) Using Script Commands To execute Fill and Dump commands to the flash memory area, you need to issue software commands.
4.5 Precautions for CPU Rewrite Mode Here following are precautions and restrictions for debugging the control program for CPU rewrite mode. IMPORTANT Note on Custom Command dbg_reset: • To debug the control program for CPU rewrite mode, you must execute the custom command dbg_reset once every time you start emulator debugger M3T-PD30. If you set the MAP setting of addresses E0000h to FFFDFh to "EXT" without executing dbg_reset, the emulator will run out of control.
IMPORTANT Notes on Setting Software Breaks: • When setting software breaks in the control program for CPU rewrite mode transferred to the RAM area, set the software break points after making the transfer. The software breaks will not function if you set them before the program is transferred to the RAM area. • When setting "1" in the CPU rewrite mode select bit, you must write "0" followed consecutively by "1".
IMPORTANT Note on Number of Program/Erase: • Flash memory is capable of 100 program/erase operations. If you are performing more than 100 program/erase operations, please replace the M30220TF-PRB with a new one. Note on Shutting OFF the Power: • When switching off the power supply to the emulator itself, first select read array mode or either press emulator debugger M3T-PD30 "RESET" button or the reset button of the emulator itself to protect the flash memory.
MEMO ( 40 / 54 )
Chapter 5. Specifications This chapter describes specifications of this product. 5.1 Specifications ............................................................................................................................. 42 5.2 External Dimensions .................................................................................................................. 43 (1) External Dimensions of the Pod Probe .................................................................................
Chapter 5. Specifications 5.1 Specifications Table 5.1 lists the specifications of the M30220TF-PRB. Table 5.1 Specifications of the M30220TF-PRB Emulators PC4701 Emulation pod main unit M30200T-RPD-E Applicable MCUs M30220 and M30221 Group MCUs Usable MCU mode Single-chip mode Emulation memory 1 MB Flash memory (128 K - 32) bytes (Address E0000h - FFFDFh; For how to use the flash memory, refer to Chapter 4.
5.2 External Dimensions (1) External Dimensions of the Pod Probe Unit: mm Figure 5.1 External dimensions of the M30220TF-PRB (2) External Dimensions of the Converter Board (FLX-144NSD) Figure 5.2 shows the external dimensions and a sample foot pattern of the pitch converter board FLX144NSD for 144-pin 0.5-mm-pitch LQFP. Sample foot pattern Unit: mm Figure 5.
(3) External Dimensions of the Converter Board (FLX-144NSE) Figure 5.3 shows the external dimensions and a sample foot pattern of the pitch converter board FLX144NSE for 144-pin 0.4-mm-pitch TQFP. Sample foot pattern Unit: mm Figure 5.3 External dimensions of the FLX-144NSE (4) External Dimensions of the Converter Board (FLX-120NSE) Figure 5.4 shows the external dimensions and a sample foot pattern of the pitch converter board FLX120NSE for 120-pin 0.4-mm-pitch LQFP.
Chapter 6. Troubleshooting This chapter describes how to troubleshoot when this product does not work properly. 6.1 When the Emulator Debugger Does Not Start Up Properly....................................................... 46 (1) When the LED Display of PC4701 is Abnormal .................................................................. 46 (2) Errors Occur When Starting Up the Emulator Debugger (When the target system is connected) ..................................................................
Chapter 6. Troubleshooting When this product does not work properly, check the following. For the latest FAQs, refer to the URL below. http://www.renesas.com/en/tools 6.1 When the Emulator Debugger Does Not Start Up Properly (1) When the LED Display of PC4701 is Abnormal Table 6.1 LED's abnormal display and its checkpoints Error LEDs do not light up. Connection to the target system Checkpoint - Recheck the power cable is connected to the PC4701. See the PC4701 User's Manual.
(2) Errors Occur When Starting Up the Emulator Debugger (When the target system is connected) Table 6.2 Checkpoints of errors when starting up the emulator debugger (target is connected) Error Checkpoint Communication ERROR Data is not sent to the target Check all emulator debugger settings, interface cable connections and switches on the rear of the PC4701 match. See the user's manuals of the PC4701 and emulator debugger. Target system is not constructed properly (1) Download the proper firmware.
(3) Errors Occur When Starting Up the Emulator Debugger (When the target system is not connected) Table 6.3 Checkpoints of errors when starting up emulator debugger (target is not connected) Error Checkpoint Communication ERROR Data is not sent to the target Check all emulator debugger settings, interface cable connections and switches on the rear of the PC4701 match. See the user's manuals of the PC4701 and emulator debugger. Target system is not constructed properly (1) Download the proper firmware.
Chapter 7. Maintenance and Warranty This chapter describes how to maintenance, repair provisions and how to request for repair. 7.1 Maintenance ............................................................................................................................... 50 7.2 Warranty ..................................................................................................................................... 50 7.3 Repair Provisions................................................................
Chapter 7. Maintenance and Guarantee 7.1 Maintenance If dust or dirt collects on any equipment of your emulation system, wipe it off with a dry soft cloth. Do not use thinner or other solvents because these chemicals can cause the equipment's surface coating to separate. 7.
7.4 How to Request for Repair If your product is found faulty, follow the procedure below to send your product for repair. Customer Fill in the Repair Request Sheet included with this product, then send it along with this product for repair to your local distributor. Make sure that information in the Repair Request Sheet is written in as much detail as possible to facilitate repair.
MEMO ( 52 / 54 )
M30220TF-PRB User's Manual Rev.1.
