SN260 datasheet(28/88 Pages) STMICROELECTRONICS

28 / 88 page

SPI protocol

SN260

28/88

6.5.1

Primary SPI bytes

There are three primary SPI bytes: SPI protocol version, SPI status, and EZSP frame.

●

SPI protocol version [0x0A]

Sending this command requests the SPI Protocol Version number from the SPI

Interface. The response will always have bit 7 set and bit 6 cleared. In this current

version, the response will be 0x81, because the version number corresponding to this

set of Command-Response values is version number 1. The version number can be a

value from 1 to 63 (0x81–0xBF).

●

SPI status [0x0B]

Sending this command asks for the SN260 status. The response status byte will always

have the upper 2 bits set. In this current version, the status byte only has one status bit

[0], which is set if the SN260 is alive and ready for commands.

●

EZSP frame [0xFE]

This byte indicates that the current transaction is an EZSP transaction and there is

more data to follow. This SPI Byte, and only this SPI Byte, will cause the transaction to

look like the full data format illustrated in Figure 7. The byte immediately after this SPI

Byte will be a Length Byte, and it is used to identify the length of the EZSP Frame. The

EZSP Frame is defined in section Section 7: EmberZNet serial protocol on page 34. If

the SPI Byte is 0xFE, it means the minimum transaction size is five bytes. All other SPI

Bytes mean the transaction size is two or three bytes.

6.5.2

Special response bytes

There are only five SPI Byte values, 0x00–0x04, ever used as error codes (see Table 16).

When the error condition occurs, any command sent to the SN260 will be ignored and

responded to with one of these codes. These special SPI Bytes must be trapped and dealt

with. In addition, for each error condition the Error Byte (instead of the Length Byte) is also

sent with the SPI Byte.

Table 16.

Byte values used as error codes

SPI byte

value

Error message

Error description

Error byte description

0x00

SN260 Reset

See Section 6.6: Powering on, power cycling,

and rebooting.

The reset type. Refer to the API

documentation discussing

EmberResetType.

0x01

Oversized EZSP

Frame

The command contained an EZSP frame with

a Length Byte greater than 125. The SN260

was forced to drop the entire command.

Reserved

0x02

Aborted

Transaction

The transaction was not completed properly

and the SN260 was forced to abort the

transaction.

Reserved

0x03

Missing Frame

Terminator

The command was missing the Frame

Terminator. The SN260 was forced to drop the

entire command.

Reserved

0x04

Reserved

[none]

SN260 数据表(PDF) 28 Page - STMicroelectronics

SN260 数据表(HTML) 28 Page - STMicroelectronics

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

数据表下载

链接网址

SN260 数据表(PDF) 28 Page - STMicroelectronics

SN260 数据表(HTML) 28 Page - STMicroelectronics

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

数据表 下载

链接网址

数据表下载