Dialogic DSI SPCI Network Interface Boards - Manual (Page 22)

4 Configuration and Operation
22
The full syntax of each command is listed in the Software Environment
Programmer’s Manual.
An example system.txt file is shown below:
*
* Example system.txt for the Development Package for Windows®.
*
* Edit this file to reflect your configuration.
*
* Essential modules running on host:
*
LOCAL
0x20 * ssd/ssds - Board interface task
LOCAL 0x00 * tim_nt - Timer task
*
* Optional modules running on the host:
*
LOCAL
0xcf * s7_mgt - Management/config task
LOCAL 0x2d * upe - Example user part task
*
* Modules running on the board (all redirected via ssd):
*
* REDIRECT
0x23 0x20 * ISUP module
* REDIRECT 0x4a 0x20 * TUP module
REDIRECT 0x22 0x20 * MTP3 module
REDIRECT 0x71 0x20 * MTP2 module
REDIRECT 0x10 0x20 * CT bus/Clocking control module
REDIRECT 0x8e 0x20 * On-board management module
*
* Redirection of status indications:
*
REDIRECT
0xdf 0x2d * LIU/MTP2 status messages -> upe
REDIRECT 0xef 0x2d * Other indications -> upe
*
* Now start-up all local tasks:
*
FORK_PROCESS ssds.exe
FORK_PROCESS tim_nt.exe
FORK_PROCESS tick_nt.exe
FORK_PROCESS s7_mgt.exe
FORK_PROCESS upe.exe
*
4.2.2 Generating a System Configuration File
This section describes the procedure for generating a system configuration
file (system.txt) and details any operating system specific differences in
behaviour of the development packages.
First, the file must contain LOCAL declarations for all modules that run on the
host computer. As a minimum this must include the SSDS module and the
timer module. Hence the following declarations must exist:
LOCAL 0x20 * ssd / ssds - Board interface task
LOCAL 0x00 * tim_xxx - Timer task
LOCAL declarations are required for any optional modules that run on the
host. Typically, this includes s7_mgt and the user's own application module.
It may also include host-based protocol modules and the s7_log utility. For
example: