B
Appendix C • Initialization Information
APEX1000 All-Purpose Edge QAM Software Version 2.4.x • Installation and Operation Manual
297
573408-001-a
Typical APEX1000 BOOTP Packet Files
The BOOTP packet file mix is not fixed, as files are added/removed consistent with
APEX1000 functionality enhancements.
The following table shows a typical list of files:
Filename
Purpose
Apex1000.fof
(File of files) Contains three field columns: source path, destination path, and force
flag.
Do not change the symbolic name of the APEX1000 in the second field, as it can
cause an initialization failure.
apex.cod
Host application code for main APEX1000
processor.
apex.ini
Contains APEX1000
configuration settings for application firmware.
apexbcmr.ini
Remapping configuration settings — holds configuration settings when the
APEX1000
is internally controlled (for example, Manual Routing, UDP Mapping).
mux.rbf
Field programming gate array personality file for Mux.
gigeapp.bin
Executable code for GigE processor.
apex.jar
Executable APEX1000-EM Java based application.
APEX1000 File of Files
#----------------------------------------------------------
---------
# APEX1000 Software File-Of-Files
#
# DESCRIPTION:
# APEX File-of-Files.
#
# FORMAT:
# ---------SOURCE--------- -------DESTINATION------- -
FLAGS---
# <boot server file name and path> <unit file name and
path>
# <flags>
#
# Note: File names must be in the standard DOS 8.3
format, i.e.,
# the “xxxxxxxx.xxx” format. The full path and file name
must be
# stated explicitly without the use of wildcards.
#----------------------------------------------------------
---------
# APEX Application Image File