EM260-RTY Ember, EM260-RTY Datasheet - Page 34

• 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
6 EmberZNet Serial Protocol
6.1
6.2
34
Byte Order
Conceptual Overview
120-1003-000D
Ember designed the EmberZNet Serial Protocol (EZSP) to be very familiar to customers who have used the
EmberZNet 2.x stack API. The majority of the commands and responses are functionally identical to those
found in EmberZNet 2.x. The variations are due mainly to the timing differences of running the application on
a separate processor across a serial interface. Communication between the EM260 and the Host consists of a
two-message transaction. The Host sends a command message to the EM260 and then the EM260 sends a
response message to the Host. If the EM260 needs to communicate asynchronously with the Host, it will
indicate this by using the interrupt line and then waiting for the Host to send the
All EZSP frames begin with a Frame Control Byte followed by a Frame ID Byte. The format of the rest of the
frame depends on the frame ID. Section 6.3 Protocol Format defines the format for all the frame IDs. Most of
the frames have a fixed length. A few, such as those containing application messages, are of variable length.
The frame control indicates the direction of the message (command or response). For commands, the frame
control also contains power management information, and for responses it also contains status information.
When a command contains an application message, the Host must supply a one-byte tag. This tag is used in
future commands and responses to refer to the message. For example, when sending a message, the Host
provides both the message contents and a tag. The tag is then used to report the fate of the message in a
later response from the EM260.
All multiple octet fields are transmitted and received with the least significant octet first, also referred to as
little endian. This is the same byte order convention specified by 802.15.4 and ZigBee. Note that EUI64 fields
are treated as a 64-bit number and are therefore transmitted and received in little endian order. Each indi-
vidual octet is transmitted most significant bit first, as shown in section 5.1, Physical Interface Configuration.
This section provides an overview of the concepts that are specific to the EM260 or that differ from the
EmberZNet 2.x stack API. The commands and responses mentioned in this overview are described in more
detail later in this document.
6.2.1
The Host can use the
There are a number of configuration values that affect the behavior of the stack. The Host can read these
values at any time using the
modify any of the default values using the
information about the application endpoints using the
Table 18 gives the minimum, default and maximum values for each of the configuration values. Also listed is
the RAM cost. This is the number of bytes of additional RAM required to increase the configuration value by
one. Since the total amount of RAM is fixed, the additional RAM required must be made available by reducing
one of the other configuration values.
Stack Configuration
version
getConfigurationValue
command to obtain information about the firmware running on the EM260.
setConfigurationValue
command. After the EM260 has reset, the Host can
addEndpoint
command. The Host must then provide
command.
callback
command.