Everything
 

Create Project dialog box


This dialog box is used to create new projects or subprojects.

Caution

A subproject cannot be added to another subproject.

Figure A.3

Create Project Dialog Box (Opened From Other Area than [Create New Multi-core Project] On Start Panel)

 

Remark

When a subproject is created, the title bar says "Create Subproject".

Figure A.4

Create Project Dialog Box (Opened From [Create New Multi-core Project] Area On Start Panel)

 

The following items are explained here.

[How to open]

(1)

When creating a main project

-

Click the [Start] button in the toolbar to open the Start panel and then click the [GO] button in the [Create New Project] area or [Create New Multi-core Project] area.

-

From the [File] menu, select [New] >> [Create New Project...].

-

From the [Project] menu, select [Create New Project...].

-

From the [File] menu, select [New] >> [Create New Project for Multi-core...]

-

From the [Project] menu, select [Create New Project for Multi-core...]

(2)

When creating a subproject

-

From the [Project] menu, select [Add] >> [Add New Subproject...].

-

On the Project Tree panel, select project or subproject, and then select [Add] >> [Add New Subproject...] from the context menu.

[Description of each area]

(1)

[Microcontroller]

Select the microcontroller type to use in the project.

You can select the item below.

-

RH850

-

RX

-

RL78

(2)

[Using microcontroller] area

Select a microcontroller to use in the project.

(a)

Microcontroller search box

You can search a microcontroller selected in the list of microcontrollers simply.

(b)

List of microcontrollers

Select a microcontroller.

The microcontrollers that correspond to the microcontroller type selected in [Microcontroller] are listed and categorized by their nicknames.

Caution

If this dialog box is opened from the [Create New Multi-core Project] area on the Start panel, only the microcontrollers for RH850 multi-core are displayed.

 

The following information on the selected microcontroller that is used in the project is shown in the box at right.

-

Product Name

-

On-chip ROM size [Kbytes] [RX]

-

Internal ROM size [Kbytes] [RH850][RL78]

-

On-chip RAM size [Bytes] [RX]

-

Internal RAM size [Bytes] [RH850][RL78]

-

Additional InformationNote

Note

Other information appears only when present.

(c)

Button

Update...

Displays the CS+ Update Manager window.

When the microcontroller to be used does not appear in the list, you can search for the microcontroller via the network.

Caution

This button is only enabled when this product is installed using the installer. It is disabled when a packaged item is being used.

(3)

[Kind of project]

Select the project type to create on [Kind of project].

You can select the item below.

Caution

Only [Boot Loader for Multi-core(CC-RH)] can be selected when this dialog box is opened from the [Create New Multi-core Project] area on the Start panel.

 

-

Application(CC-RH/CC-RX/CC-RL)

Select this to generate the load module file and hex file from C source files, by using the build tool provided by CS+.

The generated file will be the debug target.

Caution

This item is not displayed when microcontrollers for RH850 multi-core are selected in the [Using microcontroller] area.

Remark 1.

If the build tool is CC-RH, the following start-up source files are generated in the project folder.
These files are also registered in the project tree.

File Name

Description

boot.asm

For defining the processing from the occurrence of a reset to a branch to each application project and defining the interrupt vector table

cstart.asm

For defining the start-up routine from the occurrence of a reset to a branch to the main function

iodefine.h

For defining I/O registers

main.c

For defining the empty main function

Remark 2.

If the build tool is CC-RX, the following start-up source files are generated in the project folder.
The files marked with "OK" in the "Registration in Project Tree" column are also registered in the project tree. When necessary, also register the files marked with "--" in the project tree.

File Name

Description

Registration in Project Tree

ProjectName.c

For defining the main function

OK

dbsct.c

For setting up standard sections

OK

hwsetup.c

For initializing hardware

--

intprg.c

For defining interrupt functions

OK

iodefine.h

For defining I/O registers

OK

lowlvl.src

For defining low-level I/O functions (source file for assembler)

--

lowsrc.c

For defining low-level I/O functions

--

lowsrc.h

Prototypes for low-level I/O functions

--

resetprg.c

For defining initialization for C language

OK

sbrk.c

For defining the function for allocating the heap memory

OK

sbrk.h

For defining the heap size

OK

stacksct.h

For defining pragma for the stack

OK

typedefine.h

For defining typedefine for the types used in sbrk.c, etc.

OK

vect.h

Prototypes for interrupt vector functions

OK

vecttbl.c

For defining the interrupt vector table

OK

Remark 3.

