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 User’s Guide
DS51647C-page 102 © 2009 Microchip Technology Inc.
An example of a data stream in the script buffer that would direct the Comm back to
communicate in I
2
C to the unit.
Under test is as follows:
The script (above) is interpreted as follows. Tag 0x81 instructs the Comm module to
generate an I
2
C Start bit on the I
2
C bus. Tag 0x84 indicates 2 bytes will be transmitted
following the start – 0xA8 and 0x01. The first byte is the I
2
C slave address (with
Write/Read bit Reset) and a data/command byte of 0x01. The Comm module does not
place any significance on the value of the data bytes but merely transmits them ‘blindly’
– as instructed. The next Tag 0x83 instructs the Comm module to issue a Restart bit
on the I
2
C bus. Tag and data bytes - 0x84, 0x01, 0xA9 – will cause 1 byte (0xA9) to be
transmitted. Here again, the Comm module does not interpret the data – the I
2
C slave
will interpret 0xA9 as an address with Write/Read bit set. Tag 0x89 followed by data
byte 0x01 instructs the Comm module to attempt to read 1 byte from the slave then
issue a NACK on the bus. Finally, an I
2
C Stop bit is issued according to Tag 0x82. The
resulting I
2
C transaction looks like this on the bus:
[START][A8][01][RESTART][A9][data byte received][STOP]
As the script is executed, a data stream will be developed using Tags/CDATA
(described in Table 11-19) and returned to the host software via CBUF2.
0x95 1 I
2
CM _AUX1_WAIT_1 wait AUX1 == 1
0Tag
0x96 1 I
2
CM _AUX2_RST AUX2: 0
0Tag
0x97 1 I
2
CM _AUX2_SET AUX2: 1
0Tag
0x98 1 I
2
CM _AUX2_OUT AUX2 direction: OUTPUT
0Tag
0x99 1 I
2
CM _AUX2_IN AUX2 direction: INPUT
0Tag
0x9A 1 I
2
CM _AUX2_WAIT_0 wait AUX2 == 0
0Tag
0x9B 1 I
2
CM _AUX2_WAIT_1 wait AUX2 == 1
0Tag
0x81 I
2
CM_START
0x84 I
2
CM_WRITE_BYTES
0x02 Number of bytes
0xA8 I
2
C™ address for writing
0x01 I
2
C™ command code
0x83 I
2
CM_RESTART
0x84 I
2
CM_WRITE_BYTES
0x01 Number of bytes
0xA9 I
2
C™ address for reading
0x89 I
2
CM_READ_BYTES_NLB
0x01 Number of bytes
0x82 I
2
CM_STOP
TABLE 11-18: I
2
CM ‘CMD’ TAG BYTES (CONTINUED)