📄 sys_conf.h
字号:
/* @(#) pSOSystem PowerPC/V2.5.0: apps/xxxx/sys_conf.h (hello ppc) 4.68 98/11/17 16:51:28 */
/***********************************************************************/
/* */
/* MODULE: sys_conf.h */
/* DATE: 98/11/17 */
/* PURPOSE: pSOSystem configuration definitions */
/* */
/*---------------------------------------------------------------------*/
/* */
/* Copyright 1991 - 1998, 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. */
/* */
/* The "Configuration and Startup" section of the "Programmer's */
/* Reference" manual in pSOSystem contains a complete description */
/* of the symbols that are defined in this file. */
/* */
/***********************************************************************/
#ifndef _SYS_CONF_H
#define _SYS_CONF_H
#ifdef __cplusplus
extern "C" {
#endif
/***********************************************************************/
/* */
/* 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 corresponding to the value. The total space */
/* allocated is the sum of the BSP_PARMS and SC_APP_PARMS. */
/* */
/* SC_APP_NAME define controls the application name string that will */
/* be displayed during the boot dialog. */
/* */
/***********************************************************************/
#define SC_APP_PARMS 0
#define SC_APP_NAME "MULTIPLEXER"
#define SC_APP_MULTIPLEXER 1
/*---------------------------------------------------------------------*/
/* sys/types.h contains common definitions, (example YES, NO and more) */
/*---------------------------------------------------------------------*/
#include <sys/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 ensure */
/* consistency of the values stored by the boot ROM and the downloaded */
/* RAM application. */
/*---------------------------------------------------------------------*/
#include <sysvars.h>
/*---------------------------------------------------------------------*/
/* psos.h header file defines IO_AUTOINIT and IO_NOAUTOINIT */
/*---------------------------------------------------------------------*/
#include <psos.h>
/*---------------------------------------------------------------------*/
/* If USE_RARP is set to YES, then the IP address is obtained from the */
/* network. */
/*---------------------------------------------------------------------*/
#define USE_RARP NO
/***********************************************************************/
/* */
/* 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. */
/* */
/* The SC_STARTUP_DIALOG define either enables the boot dialog if set */
/* to YES, or disables the boot dialog if set to NO. */
/* */
/* SC_BOOT_ROM when set to YES, configures the application as a */
/* ROMable application. If set to NO, treats it as a RAM application. */
/* */
/* SC_SD_DEBUG_MODE determines the mode of the system, 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, SMODE_MASK */
/* in TD_FLAGS is always set. (See pROBE+ configuration */
/* parameters below.) */
/* */
/* 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. */
/* */
/* DBG_AP */
/***********************************************************************/
#define SC_SD_PARAMETERS SYS_CONF
#define SC_STARTUP_DIALOG NO
#define SC_BOOT_ROM NO
#define SD_STARTUP_DELAY 60
#define SC_SD_DEBUG_MODE DBG_AP /*DBG_XN:Debug*/
/***********************************************************************/
/* */
/* 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. */
/*---------------------------------------------------------------------*/
/* pSOS+: It is an error to specify both SC_PSOS and SC_PSOSM as */
/* present! */
/* */
/*---------------------------------------------------------------------*/
/* pROBE+: The following set of macros control which features will be */
/* built in to the pROBE+ Target Agent. pROBE+ can run either in */
/* console mode (dumb terminal) or as a back-end to a Source Level */
/* Debugger on the host. Not all modules are needed for all cases.*/
/* By eliminating modules you can save memory. The definition of */
/* the modules are as follows: */
/* */
/* SC_PROBE - pROBE+ core module. This must always be present if */
/* any part of pROBE+ is to be used. Setting this to NO will */
/* force all other pROBE+ modules to NO (even if they say YES */
/* in this file). */
/* */
/* SC_PROBE_CIE - pROBE+ Console Executive. Set this to YES if you */
/* wish to control pROBE+ from a dumb terminal. If you only */
/* use a source debugger and/or pRISM+, you can save memory by */
/* setting it to NO. If it is YES, you also need to sepcify the */
/* serial port used by the pROBE+ via SC_PROBE_CONSOLE. */
/* */
/* SC_PROBE_DISSAM - pROBE+ Console Dissassembler. If you set */
/* SC_PROBE_CIE to YES and wish to view disassembled memory, set */
/* this to YES as well. If you are using a host debugger and/or */
/* pRISM+, you can save memory by setting this to NO. */
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -