CHAPTER 2 SYSTEM BUILDING
This chapter describes how to build a system (load module) that uses the functions provided by the RI600V4.
System building consists in the creation of a load module using the files (kernel library, etc.) installed on the user development environment (host machine) from the RI600V4's supply media.
Figure 2-1 Example of System Building
The RI600V4 provides a sample program with the files necessary for generating a load module.
The sample programs are stored in the following folder. The source files are stored in "appli" sub-folder.
<ri_sample> = <CubeSuite+_root>\SampleProjects\RX\
device_name_RI600V4
Indicates the installation folder of CubeSuite+.
The default folder is "C:\Program Files\Renesas Electronics\CubeSuite+\".
Indicates the sample project folder of CubeSuite+.
Indicates the sample project folder of RX MCU.
Indicates the sample project folder of the RI600V4. The project file is stored in this folder.
device_name: Indicates the device name which the sample is provided.
2.2 Coding Processing Programs
Code the processing that should be implemented in the system.
In the RI600V4, the processing program is classified into the following four types, in accordance with the types and purposes of the processing that should be implemented.
-
Tasks
A task is processing program that is not executed unless it is explicitly manipulated via service calls provided by the RI600V4, unlike other processing programs (interrupt handler, cyclic handler and alarm handler).
-
Cyclic handlers
The cyclic handler is a routine started for every specified cycle time.
The RI600V4 handles the cyclic handler as a "non-task (module independent from tasks)". Therefore, even if a task with the highest priority in the system is being executed, the processing is suspended when a specified activation cycle has come, and the control is passed to the cyclic handler.
-
Alarm Handlers
The alarm handler is a routine started only once after the specified time.
The RI600V4 handles the alarm handler as a "non-task (module independent from tasks)". Therefore, even if a task with the highest priority in the system is being executed, the processing is suspended when a specified activation cycle has come, and the control is passed to the cyclic handler.
-
Interrupt Handlers
The interrupt handler is a routine started when an interrupt occurs.
The RI600V4 handles the interrupt handler as a "non-task (module independent from tasks)". Therefore, even if a task with the highest priority in the system is being executed, the processing is suspended when an interrupt occurs, and the control is passed to the interrupt handler.
2.3 Coding System Configuration File
Note 2 When the Realtime OS Task analyzer is used in "Taking in trace chart by software trace mode" or "Taking in long-statistics by software trace mode", it is necessary to define the interrupt handler implemented in user-own coding module to the system configuration file. For details, refer to "
CHAPTER 15 REALTIME OS TASK ANALYZER".
2.4 Coding User-Own Coding Module
-
Boot processing function (PowerON_Reset_PC( ))
The boot processing is defined in the reset vector, and dedicated to initialization processing that is extracted as a user-own coding module to initialize the minimum required hardware for the RI600V4 to perform processing.
And the boot processing plays the role to take the ROM definition file and RAM definition file which are generated by the cfg600.
1 ) Create or load a project
Create a new project, or load an existing one.
Note See "RI Series Start", "CubeSuite+ Start" and the Release Notes of this product for details about creating a new project or loading an existing one.
2 ) Set a build target project
When making settings for or running a build, set the active project.
If there is no subproject, the project is always active.
Note See "CubeSuite+ RX Build" for details about setting the active project.
Select the Realtime OS node on the project tree to open the
Property panel.
Confirm the version of RI600V4 to be used in the [Kernel version] property on the
[ RI600V4 ] tab.
Figure 2-2 Property Panel: [RI600V4] Tab
4 ) Set build target files
For the project, add or remove build target files and update the dependencies.
Note See "CubeSuite+ RX Build" for details about adding or removing build target files for the project and updating the dependencies.
The following lists the files required for creating a load module.
- Processing programs (tasks, cyclic handlers, alarm handlers, interrupt handlers)
Note Specify "cfg" as the extension of the system configuration file name. If the extension is different, "cfg" is automatically added (for example, if you designate "aaa.c" as a file name, the file is named as "aaa.c.cfg").
- User-own coding module (system down routine, boot processing)
- Library files provided by the RI600V4
- Library files provided by the C compiler package
- Standard library, runtime library, etc.
Note 1 If the system configuration file is added to the
Project Tree panel, the Realtime OS generated files node is appeared.
The following information files are appeared under the Realtime OS generated files node. However, these files are not generated at this point in time.
- System information header file (kernel_id.h)
- Service call definition file (kernel_sysint.h)
- ROM definition file (kernel_rom.h)
- RAM definition file (kernel_ram.h)
- System definition file (ri600.inc)
- CMT timer definition file (ri_cmt.h)
- Table file (ritable.src)
Figure 2-3 Project Tree Panel
Note 2 When replacing the system configuration file, first remove the added system configuration file from the project, then add another one again.
Note 3 Although it is possible to add more than one system configuration files to a project, only the first file added is enabled. Note that if you remove the enabled file from the project, the remaining additional files will not be enabled; you must therefore add them again.
5 ) Set the output of Realtime OS generation files
Select the system configuration file on the project tree to open the
Property panel.
Figure 2-4 Property Panel: [System Configuration File Related Information] Tab
6 ) Specify the output of a load module file
Set the output of a load module file as the product of the build.
Note See "CubeSuite+ RX Build" for details about specifying the output of a load module file.
Set the options for the compiler, assembler, linker, and the like.
Please be sure to refer to "
2.6 Build Options".
Note See "CubeSuite+ RX Build" for details about setting build options.
Run a build to create a load module.
Note See "CubeSuite+ RX Build" for details about running a build.
Figure 2-5 Project Tree Panel (After Running Build)
Save the setting information of the project to the project file.
Note See "CubeSuite+ Start" for details about saving the project.
This section explains the build options that should be especially noted.
2.6.1 Service call information files and "-ri600_preinit_mrc" compiler option
The service call information file (mrc files) are generated to the same folder as object files at compilation of the source files that includes kernel.h file.
The name of service calls used in the source files are outputted in the mrc files. It is necessary to input all files to the table generation utility mkritbl. If there is a leaking in the input file, service call modules that application uses might not be linked. In this case, the system down will occur when the service call is issued.
On the other hand, if the mrc files which are generated in the past and which is invalid in now are input to the mkritbl, the service call modules that are not used in the application may be linked. In this case, there is no problem in the operation of the RI600V4 but the module size uselessly grows.
Specify "-ri600_preinit_mrc" compiler option for the source file that includes kernel.h file even if this option is not specified, there is no problem in the operation of the RI600V4 but the service call module that is not used in the application may be linked.
When application libraries are used, the mrc files that is generated at compilation of the library source should be inputted to the mkritbl. If this way is difficult for you, make mrc file where name of using service calls is described (see belows), and input the mrc file to the mkritbl.
Note, the system down will occur when the service call that is not linked is called.
sta_tsk
snd_mbx
rcv_mbx
prcv_mbx
|
2.6.2 Compiler option for the boot processing file
To set "-nostuff" option only for the boot processing file, please set any of the following in the [Individual Compile Options] tab of [Property] panel for the boot processing file. To set "-nostuff" option for all, please set any of the following in the [Compiler Options] tab of [Property] panel for [CC-RX (Build Tool)].
1 ) Set in the [Object] category
Like
Figure 2-6, set "Yes" in [Allocates uninitialized variables to 4-byte boundary alignment sections], [Allocates initialized variables to 4-byte boundary alignment sections] and [Allocates const qualified variables to 4-byte boundary alignment sections].
Figure 2-6 [Object] category
2 ) Set in the [Others] category
Like
Figure 2-7, add "-nostuff" to [Other additional options].
Figure 2-7 [Others] category
The kernel libraries are stored in the folders described in Table 2-1. Note, CubeSuite+ links the appropriate kernel library automatically, you need not consider the kernel libraries.
Table 2-1 Kernel libraries
|
|
|
Compiler version corresponding to the library
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RXv1 architecture and RXv2 architecture
|
|
|
|
|
|
Note 1 <ri_root> indicates the installation folder of RI600V4.
The default folder is "C:\Program Files\Renesas Electronics\CubeSuite+\RI600V4".
Note 2 The kernel described in item-2 of
Table 2-1 is linked when compiler V2.01.00 or later is used. In the case of others, the kernel library described in item-1 of
Table 2-1 is linked.
2.6.4 Arrangement of section
Arrangement section is defined by using "-start" linker option. In CubeSuite+, it is set in [Section] category of [Link Options] tab in [Property] panel for [CC-RX (Build Tool)].
1 ) RI600V4 sections
Table 2-2 shows RI600V4 sections.
Table 2-2 RI600V4 sections
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixed vector table/Exception vector table
|
|
|
|
|
|
Relocatable vector table (1KB)
|
|
|
|
|
|
This section includes data queue area.
|
|
|
|
|
|
RI600V4's initialized data. The size is 4 bytes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The section name assigned to message buffer area, fixed-sized memory pool area and variable-sized memory pool area can be specified in the system configuration file. When this is omitted, BRI_HEAP is applied as the section name.
|
|
|
|
|
|
|
|
|
|
|
|
The section name assigned to the user stack for tasks can be specified in the system configuration file. When this is omitted, SURI_STACK is applied as the section name.
|
2 ) FIX_INTERRUPT_VECTOR section
The configurator cfg600 generates fixed vector table/exception vector table as FIX_INTERRUPT_VECTOR section according to the contents of definitions of "interrupt_fvector[]" in the system configuration file.
- At the time of RXv1 architecture use
In the RXv1 architecture, fixed vector table is being fixed to address 0xFFFFFF80. It is necessary to arrange the FIX_INTERRUPT_VECTOR section at address 0xFFFFFF80.
When the FIX_INTERRUPT_VECTOR section is not arranged to address 0xFFFFFF80, all "interrupt_fvector[]" in the system configuration file are ignored. And the system-down function when an exception (except Reset) assigned to fixed vector table is occurred does not operate normally. Please generate fixed vector table to address 0xFFFFFF80 by the user side.
- At the time of RXv2 architecture use
In the RXv2 architecture, the name of fixed vector table is changed into exception vector table, and can set up the start address by EXTB register. The initial value of EXTB register at the time of reset is 0xFFFFFF80, it is same as fixed interrupt vector table in RXv1 architecture.
Usually, please arrange the FIX_INTERRUPT_VECTOR section to address 0xFFFFFF80.
When the FIX_INTERRUPT_VECTOR section is not arranged to address 0xFFFFFF80, "interrupt_fvector[31]" (reset vector) in the system configuration file is ignored. Please generate the reset vector (address 0xFFFFFFFC) by the user side. And initialize EXTB register to the start address of FIX_INTERRUPT_VECTOR section in
Boot processing function (PowerON_Reset_PC( )).
3 ) Attention concerning address 0
The following must not become address 0.
- Fixed-sized memory pool area
- Variable-sized memory pool area
- Message sent to a mailbox
2.6.5 Initialized data section
About sections described in DTBL of the
Section information file (User-Own Coding Module), it is necessary to perform setting to map sections placed on ROM to sections placed on RAM by using "-rom" linker option. Set [Link Options] tab of [Property] panel for [CC-RX (Build Tool)] like
Figure 2-8.
Figure 2-8 ROM to RAM mapped section
Note In sample projects provided by RI600V4, it is already set up that the "DRI_ROM" section of RI600V4 is mapped to "RRI_RAM" section.
2.6.6 Options for Realtime OS Task Analyzer
According to a setup of [Task Analyzer] tab, the build-options shown in
Table 2-3 are set up automatically. Note, this automatic setting function is not being interlocked with corresponding property panel of a function. For this reason, don't change the contents set up automatically in corresponding property panel of a function.
Table 2-3 The options set up automatically for Realtime OS Task Analyzer
|
|
|
|
Taking in trace chart by hardware trace mode
|
|
|
Taking in trace chart by software trace mode, Kernel buffer
|
-define=TRCBUFSZ= <Buffer size>
The following is also set up when "Stop the trace taking in" is chosen as "Operation after used up the buffers".
|
|
Taking in trace chart by software trace mode, Another buffer
|
The following is also set up when "Stop the trace taking in" is chosen as "Operation after used up the buffers".
|
-define=__RI_TRCBUF= <Buffer address>
-define=__RI_TRCBUFSZ= <Buffer size>
|
Taking in long-statistics by software trace mode
|
|
|
|
|
|
|
Note 1 The "TRCMODE" is used by following files.
- ritable.src: This file is generated by the configurator cfg600.
- trcSW_cmt.src: User-own coding sample module for "Taking in trace chart by software trace mode"
- trcLONG_cmt.src: User-own coding sample module for "Taking in long-statistics by software trace mode"
Note 2 The "TRCBUFSZ" and "TRCBUFMODE" are used by "ritable.src".