If the build tool is CC-RL, the following start-up source files are generated in the project folder.
For some devices, files other than those listed below may be added to the project folder.
These files are also registered in the project tree.

File Name

Description

cstart.asm

For defining the start-up routine from the occurrence of a reset to a branch to the main function

The memory address and stack area need to be modified to match the microcontroller used.

hdwinit.asm

File for initializing the hardware

stkinit.asm

File for initializing the stack

iodefine.h

For defining the names of I/O registers and interrupt requests

iodefine_faa.inc

For defining the FAA registers (only for a device with an FAA)

main.c

For defining the empty main function

-

C++ Application(CC-RX/CC-RL)

Select this to generate the load module file and hex file from a C++ source file (only a file that has a main function) and C source files, by using build tool CC-RX/CC-RL provided by CS+.

The generated file will be the debug target.

Remark 1.

When the build tool is CC-RX, The following start-up source files are generated in the project folder.
The files marked with "OK" in the "Registration in Project Tree" column are also registered in the project tree. When necessary, also register the files marked with "--" in the project tree.

File Name

Description

Registration in Project Tree

ProjectName.cpp

For defining the main function

OK

dbsct.c

For setting up standard sections

OK

hwsetup.cpp

For initializing hardware

--

intprg.c

For defining interrupt functions

OK

iodefine.h

For defining I/O registers

OK

lowlvl.src

For defining low-level I/O functions (source file for assembler)

--

lowsrc.c

For defining low-level I/O functions

--

lowsrc.h

Prototypes for low-level I/O functions

--

resetprg.c

For defining initialization for C language

OK

sbrk.c

For defining the function for allocating the heap memory

OK

sbrk.h

For defining the heap size

OK

stacksct.h

For defining pragma for the stack

OK

typedefine.h

For defining typedefine for the types used in sbrk.c, etc.

OK

vect.h

Prototypes for interrupt vector functions

OK

vecttbl.c

For defining the interrupt vector table

OK

Remark 2.

When the build tool is CC-RL, the following start-up source files are generated in the project folder during the creation of a project. For some devices, files other than those listed below may be added to the project folder. These files are also registered with the project tree.

File Name

Description

cstart.asm

For defining the start-up routine from the occurrence of a reset to a branch to the main function

The memory address and stack area need to be modified to match the microcontroller used.

hdwinit.asm

File for initializing the hardware

stkinit.asm

File for initializing the stack

iodefine.h

For defining the names of I/O registers and interrupt requests

iodefine_faa.inc

For defining the FAA registers (only for a device with an FAA)

main.cpp

For defining the empty main function

-

Empty Application(CC-RH/CC-RX/CC-RL/GHS CCRH850)

Select this to generate the load module file, by using build tool CC-RH/CC-RX/CC-RX/CC-RL or build-tool plugin for GHS CCRH850 provided by CS+.

The generated file will be the debug target.

Sample startup programs are not generated when the project is created.

-

Boot Loader for Multi-core(CC-RH)

Select this to create a boot loader project for multi-core, by using build tool CC-RH provided by CS+.

A boot loader project is used to set application projects configuring a project for multi-core.

Caution

This item is displayed only when microcontrollers for RH850 multi-core are selected in the [Using microcontroller] area.
For a project for a multi-core device, we recommend creating boot loader and application projects for the multi-core device in a single operation.
To create boot loader and application projects for the multi-core device in a single operation, select [File] >> [New] >> [Create New Project for Multi-core…].
When boot loader and application projects for the multi-core device are not created in a single operation, an application project for a multi-core device is always created as a project for the PE number of the top core.

Remark

The following start-up source files are generated in the project folder.
These files are also registered in the project tree.

-

When [Create a structure of startup files including main functions for each core.] check box is not selected or when [Create a structure of startup files including main functions for each core.] check box and [Create them as application projects] radio button are selected

File Name

Description

bootn.asm

For defining the processing from the occurrence of a reset to a branch to each application project and defining the interrupt vector table

iodefine.h

For defining I/O registers

-

When [Create a structure of startup files including main functions for each core.] check box and [Create them as a single project] radio button are selected

File Name

Description

bootn.asm

For defining the processing from the occurrence of a reset to a branch to each application project and defining the interrupt vector table

cstartn.asm

For defining the start-up routine for each application

iodefine.h

For defining I/O registers

mainn.c

For defining the empty main function

The core number n is sometimes included in the file name of a startup file (bootn.asm, cstartn.asm, or mainn.c) for a core.

-

