 |
|
|
RENESAS TOOL NEWS on March 1, 2005: RSO-HEW_5-050301D
Supplements to Renesas Tool News
on the High-performance Embedded Workshop
Issued on January 26, 2005
--Three Problems Arising at Using the monitor_set Command Fixed--
|
We inform you of the supplements to RENESAS TOOL NEWS "The High-performance
Embedded Workshop, an Integrated Development Environment, Revised to Its
V.4.00.00," issued on January 26, 2005.
- Three problems arising at using the monitor_set command fixed
- Description
Omissions are found in Section 2.3 "Problems Fixed" in
RENESAS TOOL NEWS
"The High-performance Embedded Workshop, an Integrated Development
Environment, Revised to Its V.4.00.00" (Doc. No. RSO-HEW-050126D),
issued on January 26, 2005. Here we provide you with the supplements to the news.
Three problems, which are described later in Section 2, arise when
the monitor_set command is used in the emulators listed below.
These problems has already been fixed in the High-performance
Embedded Workshop V.4.00.00. So, please update yours to it using
its update program.
| (1) |
E10A-USB emulators
HS0005KCU01H
HS0005KCU02H
Note that the problems occur if any MCU of the New_SH-Mobile,
SH-4A, and SH-2A groups is emulated.
|
| (2) |
E6000H emulators
All the E6000H emulators that can be used in combination with
the High-performance Embedded Workshop
|
| (3) |
E6000 emulators
All the E6000 emulators that can be used in combination with
the High-performance Embedded Workshop
Note that in the following emulators, the problems occur only
when the bus monitoring board is connected:
HS2195EPI60H
HS3008EPI60H
HS3644EPI60H
HS3L08EPI60H
HS388REPI60H
HS3800EPI60H
|
| (4) |
An E200F emulator
R0E0200F0EMU00 |
- Problems Arising at Using the monitor_set Command
The following three problems occur when the monitor_set command is
used. They are fixed in the High-performance Embedded Workshop
V.4.00.00, where no monitoring points are set, and an error message
is displayed if the command is used.
| (1) |
Entering the monitor_set <monitor-window name
(monitoring point name)> command displays the descriptions of
a monitoring point. However, if no monitoring point is specified,
a monitoring point is set all of whose parameters have
their default values (for example, an address of H'0).
Command syntax (the monitoring point name is specified):
monitor_set [<monitor-window name>]
Example: monitor_set monitor1 |
| (2) |
If the values of the address and size parameters exceed their
maximums specified, they are set to the maximums settable in each
monitoring point. Because maximum values settable are different
between emulators, monitoring points having different values of
parameters from your intention are set.
Command syntax (without keywords):
monitor_set <monitor-window name> <address> [<size>] [<format>]
[<refresh_rate>] [<state>] [<detail>]
Example in CPU with 24-bit memory space:
monitor_set monitor1 H'FFFFFFE0 H'20 |
| (3) |
If the size parameter is not specified when the address and other
parameters are specified, size is set to another value than its
default of H'20 in a monitoring point.
Command syntax (with keywords):
monitor_set [name <monitor-window name>] [<address>] [<size>]
[format <format>] [type <type>] [rate <refresh_rate>]
[initial_value <state>] [detail <user specific value
according to respective Target Emulator>]
Example: monitor_set name monitor1 H'FF00 format word
Workaround of Item (3):
Specify the size parameter when specifying address and others.
Example: monitor_set name monitor1 H'FF00 H'20 format word |
|
|
