Sketch environment V1.12 for GR-KURUMI e2studio (V4)

Original Location:
Owner: Okamiya Yuuki
Date: Oct. 16, 2013 14:48

Although GR-KURUMI sketches are normally created with the Web compiler, the integrated development environment e2studio can also be used for sketch development, helping to reduce frustration with slow responses caused by the network. Note that e2studio can only be sued in Windows.

Supplement: The e2studio V2.x version was created to enable developments in Japanese, as users were experiencing difficulties importing projects in V1x.

Note: The custom linker file specification (-T) in the Japanese language version has a bug and you won’t be able to build the program. You will need to add -Duser.language=en by editing the e2studio.ini file in the directory where the e2studio.exe is located, under the install directory eclipse\ (this is an English environment).

How to Construct the Local Build Environment

The version and download location of each tool is as follows:

How to Set Up the Local Build Environment 

  1. Download e2studio. (User must be registered in MyRenesas to download.)
  2. Download KPIT GNU Tools. (User registration required.)
  3. First, install e2studio. The install folder is executed as the default (C:\Renesas\e2studio)
  4. Next, install KPIT GNU Tools.

* Important --- Make sure you install e2studio first, then KPIT GNU Tools. If you make a mistake, copy GNU RL78 into the C:/Renesas/e2studio folder.

Import and Build Project

  1. Extract the attached file, which will automatically be saved in the RLduino78 folder.
  2. Start up e2studio and select [File]  [Import] from the menu.
  3. In the [Import] dialog, select [General]  [Existing Projects into Workspace], and click [Next].
  4. Select [Select archive file:], click [Browse], select the extracted RLduino78 folder, and click [Finish]. 

  5. The project will then be automatically created - all you need to do is build and debug.

Helpful Hints

  • E1, E2 connections → Here
  • Import/Export
    • Using Import is handy as you use an archive file (zip or compressed files) as is; the demerit is you can’t change the project name.  You can, however, change the project name by changing it in the project tree. Also, you can name a project for an export when you output the archive file. For example, you can rename a project named “KURUMIchan” to “KURUMI_Channel” so that others may use it.
  • Changing the compiler version
    • Almost all tool settings are carried out with the  button. Although the compiler version can be changed in the “change tool version” tab, because KURUMI was created for use in the Web compiler environment, startup objects (crt ~ .o) are specified in the path fixed for each version. If you really need to change the compiler version, you can do so by going to setting→linker→Input.
  • Appearance of many warnings… 
    • This happens in my environment a lot as well. During a make, when defining a macro (setting→compiler→Macro Defines) other than the inline macro definitions (#define), it seems like the editor plugin ignores the macro. Various warnings are generated indicating causes such as there is no function reference pointer or various factors don’t match. However, if the build completes successfully, these bugs won’t result in any problems.




Currently the tool chain downloadable from KPIT is 13.02 and the default install directory for e2studio is, for some reason, e2_studio. For example, the following would be the automatically generated file?

# Automatically-generated file. Do not edit!
USER_OBJS := "C:/Renesas/e2studio/GNURL78v13.01-ELF/rl78-elf/lib/gcc/rl78-elf/4.8-GNURL78_v13.01/crtbegin.o" "C:/Renesas/e2studio/GNURL78v13.01-ELF/rl78-elf/lib/gcc/rl78-elf/4.8-GNURL78_v13.01/crtend.o" "C:/Renesas/e2studio/GNURL78v13.01-ELF/rl78-elf/rl78-elf/lib/crtn.o"

Since there is no consistency here, the compile cannot be completed.

Fujita Nozomu

You can download older versions here.


That’s true, but I wonder about writing a version dependent absolute path?
Also, whoever created the e2studio install file should decide on one or the other -- e2studio or e2_studio.


それ以外に、kurumi_sketch_v104_e2studio.zipをインポートしてプロジェクトを作ったんですが、Ethernet.cppでエラーが発生します。In addition, I imported and created a project but I get an error in Ethernet.cpp. as follows.

#include "Ethernet.h"

And here:
if(_dhcp != NULL){

The former error follows the include path to the directory which has this header file.


Since I don’t know the definition of c++ NULL, I used the following as the path for the latter. (或いはSince the latter does not know the definition of c++ NULL it follows an appropriate path, like,
if(_dhcp != 0){

Okamiya-san, are you sure your program compilation succeeded?


Hmmm….something disappeared!
#include <Ethernet.h>

Okamiya Yuuki

I’ve been on a business trip and just got back. I’ll take a look tomorrow.


If you have any info on the following, please let me know.
Since e2studio is based on Eclipse, is there any way to create a template of a project in Eclipse, and copy it to use for a derivative project? I am hoping there is quick and easy process for this.

Okamiya Yuuki

Sorry for the delayed response. Yes, I was able to complete the build successfully. Would you mind pasting the error message here?
And, about creating a project template: this version allows the user to zip the project in the export process, then read the zip file as during import, which makes things really easy. Are you looking for something even simpler?


Ethernet.h and NULL issue: for some reason the error is no longer generated. I can’t figure out the cause, but since the problem is solved, let’s leave it be!
Derivative project question: for example, create “project” folder from the original project, then create folders for derivate projects, such as project1, project2, so that I can work on different projects.
Is it possible to import a project using a different name when exporting and importing a zip folder?

Okamiya Yuuki

Sorry, you can change a name when importing. However, you can rename a folder by changing the name after startup.


Hmmm… I never thought about changing the name after importing the folder…
Could you document that procedure?
Something about Export  Import  Rename.

Okamiya Yuuki

Sure. First I will write the procedure in this Rulz blog. Anything else you need documented?