EM260-RTR Ember, EM260-RTR Datasheet - Page 27

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

Specifications of EM260-RTR

• 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
• For Use With: 636-1009 - PROGRAMMER USB FLASH EM250/260
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Memory Size: -
• Other names: 636-1007-2; EM260-RTR

5.4
5.5
Data Format
SPI Byte
Parameter
t7
t8
t9
t10
The data format, also referred to as a command, is the same for both the Command section and the Response
section. The data format of the SPI Protocol is straightforward, as illustrated in Figure 7.
The total length of a command must not exceed 128 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 EZSP Frame (EmberZNet Serial Protocol Frame)
and the Length Byte defines the length of just the EZSP Frame. Therefore, if a command includes an EZSP
Frame, the Length Byte can have a value from 2 through 125 and the overall command size will be 5 through
128. The SPI Byte can be a specific value indicating if there is an EZSP Frame or not, and if there is an EZSP
Frame, then the Length Byte can be expected.
The Error Byte is used by the error responses to provide additional information about the error. This addi-
tional information is described in the following sections.
The EZSP Frame contains the data needed for operating the networking stack. The EZSP Frame and its format
are explained in Chapter 6, EmberZNet Serial Protocol.
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 EM260 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 EM260 just reset and the corrupt Response should
be discarded.
Note:
tor.
Table 16 lists the possible commands and their responses in the SPI Byte.
SPI Byte
The Length Byte only specifies the length of the EZSP Frame. It does not include the Frame Termina-
Description
Wait section
nHOST_INT deasserting after Response
nHOST_INT asserting after transaction
Inter-command spacing
Length or
Error
Figure 7. SPI Level Data Format
EZSP Frame (Variable Length)
Min.
25
20
25
1
Typ.
755
130
70
120-1003-000D
Max.
200000
800
800
EM260
Terminator
Frame
µs
Unit
µs
µs
ms
27