2.3.2.
Downloading the CDP and HOT Files
PDKManager
is used to download the PDK protocol firmware (HOT file) and the protocol
parameters (CDP file) to a DM3 board.
There
are two ways to run PDKManager:
Running
PDKManager Manually
To manually
download and configure the protocol using PDKManager from the command line,
perform the following:
- From the command prompt, go to the Dialogic\Cfg
directory.
- In Windows, run PDKManager by typing:
PDKManager -board <n> [-options]
In
Linux, run PDKManager by typing:
PDKManager -board <n> [-options]
where
<n> is the DM3 logical board identifier and is defined as follows:
- Windows - the value of the LogicalID
parameter as set in DCM. For details, refer to the DCM Online Help.
- Linux - board ID as defined in
the pyramid.scd file. For details, refer to the System Release
Installation and Configuration Guide for your operating system.
The
protocol and parameter settings are downloaded to the board(s) as specified
by the command. For a list of the PDKManager command line options, refer
to Table 1.
Table 1.
PDKManager Command Line
Options
|
Option
|
Description
|
| -board
<n> |
Required.
Specifies the board(s)
to which the command applies. For
multiple boards, n = {n1 n2 ... nx} For
example, to download and assign the pdk_ar_r2_io protocol to
all lines on boards 1 and 3, type: PDKManager
-board {1 3} -variant pdk_ar_R2_io.cdp |
| -line
<n> |
Specifies
the T-1 or E-1 line(s) to which the command applies. If this parameter
is not specified, then all lines defined by the FCD file are used.
For multiple lines, n
= {n1 n2 ... nx} For
example, to download and assign the pdk_ar_r2_io protocol to
lines 1 and 2 on board 1, type: PDKManager
-board 1 -line {1 2} -variant pdk_ar_R2_io.cdp |
| -chan
<n> |
Specifies
the channel(s) to which the command applies. If this parameter is not
specified, then all channels defined by the FCD file are used.
For multiple channels,
n = {n1 n2 ... nx} For
example, to download and assign the pdk_ar_r2_io protocol to
channels 1 and 2 on line 1 on board 2, type:
PDKManager -board
2 -line 1 -channel {1 2} -variant pdk_ar_R2_io.cpd |
| -pcdfile
<file> |
Required
if -mlm file option is not used. Specifies
the .mlm file by parsing the PCD file. |
| -fcdfile
<file> |
Required
if -line and -channel options are not used. Determines
line and channel configurations by parsing the FCD file. |
| -variant
<file> |
Required
if the -load option is not used. Specifies
the CDP file used. Downloads and configures the protocol on the board(s)
specified, and then assigns the variant to the lines and channels. |
| -load
<file> |
Required
if the -variant option is not used. Specifies
the CDP file used. Downloads and configures the protocol to the board(s)
specified, but does not assign the variant to any lines. |
| -mlmfile
<file> |
Overrides
the firmware file (.mlm) specified in the PCD file. |
| -fastset |
Not
supported. |
| -help |
Invokes
the PDKManager help menu which displays the command options. |
Running
PDKManager Automatically
To automatically
invoke PDKManager from DCM (Windows) or dlstart (Linux), the user must create
a file called pdk.cfg. This file specifies the protocol and the parameter
settings downloaded to each board.
- From the command prompt, go to the Dialogic\Cfg
directory.
- Using a text editor (for example, WordPad
in Windows or vi in Linux), create a file called pdk.cfg.
- For each board or line to be configured,
add the following entry to the file:
board <n> [options] variant <file>
where
<n> is the DM3 logical board identifier and is defined as follows:
- In a Windows environment, to automatically
run PDKManager whenever DCM is invoked, type the following at the command
line:
pdkmanagerregsetup add
To
stop PDKManager from automatically running when DCM is invoked, type the
following at the command prompt:
pdkmanagerregsetup remove
- Note:
In a Linux environment, dlstart will automatically invoke PDKManager if
the pdk.cfg file is present in the dialogic/cfg directory. To stop PDKManager
from automatically running, remove the pdk.cfg file from the dialogic/cfg
directory.
For
a list of PDKManager options used in the pdk.cfg file, refer to Table
2.
Table 2.
PDKManager pdk.cfg File Options
|
Option
|
Description
|
| board
<n> |
Required.
Specifies
the board(s) to which the command applies. For
multiple boards, n = {n1 n2 ... nx} For
example, to download and assign the pdk_ar_r2_io protocol to
all lines on boards 1 and 3, type: board
{1 3} variant pdk_ar_R2_io.cdp |
| line
<n> |
Specifies
the T-1 or E-1 line(s) to which the command applies. If this parameter
is not specified, then all lines defined by the FCD file are used.
For multiple lines, n
= {n1 n2 ... nx} For
example, to download and assign the pdk_ar_r2_io protocol to
lines 1 and 2 on board 1, type: board
1 line {1 2} variant pdk_ar_R2_io.cdp |
| chan
<n> |
Specifies
the channel(s) to which the command applies. If this parameter is not
specified, then all channels defined by the FCD file are used.
For multiple channels,
n = {n1 n2 ... nx} For
example, to download and assign the pdk_ar_r2_io protocol to
channels 1 and 2 on line 1 on board 2, type:
board 2 line 1 channel
{1 2} variant pdk_ar_R2_io.cpd |
| pcdfile
<file> |
Required
if the default PCD file, qs_r2mf.pcd, is not used.
Specifies the .mlm
file by parsing the PCD file. |
| fcdfile
<file> |
Required
if the default FCD file, qs_r2mf.fcd, is not used.
Determines line and channel
configurations by parsing the FCD file. |
| variant
<file> |
Required.
Specifies the CDP file
used. Downloads and configures the protocol on the board(s) specified,
and then assigns the variant to the lines and channels. |
| mlmfile
<file> |
Overrides
the firmware file (.mlm) specified in the PCD file. |
