 |
|
|
RENESAS TOOL NEWS on March 1, 2005: RSO-M3062PT3-RPD-E-050301D
A Note on Using Emulation Pods
for the PC4701 Emulator
|
Please take note of the following problem in using emulation pods for the
PC4701 emulator, which emulates the M16C/60 series of MCUs together with
the M16C PC4701 emulator debugger:
- On the space in the work area necessary to control the emulator
- Product Types Concerned
- For the M16C/62P and M16C/30P groups:
| |
M3062PT3-RPD-E |
| |
M3062PT3-RPD *
* Only the products bearing A at the end of the serial number (those upgraded from TS and WS) |
- For the M16C/62N and M16C/30L groups:
M3062NT3-RPD-E
- For the M30245 MCU (a member of the M16C/24 group):
| |
M30245T3-RPD-E |
| |
M30245T-RPD *
* Only the products bearing M at the end of the serial number (those upgraded from TS, WS, and ES) |
- For the M16C/6N4, /6N5, /6NK, /6NL, /6NM, and /6NN MCUs (members of the M16C/6N group):
M306NKT3-RPD-E
M306NKT3-RPD
- For the M16C/6N4 and /6N5 MCUs (members of the M16C/6N group):
M306N4T3-RPD-E
- For the M306H3 MCU (a member of the M16C/6H group):
M306H3T3-RPD-E
M306H3T3-RPD
- Description
The following known problem has been fixed:
About memory mapping*1: In the firmware file included with the M16C PC4701
emulator debugger*2, if "External" is selected at mapping memory to the
area used as a stack, the data items in register R0 and at address 0000Ah
become indefinite.
| *1: |
For details, see RENESAS TOOL NEWS "A Note on Using Emulation Pods
for the PC4701 Emulator" (Doc. No. RSO-M3062PT3-RPD-E_041001D),
issued on October 1, 2004. |
| *2: |
This emulator debugger is included with the M16C R8C debugger package
V.1.00 Release 00, which was released on January 26, 2005.
For details of the product, see
RENESAS TOOL NEWS "The Debugger Package V.1.00 Release 00
for the M16C/60, M16C/30, M16C/20, M16C/10, M16C/Tiny, and R8C/Tiny Series of MCUs Released"
(Doc. No. RSO-M3062PT3-RPD-E_041001D), issued on January 26, 2005.
|
As a result, the space in the work area necessary to control the
emulator has been increased from 32 bytes to 54 bytes if the pod is
used in combination with the M16C PC4701 emulator.
So, be aware that the emulator takes up 54 bytes from the beginning
address of the work area specified in the Firmware and Work Area tab
(which appears in the INIT window opening when the M16C PC4701 emulator
launched).
However, when the pod is used together with the M3T-PD30 emulator
debugger, a 32-byte space is necessary to control the emulator
as before.
Note that the user's manual included with the emulation pod is still
saying that the necessary space is 32 bytes.
|
|
