⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 sys_conf.h

📁 wm PNE 3.3 source code, running at more than vxworks6.x version.
💻 H
📖 第 1 页 / 共 4 页
字号:
/* $Header: /usr/cvsroot/target/h/wrn/wm/util/port/isisnmp/mcf250/sys_conf.h,v 1.1.1.1 2001/11/05 17:47:10 tneale Exp $ *//* * Copyright (C) 1999-2004 Wind River Systems, Inc. * All rights reserved.  Provided under license only. * Distribution or other use of this software is only * permitted pursuant to the terms of a license agreement * from Wind River Systems (and is otherwise prohibited). * Refer to that license agreement for terms of use. *//**************************************************************************** *  Copyright 1998 Integrated Systems, Inc. *  All rights reserved. ****************************************************************************//* * $Log: sys_conf.h,v $ * Revision 1.1.1.1  2001/11/05 17:47:10  tneale * Tornado shuffle * * Revision 1.1  2000/02/24 16:05:56  josh * configuration files for pSOS for ColdFire * * *//* [clearcase]modification history-------------------*//* @(#) pSOSystem PowerPC/V2.5.0-BETA1: apps.v22/xxxx/sys_conf.h (snmpsa ppc) 3.72 98/06/05 11:02:22 *//***********************************************************************//*                                                                     *//*   MODULE:  sys_conf.h                                               *//*   DATE:    98/06/05                                                 *//*   PURPOSE: pSOSystem configuration definitions                      *//*                                                                     *//*---------------------------------------------------------------------*//*                                                                     *//*           Copyright 1991 - 1997, Integrated Systems, Inc.           *//*                      ALL RIGHTS RESERVED                            *//*                                                                     *//*   Permission is hereby granted to licensees of Integrated Systems,  *//*   Inc. products to use or abstract this computer program for the    *//*   sole purpose of implementing a product based on Integrated        *//*   Systems, Inc. products.   No other rights to reproduce, use,      *//*   or disseminate this computer program, whether in part or in       *//*   whole, are granted.                                               *//*                                                                     *//*   Integrated Systems, Inc. makes no representation or warranties    *//*   with respect to the performance of this computer program, and     *//*   specifically disclaims any responsibility for any damages,        *//*   special or consequential, connected with the use of this program. *//*                                                                     *//*---------------------------------------------------------------------*//*                                                                     *//*   This is a header file which defines all of the system-level       *//*   parameters that are likely to need changing.                      *//*                                                                     *//*   It has been set up to be as close as possible to the settings     *//*   which are appropriate for this application.  However, you may     *//*   need to make some changes to parameters to reflect your           *//*   environment, such as IP addresses, etc.                           *//*                                                                     *//*   Chapter 7 of the pSOSystem Getting Started manual contains a      *//*   complete description of the symbols that are defined in this      *//*   file.                                                             *//*                                                                     *//***********************************************************************/#ifdef __cplusplusextern "C" {#endif#ifndef _SYS_CONF_H#define _SYS_CONF_H/***********************************************************************//*                                                                     *//* SC_APP_PARMS Must be defined before you include sysvars.h file.     *//* Since "sysvars.h" file depends on SC_APP_PARMS and BSP_PARMS        *//* to define the Storage Parms Structure.                              *//*                                                                     *//* Defining this variable to a Non-Zero Value will create a space in   *//* the Storage Parms. structure for your application use.              *//*                                                                     *//***********************************************************************/#define SC_APP_PARMS 0#define SC_APP_NAME  "snmpsa Application"/*---------------------------------------------------------------------*//* types.h contains common definitions for example YES and NO          *//*---------------------------------------------------------------------*/#include <types.h>/***********************************************************************//* sysvars.h contains the structures and definitions for the system    *//* variables that are stored in NVRAM. These structures and            *//* definitions are also used when creating the boot rom for the        *//* target system. By using the same sysvars.h file it will insure the  *//* consistency of the values stored by the boot rom and later read by  *//* the downloaded application.                                         *//***********************************************************************/#include <sysvars.h>/*---------------------------------------------------------------------*//* include psos.h for defines IO_AUTOINIT and IO_NOAUTOINIT            *//*---------------------------------------------------------------------*/#include <psos.h>/***********************************************************************//*                                                                     *//*  These symbols are used to define other symbols in this file.       *//*  They should never be changed.                                      *//*                                                                     *//***********************************************************************/#define USE_RARP 0/***********************************************************************//*                                                                     *//*                 B A S I C   P A R A M E T E R S                     *//*                                                                     *//*  The parameters in this section determine the fashion in which      *//*  many of the other parameters in this file will be used.            *//*                                                                     *//*  Many of the parameters in this file have names beginning with      *//*  either "SC_" or "SD_".  Those beginning with "SC_" are ALWAYS      *//*  controlled by the values you set in this file.  The values of      *//*  the "SD_" parameters can be determined either by the definitions   *//*  given in this file, or by the data found in the target board's     *//*  parameter storage area.  SC_SD_PARAMETERS determines this.  If     *//*  SC_SD_PARAMETERS is "SYS_CONF", then the values given in this      *//*  file will be used for the SD_ parameters.  If SC_SD_PARAMETERS     *//*  is "STORAGE", then pSOSystem will attempt to use the values found  *//*  in the board's parameter storage area for the SD_ variables.  If   *//*  the parameter storage area has not been initialized or has been    *//*  corrupted, then the values given in this file will be used.  They  *//*  will also be written to the storage area.                          *//*                                                                     *//*  If SC_SD_PARAMETERS is STORAGE, you may enable a "startup dialog"  *//*  which will allow you to view, and optionally change, the           *//*  parameter values found in the storage area.  The dialog is enabled *//*  by setting SC_STARTUP_DIALOG to YES.  In this case,                *//*  SD_STARTUP_DELAY specifies the number of seconds that the dialog   *//*  will wait for input before proceeding to boot the system.          *//*                                                                     *//* SC_SD_DEBUG_MODE determines how the system will operate, as follows:*//*                                                                     *//*     DBG_SA: Boot pROBE+ in standalone mode.                         *//*                                                                     *//*     DBG_XS: Boot into pROBE+ and wait for the host debugger         *//*             via a serial connection                                 *//*                                                                     *//*     DBG_XN: Boot into pROBE+ and wait for the host debugger         *//*             via a network connection                                *//*                                                                     *//*     DBG_AP: Same as DBG_SA, but also does a pROBE+ "silent startup",*//*             meaning that pROBE+ initializes itself without          *//*             printing a startup banner.  pROBE+ then initializes     *//*             pSOS+ and starts the application running.   This mode   *//*             was created to simplify implementation of the pSOSystem *//*             Boot ROMs.  Note that when this mode is used, the value *//*             you specify for RC_SMODE (see "pROBE+ Configuration     *//*             Parameters", below) is overridden.                      *//*                                                                     *//*    STORAGE: Use the mode (DBG_SA, DBG_XS, or DBG_XN) found in the   *//*             parameter storage area.  If a valid mode is not found,  *//*             then use DBG_SA.                                        *//*                                                                     *//*  An important consequence of using SC_SD_DEBUG_MODE=STORAGE should  *//*  be noted.  If you use the TFTP bootloader in the pSOSystem ROMs    *//*  to download and start your system, you will be setting             *//*  SC_SD_DEBUG_MODE = DBG_AP in your target board's parameter storage *//*  area.  Thus, if you have left SC_SD_DEBUG_MODE set to STORAGE in   *//*  this file, your downloaded system will also use DBG_AP, meaning    *//*  that the application will begin running immediately after the      *//*  TFTP bootloader has loaded and started your system.                *//*                                                                     *//***********************************************************************/#define SC_SD_PARAMETERS    STORAGE#define SC_STARTUP_DIALOG   NO#define SC_BOOT_ROM         NO#define SD_STARTUP_DELAY    60#define SC_SD_DEBUG_MODE    STORAGE/***********************************************************************//*                                                                     *//*        O P E R A T I N G   S Y S T E M   C O M P O N E N T S        *//*                                                                     *//*  Setting the definition line to YES will cause that component to    *//*  be built into the system.  NO means the component will NOT be      *//*  put into the system.  It is an error to specify both SC_PSOS       *//*  and SC_PSOSM as present!                                           *//*                                                                     *//***********************************************************************/#define SC_PSOS             YES  /* pSOS+ real-time kernel             */#define SC_PSOSM             NO  /* pSOS+ real-time multiproc kernel   */#define SC_PSOS_QUERY        NO  /* pSOS+ Query Services               */#define SC_PROBE             NO  /* pROBE+ (processor svcs)            */#define SC_PROBE_DISASM      NO  /* pROBE+ (disassembler)              */#define SC_PROBE_CIE         NO  /* pROBE+ (console executive)         */#define SC_PROBE_QUERY       NO  /* pROBE+ (query services)            */#define SC_PROBE_DEBUG       NO  /* pROBE+ (debug interface executive) */#define SC_PROBE_HELP        NO  /* pROBE+ Help command Handler.       */#define SC_PHILE            YES  /* pHILE+ file system manager         */#define SC_PHILE_PHILE      YES  /* pHILE+ (pHILE+ real-time file sys) */#define SC_PHILE_MSDOS       NO  /* pHILE+ (MS-DOS FAT file system)    */#define SC_PHILE_NFS         NO  /* pHILE+ (NFS client)                */#define SC_PHILE_CDROM       NO  /* pHILE+ (ISO 9660 CD-ROM file sys)  */#define SC_PREPC            YES  /* pREPC+ C run-time library          */#define SC_PNA              YES  /* pNA+ TCP/IP networking manager     */#define SC_PNET              NO  /* pNET Library for BOOT ROMS         */#define SC_PRPC              NO  /* pRPC+ RPC component                */#define SC_PSE_PRPC          NO  /* pRPC+ RPC component Over pSE+      */#define SC_PSE               NO  /* pSE+ streams component             */#define SC_PSKT              NO  /* pSKT+ SKT library component        */#define SC_PTLI              NO  /* pTLI+ TLI library component        */#define SC_PMONT             NO  /* pMONT+                             */#define SC_PLM               NO  /* pLM+ Shared library manager        */#define SC_PROFILER          NO  /* Profiler is enabled/Disabled       */#define SC_RTEC              NO  /* Diab's Run time error checker      *//*---------------------------------------------------------------------*//* If SC_QBIND is set to YES then the Quick bindings for pSOS+ System  *//* calls will be used. If it is set to NO then the normal bindings     *//* will be used.                                                       *//*                                                                     *//* Quick bindings will not be supported for the applications with      *//* USER mode Tasks. So make sure your Application does not have any    *//* USER mode Tasks.                                                    *//*---------------------------------------------------------------------*/#define SC_QBIND             NO   /* Quick bindings for pSOSystem calls*//*---------------------------------------------------------------------*//* If set to IO_AUTOINIT device drivers that are installed be the      *//* InstallDriver function will have their autoinit field set. This     *//* will cause pSOS+ call the drivers initialization function when      *//* pSOS+ starts up. The de_init call will not have to be called for    *//* each driver if this is done.                                        *//*                                                                     *//* NOTE: This Auto Initialization will not work on all drivers.        */

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -