 |
|
|
RENESAS TOOL NEWS on December 1, 2004: RSO-M3T-PD308F-041201D
A Note on Using Emulator Debuggers
M3T-PD308F, M3T-PD30F, and M3T-PD30MF
|
|---|
Please take note of the following problem in using the M3T-PD308F, M3T-PD30F, and M3T-PD30MF emulator debuggers:
- On using the C Watch window
- Versions Concerned
M3T-PD308F V.1.00 Release 1 through V.3.20 Release 1
(for the M32C/80 series of MCUs)
M3T-PD30F V.1.00 Release 1 through V.2.20 Release 1
(for the M16C/60 and /Tiny series of MCUs)
M3T-PD30MF V.1.00 Release 1
(for the M16C/Tiny series of MCUs)
- Description
Incorrect values of variables may be displayed in the C Watch window if RAM-monitoring display * is used.
| * |
RAM-monitoring display is to provide the values at the locations
of the program executed on RAM in real time using the real-time RAM
monitoring function. The range of RAM to be displayed is 256 bytes
at a time and is set as a RAM monitoring area. |
- Conditions
This problem occurs if the following conditions are all satisfied:
| (1) | The target program is under execution. |
| (2) |
The values of variables are displayed in the C Watch window
using RAM-monitoring display. |
| (3) |
The range of the addresses assigned to the variables in (2) spreads across the 256-byte boundary of the RAM monitoring area.
For example, if a RAM monitoring area is set at addresses 1000H through 11FFH (they are split into two areas, 1000H through 10FFH
and 1100H through 11FFH), RAM monitoring will incorrectly provide the variables of type long at addresses 10FEH through 1101H in the C Watch window. |
- Workaround
If variables concerned are referenced during executing the target
program, display them in the RAM Monitor window.
And, if variables concerned are referenced using the RAM Monitor
window, specify the addresses assigned to them.
- Schedule of Fixing the Problem
We plan to fix this problem in our next release of the products.
|
|
