DV164122 Microchip Technology, DV164122 Datasheet - Page 111

ANALYZER SRL PICKIT W/DEMO BOARD

DV164122

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

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

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
DV164122
Manufacturer:
Microchip Technology
Quantity:
135
Part Number:
DV164122
Manufacturer:
MICROCHIP
Quantity:
12 000
© 2007 Microchip Technology Inc.
limits of the register will cause the write data to be discarded. Reading from a
‘WRITE-ONLY’ register or attempting to read beyond the addressable limits of the reg-
ister will result in default data (0xFF).
FIGURE 11-4:
11.7.1.3.1 Operation:
The HOST configures the AUTO mode as follows:
1. Issue COLD START (Reset)
2. Write CONFIGURATION BLOCK (comm=I2CS, mode=2, appropriate EVENT
3. Write SLAVE PROFILE to CBUF3
4. Issue WARM START
The AUTO mode allows the PKSA to operate autonomously (i.e. without HOST inter-
vention). Practically speaking, the HOST GUI will most likely want to reflect activity with
the SLAVE registers as it occurs. A couple options can be employed.
Option 1 would call for the HOST to enable I
each I
decode/interpret the transactions on a byte-by-byte basis.
Option 2 utilizes the ‘register access’ EVENT MARKERS (I2CS_EVENT_REG_READ
& I2CS_EVENT_REG_WRITE) fired to the HOST when a register within the SLAVE
PROFILE is accessed. The fact that a slave register was read is an ‘event’ but does not
represent a change in the data loaded in the SLAVE PROFILE. In the event that a reg-
ister within the SLAVE PROFILE was written, it may be important for the HOST moni-
toring the SLAVE PROFILE to fetch the ‘new’ data from that register for
processing/display. Data is retrieved from a register using SCMND TAG:
I2CS_REGDATA_READ. The register contents are returned with SDATA TAG:
I2CS_REGDATA.
The register contents can be written or read by the HOST. To insure data integrity of
multi-byte registers, the contents are accessed only ‘between’ I
may cause a slight delay in executing the request or in servicing the next/pending I2C
transactions.
O
H
S
T
MARKERS enabled)
USB
2
C transaction in which the PKSA participated. This requires that the HOST
PKSA
EXEC
CONTROL
(PROFILE)
STATUS
CBUF1
CBUF2
CBUF3
2
C transaction EVENT MARKERS detailing
A - event data
B - I
B
A
2
C read data
COMM
I
2
CS
2
C transactions. This
I
2
DS51647B-page 105
C
D
E
V
C
E
I

Related parts for DV164122