Specifications

Software Interface 47
6. The module acknowledges the alert by clearing the module alert bit in
the CSR. Then the module begins to process commands received from
the host.
3.4.2 Stage 2
The host loads the microcode into the module’s private memory, then
executes the microcode as follows:
1. The host sends a STATUS command to the module to get the base
address and size of the block of shared memory that is available for
allocation.
2. The host allocates module memory based on the message the module
returns after receiving the STATUS command. The host copies the
module microcode into memory using the LOAD command, then
transfers control to the entry point of the resident microcode using a
JUMP command.
NOTE
The host maintains the module memory map and determines
which areas of memory to assign to each module subsystem.
3.4.3 Stage 3
The module microcode synchronizes with the TLI as follows:
1. The module tries to synchronize with the TLI hardware, and
determine its identity code. The host can request the outcome of
this attempt by sending a STATUS command to the module. If the
module cannot sychronize with the TLI hardware, the module disables
the TLI processor. If the module cannot synchronize with the TLI, the
TLI probably has a hardware problem that must be fixed. To enable
the TLI, the host must begin the initialization process over again.
The module can continue to operate with a broken TLI. However, the
module will not be able to communicate with the telephone network.
2. If the module synchronizes with the TLI hardware, the module writes
the telephone line identity code into a status message. Then the
module enables the TLI.