 |
|
|
MAEC TOOL NEWS:
MAECT-PD32R-010401D
Please take note of the following problems in using emulator debugger PD32R for the M32R family of microcomputers:
- On the displays of time in real-time tracing and measurement results in the time measurement window
- On the FDD (Flash Device Definition) file included with PD32R
-
The Problem on the Displays of Time in Real-Time Tracing and Measurement Results in the Time Measurement Window
- 1.1 The Versions Concerned
- PD32R V.1.00 Release 1 -- V.2.00 Release 2
- 1.2 Descriptions
- (1) Time in real-time tracing may be displayed as 00"00'00:000.000.
Time information can be viewed in the following window and commands:
- the Trace window
- the TraceData command
- the TraceList command
- (2) Measurement results in the Time Measurement Window may also be displayed as 00"00'00:000.000.
- 1.3 Conditions
- This problem occurs if hardware breakpoints are set any of the following ways:
- (1) Hardware breakpoints are set by right-clicking the breakpoint display area in the program window.
- (2) Hardware breakpoints are set by right-clicking the breakpoint display area in the source window.
- (3) The "OR" option is selected as a combination type in the hardware breakpoint setting dialog box.
- (4) The "OR" option is selected as a combination type by using the Hardware Break command.
- 1.4 Workaround
- Set hardware breakpoints using the state transition break window.
Should this problem arise, restart PD32R to display correct time.
- 1.5 The Schedule of Fixing the Problem
- We plan to fix this problem in our next release.
- Problem on the FDD (Flash Device Definition) File Included with PD32R
- 2.1 The Versions Concerned
- PD32R V.2.00 Release 1 -- V.2.00 Release 2
- 2.2 Descriptions
- When an FTD (Flash Target Definition) file is created by using the Target Dependence Memory tab in the Init dialog, a device type different from the actual one is displayed in the Device Feature group box in the External Flash ROM Define dialog.
- 2.3 Conditions
- This problem occurs if either of the following conditions is satisfied:
- (1) The M5M29FB160.FDD file included with PD32R V.2.00 is selected as the FDD file.
- In this case, device type M5M26FB160 is displayed in the Device Feature group box.
- (2) The M5M29FT160.FDD file included with PD32R V.2.00 is selected as the FDD file.
- In this case, device type M5M26FT160 is displayed in the Device Feature group box.
- 2.4 Workaround
- Use the FDD files as they are because target files are correctly downloaded to the external flash ROM area though incorrect device names are displayed.
- 2.5 The Schedule of Fixing the Problem
- We plan to fix this problem in our next release.
|
|
