Development Tools

2.3 Create a Project

A project is managed by CS+ as the unit for application system development.

CS+ saves settings information used in the project such as the microcontroller, build tool, and source files, to the project file (*.mtpj) and references it.

Remark

The following lists types of project files other than *.mtpj.

Extension

Description

*.mtud

Environment-dependent information-saving file

This file is for saving information that does not affect the generation of object files but changes in succession according to the environment you are using or the operations in each project or in each project per user.

It is recommended that environment-dependent information-saving files not be registered with the source management tools.

For details, see 2.9.5 Save and share environment-dependent information-saving files.

*.rcpe

Renesas common project file (for porting a project to the e2 studio)

(1)	Project tree organization and detailed settings

The project's settings are made on the Project Tree panel.

Figure 2.3

Project Tree Panel

On the project tree, project components are displayed as the nodes below in a tree view.

If you select each component (node or file), its detailed information (properties) is displayed in the Property panel and you can change its settings.

You can also make project settings from the context menu for each component (node or file).

Node

Explanation

Project name (Project)

(Hereafter referred to as "Project node")

The project's name.

Microcontroller name (Microcontroller)

(Hereafter referred to as "Microcontroller node")

The microcontroller used in the project.

Boot Loader (Configuration Tool for Multi-core node) [RH850]

(Hereafter referred to as "Configuration Tool for Multi-core node")

The node for setting application projects which configure a project for multi-core.

Note that this node is shown when the project type is a boot loader project.

Design Tool name (Design Tool)

(Hereafter referred to as "Design Tool node")

The design tool (pin configurator, code generator, smart configurator [RX][RL78], etc.) used.

Note that Code Generator (Design Tool) node is not shown when the project type is a debug-dedicated project.

Build tool name (Build tool)

(Hereafter referred to as "Build Tool node")

The build tool (compiler, assembler, etc.) used.

When the project type is a debug-dedicated project, "None" is shown as build tool name.

Debug tool name (Debug Tool)

(Hereafter referred to as "Debug Tool node")

The debug tool (in-circuit emulator, simulator, etc.) used.

Program Analyzer (Analyze Tool)

(Hereafter referred to as "Analyze Tool node")

The analyze tool used.

Note that this node is not shown when the project type is a debug-dedicated project.

File

(Hereafter referred to as "File node")

Files registered to the project are displayed directly below the File node.

Download files

(Hereafter referred to as "Download files node")

This is a node for adding download files to the project.

Note that this node is shown only when the project type is a debug-dedicated project.

Build tool generated files

(Hereafter referred to as "Build tool generated files node")

This node is created during a build. Files created by the build tools are displayed directly below the node (except for object files).

Note that this node is not shown when the project type is a debug-dedicated project.

Startup [RL78]

(Hereafter referred to as "Startup node")

This is a node for adding other than standard startup files to the project. This node is always shown under the File node.

Note that this node is not shown when the project type is a debug-dedicated project.

Category name

(Hereafter referred to as "Category node")

These user-defined categories are used to classify files into modules.

Subproject name (Subproject)

(Hereafter referred to as "Subproject node")

Subprojects added to the project.

For subprojects, see "(2) Projects and subprojects".

Remark 1.

Only the tools corresponding to the microcontroller in use are shown.

Remark 2.

When more than one component are selected, only the tab that is common to all the components is displayed.
When more than one file are selected and their common properties are different, that field is left blank.

Remark 3.

See "E. USING AN EXTERNAL BUILD TOOL" for details on a debug-dedicated project.

(2)	Projects and subprojects

Projects can have subprojects added to the level beneath them.

The subproject's settings information is saved to a subproject file (*.mtsp).

Subprojects, for example, are used in the following ways.

-	When also creating a project to create library files used in the project, create a project to create library files as a subproject.

-	When developing the same application system for different microcontrollers, create the projects that differ for the microcontroller as subprojects.

When subprojects are added, this manual call the project "main project", as opposed to its subprojects. "Project" is a common term for the main project and subprojects.

Figure 2.4

Project Tree Panel (When Subprojects Added)

In addition, project settings and the settings for subprojects added to a project are independent and have no effect on each other. When making the same settings between the main project and subprojects, or between differing subprojects, select multiple nodes to set on the project tree, and make the settings with the Property panel.

Caution

A subproject cannot be added to another subproject.

Remark

See "2.3.3 Add a new subproject" and "2.4.2 Add an existing subproject", for how to add subprojects.