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 126 © 2009 Microchip Technology Inc.
The auto-baud operation depends on receiving a ‘Break’ (13 bits of 0’s) followed by a
‘Sync’ (byte 0x55). Referring to the timing diagram below – the Break begins at ‘A’. At
‘B’ the PICkit Serial Analyzer expected a Stop bit – the USART interrupts the PICkit
Serial Analyzer (RCIF – receive interrupt flag) and sets FERR (framing error). The
PICkit Serial Analyzer interprets (1) DATA = 0 and (2) FERR (framing error) as having
received a Break; therefore, the FERR is automatically reset and not reported to the
host. If Auto-Baud Detection is enabled, the PICkit Serial Analyzer will wait a maximum
of ‘WAIT-BRK’ for the Break to complete at ‘C’. The duration of WAIT-BRK must be set
to accommodate the slowest baud rate supported (6 msec was chosen to support 1000
baud +/- 50%). If the end of Break is not seen in that time, the Auto-Baud Error bit is
set in the STATUS_BLOCK and the operation is aborted. If the end of Break is seen, the
auto-baud mechanism is enabled and the baud rate of the Sync character is measured.
At the second interrupt (RCIF (2)) at ‘E’, the operation is complete and the new/mea-
sured baud rate is used for subsequent transactions. If the auto-baud measurement
experienced an overflow, the Auto-Baud Error bit is set in the STATUS_BLOCK and the
default baud rate from the CONTROL_BLOCK is reloaded into the USART. In either case,
the resultant baud rate is reflected in the STATUS_BLOCK. After the Break, the PICkit
Serial Analyzer will wait indefinitely for the Sync character to begin with the USART
receiver disabled.
FIGURE 11-5:
WARNING
The Sync character is not actually ‘received’ by the PICkit Serial Analyzer during an
auto-baud operation; therefore, it is not reflected/reported to the host. The event
marker sequence would be BREAK_RX and auto-baud followed by BAUD_L, BAUD_H.
If auto-baud was not enabled, the event marker sequence would be BREAK_RX then
BYTE_RX followed by 0x55.
RCIF (1)
RCIF (2)
Sync
WAIT-BRK
Break
A B C D E F
S
P
0
1
2
3
4
5
6
7