SN260 View Datasheet(PDF) - STMicroelectronics
Part Name
Description
MFG CO.
'SN260' PDF : 88 Pages View PDF
SPI protocol
SN260
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
0x01
SN260 Reset
Oversized EZSP
Frame
See Section 6.6: Powering on, power cycling,
and rebooting.
The command contained an EZSP frame with
a Length Byte greater than 125. The SN260
was forced to drop the entire command.
The reset type. Refer to the API
documentation discussing
EmberResetType.
Reserved
0x02
Aborted
Transaction
The transaction was not completed properly
and the SN260 was forced to abort the
transaction.
Reserved
0x03
Missing Frame
Terminator
0x04 Reserved
The command was missing the Frame
Terminator. The SN260 was forced to drop the Reserved
entire command.
[none]
[none]
28/88
Share Link: 
