DV164122 Microchip Technology, DV164122 Datasheet - Page 84

• Manufacturer Part Number: DV164122
• Description: ANALYZER SRL PICKIT W/DEMO BOARD
• Manufacturer: Microchip Technology
• Series: PICkit™r
• Type: MCUr

Specifications of DV164122

• Contents: PICkit™ Serial Analyzer, 28-pin Demo Board, USB Cable, and Software with Documentation CD
• Processor To Be Evaluated: PIC16F886
• Interface Type: USB
• Silicon Manufacturer: Microchip
• Kit Application Type: Interface
• Application Sub Type: USB
• Silicon Family Name: PIC16F
• Kit Contents: PICkit Serial Analyzer, Demo Board, USB Cable, Software
• Rohs Compliant: Yes
• Lead Free Status / RoHS Status: Not applicable / Not applicable
• For Use With/related Products: PIC16F886
• For Use With: PKSERIAL-SPI1 - BOARD DEMO PICKIT SERIAL SPIPKSERIAL-I2C1 - BOARD DEMO PICKIT SERIAL I2C
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: Q3260228

PICkit™ Serial Analyzer User’s Guide
9.5
DS51647A-page 78
COMM
TABLE 9-9:
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:
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.
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
TAG/EDATA
Byte
0x87
0x88
0
1
2
3
LEN
N+2
EXEC TAG (EDATA) BYTES (CONTINUED)
EXEC STATUS BLOCK
2
7:0
7:0
7:0
7:0
Bit
0
1
2
3
4
5
6
7
CBUF3_DATA
PACKET_ID
EXEC status
CBUF1 overflow
CBUF2 overflow
CBUF3 overflow
Data error (e.g. illegal TAG, missing TAG-dependent data, etc.)
Restore control block failed – defaults used
Composite error
Name
EXEC
Data from CBUF3
Packet number
2 : N+1
Description
0
1
0
1
TAG
Configuration byte
Data: from CBUF3
TAG
Data: arbitrary packet ID#
© 2007 Microchip Technology Inc.
Description