SN260Q STMicroelectronics, SN260Q Datasheet - Page 25

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

SN260
7.2.7
Error conditions
If two or more different error conditions occur back to back, only the first error condition will
be reported to the Host (if it is possible to report the error). The following are error conditions
that might occur with the SN260.
●
●
●
●
●
●
Unsupported SPI command
If the SPI Byte of the command is unsupported, the SN260 will drop the incoming
command and respond with the Unsupported SPI Command Error Response. This
error means the SPI Byte is unsupported by the current Mode the SN260 is in.
Bootloader Frames can only be used with the bootloader and EZSP Frames can only
be used with the EZSP.
Oversized Payload frame
If the transaction includes a Payload Frame, the Length Byte cannot be a value greater
than 133. If the SN260 detects a length byte greater than 133, it will drop the incoming
Command and abort the entire transaction. The SN260 will then assert nHOST_INT
after Slave Select returns to Idle to inform the Host through an error code in the
Response section what has happened. Not only is the Command in the problematic
transaction dropped by the SN260, but the next Command is also dropped, because it
is responded to with the Oversized Payload Frame Error Response.
Aborted transaction
An aborted transaction is any transaction where Slave Select returns to Idle
prematurely and the SPI Protocol dropped the transaction. The most common reason
for Slave Select returning to Idle prematurely is the Host unexpectedly resetting. If a
transaction is aborted, the SN260 will assert nHOST_INT to inform the Host through an
error code in the Response section what has happened. When a transaction is
aborted, not only does the Command in the problematic transaction get dropped by the
SN260, but the next Command also gets dropped since it is responded to with the
Aborted Transaction Error Response.
Missing frame terminator
Every Command and Response must be terminated with the Frame Terminator byte.
The SN260 will drop any Command that is missing the Frame Terminator. The SN260
will then immediately provide the Missing Frame Terminator Error Response.
Long transaction
A Long Transaction error occurs when the Host clocks too many bytes. As long as the
inter-command spacing requirement is met, this error condition should not cause a
problem, since the SN260 will send only 0xFF outside of the Response section as well
as ignore incoming bytes outside of the Command section.
Unresponsive
Unresponsive can mean the SN260 is not powered, not fully booted yet, incorrectly
connected to the Host, or busy performing other tasks. The Host must wait the
maximum length of the Wait section before it can consider the SN260 unresponsive to
the Command section. This maximum length is 200 milliseconds, measured from the
end of the last byte sent in the Command Section. If the SN260 ever fails to respond
during the Wait section, it is valid for the Host to consider the SN260 unresponsive and
to reset the SN260. Additionally, if nHOST_INT does not assert within 10ms of nWAKE
asserting during the wake handshake, the Host can consider the SN260 unresponsive
and reset the SN260.
SPI protocol
25/47