User's Manual

Table Of Contents

CATC MERLIN MOBILE 1.00 CHAPTER 7

User’s Manual Decoding Trace Data

DRAFT

• Serial Cable Emulation Protocol (RFCOMM) commands

• Object Exchange Protocol (OBEX) packets

• AT commands

• High-Level Data Link Control (HDLC) frames

• Point-to-Point Protocol (PPP) packets

• Bluetooth Network Encapsulation Protocol (BNEP) messages

• Human Interface Device (HID) packets

Additionally, users may create custom decoders for their own specific development needs.

For more information about custom decoding, see Section 7.4, “CATC Decoder Scripting

Files” on page 78.

7.2.1 Protocol Fields

The fields in protocol rows vary depending on the protocol data that is represented;

however, they do all contain the following four fields:

• Protocol Number Field (Protocol name): The first field for all protocol-level rows in a

Trace is the protocol number field. The field heading displays the protocol name, and

the value cell contains the protocol transmission number.

• Transmitting Device (T): The value of this field indicates whether the transmission was

sent from the master or slave device. Possible values are M (master) or S (slave).

• Active Member Address (Addr): The value cell of this field contains the AM_ADDR of

the slave device that the transmission was sent to or from.

• Time (Time): The value of this field is the starting time for the first packet in the trans-

mission, based on the packets’s time stamp. The time is formatted as Seconds.Millisec-

onds.

7.3 Protocol Assignments

Sometimes further configuration of protocol decoding is necessary in order to give Merlin

Mobile the information that it needs to correctly decode the data. Merlin Mobile provides

tools for manual configuration of the following information:

• L2CAP Channel Decoding Assignments

• L2CAP Channel Connection Assignments

• RFCOMM Channel Assignments

• OBEX Client/Server Status Assignments