 |
|
|
MESC TOOL NEWS:
MESCT-PD308SIM-000601D
PD308SIM, PD308, PD30SIM, PD30,
PD79SIM, and PD79
Precautions
|
|---|
Please take note of the following problems in using simulator debuggers PD308SIM, PD30SIM, and PD79SIM, and emulator debuggers PD308, PD30, and PD79:
-
Versions Concerned
| M16C/80 series MCUs | PD308SIM V.1.00 Release 1 -- V.2.00 Release 1 |
| PD308 V.1.00 Release 1 -- V.2.00 Release 1 |
| M16C/60 and 20 series MCUs | PD30SIM V.4.00 Release 1 |
| PD30 V.3.00 Release 1 -- V.5.00 Release 1 |
| 7900 series MCUs | PD79SIM V.2.00 Release 1 -- V.3.00 Release 1 |
| PD79 V.1.10 Release 1 -- V.3.00 Release 1 |
-
Problem on Using the MR Window
Clicking the MPL button in the MR window may display Windows' error message "This program has performed an illegal operation. . . ."
- 2.1 Conditions
- This problem occurs if the following two conditions are satisfied:
- (1) The program has been created using any of the following real-time OSes:
- * MR308 V.1.00 Release 1 -- V.1.00 Release 2
- * MR30 V.3.10 Release 1 -- V.3.20 Release 1
- * MR79 V.2.00 Release 2 -- V.2.00 Release 3
- (2) In the program a variable-size memorypool is used, and the maximum size of the reserved memory block is set to
less than 120 bytes.
- 2.2 Workaround
- Set the maximum size of the reserved memory block to 120 bytes or more when creating programs that use a variable-size memorypool.
- 2.3 Schedule of Fixing Problem
- We plan to fix this problem in our next release.
PD308SIM, PD308, PD30SIM, PD30, PD79SIM, and PD79 Precautions
MESCT-PD308SIM-000601D
-
Problem on Using the MR Trace and MR Analyze Windows(PD308 and PD30 Only)
Incorrect results of measurements may be displayed in the MR trace and MR analyze windows.
* Even if incorrect results are displayed, the user's target program will maintain correct values.
- 3.1 Condition
- This problem occurs if an OS-dependent interrupt is serviced during the processing of the ret_int system call on either of the following real-time OSes:
- * MR308 V.1.00 Release 1 -- V.1.00 Release 2
- * MR30 V.2.00 Release 1 -- V.3.20 Release 1
- 3.2 Interval Where Incorrect Results Displayed
- Incorrect results are displayed at the interval from servicing an OS-dependent interrupt during the processing of the ret_int system call to switching to another task.
- 3.3 Workaround
- We are sorry that there is no way to circumvent this problem of incorrect display in the MR trace and MR analyze windows, so that please use your product with care about this problem.
- 3.4 Schedule of Fixing Problem
- We plan to fix this problem in our next release.
|
|
