June 17th
June 17th, 2010
KPIT Eclipse v2.2, an Eclipse-based Integrated Development Environment (IDE) is
intended for users of Renesas RX, Super-H and H8 series of microcontrollers.
SALIENT FEATURES:
KPIT Eclipse v2.2, which is based on Eclipse version 3.4.1 [Ganymede] and CDT
version 5.0.1 (For more information please visit
http://www.eclipse.org), is a significant
update to KPIT Eclipse(v2.1) and includes the following features:
1.
Integration support for the Renesas RXC toolchain.
2. Hardware
debugging support for the SH and RX targets on the Windows platform. Please
visit the following FAQ link for details on all the configurations:
http://www.kpitgnutools.com/phpmyfaq/index.php?aktion=artikel&rubrik=009001&id=495&lang=en
GNUH8 projects can be easily debugged on hardware using HEW IDE.
Please refer to the KPIT Eclipse User Manual, Section 6 for detailed
steps on hardware debugging. You may also visit the following FAQ link:
http://www.kpitgnutools.com/phpmyfaq/index.php?aktion=artikel&rubrik=009001&id=442&lang=en
3. Simulator debugging support for GNU projects for RX, SH and H8 targets
using GDB.
4. Separate build and debug configurations for hardware debug, simulator
debug, HEW debug and custom debug. Please visit the following FAQ link
for details on all the configurations:
http://www.kpitgnutools.com/phpmyfaq/index.php?aktion=artikel&rubrik=009001&id=495&lang=en
5. Projects built in KPIT Eclipse IDE can be easily debugged in HEW. KPIT
Eclipse provides a feature to launch HEW for debugging.
CHANGES IN THIS RELEASE:
The enhancements in the KPIT Eclipse v2.2 release are as follows:
1. Hardware debug support for RX and SH targets.
In order to debug your application on RX hardware targets via an E1/E20
JTAG interface or on SH hardware targets via an E10A-USB JTAG interface
you must install the corresponding Windows device drivers first.
Typically these drivers are installed by the HEW IDE installer that was
supplied on a CD with your development kit or emulator hardware. In the
event of any problems installing these drivers, please contact either
your distributor, Renesas tools support or the KPIT GNU Support team for
assistance.
2. Extended HEW debug feature support is added. Pre-configured HEW workspaces
have been added for few targets; RX600/RX610, SH7211, SH7264 to extend the
HEW debugging feature. This will allow you to directly download and debug
project (built in KPIT Eclipse) in HEW environment.
The issues fixed in the KPIT Eclipse v2.2 release are as follows:
1. Issue: The 'Debug Configuration' view generates null pointer exceptions
when no project is selected.
The issue is now fixed.
2. Issue: The local variables are not visible in the 'Watch' window while
debugging the GNUH8 projects in KPIT Eclipse.
The issue is now fixed in the GNUH8 v10.01 toolchain.
3. The KEEP() attribute cannot be used per section; instead, it has to be
used per group. This issue is now fixed.
CHANGES IN THE KPIT ECLIPSE v2.2 MAINTENANCE PACK 1 RELEASE:
For all newly created RXC/SHC/GNURX/GNUSH projects using KE v2.2,
'HardwareDebug' is set as active configuration by default. However, at
times, the output (abs/.x) files were generated into the 'Debug' directory
rather than the 'HardwareDebug' directory. Also, the 'Debug' build
configuration was found to be set as active, while the debug configuration
was looking for the output file (.x) file in the 'HardwareDebug'
directory. The issue is now fixed.
CHANGES IN THE KPIT ECLIPSE v2.2 MAINTENANCE PACK 2 RELEASE:
The KE v2.2 failed to launch if it was installed with Japanese support
feature.
The issue is now fixed.
CHANGES IN THE KPIT ECLIPSE v2.2 MAINTENANCE PACK 3 RELEASE:
The version of GDBRX released along with GNURX v10.02 includes some
enhancements to force loading of ELF sections at the LMA (Load Memory
Address, typically in ROM). Integration of the GNURX v10.02 toolchain
with KPIT Eclipse requires the latest version of RX debug components in
KPIT Eclipse. The issue is now fixed in the KPIT Eclipse v2.2 update for
Windows (Maintenance Pack 3).
ABOUT KPIT ECLIPSE v2.2:
Release version : KPIT Eclipse v2.2 (Maintenance Pack 3)
Release Date : June 17th, 2010
Toolchains Supported : Renesas SHC v9.3.0 onwards (*see below)
Renesas RXC v1.0.0 onwards (*see below)
GNUSH v0902 onwards
GNUH8 v0902 onwards
GNURX v10.01 onwards
Platforms Supported : Windows XP / Vista, Windows XP (Japanese),
Windows 7
Language : C, C++
KNOWN LIMITATIONS:
This section describes the known limitations in this release on Windows
platform. We intend to fix these limitations in future releases.
1. The known limitations in the linker script wizard are listed below:
a. Groups/sections are added or modified to get the start address type as
'Label'. However, when moved up or down using the 'Move up' or 'Move down'
buttons, data gets corrupted and the wizard behaves incorrectly.
Workaround: In such cases, please click 'Cancel' instead of 'Apply' to
go back to the previously saved data and condition.
Alternatively, delete all sections from the GUI editor and specify the
sections in the linker user options.
b. While modifying the address of a group, user is not allowed to delete the
preceding '0x'.
c. The memory region feature is not provided in this release for GNU tools.
d. While adding or modifying a group's start address from 'Follow on from
previous group' to 'Label', the group does not get added or modified
if the last label (e.g. _stack) is selected for GNU tools.
2. The software update feature is unavailable in this version due to
limitations in platform configuration.
Please visit the following link for details,
http://kpitgnutools.com/phpmyfaq/index.php?aktion=artikel&rubrik=009001&id=483&lang=en
3. When the user attempts to change the build phase settings, however does
not change any settings ultimately and clicks "OK" or "Apply" rather than
"Cancel", the project re-builds on selecting "Build".
This is native behaviour of Eclipse.
4. When 'Optimization for access to external variable' is set to
'Inter-module' option i.e., when late optimization is set to the working
project and if one or more files are modified, the complete project will
be re-built rather than only the modified files, in both the first and
the second build phase passes.
5. When compiler 'Output file type' is set as 'Preprocessed source file
(*.p/*.pp)' or 'Suppress #line in preprocessed source file (*.p/*.pp)',
the compiler generates the preprocessed file with an '.obj' extension
rather that *.p/*.pp for *.c/*.cpp files. This results in linker error:"** L2200 (E) Illegal object file "
6. For imported projects, 'Debug' is set as the active configuration by
default. Please set the required active configuration manually. To change
a configuration click on 'Project' -> 'Build configurations' ->
'Set active' -> 'Debug/HardwareDebug/HewDebug/CustomDebug/Release'.
The KPIT Eclipse RX and SH samples can be debugged on hardware. Please
note that the configuration needs to be changed to 'HardwareDebug' after
importing the samples. Also, the path of GDB needs to be set under
'Run' -> 'Debug Configurations' -> 'SH/RX Hardware Debugging :
<current configuration name> -> 'Debugger' tab.
7. The 'Debug' icon in the toolbar can be used to invoke debug sessions for
hardware debug by default. If the workspace contains only projects with
'Debug using HEW' / 'Simulator Debug' as default configurations, a dialog
box showing following debug options is displayed:
- HEW Debugging
- SH/RX Hardware Debugging
- Simulator Debugging. Please select "HEW Debugging" and HEW will be launched. Pre-configured
workspaces have been added for few targets; RX600/RX610, SH7211, SH7264
to extend the HEW debugging feature. This will allow you to directly
download project (built in KPIT Eclipse) in HEW environment.
Alternatively, right click on the project and select 'Debug As' ->'HEW Debugging'. This will launch HEW for debugging.
8. Debug configuration for debugging using GDB simulator (**see below) has
been provided in KPIT Eclipse for SH /RX targets. However, debugging
feature for simulator debug has limitations for projects created using
Renesas RXC toolchain in KPIT Eclipse IDE.
Known Issues: Eclipse CDT 5.0.1:
The following are the known issues in Eclipse CDT 5.0.1. These issues are
also present in KPIT Eclipse v2.2.
1. Exception on opening the debug-modules tree:
In the debug perspective, the tree view for "<project_name>.x" module
gives an exception, when clicked on the 'Modules' tab. This error occurs
the first time a project is debugged. Later, the label gets populated and
only then, the files are visible.
Please refer to the following bugs:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=250929
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247274
2. The error 'mi_cmd_var_create: unable to create variable object’ occurs
repeatedly during debug. This error is observed in Eclipse CPP runtime,
when the variables (which are not accessible at the breakpoint while
debugging and which are defined at some other location in the source code)
are added in the watch window. This error can be fixed by deleting the
particular variable from the watch window.
Please refer to the following bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=182206
3. Warnings are displayed after the debug session is terminated. Similar
warnings are observed with the native CPP runtime using the native GDB.
NOTE :
(*) For Windows Users:
1. The KPIT Eclipse v2.2 supports integration with Renesas SHC toolchains
(v9.0.0 onwards). However, Renesas SHC toolchains with versions lower than
v9.3.0 are not officially supported in KPIT Eclipse v2.2.
2. KPIT Eclipse v2.2 supports integration with Renesas RXC toolchains
(v1.0.0 onwards).
Important: KPIT Eclipse v2.2 supports integration of Renesas SHC and
RXC toolchains on the Windows platform only, and not for the Linux platform.
This is because these toolchains are not available for the Linux platform.
(**) For Linux Users:
The 'Debugging in simulator' feature in KPIT Eclipse v2.1 for Linux may
exhibit some issues while working with GNURX ELF v10.02 toolchain objects.
This is due to the enhanced GDBRX version released along with GNURX v10.02.
These issues will be fixed in the KE v2.3 update/release.
For free technical support, please register at
http://www.kpitgnutools.com.
For your feedback and suggestions, please visit
http://www.kpitgnutools.com/feedback.php.
|