 |
|
|
RENESAS TOOL NEWS on February 16, 2005: RSO-HEW_5-050216D
A Note on Using the High-performance Embedded Workshop V.4.00.00
--On Specifying Radixes in HDI Commands--
|
Please take note of the following problem in using the High-performance
Embedded Workshop V.4.00.00, an integrated development environment:
- On specifying radixes in HDI* commands
* Hitachi Debugging Interface
- Product and Version Concerned
The High-performance Embedded Workshop V.4.00.00
To check for the version number of your High-performance Embedded
Workshop, open the Help menu and select the About High-performance Embedded Workshop command.
- Description
- 2.1 On a Change Made to the Specification of Radixes in HDI Commands
- In the High-performance Embedded Workshops V.2.2, V.3.0, and V.3.1,
every number with no prefix in HDI commands is always interpreted as
a decimal number. In its V.4.00.00, on the contrary, a change has
been made so that numbers are represented in the numeral system with
the specified radix. (The specified radix can be checked for using
the Radix button on the toolbar or the Radix command.)
Consequently, when you manipulate in V.4.00.00 numbers entered using
a previous version with no prefix, you need to represent them in the
decimal system by selecting a radix of 10. Or, if you select a radix
in another numeral system, you need to place a D' at the beginning of
the numbers you want to manipulate as decimal ones. Examples are
shown below.
Examples in the hdi status command:
Command syntax: hdi status <linenumber>
When linenumber is set to 11 in the High-performance Embedded
Workshop V.3.1 (see Example 1 below), V.4.00.00 interprets it as a
hexadecimal number. If you want to manipulate it as a decimal number,
place a D' in front of it (see Example 2).
Example 1: hdi status 11
Example 2: hdi status D'11
However, the following two problems occur at specifying radixes in
HDI commands.
- 2.2 Problems
-
| (1) |
When a number has no prefix in the hdi memwrite command with a radix
of 16 being selected (hexadecimal notation), an error will arise if
all of these letters, A, B, C, D, E, and F, are contained in this
number (see Example below).
(This problem occurs in the High-performance Embedded Workshops
V.2.2, V.3.0, and V.3.1.)
Example in the hdi memwrite command:
Command syntax: hdi memwrite <space> <address> <size> <data>
Example: hdi memwrite 0 0 4 89ABCDEF
|
| (2) |
When a number has a prefix of 0x in the hdi memread command with
a radix of 2, 8, or 10 being selected, an error will arise.
Example in the hdi memread command:
Command syntax: hdi memread <space> <address> <count> <size>
If a prefix of 0x is used in all the space, count, and size
parameters, an error arises (see Example Below).
Example: hdi memread 0x0 0x10 0xA 0x1
Example in the hdi memwrite command:
Command syntax: hdi memwrite <space> <address> <size> <data>
If a prefix of 0x is used in all the space, size, and data
parameters, an error arises (see Example Below).
Example: hdi memwrite 0x0 0x10 0x1 0xFF
Example in the hdi msgbox command:
Command syntax: hdi msgbox <text> [<options>]
If a prefix of 0x is used in the options parameters, an error
arises (see Example Below).
Example: hdi msgbox Message 0x1
Example in the hdi progress command:
Command syntax: hdi progress <text> <percentage>
If a prefix of 0x is used in the percentage parameters, an
error arises (see Example Below).
Example: hdi progress Message 0x1
Example in the hdi status command:
Command syntax: hdi status <linenumber>
If a prefix of 0x is used in the linenumber parameters, an
error arises (see Example Below).
Example: hdi status 0x1 |
- Workaround
| (1) | If a number contains all of these letters, A, B, C, D, E, and F, in
the hdi memwrite command with a radix of 16 being selected, give a
prefix of H' to the number.
Example: hdi memwrite 0 0 4 H'89ABCDEF |
| (2) | When a number has a prefix of 0x with a radix of 2, 8, or 10 being
selected, remove the 0x or give a prefix of H' depending on the
value.
Example: hdi memread 0 0x10 H'A 1 |
- Schedule of Fixing the Problem
We plan to fix this problem in our next release of the product.
|
|
