User's Manual

Engineering Test Software Operation

Rev 28_A Sept 2005

50 VIA Telecom, Inc. Proprietary

the purpose of automated processing the interface used can be specified from the command line of the ETS

Main.

5.1.5.1 Serial Interface

The serial interface sub-module provides a bi-directional byte stream interface through which link layer data is

sent.

5.1.5.2 Message Encapsulation

The message encapsulation sub-module translates between the byte stream to the serial interface and the

message level. Messages that are to be sent are provided to the communication interface as a byte array.

Messages that are received are provided as a byte array for decoding.

The escape sequences and checksums for framing messages are processed based on the direction of transfer.

5.1.6 Message Router

The message router decodes the following and routes the event or information to the correct message object:

• Message Id of received messages

• Menu events

• OLE Automation interface commands

5.1.7 OLE Automation Interface

As entries are made in the log the OLE Automation Interface (OAI) receives a copy of the entry. The OAI is

composed of three outgoing queues for commands, responses, and errors. Log entries are placed in the

appropriate queue when the queue is enabled.

A command interface is also provided. As commands are received they are sent to the Message Router for

decoding and distribution.

System control functions will also be provided. At this time the system modes have not yet been defined.

5.1.8 Specialized Message Handlers

This section describes the operation of the specialized message handlers that are not supported by the MCL.

5.1.8.1 Loopback Test

For the purpose of testing the communication interface, a Loopback message test can be selected using the

Debug/Loopback… menu item. This test uses the loopback message to send data to the unit and then receive

the echoed data. It allows fixed and random data patterns. The test can be run continuously or one message at

a time.

5.1.8.2 Printf Message Handler

This message handler processes the MON_PRINTF_SYS message in order to simulate the C printf function.

5.1.8.3 Trace Message Handler

The trace message handler processes the MON_TRACECP_SYS, MON_TRACEDSPM_SYS and

MON_TRACEDSPV_SYS messages. These messages are declared as “MCL Trace” messages. For each of

the trace ids for these messages there is a PrintFormat string in the message definition that specifies a Class,

Level, and Format string in the following format: