Hardware manual

e
2
studio 3.1 Release Note
Rev 1.4, Sep 23, 2014 Page 21
4303
RL78 GCC build
plugin
When the project has a toolchain that does not match the path for the toolchain installed on the
machine problems with build can occur.
Workaround is to delete the 'org.eclipse.cdt.core.prefs' file from .settings folder and then import the
project.
Alternatively you can modify the toolchain path from Properties > C/C++ Build > Environment.
Modifying the toolchain path builds the project successfully.
4314 GDB Server SH
For the SH debugger the Debug Tool Settings -> Use User Stack option is not processed by the
debugger. The setting is not used.
4350
CubeSuite+
importer/exporter
When importing a project from CubeSuite+ to e2 studio the “toolchain version is changed" dialog is
always displayed.
This is because the version string in imported project file and the toolchain information in e2 studio
does not match. Ignoring this dialog and continuing should result in a successful import.
4422 Application
When debugging a project that has been imported but that has not been rebuilt you need to setup
the debugger to look in the original source file location.
This is done via the Source tab of the Debug Configurations dialog.
4450
CCRX Build
plugin
Linker section settings of Renesas toolchain are not getting saved for multiple configurations.
4492 Application
The Module View of e2 studio does not display any information when an executable which includes
debug information was downloaded to the target.
4515
CCRX Build
plugin
When building projects with CCRX that are in deep directory structures it is possible to experience
build issues. e2 studio is unable to build projects which create command lines greater than 8191
characters.
4579
RX GCC build
plugin
All configuration changes are not saved on changing multiple configuration settings in one session
for GCC tools. Specifically this is referring to multiple settings changes across multiple
configurations and the clicking apply.
4597 Application
In some cases when a before PC eventpoint is set just after a break point, the program execution
will not stop at the address the eventpoint is located at.
4607
Event points
plugin
When sub menu "Add Watchpoint" is performed from a Memory view, it seems to have been
registered correctly in the Breakpoints view even if there is an error condition.
An error occurs by "Add Watchpoint", when the maximum number of events was exceeded, or when
a ROM area is specified.
4634 Real-time Chart
The Log scale check box in the real-time chart properties does not work. Setting the box as checked
and clicking OK will reset it to 0.
4783
Performance
Analysis
The option to Reset timer before each run, which is setup on the "Performance Analysis" dialog box
is not reflected for RL78.
The specification for RL78 is that the values are reset all of the time so the option has no meaning.
4819
CCRX Build
plugin
Individual compile is not execute when Level2 is specified at the "Perform inter-module optimization".
4833 Application
The clean functionality executes every time irrespective of whether the object file is present or not.
4857 GDB
GDB considers PUSHC instruction to be part of the function prologue and it skips it.
Inserting a break point at *functionname
instead of functionname solves the problem. (* tells GDB to start at the actual beginning of the
function without skipping the prologue).