SN260Q STMicroelectronics, SN260Q Datasheet - Page 27

IC ZIGBEE/802.15.4 PROC 40-QFN

SN260Q

Manufacturer Part Number
SN260Q
Description
IC ZIGBEE/802.15.4 PROC 40-QFN
Manufacturer
STMicroelectronics
Datasheet

Specifications of SN260Q

Frequency
2.4GHz
Modulation Or Protocol
802.15.4
Applications
ZigBee™
Power - Output
-32dBm ~ 5dBm
Sensitivity
-97.5dBm
Voltage - Supply
2.1 V ~ 3.6 V
Current - Receiving
35.5mA
Current - Transmitting
35.5mA
Data Interface
PCB, Surface Mount
Antenna Connector
PCB, Surface Mount
Operating Temperature
-40°C ~ 85°C
Package / Case
40-QFN
For Use With
497-6404 - BOARD EVAL SPZB260 MOD FOR STR9497-5990 - KIT EVAL REVA FOR ZIGBEE497-5879 - NETWORK DEVELOPMENT FOR SN260497-5877 - KIT RADIO CARRIER FOR SN260
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Memory Size
-
Data Rate - Maximum
-
SN260
Note:
7.5
Figure 8.
The total length of a command must not exceed 136 bytes.
All commands must begin with the SPI Byte. Some commands are only two bytes—that is,
they contain the SPI Byte and Frame Terminator only.
The Length Byte is only included if there is information in the Payload Frame and the Length
Byte defines the length of just the Payload Frame. Therefore, if a command includes a
Payload Frame, the Length Byte can have a value from 2 through 133 and the overall
command size will be 5 through 136 bytes. The SPI Byte can be a specific value indicating if
there is a Payload Frame or not, and if there is a Payload Frame, then the Length Byte can
be expected.
The Error Byte is used by the error responses to provide additional information about the
error and appears in place of the length byte. This additional information is described in the
following sections.
The Payload Frame contains the data needed for operating EmberZNet. The EZSP Frame
and its format are explained in the EZSP Reference Guide (120-3009-000). The Payload
Frame may also contain the data needed for operating the bootloader, which is called a
Bootloader Frame. Refer to the EmberZNet Application Developer’s Guide (120-4028-000)
for more information on the bootloader.
The Frame Terminator is a special control byte used to mark the end of a command. The
Frame Terminator byte is defined as 0xA7 and is appended to all Commands and
Responses immediately after the final data byte. The purpose of the Frame Terminator is to
provide a known byte the SPI Protocol can use to detect a corrupt command. For example, if
the SN260 resets during the Response Section, the Host will still clock out the correct
number of bytes. But when the host attempts to verify the value 0xA7 at the end of the
Response, it will see either the value 0x00 or 0xFF and know that the SN260 just reset and
the corrupt Response should be discarded.
The Length Byte only specifies the length of the Payload Frame. It does not include the
Frame Terminator.
SPI byte
Table 8
Table 8.
Command
value
Any
Any
Any
lists the possible commands and their responses in the SPI Byte.
SPI protocol data format
Command
SPI commands & responses
Any
Any
Any
Response
value
0x00
0x01
0x02
SN260 reset occurred—This is never used in another
response; it always indicates an SN260 Reset.
Oversized Payload Frame received—This is never used in
another response; it always indicates an overflow occurred.
Aborted Transaction occurred—This is never used in
another response; it always indicates an aborted transaction
occurred.
Response
SPI protocol
27/47

Related parts for SN260Q