Application for Multi-core(CC-RH)

Select this to create an application project for multi-core, by using build tool CC-RH provided by CS+.

Caution

This item is displayed only when microcontrollers for RH850 multi-core are selected in the [Using microcontroller] area.
For a project for a multi-core device, we recommend creating boot loader and application projects for the multi-core device in a single operation.
To create boot loader and application projects for the multi-core device in a single operation, select [File] >> [New] >> [Create New Project for Multi-core…].
When boot loader and application projects for the multi-core device are not created in a single operation, an application project for a multi-core device is always created as a project for the PE number of the top core.

Remark

The following start-up source files are generated in the project folder.
These files are also registered in the project tree.

File Name

Description

cstartn.asm

For defining the start-up routine for each application

iodefine.h

For defining I/O registers

main.c

For defining the empty main function

The core number n is sometimes included in the file name of a startup file (cstartn.asm) for a core.

-

Using Existing GHS Project File (GHS CCRH850)

Select this to debug a load module file built by the GHS compiler.

This makes it easier to build based on existing GHS project files.

-

Library (CC-RH/CC-RX/CC-RL/GHS CCRH850)

Select this to generate a library file for a user library, by using build tool CC-RH/CC-RX/CC-RL or build-tool plugin for GHS CCRH850 provided by CS+.

-

Debug Only

Select this to debug a load module file or hex file generated with a build tool other than the one provided by CS+ (i.e. creates a debug-dedicated project).

See "E. USING AN EXTERNAL BUILD TOOL" for details on how to create and use the debug-dedicated project.

(4)

Project Creation area

Set the project to create.

(a)

[Project name]

Directly enter the name of the project to create.

The entered project name is followed by the extension, ".mtpj" and this forms the project file name.

Remark

When the subproject is created, the entered project name is followed by the extension, ".mtsp" and forms the subproject name.

(b)

[Place]

Designate the location to create the project file by directly entering it with absolute path or selecting from the [Browse...] button.

The last designated location is shown in the box. "C:\Users\User name\Documents" is shown by default when the project is created for the first time.

Caution

The name of a network path cannot be used for [Place]. Assign the name of a path on a drive.

(c)

Button

Browse...

Opens the Browse For Folder dialog box.

When a folder is selected, an absolute path of the folder is shown in [Place].

(d)

[Make the project folder]

Use this check box to select whether to create a folder with the project name under the location specified in [Place].

The check box is selected by default.

(e)

Project file path

The full path of the project file (specified via [Project name] and [Place]) is shown.

Remark 1.

The number of characters that can be entered in [Project name] and [Place] is up to 259 both for the path name and file name together.

Remark 2.

When the input for [Project name] violates any restriction, the following messages are shown in the tooltip.

Message

Description

The project name is invalid. Enter characters that can be used as a file name.

The project file name uses characters that are not allowed.

Characters xx cannot be used in a project name.

Characters that are not allowed (from the viewpoint of preventing build errors) have been used in the project name.

Characters xx cannot be used at the start of a project name.

Characters that are not allowed (from the viewpoint of preventing build errors) have been used at the start of the project name.

A subproject with the same ID has already been registered.

A subproject with the same ID has already been registered.

The subproject name is invalid. A subproject with the same name cannot be made in the location where the main project exists.

In the specified location there is already a main project with the same name (excluding extension).

Remark 3.

When the input for [Place] violates any restriction, the following messages are shown in the tooltip.

Message

Description

The folder name including the path is too long. Make it within 247 characters.

The folder name is more than 247 characters.

The file name including the path is too long. Make it within 259 characters.

The file name with the path is more than 259 characters.

The location where the project is to be created does not exist.

The folder creation was canceled or failed, so that a nonexistent folder has been specified.

The location for project creation is invalid. Enter characters that can be used as a path name.

The file name with the invalid path is designated. The characters, \, /, :, *, ?, ", <, >, |, cannot be used for the folder name.

Remark 4.

When the project name and the path name is too long to be shown in each text area, is displayed. The absolute path pops up when the mouse cursor is hovered over .

(5)

Pass project area

Set this area when reusing the file composition of the existing project (main or subproject) to create a new project.

Caution 1.

This area is not displayed when this dialog box is opened from the [Create New Multi-core Project] area on the Start panel.

Caution 2.

When you create a project, only the settings for the default debug tool will be imported.
In the RX family, however, internal processing is common to the emulator and simulator, so the settings are imported regardless of which debug tool is selected.

(a)

[Pass the file composition of an existing project to the new project]

Select this check box when reusing the file composition of the existing project to create a new project.

The check box is unselected by default.

The category of the file can be also reused.

Remark

The settings of the properties of the build tool are changed to those for the specified microcontroller. iodefine.h and the start-up source files of the specified microcontroller are copied as sample source files. For the start-up files, create a folder named "<device name after change>.nnn" (nnn = 000, 001, …) and copy them to that folder. The details of the changes are displayed in the Output panel.
For an RH850 device, however, if the source or destination project is for a multi-core microcontroller, the start-up source file will not be copied.
[RX] If you have selected a microcontroller that has a different ROM size from that set in the source project, the differences between the ROM sizes may not be reflected in the value of the [Section start address] property on the [Link Options] tabbed page. Check the value of the [Section start address] property.

(b)

[Project to be passed]

Designate the name of the source project when diverting the file composition of the existing project to create a new project.

Designate the name of the source project by directly entering it with absolute path or selecting with the Open Project dialog box after pressing the [Browse...] button.

The last designated location is shown in the box. "C:\Users\User name\Documents" is the default location when the file is created for the first time.

This field is enabled only when the [Pass the file composition of an existing project to the new project] check box is selected.

Caution

You cannot designate the e2 studio, CubeSuite, HEW, or PM+ project file.

Remark 1.

Up to 259 characters can be entered.

Remark 2.

When the input violates any restriction, the following messages are shown.

Message

Description

File name with the path is too long. Shorten within 259 characters.

The file name with the path is more than 259 characters.

The divert project does not exist.

The path includes a nonexistent folder, or the specified project file cannot be found.

The divert project name is invalid. Enter characters that can be used as a file name.

The file name with the invalid path is designated. The characters, \, /, :, *, ?, ", <, >, |, cannot be used for the folder name.

The project which is being used can't be diverted.

The currently open project (main project or subproject) has been specified as the source project.

The specified file is invalid. Enter a divert project file.

An existing file that is not a project file or subproject file has been specified.

Remark 3.

When the path name is too long to be shown in the text area, is displayed. The absolute path pops up when the mouse cursor is hovered over .

(c)

Button

Browse...

Open Project dialog box appears.

When a project file is selected, an absolute path of the project file is shown in [Project to be passed].

(d)

[Copy composition files in the diverted project folder to a new project folder.]

Select this check box when copying composition files in the project folder of the project specified in [Project to be passed] to a new project folder.

The check box is unselected by default.

This field is enabled only when the [Pass the file composition of an existing project to the new project] check box is selected.

Remark 1.

When the version of the build tool used in the source project is different from the version of the build tool in the project to be created, it is automatically diverted (except for a debug-dedicated project).

Remark 2.

When the build tool for the project to be created does not support a node of the source project, the node will be displayed as a normal Category node on the project tree (e.g., Startup node or Download files node etc.).

(6)

Area for creating a structure of startup files

Set this area when simultaneously creating a structure of startup files for each core.

Caution

This area is displayed only when this dialog box is opened from the [Create New Multi-core Project] area on the Start panel.

(a)

[Create a structure of startup files including main functions for each core.]

Select this check box when simultaneously creating a structure of startup files for each core.

The check box is selected by default.

(b)

[Create them as application projects]

Select this radio button when a structure of startup files for each core is created as an application project for the number of cores.

The radio button is selected by default.

This field is enabled only when the [Create a structure of startup files including main functions for each core.] check box is selected.

(c)

[Create them as a single project]

Select this radio button when a single project that includes structures of all startup files is created

This field is enabled only when the [Create a structure of startup files including main functions for each core.] check box is selected.

[Function buttons]

Button

Function

To dialog with multi-core option

Moves to the Create Project dialog box for creating a boot loader project for a multi-core device and application projects for each core of a multi-core device at the same time. For creating a project for a multi-core device, refer to section 2.3.2 Create a new project.

This button is displayed when a main project is created and a microcontroller to suit the types of projects for a multi-core device is included in the [Microcontroller] list box.

Create

Creates a project according to the designated condition and closes the dialog box.

When the [Pass the file composition of an existing project to the new project] check box is selected, creates a project by diverting the file composition of the project (main or subproject) designated in [Project to be passed].

If the build tool of the source project is CA78K0R or CA78K0, and the build tool of the project to create is CC-RL, opens the Source Convert Setting dialog box [CC-RL] to select whether to convert the source files and the like.

Cancel

Cancels the designated condition and closes the dialog box.

Help

Displays the help of this dialog box.