SN260Q STMicroelectronics, SN260Q Datasheet - Page 28

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

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: -

SPI protocol
7.5.1
28/47
Table 8.
Primary SPI bytes
There are four primary SPI bytes: SPI protocol version, SPI status, Bootloader frame and
EZSP frame.
●
●
●
●
Command
0xF0 –
0x00 –
value
0xFC
0xFD
0x0A
0x0B
0xFE
0xFF
0x0F
Any
Any
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 0x82, since the version number
corresponding to this set of Command-Response values is version number 2. 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.
Bootloader frame [0xFD]: This byte indicates that the current transaction is a
Bootloader transaction and there is more data to follow. This SPI Byte will cause the
transaction to look like the full data format illustrated in Figure 8. The byte immediately
after this SPI Byte will be a Length Byte, and it is used to identify the length of the
Bootloader Frame. Refer to the EmberZNet Application Developer’s Guide (120-4028-
000) for more information on the bootloader. If the SPI Byte is 0xFD, it means the
minimum transaction size is four bytes.
EZSP frame [0xFE]: This byte indicates that the current transaction is an EZSP
transaction and there is more data to follow. This SPI Byte will cause the transaction to
look like the full data format illustrated in Figure 8. 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 the EZSP Reference Guide, 120-3009-000.) If the SPI Byte
is 0xFE, it means the minimum transaction size is five bytes
Command
Bootloader
SPI Status
SPI commands & responses (continued)
Reserved
Reserved
Protocol
Version
Frame
Frame
Invalid
EZSP
Any
Any
SPI
Response
0xC0 –
0x81 –
[none]
[none]
value
0xFD
0xBF
0xC1
0xFE
0xFF
0x03
0x04
Missing Frame Terminator—This is never used in another
response; it always indicates a missing frame terminator in
the command.
Unsupported SPI Command—This is never used in another
Response; it always indicates an unsupported SPI Byte in
the command.
[none]
bit[7] is always set. bit[6] is always cleared. bit[5:0] is a
number from 1–63.
bit[7] is always set. bit[6] is always set. bit[0]—Set if Alive.
[none]
Bootloader frame
EZSP frame
Invalid
Response
SN260