 |
|
|
MESC TOOL NEWS:
MESCT-PD30-981201D
PD30 V.3.00 and PD38 V.2.00
Precautions
|
|---|
Please take note of the following problem in using emulator debuggers PD30 for the M16C/60 and M16C/20 series and PD38 for the 740 series of microcomputers.
Versions Concerned
The following versions of the products are concerned with this problem:
- PD30 V.3.00 Release 1, Release 1A
- PD38 V.2.00 Release 1
Problem
PD30 V.3.00 and PD38 V.2.00 support the storing and reading functions of information on breakpoints and trace points. However, the phenomenon that information at storing data and one at reading the data differ each other occurs in the following two items of information:
- Information on hardware breakpoints in the hardware breakpoint setting dialog box
- Information on trace points in the trace point setting dialog box (for emulators PC4701HS and PC4700H only)
Workaround
If information at storing data differs from one at reading the data, follow the procedure described below:
- For information on hardware breakpoints in the hardware breakpoint setting dialog box
- Emulators PC4701HS/PC4700H used
Among five buttons ("A1" to "A5"), click the buttons corresponding to hardware breakpoints to be used immediately after reading the file containing information on hardware breakpoints. You see the address breakpoint setting dialog box to be open, and then click the "OK" button to close the dialog box (the setting need not be modified).
- Emulators PC4701L/PC4700L used
Check the contents of pass counts, comparison data, and mask data after reading the file containing information on hardware breakpoints. If you recognize errors in the setting, modify them.
- Information on trace points in the trace point setting dialog box (for emulators PC4701HS and PC4700H only)
Among five buttons ("B1" to "B5"), click the buttons corresponding to trace points to be used immediately after reading the file containing information on trace points. You see the address trace point setting dialog box to be open, and then click the "OK" button to close the dialog box (the setting need not be modified).
Schedule of Fixing Problem
We plan to fix this problem in our next release.
|
|
