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
M30220TF-PRB User’s Manual Pod Probe for M30220 and M30221 Group MCUs Rev.1.00 2003.09...
Page 4
• These materials are intended as a reference to assist our customers in the selection of the Renesas Technology product best suited to the customer's application; they do not convey any license under any intellectual property rights, or any other rights, belonging to Renesas Technology Corporation, Renesas Solutions Corporation or a third party.
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.
Contents Terminology ... 6 Chapter 1. Precautions for Safety ... 7 1.1 Safety Symbols and Meanings ... 8 Chapter 2. Preparation ... 13 2.1 Package Components ... 14 2.2 Other Tool Products Required for Development ... 14 2.3 System Configuration ... 15 Chapter 3.
Page 7
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) ... 47 (3) Errors Occur When Starting Up the Emulator Debugger (When the target system is not connected) ...48 6.2 Operation Differs from That of Actual MCUs ...
This means the emulation pod M30200T-RPD-E for the M16C/20 Series MCUs. Pod probe This means pod probe M30220TF-PRB (this product) for the M30220 and M30221 Groups. Host machine This means a personal computer used to control the emulator and emulation pod.
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 ...
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.
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.
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.
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* system uses the area below as a work area. 02C00h - 02C0Fh: Work area •...
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 ... 15 ( 13 / 54 )
M30220TF-PRB User's Manual (Japanese) M30220TF-PRB Repair Request Sheet (English/Japanese) Please keep the M30220TF-PRB's packing box and cushion material in your place for reuse at a later time when sending your product for repair or other purposes. Always use these packing box and cushion material when transporting the M30220TF-PRB.
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.
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 ... 21 3.4 Connecting the Target System...
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.
Page 21
Apply 4.5V to 5.5V voltage to the CNVSS pin of the target system. When the target system is NOT connected: Set the jumper switch JP1 of the M30220TF-PRB to "VDD". 5V voltage is applied from the emulation pod to the CNVSS. Switch 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.2 Foot patterns of A-D conversion bypass capacitor Note on the Operation of A-D Converter: IMPORTANT...
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.
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.5 Connecting the target system ( 22 / 54 )
Page 25
144NSD (separately available) to the target system. (2) Connect the YQPACK144SD included in the FLX- 144NSD to the NQPACK144SD. Secure the YQPACK144SD using the YQ-GUIDE's. (3) Connect the FLX-144NSD to the M30220TF-PRB. (4) Connect the FLX-144NSD to the YQPACK144SD. CAUTION ( 23 / 54 )
Page 26
144NSE (separately available) to the target system. (2) Connect the YQPACK144SE included in the FLX- 144NSE 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. CAUTION ( 24 / 54 )
Page 27
120NSE (separately available) to the target system. (2) Connect the YQPACK120SE included in the FLX- 120NSE 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. CAUTION ( 25 / 54 )
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"...
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 ... 29 (2) Custom Command fmcr1set ...
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.
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.
(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"...
Page 33
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).
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. Figure 4.2 Memory map when debugging in microcomputer mode Procedure Downloading the control program for CPU rewrite mode •...
Page 35
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 • 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"."...
(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 DE000h Boot ROM area E0000h User ROM area FFFFFh Inside of MCU (MAP: "EXT") Figure 4.3 Memory map when debugging in boot mode Procedure...
Page 37
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 • 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"."...
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.
When the target system is NOT connected: Set the jumper switch JP1 of the M30220TF-PRB to "VDD". 5V voltage is applied from the emulation pod to the CNVSS. • Table 4.5 shows the areas of memory addresses E0000h to FFFDFh that are enabled according to the MAP setting and the value of the CPU rewrite mode select bit (FMCR1).
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.
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"...
This chapter describes specifications of this product. 5.1 Specifications ... 42 5.2 External Dimensions ... 43 (1) External Dimensions of the Pod Probe ... 43 (2) External Dimensions of the Converter Board (FLX-144NSD) ... 43 (3) External Dimensions of the Converter Board (FLX-144NSE) ... 44 (4) External Dimensions of the Converter Board (FLX-120NSE) ...
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 Emulation pod main unit Applicable MCUs Usable MCU mode Emulation memory Flash memory Program/erase iterations of flash memory Operating power voltage...
5.2 External Dimensions (1) External Dimensions of the Pod Probe 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 FLX- 144NSD for 144-pin 0.5-mm-pitch LQFP.
(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 FLX- 144NSE for 144-pin 0.4-mm-pitch TQFP. 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 FLX- 120NSE 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) ...
The CLOCK LED of "STATUS OF TARGET" does not light up. The RESET LED of "STATUS OF TARGET" does not go out. http://www.renesas.com/en/tools Connection to the target system 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 Communication ERROR Data is not sent to the target Target system is not constructed properly The version of M3T-PD30 and the firmware on the target system are not same Target MCU is reset state...
(3) Errors Occur When Starting Up the Emulator Debugger Table 6.3 Checkpoints of errors when starting up emulator debugger (target is not connected) Communication ERROR Data is not sent to the target Target system is not constructed properly The version of M3T-PD30 and the firmware on the target are not same Target MCU is in "HOLD"...
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... 50 7.4 How to Request for Repair ... 51 ( 49 / 54 )
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.
After checking the contents of fault, the distributor should please send the faulty product along with the Repair Request Sheet to Renesas Solutions Corp. When the faulty product is repaired, it will be returned to the customer at the earliest convenience.