EM260-RTY Ember, EM260-RTY Datasheet - Page 28

• Manufacturer Part Number: EM260-RTY
• Description: IC ZIGBEE SYSTEM-ON-CHIP 40-QFN
• Manufacturer: Ember

Specifications of EM260-RTY

• Frequency: 2.4GHz
• Data Rate - Maximum: 250kbps
• Modulation Or Protocol: 802.15.4
• Applications: ZigBee™
• Power - Output: -32dBm ~ 3dBm
• Sensitivity: -97dBm
• Voltage - Supply: 2.1 V ~ 3.6 V
• Current - Receiving: 30mA
• Current - Transmitting: 34mA
• Data Interface: PCB, Surface Mount
• Antenna Connector: PCB, Surface Mount
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 40-QFN
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Memory Size: -
• Other names: 636-1003

EM260
28
120-1003-000D
Command
Value
Any
Any
Any
Any
Any
0x00 – 0x0F
0x0A
0x0B
0xF0 – 0xFD
0xFE
0xFF
5.5.1
There are three primary SPI Bytes: SPI Protocol Version, SPI Status, and EZSP Frame.
5.5.2
There are only five SPI Byte values, [0x00–0x04], ever used as error codes (see Table 17). When the error
condition occurs, any command sent to the EM260 will be ignored and responded to with one of these codes.
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], since 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 EM260 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 EM260 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 6, EmberZNet Serial
Protocol. 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.
Primary SPI Bytes
Special Response Bytes
Reserved
Reserved
Command
Any
Any
Any
Any
Any
SPI Protocol Version
SPI Status
EZSP Frame
Invalid
Table 16. SPI Commands & Reponses
0x00
0x02
None
0xC0 – 0xC1
None
0xFE
Response
Value
0x01
0x03
0x04
0x81 – 0xBF
0xFF
Response
EM260 reset occurred—This is never used in
another Response; it always indicates an EM260
Reset.
Oversized EZSP 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.
Missing Frame Terminator—This is never used in
another Response; it always indicates a Missing
Frame Terminator in the Command.
Reserved
[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]
EZSP Frame
Invalid