CHAPTER 17 SYSTEM CONFIGURATION FILE
This chapter explains the coding method of the system configuration file required to output information files (system information table file, system information header file and entry file) that contain data to be provided for the RI850V4.
- Character code
Create the system configuration file using ASCII code.
The CF850V4 distinguishes lower cases "a to z" and upper cases "A to Z".
Create the system configuration file using ASCII code.
The CF850V4 distinguishes lower cases "a to z" and upper cases "A to Z".
- Comment
In a system configuration file, parts between /* and */ and parts from two successive slashes (//) to the line end are regarded as comments.
In a system configuration file, parts between /* and */ and parts from two successive slashes (//) to the line end are regarded as comments.
- Numeric
In a system configuration file, words starting with a numeric value (0 to 9) are regarded as numeric values.
The CFV850V4 distinguishes numeric values as follows.
In a system configuration file, words starting with a numeric value (0 to 9) are regarded as numeric values.
The CFV850V4 distinguishes numeric values as follows.
Note Unless specified otherwise, the range of values that can be specified as numeric values are limited from 0x0 to 0xffffffff.
- Symbol name
In a system configuration file, words starting with an alphabetic character, "a to z, A to Z", or underscore "_" are regarded as symbol names.
Describing a symbol name in the format "symbol name + offset" is also possible, but the offset must be a constant expression.
The following shows examples of describing symbol names.
The CF850V4 distinguishes between symbol names and other names based on the context in the system configuration file.
In a system configuration file, words starting with an alphabetic character, "a to z, A to Z", or underscore "_" are regarded as symbol names.
Describing a symbol name in the format "symbol name + offset" is also possible, but the offset must be a constant expression.
The following shows examples of describing symbol names.
The CF850V4 distinguishes between symbol names and other names based on the context in the system configuration file.
func + 0x80000 // func name
symbol + 0x90 * 80 // symbol name
symbol + BASE // data macro
(func + 0x8000) // The start character is illegal.
0x8000 + func // The start character is illegal.
BASE + func // Data macro BASE is handled as a symbol name.
func * 0x8000 // It is not the format of offset.
- Name
In a system configuration file, words starting with an alphabetic character, "a to z, A to Z", or underscore "_" are regarded as names.
The CF850V4 distinguishes between symbol names and other names based on the context in the system configuration file.
In a system configuration file, words starting with an alphabetic character, "a to z, A to Z", or underscore "_" are regarded as names.
The CF850V4 distinguishes between symbol names and other names based on the context in the system configuration file.
- Preprocessing directives
The following preprocessing directives can be coded in a system configuration file.
The following preprocessing directives can be coded in a system configuration file.
- Keywords
The words shown below are reserved by the CFV850V4 as keywords.
Using these words for any other purpose specified is therefore prohibited.
The words shown below are reserved by the CFV850V4 as keywords.
Using these words for any other purpose specified is therefore prohibited.
ATT_INI, CLK_INTNO, CPU_TYPE, CRE_CYC, CRE_DTQ, CRE_FLG, CRE_MBX, CRE_MPF, CRE_MPL, CRE_MTX, CRE_SEM, CRE_TSK, DEF_EXC, DEF_FPSR, DEF_INH, DEF_SVC, DEF_TEX, DEF_TIM, INCLUDE, INT_STK, MAX_CYC, MAX_DTQ, MAX_FLG, MAX_INT, MAX_INTPRI, MAX_MBX, MAX_MPF, MAX_MPL, MAX_MTX, MAX_PRI, MAX_SEM, MAX_SVC, MAX_TSK, MEM_AREA, NULL, SERVICECALL, RI_SERIES, SIZE_AUTO, STK_CHK, SYS_STK, TA_ACT, TA_ASM, TA_CLR, TA_DISINT, TA_DISPREEMPT, TA_ENAINT, TA_HLNG, TA_MFIFO, TA_MPRI, TA_OFF, TA_ON, TA_PHS, TA_RSTR, TA_STA, TA_TFIFO, TA_TPRI, TA_WMUL, TA_WSGL, TBIT_FLGPTN, TBIT_TEXPTN, TIC_DENO, TIC_NUME, TKERNEL_MAKER, TKERNEL_PRID, TKERNEL_PRVER, TKERNEL_SPVER, TMAX_ACTCNT, TMAX_MPRI, TMAX_SEMCNT, TMAX_SUSCNT, TMAX_TPRI, TMAX_WUPCNT, TMIN_MPRI, TMIN_TPRI, TSZ_DTQ, TSZ_MBF, TSZ_MPF, TSZ_MPL, TSZ_MPRIHD, VATT_IDL, VDEF_RTN, G3K, G3M, G3KH, G3MH
Note In addition to the above words, service call names (such as act_tsk or slp_tsk), words starting with _kernel_, and the section names shown in Table B-1 to be used by the RI850V4 are reserved as keywords in the CF850V4.
The configuration information that is described in a system configuration file is divided into the following three main types.
- Declarative Information
Data related to a header file (header file name) in which data macro entities used in the system configuration file are defined.
Data related to a header file (header file name) in which data macro entities used in the system configuration file are defined.
- System Information
Data related to OS resources (such as real-time OS name, processor type) required for the RI850V4 to operate.
Data related to OS resources (such as real-time OS name, processor type) required for the RI850V4 to operate.
- Static API Information
Data related to management objects (such as task and task exception handling routine) used in the system.
Data related to management objects (such as task and task exception handling routine) used in the system.
In the system configuration file, describe the system configuration information (Declarative Information, System Information, Static API Information) in the following order.
The information items in the System Information group (such as RI series information or Basic information) and those in the Static API Information group (such as Task information or Semaphore information) can be coded in any order within each respective group.
-- Declarative Information (Header file declaration) description /* ......... */ -- System Information (RI series information, etc.) description /* ......... */ -- Static API Information (Task information, etc.) description /* ......... */ |