 |
|
|
RENESAS TOOL NEWS on December 16, 2003: RSO-HEW_2-031216D
Notes on Using
Integrated Development Environment
High-performance Embedded Workshop
Bundled with the M3T-NC30WA V.5.20 R1 C Compiler
|
|---|
Please take note of the following problems in using the High-performance Embedded Workshop, an integrated
development environment. These problems arise when the Create New Project
Workspace function is used in the High-performance Embedded Workshop:
- On the name of the workspace
- On the selection of PD debuggers
- On using the E7 debugger
- Product and Version Concerned
- The High-performance Embedded Workshop Version 3.01 (release 1)
bundled with the M3T-NC30WA V.5.20 Release 1 C compiler
- The High-performance Embedded Workshop Version 3.01 (release 1)
bundled with the M3T-NC30WA C compiler (Free version for R8C/Tiny only)
- Descriptions
- 2.1 Problem on the Name of the Workspace
- If in the directory created by the Create New Project Workspace
function already exists the same file by name as the one created by
the function, the High-performance Embedded Workshop terminates unsuccessfully during creating the
new project workspace.
When c:\work and test, for example, are used as the directory and
workspace names, the High-performance Embedded Workshop creates the following four directories and
two files:
- Directories:
- c:\work\test
- c:\work\test\test
- c:\work\test\test\release
- c:\work\test\test\debug
- Files:
- c:\work\test\test\ncrt0.a30
- c:\work\test\test\test.c
- If in any of the above directories already exists either of these
files, the High-performance Embedded Workshop is closed unsuccessfully.
- Workaround
- When creating a new workspace, use a fresh directory name as
the directory or workspace name in the New Project Workspace
dialog box.
For example, if a file named c:\work\test\test\ncrt0.a30 already
exists, use a name other than c:\work as a directory name or use
a name other than test as a workspace name.
Notes on Using Integrated Development Environment High-performance Embedded Workshop
Bundled with the M3T-NC30WA V.5.20 R1 C Compiler
RSO-HEW_2-031216D
- 2.2 Problem on the Selection of PD Debuggers
- In the Create New Project Workspace function, if an external debugger
is selected out of the External Debugger list on the New
Project-5/6-Setting the Target System for Debugging dialog box, the
debugger is not accepted as effective information by the workspace.
Consequently, selecting the [Tools] → [Launch External Debugger...]
command fails to work and the High-performance Embedded Workshop cannot be invoked in the debugger.
- Workaround
- When selecting a PD debugger, type the necessary information about
it in the Debugger tab of the Customize dialog box as follows (this
dialog box is opened by selecting the Tool → Customize command):
| (1) |
Select the "PD debugger" command in the drop-down list of the
[External debugger selected] combo box.
|
| (2) |
Type the name of the executable file PDxx.exe in the [PD debugger location] text box.
|
| (3) |
Type "$(CONFIGDIR)\(PROJECTNAME).x30" in the [Download module] text box.
|
For further information, see Section 7.1 "Using the PDxx Debugger"
in the Release Note of the M3T-NC30WA V.5.20 Release 1 or
"How to Register PD Debugger as External Debugger of High-performance Embedded Workshop"
Notes on Using Integrated Development Environment High-performance Embedded Workshop
Bundled with the M3T-NC30WA V.5.20 R1 C Compiler
RSO-HEW_2-031216D
- 2.3 Problem on Using the E7 Debugger
- When the E7 SYSTEM debugger is selected in the Create New Project
Workspace function, clicking the BACK button at the last page
(page 7/7) closes the High-performance Embedded Workshop unsuccessfully.
- Workaround
- When using the E7 SYSTEM debugger, don't click the BACK button at the last page.
- Schedule of Fixing the Problems
We plan to fix these problems in our next release of the product.
|
|
