📄 sys_conf.h
字号:
/* *//* *//***********************************************************************/#define SD_LAN1 NO#define SD_LAN1_IP 0x00000000#define SD_LAN1_SUBNET_MASK 0/***********************************************************************//* *//* S H A R E D M E M O R Y C O N F I G U R A T I O N *//* *//* *//***********************************************************************//*---------------------------------------------------------------------*//* If you want to build a Shared Memory Interface for the network or *//* multi-processing pSOS+m, set SD_SM_NODE (a non-zero value) to the *//* node number of THIS node. *//*---------------------------------------------------------------------*/extern int _node_number;#define SD_SM_NODE (_node_number+1)/*---------------------------------------------------------------------*//* Shared memory network interface - SC_NISM_LEVEL should be 1 if this *//* will be the FIRST system to use the SMNI on this board. It should *//* be 2 if this will not be the first system to use the SMNI on this *//* board. Usually this means that SC_NISM_LEVEL should be 1 if you *//* are building Boot ROMs, and 2 for a system that will be downloaded *//* and started using the Boot ROMs. See the comments at the beginning *//* of drivers/ni_smem.c for more explanation. *//*---------------------------------------------------------------------*/#define SD_NISM NO#define SD_NISM_IP 0x00000000#define SD_NISM_DIRADDR **UNUSED**#define SC_NISM_BUFFS 30#define SC_NISM_LEVEL 2#define SD_NISM_SUBNET_MASK 0/*---------------------------------------------------------------------*//* If you want to build a multi-node pSOS+m system, set SD_KISM *//* to the number of nodes in the system. *//*---------------------------------------------------------------------*/extern int _number_of_nodes;#define SD_KISM _number_of_nodes#define SD_KISM_DIRADDR **UNUSED**/*---------------------------------------------------------------------*//* Stack overflow check. The following macro defines the number of *//* bytes at the end of the stack (of each task) which will be filled *//* with a known pattern, and which will be checked for being *//* overwritten at each system call. In case overwrite is detected, *//* then pSOS execution will abort with fatal error FAT_STKOVF (0xF30) *//* SC_STACK_OVF_CHECK will be truncated to an integral number of words.*//* It has a default of 8 bytes. *//*---------------------------------------------------------------------*/#define SC_STACK_OVF_CHECK 8 /* default *//***********************************************************************//* *//* M I S C E L L A N E O U S N E T W O R K I N G *//* P A R A M E T E R S *//* *//***********************************************************************/#define SD_DEF_GTWY_IP 0/***********************************************************************//* *//* B U S C O N F I G U R A T I O N *//* *//* *//***********************************************************************/#define SD_VME_BASE_ADDR 0x01000000/***********************************************************************//* SC_RAM_SIZE *//* *//* Normally, pSOSystem uses ALL of the memory remaining on a board for *//* dynamic allocation ("region 0"). You may override this by setting *//* SC_RAM_SIZE to a non-zero value. If you do, pSOSystem will not *//* touch any memory after address (BSP_RAM_BASE + SC_RAM_SIZE - 1). *//* *//* NOTE: This is useful when making a BOOT ROM and you want to ensure *//* that the ROM's RAM area does not overflow the space alloted for it. *//***********************************************************************/#define SC_RAM_SIZE Unused by Trimedia PSOS; claims max avail/* * TCS_MALLOC_USE: When YES, do *not* map malloc/free on * rn_getseg/rn_free from region 0, as is standard * in pSOS. Instead, use the TCS memory manager instead. * The pSOS region manager might be more predictable * in its real-time behavior, but this at the cost of * larger unit sizes (see KC_RN0USIZE). Also, * the pSOS region manager cannot hold more than * 32K units, which is 8M with the current KC_RN0USIZE, * but proportionally less when the unit size is * decreased. * If this option is enabled, then define TCS_REGION0_SIZE * such that region 0 does not occupy all free memory. */#define TCS_MALLOC_USE NO/* * TCS_REGION0_SIZE: When *not* defined, then all free memory * (limited to 32K units) is given to region 0. * otherwise, region 0 is created with the specified * size, but limited to 32K units; all other * memory is available via the TCS memory manager. * Use this option in combination with TCS_MALLOC_USE * when the desired KC_RN0USIZE results in a * region 0 which is not able to contain all available * SDRAM. */#if 0#define TCS_REGION0_SIZE 512 /* empty region */#endif/***********************************************************************//* *//* I / O D E V I C E S *//* *//* Each device may be included in the system by specifying a major *//* number for it, which determines its slot in the pSOS+ I/O switch *//* table. To leave a device driver out of the system, use NO for *//* the major number. *//* *//* Note the following: *//* * Major device 0 is reserved and cannot be used for any of these *//* devices. Setting a device number to 0 here is the same as NO. *//* * No device number may be higher than SC_DEVMAX (SC_DEVMAX may *//* be increased, if desired) *//* * The lines defining the symbols DEV_SERIAL, DEV_TIMER, etc, *//* should not be changed. These are for use by application *//* programs as the "device number" parameter on de_* calls. *//* *//***********************************************************************/#define SC_DEV_SERIAL 1 /* Serial driver */#define SC_DEV_TIMER 2 /* Periodic tick timer */#define SC_DEV_RAMDISK NO /* 3 RAM disk */#define SC_DEV_SCSI NO /* 4 SCSI bus */#define SC_DEV_SCSI_TAPE NO /* 5 SCSI bus, tape device */#define SC_DEV_TFTP NO /* 6 TFTP pseudo driver */#define SC_DEV_DLPI NO /* DLPI pseudo driver */#define SC_DEV_OTCP NO /* 8 TCP/IP for OpEN */#define SC_IP SC_DEV_OTCP /* 8 IP */#define SC_ARP NO /* 9 ARP */#define SC_TCP NO /* 10 TCP */#define SC_UDP NO /* 11 UDP */#define SC_RAW NO /* 12 RAW */#define SC_LOOP NO /* 13 LOOP = (SC_DEV_OTCP + 5) */#define SC_DEV_SOSI NO /* 14 OSI for OpEN */#define SC_DEVMAX 20 /* Maximum device number */#define DEV_SERIAL (SC_DEV_SERIAL << 16)#define DEV_TIMER (SC_DEV_TIMER << 16)#define DEV_RAMDISK (SC_DEV_RAMDISK << 16)#define DEV_SCSI (SC_DEV_SCSI << 16)#define DEV_SCSI_TAPE (SC_DEV_SCSI_TAPE << 16)#define DEV_TFTP (SC_DEV_TFTP << 16)/***********************************************************************//* *//* C O M P O N E N T C O N F I G U R A T I O N P A R A M E T E R S *//* *//* These parameters should work as is for this application. You *//* may want to change some of them if you start customizing this *//* application. *//* *//***********************************************************************//*---------------------------------------------------------------------*//* pSOS+ configuration parameters *//*---------------------------------------------------------------------*/#define KC_RN0USIZE 0x100 /* region 0 unit size */#define KC_NTASK 12 /* max number of tasks */#define KC_NQUEUE 10 /* max number of message queues */#define KC_NSEMA4 30 /* max number of semaphores */#define KC_NMSGBUF 100 /* max number of message buffers */#define KC_NTIMER 10 /* max number of timers */#define KC_NLOCOBJ 50 /* max number of local objects */#define KC_TICKS2SEC 100 /* clock tick interrupt frequency */#define KC_TICKS2SLICE 10 /* time slice quantum, in ticks */#define KC_SYSSTK 0x1000 /* pSOS+ system stack size (bytes) */#define KC_ROOTSSTK 0x1000 /* ROOT supervisor stack size */#define KC_ROOTUSTK 0 /* ROOT user stack size */#define KC_ROOTMODE 0x2000 /* ROOT initial mode *//*---------------------------------------------------------------------*//* The following are examples for modifying the following defines *//* */
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -