Generating A System Configuration File - Dialogic DSI SPCI Network Interface Boards Programmer's Manual

4 Configuration and Operation
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
LOCAL
*
* Optional modules running on the host:
*
LOCAL
LOCAL
*
* Modules running on the board (all redirected via ssd):
*
* REDIRECT 0x23
* REDIRECT 0x4a
REDIRECT
REDIRECT
REDIRECT
REDIRECT
*
* Redirection of status indications:
*
REDIRECT
REDIRECT
*
* Now start-up all local tasks:
*
FORK_PROCESS
FORK_PROCESS
FORK_PROCESS
FORK_PROCESS
FORK_PROCESS
*
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
LOCAL
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:
22
0x20
0x00
0xcf
0x2d
0x20 * ISUP module
0x20 * TUP module
0x22 0x20 * MTP3 module
0x71 0x20 * MTP2 module
0x10 0x20 * CT bus/Clocking control module
0x8e 0x20 * On-board management module
0xdf 0x2d * LIU/MTP2 status messages -> upe
0xef 0x2d * Other indications -> upe
ssds.exe
tim_nt.exe
tick_nt.exe
s7_mgt.exe
upe.exe
0x20 * ssd / ssds - Board interface task
0x00 * tim_xxx - Timer task
* ssd/ssds - Board interface task
* tim_nt - Timer task
* s7_mgt - Management/config task
* upe - Example user part task