User manual

PICkit™ Serial Analyzer User’s Guide

TAG byte 0x80 means the transaction is over. TAG byte 0x81 signifies that the following

data is the firmware version. 0x82 signifies that the data following is the control block

(CONTROL_BLOCK). 0x83 signifies that the data following data is the status block

(STATUS_BLOCK). The EXEC portion of STATUS_BLOCK is shown in Table 9-10.

TABLE 9-10: EXEC STATUS BLOCK

TAG byte 0x84 is the script buffer status which shows availability of memory in each

buffer. TAG bytes 0x85, 0x86 and 0x87 identify data streams coming from RAM buffers

CBUF1, CBUF2 and CBUF3, respectively. RAM buffer 2 (CBUF2) is used in this archi-

tecture to queue the data stream from the COMM module to be sent to the host

software, thus TAG byte 0x86 identifies this stream.

TAG bytes 0x85 and 0x87 are typically unused.

9.5 COMM

The COMM module will decode TAG bytes from the data stream in the script buffer. The

TAG bytes may represent commands to internally configure the PICkit™ Serial Ana-

lyzer and report status, or the TAG bytes may be protocol specific identification that

needs to be translated into the device under test’s protocol and communicated to the

device. The COMM module performs both of these functions. This section will describe

the COMM TAGs common to all supported serial protocols. Table 9-11 describes the

TAGs (CCMD) used in the data stream to the COMM controller. Table 9-12 describes

TAGs (CDATA) used in the data stream from the COMM controller

0x87 N+2 CBUF3_DATA Data from CBUF3

0TAG

1 Configuration byte

2 : N+1 Data: from CBUF3

0x88 2 PACKET_ID Packet number

0TAG

1 Data: arbitrary packet ID#

Byte Bit Description

EXEC

0 7:0 EXEC status

1 CBUF1 overflow

2 CBUF2 overflow

3 CBUF3 overflow

4 Data error (e.g. illegal TAG, missing TAG-dependent data, etc.)

5 Restore control block failed – defaults used

7 Composite error

17:0

27:0

37:0

TABLE 9-9: EXEC TAG (EDATA) BYTES (CONTINUED)

TAG/EDATA LEN Name Description