MCP3564-ESLASHST datasheet(59/108 Pages) MICROCHIP

59 / 108 page

 2019-2021 Microchip Technology Inc.

DS20006181C-page 59

MCP3561/2/4

6.0

SPI SERIAL INTERFACE AND

DEVICE OPERATION

6.1

Overview

The MCP3561/2/4 devices use an SPI interface to read

and write the internal registers. The device includes a

four-wire (CS, SCK, SDI, SDO) serial SPI interface that

is compatible with SPI Modes 0,0 and 1,1. Data are

clocked out of the device on the falling edge of SCK

and data are clocked into the device on the rising edge

of SCK. In these modes, the SCK clock can Idle either

high (1,1) or low (0,0). The digital interface is asynchro-

nous with the MCLK clock that controls the ADC

sampling and digital filtering. All digital input pins are

Schmitt Triggered to avoid system noise perturbations

on the communications. The SPI interface is

maintained in a Reset state during POR.

Each SPI communication starts with a CS falling edge

and stops with the CS rising edge. Each SPI communi-

cation is independent. When CS is logic high, SDO is

in high-impedance, the transitions on SCK and SDI

have no effect. Changing from SPI Mode 1,1 to an SPI

Mode 0,0 and vice versa is possible and must be done

while the CS pin is logic high. Any CS rising edge clears

the communication and resets the SPI digital interface.

See Figure 1-1 for the SPI timing details.

The MCP3561/2/4 digital interface is capable of

handling various Continuous Read and Write modes,

which allows for ADC data streaming or full register

map writing within only one communication (and there-

fore, with only one unique command byte). It also

includes single byte Fast commands. The device does

not include a Master Reset pin, but it includes an SPI

Fast command to be able to fully reset the part at any

time and place it back in a default configuration.

The device family also includes advanced security

features to secure communication and alert users of

unwanted Write commands that change the desired

configuration. To secure the entire configuration, the

device includes an 8-bit lock code (LOCK[7:0]), which

blocks all Write commands to the full register map if the

value of the lock code is not equal to a defined pass-

word (0xA5). The user can protect its configuration by

changing the LOCK[7:0] value to 0x00 after full

programming, so that any unwanted Write command

will not result in a change in the configuration. Each SPI

read communication can be secured through a select-

able CRC-16 checksum provided on the SDO pin at the

end of every communication sequence. This checksum

computation is compatible with the DMA CRC hard-

ware of the PIC24 and PIC32 MCUs, as well as many

other MCU references, resulting in no additional

overhead for the added security.

Once the part is locked (write-protected), an additional

checksum calculation also runs continuously in the

background to ensure the integrity of the full register

map. All writable registers of the register map are

processed through a CRC-16 calculation engine and

give a CRC-16 checksum that depends on the con-

figuration. This checksum is readable from the CRC

a change in the checksum, a CRC interrupt generates

a flag to warn the user that the configuration has been

corrupted.

The MCP3561/2/4 devices also include additional digi-

tal signal pins, such as a dedicated IRQ interrupt output

pin and a Master Clock (MCLK) input/output pin, which

allow easier synchronization and faster interrupt

handling, facilitating the implementation of the device in

many different applications.

6.2

SPI Communication Structure

The MCP3561/2/4 interface has a simple communica-

tion structure. Every communication starts with a CS

falling edge and stops with a CS rising edge.

The communication is always started by the

COMMAND byte (eight bits) clocking on the SDI input.

The COMMAND byte defines the command that will be

executed by the digital interface. It includes the device

address,

the

address

bits

and

the

command-type bits.

The COMMAND byte is typically followed by data bytes

clocked on SDI if the command type is a write and on

SDO if the command type is a read. The COMMAND

byte can also define a Fast command, and in this case,

it is not followed by any other byte. The following sub-

sections detail the COMMAND byte structure and all

possible commands.

During the COMMAND byte clocking on SDI, a

STATUS byte is also propagated on the SDO output to

enable easy polling of the device status. During this time,

the interface is full-duplex, but the part can still be used

by MCUs handling only half-duplex communications if

the STATUS byte is ignored.

6.2.1

COMMAND BYTE STRUCTURE

The COMMAND byte fully defines the command that

will be executed by the part. This byte is divided into

three parts: the device address bits (CMD[7:6]), the

command

address

bits

(CMD[5:2])

and

the

command-type bits (CMD[1:0]). See Table 6-1.

TABLE 6-1:

COMMAND BYTE

CMD[7] CMD[6] CMD[5] CMD[4] CMD[3] CMD[2] CMD[1] CMD[0]

Device Address

Bits

Command Type

Bits

MCP3564-E/ST 数据表(PDF) 59 Page - Microchip Technology

MCP3564-E/ST 数据表(HTML) 59 Page - Microchip Technology

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

数据表下载