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 93
Tag bytes 0x03, 0x04 and 0x05 write data bytes to their respective script buffers. In the
current architecture, Script Buffer 1 (CBUF1) is used to store communication com-
mands that will be fetched and executed by the Comm block. So, Tag byte 0x03 is used
to delineate data that is to be sent to the script buffer including communication proto-
cols to be sent to the unit under test. Tag bytes 0x04 and 0x05 are typically not used.
Tag bytes 0x06 and 0x07 configure the LEDs as follows:
TABLE 11-8: LED CONFIGURATION
Exec data Tag bytes identify data streams sent from the Exec block back to the host
software.
Description
Mode
M = CFG[7:6]
State
S = CFG[5]
Time
T = CFG[4:0]
Set immediate 00 1 = On, 0 = Off N/A
Blink once – On or Off 10 1 = On, 0 = Off T + 1 units
Blink continuous 11 Initial state: 1 = On, 0 = Off T + 1 units
Reserved 01
Legend: Time “unit” = 50 ms
Note: Set LED to blink continuously, on/off time = 100 ms.
CFG = 0xC1 (M = b’11’, S = 0, T = 1)
TABLE 11-9: EXEC TAG (EDATA) BYTES
Tag/EDATA LEN Name Description
0x80 1 END OF DATA Marks the end of valid data
0Tag
0x81 1 FIRMWARE_VERSION Firmware version
0Tag
1 Data: 20-byte STATUS_BLOCK
2 Date: major version
0x82 25 CONTROL_BLOCK_DATA Control block contents
0Tag
1:24 Data: CONTROL_BLOCK
0x83 21 STATUS_BLOCK_DATA Status block contents
0Tag
1:20 Data: minor version
0x84 7 CBUF_STATUS Status block contents
0Tag
1 Data: CBUF1: # bytes used
2 Data: CBUF1: # bytes unused
3 Data: CBUF2: # bytes used
4 Data: CBUF2: # bytes unused
5 Data: CBUF3: # bytes used
6 Data: CBUF3: # bytes unused
0x85 N+2 CBUF1_DATA Data from CBUF1
0Tag
1 Byte count
2 : N+1 Data: from CBUF1
0x86 N+2 CBUF2_DATA Data from CBUF2
0Tag
1 Byte count
2 : N+1 Data: from CBUF2