 |
|
|
MESC TOOL NEWS:
MESCT-PD30-980516D
Mitsubishi requests that care should be exercised about a problem that may occur in using emulator debugger PD30 for the M16C/60 series of microcomputers.
Conditions Concerned
The problem occurs under the following conditions:
- PD30 V.3.00 Release 1 or PD30 V.3.00 Release 1A is used and
- Programs are developed for MCUs with 20 KB of internal RAM area by using M16C/62 group emulation pod M30620T-RPD or M30620TB-RPD.
Problem
When an M16C/62 group emulation pod is used with PD30, it is necessary to specify a work area*. This work area can be set within the range of 2C00h--3FFFh in PD30. If a program is developed, however, for an MCU with 20 KB of internal RAM area by using M16C/62 group emulation pod M30620T-RPD or M30620TB-RPD, the work area must be set at 5C00h. How to set it at such an address is explained below.
* A work area means a 10-byte area in the target memory used for debug by the emulator. It is usually set in the internal reserved area in the MCU.
Workaround
A custom command (monw command) and firmware files are provided to set a work area at any address.
Download a self-extracting archive, monw_e.exe (366KB), which comprises the following five files:
| File Name | Description |
| M30620BH.s | Firmware file (for PC4701HS) Ver. 1.20.10 |
| M30620BL.s | Firmware file (for PC4701L) Ver. 1.20.10 |
| monw.p | Program file of custom command monw |
| ini_monw.scr | Sample of a script file at start up |
| readme_e.txt | Readme document of custom command monw |
By installing these files into PD30, a work area can be specified even in the case mentioned above. Also, the setting of a work area with the custom command is automatically performed at launching PD30 after installing these files. For information on installing custom command monw into PD30 and on using it, refer to the Readme file (readme_e.txt) we will provide.
|
|
