User's Manual

Table Of Contents

CATC MERLIN MOBILE 1.00 CHAPTER 7

User’s Manual Decoding Trace Data

DRAFT

• Sync word type (CAC, DAC, GIAC, or DIAC): The value of the sync word of the

access code.

• Access code trailer (Trail): The value of the trailer of the access code.

Packet Header Block

The packet header block contains fields from the packet header, as described in the

Bluetooth Specification, version 1.1. The packet header block can be expanded and

collapsed to show or hide the fields, as explained in Section 6.2.3 on page 55.

• Header block identifier (HDR): Identifies the block as the packet header block.

• AM_ADDR (Addr): The AM_ADDR of the slave device that the transmission was sent

to or from.

•TYPE (Packet Type): The heading for this field indicates the type of packet; the value is

the packet type code.

• FLOW (Flow): The value of the flow bit in the packet header. Possible values:

•1 = GO

•0 = STOP

• ARQN (Arqn): The value of the acknowledgment indication bit in the packet header.

Possible values:

• 1 = ACK (positive acknowledge)

• 0 = NAK (negative acknowledge)

• SEQN (Seqn): The value of the sequential numbering scheme bit in the packet header.

• HEC (HEC): The header-error-check value from the packet header.

Payload Block

The payload block contains the fields from the packet payload, as described in the Bluetooth

Specification, version 1.1. Two payload formats are defined for synchronous and

asynchronous packets: voice field (SCO packets) and data field (ACL packets). DV packets

contain both fields. The NULL, POLL, and ID link control packets do not contain payloads,

but FHS packets have their own payload format.

SCO Packet Payload Fields

• Voice data field (Voice Data): The payload data for a voice field payload format packet.

The data field can be expanded and collapsed, as explained in Section 6.2.2 on page 54.

ACL Packet Payload Fields

• Logical channel (L_CH): The value of the L_CH field of the payload header. Possible

values:

• NA (00) = undefined

• UA/UI (01) = Continuation fragment of an L2CAP message

• UA/UI (10) = Start of an L2CAP message or no fragmentation