Datasheet
Table Of Contents
- PICkit™ Serial Analyzer User's Guide
- Trademarks
- Table of Contents
- Chapter 1. PICkit™ Serial Analyzer Overview
- 1.1 Introduction
- 1.2 Highlights
- 1.3 PICkit™ Serial Analyzer Contents
- 1.4 PICkit™ Serial Analyzer Development System
- 1.5 PICkit™ Serial Analyzer Hardware
- 1.6 PICkit™ Serial Analyzer Software
- Chapter 2. Getting Started
- 2.1 Introduction
- 2.2 Highlights
- 2.3 Installing the PICkit™ Serial Analyzer Software
- 2.4 Connecting the PICkit™ Serial Analyzer to the PC
- 2.5 Connecting the PICkit™ Serial Analyzer to the 28-Pin Demo Board
- 2.6 Starting the PICkit™ Serial Analyzer Program
- 2.7 Running the 28-Pin Demo I2C™ Demonstration Program
- 2.8 I2C™ Communications – Basic Operations
- 2.9 28-Pin Demo I2C™ Source Code and Firmware
- Chapter 3. PICkit™ Serial Analyzer PC Program
- 3.1 Introduction
- 3.2 Highlights
- 3.3 Installing the PICkit™ Serial Analyzer Software
- 3.4 Starting the Program
- 3.5 Configuration Wizard
- 3.6 Main Window
- 3.7 Serial Communications Modes
- Chapter 4. I2C™ Master Communications
- 4.1 Introduction
- 4.2 Highlights
- 4.3 PICkit Serial Pin Assignments
- 4.4 Selecting Communications Mode
- 4.5 Configuring I2C Communications Mode
- 4.6 Communications: Basic Operations
- 4.7 Script Builder
- 4.8 Script Execute
- Chapter 5. I2C™ Slave Communications
- 5.1 Introduction
- 5.2 Highlights
- 5.3 PICkit Serial Pin Assignments
- 5.4 Selecting Communications Mode
- 5.5 Configuring I2C Slave Communications Mode
- 5.6 Communications: Basic Operations
- 5.7 Communications: Profile Generator
- Chapter 6. Lin Communications
- 6.1 Introduction
- 6.2 Highlights
- 6.3 PICkit Serial Pin Assignments
- 6.4 Selecting Communications Mode
- 6.5 Configuring Lin Slave Communications Mode
- 6.6 Communications: Basic Operations
- Chapter 7. SPI and Microwire Master Communications
- 7.1 Introduction
- 7.2 Highlights
- 7.3 PICkit™ Serial Analyzer Pin Assignments
- 7.4 Selecting Communications Mode
- 7.5 Configurating SPI Communications Mode
- 7.6 Communications: Basic Operations
- 7.7 Script Builder
- 7.8 Script Execute
- Chapter 8. USART Asynchronous Communications
- 8.1 Introduction
- 8.2 Highlights
- 8.3 PICkit Serial Pin Assignments
- 8.4 Selecting Communications Mode
- 8.5 Configuring USART Asynchronous Communications Mode
- 8.6 Communications: Basic Operations
- 8.7 Script Builder
- 8.8 Script Execute
- Chapter 9. USART Master Synchronous Communications
- 9.1 Introduction
- 9.2 Highlights
- 9.3 PICkit Serial Pin Assignments
- 9.4 Selecting Communications Mode
- 9.5 Configuring USART Synchronous Master Communications Mode
- 9.6 Communications: Basic Operations
- 9.7 Script Builder
- 9.8 Script Execute
- Chapter 10. User Defined Templates
- 10.1 Introduction
- 10.2 Highlights
- 10.3 Creating and Using Templates
- 10.4 My Templates
- 10.5 Graphing Data
- Chapter 11. PICkit™ Serial Analyzer Firmware
- 11.1 Introduction
- 11.2 Highlights
- 11.3 Overview
- 11.4 Exec
- 11.5 Comm
- 11.6 I2CM Communications
- 11.7 I2CS Communications
- 11.8 SPI Communications
- 11.9 USART Communications
- 11.10 LIN Communications
- Chapter 12. PICkit™ Serial Analyzer DLL
- 12.1 Introduction
- 12.2 Overview
- Chapter 13. Troubleshooting
- 13.1 Introduction
- 13.2 Frequently Asked Questions
- Appendix A. PICkit Serial Analyzer Schematics
- A.1 Introduction
- Appendix B. 28-Pin Demo Board I2C™ Demonstration Firmware
- B.1 Introduction
- B.2 Highlights
- B.3 Hardware
- B.4 Firmware
- B.5 I2C Communications
- B.6 Slave Devices
- B.7 Functions
- Worldwide Sales
PICkit™ Serial Analyzer Firmware
© 2009 Microchip Technology Inc. DS51647C-page 107
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 = I
2
CS, Mode = 2, appropriate Event Markers
enabled)
3. Write Slave Profile to CBUF3
4. Issue Warm Start
The Auto mode allows the PICkit Serial Analyzer to operate autonomously (i.e., without
host intervention). Practically speaking, the host GUI will most likely want to reflect
activity with the slave registers as it occurs. A couple of options can be employed.
Option 1 would call for the host to enable I
2
C transaction Event Markers detailing each
I
2
C transaction in which the PICkit Serial Analyzer participated. This requires that the
host decode/interpret the transactions on a byte-by-byte basis.
Option 2 utilizes the ‘register access’ event markers (I2CS_EVENT_REG_READ and
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 register within the
slave profile was written, it may be important for the host monitoring 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
2
C transactions. This
may cause a slight delay in executing the request or in servicing the next/pending I
2
C
transactions.
11.7.1.3.2 Slave Profile
In Auto mode the PICkit Serial Analyzer personality is defined by a “slave profile” down-
loaded by the host to PICkit Serial Analyzer RAM (i.e., CBUF3). The profile defines one
or more I
2
C slave addresses and a set of one or more device registers for each. The
profile must begin with a Slave Address Tag and be terminated by an ‘End’ Tag.
Comm
I
2
CS
CBUF3
(Profile)
CBUF2
CBUF1
Status
Control
Exec
PICkit™ Serial Analyzer
USB
H
O
S
T
D
E
V
I
C
E
I
2
C™
B
A
A - event data
B - I
2
C™ read data