EM260-RTY Ember, EM260-RTY Datasheet

IC ZIGBEE SYSTEM-ON-CHIP 40-QFN

EM260-RTY

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
Ember Corporation
343 Congress Street
Boston MA 02210 USA
+1 617.951.0200
www.ember.com
120-1003-000D
July 21, 2006
EM260
ZigBee/802.15.4 Network Processor
RF_TX_ALT_P,N
Integrated 2.4GHz, IEEE 802.15.4-compliant trans-
ceiver:
Integrated IEEE 802.15.4 PHY and MAC
Ember ZigBee-compliant stack running on the
dedicated network processor
Controlled by the Host using the EmberZNet Serial
Protocol (EZSP)
VREG_OUT
RF_P,N
BIAS_R
Robust RX filtering allows co-existence with
IEEE 802.11g and Bluetooth devices
- 97dBm RX sensitivity (1% PER, 20byte packet)
+ 3dBm nominal output power
Increased radio performance mode (boost
mode) gives – 98dbm sensitivity and + 5dBm
transmit power
Integrated VCO and loop filter
Secondary TX-only RF port for applications re-
quiring external PA.
OSCA
OSCB
wireless semiconductor solutions
PA select
PA
Regulator
manager
HF OSC
RC-OSC
Internal
Chip
Bias
LNA
PA
Controller
Encryption acclerator
Serial
SYNTH
IF
Controller
Interrupt
IO Controller
DAC
ADC
Always
powered
Sleep
timer
TX_ACTIVE
Baseband
PacketTrace
Integrated Flash and RAM
MAC
+
Network Processor
Non-intrusive debug interface (SIF)
Integrated hardware and software support
for InSight Development Environment
Dedicated peripherals and integrated
memory
Provides integrated RC oscillator for low
power operation
Three sleep modes:
Watchdog timer and power-on-reset
circuitry
Integrated AES encryption accelerator
Integrated 1.8V voltage regulator
Watchdog
Peripherals
Standard Serial Interface (allows for
connection to a variety of Host mi-
crocontrollers)
Processor idle (automatic)
Deep sleep—1.0µA
Power down—1.0µA
Processor
(XAP2b)
Network
POR
SIF
nRESET
SIF_CLK
SIF_MISO
SIF_MOSI
nSIF_LOAD

Related parts for EM260-RTY

EM260-RTY Summary of contents

Page 1

... EM260 ZigBee/802.15.4 Network Processor Integrated 2.4GHz, IEEE 802.15.4-compliant trans- ceiver: • Robust RX filtering allows co-existence with IEEE 802.11g and Bluetooth devices • - 97dBm RX sensitivity (1% PER, 20byte packet) • + 3dBm nominal output power • Increased radio performance mode (boost mode) gives – 98dbm sensitivity and + 5dBm transmit power • ...

Page 2

... EmberZNet API across a standard SPI module, allowing application development on a Host processor. This means that the EM260 can be viewed as a ZigBee peripheral connected over a SPI. The XAP2b microprocessor is a power-optimized core integrated in the EM260. It contains integrated Flash and RAM memory along with an optimized peripheral set to enhance the operation of the network stack ...

Page 3

... SPI Transaction 5.2.1 Command Section 5.2.2 Wait Section 5 5.2.3 Response Section 8 5.2.4 Asynchronous Signaling 10 5.2.5 Spacing 5.2.6 Waking the EM260 from Sleep 25 10 5.2.7 Error Conditions 5.3 SPI Protocol Timing 10 5.4 Data Format 11 5.5 SPI Byte 12 5.5.1 Primary SPI Bytes 12 5 ...

Page 4

... EM260 6.4.2 Binding 6.4.3 Sending 6.4.4 Receiving 7 SIF Module Programming and Debug Interface 8 Typical Application 4 120-1003-000D 85 9 Mechanical Details 85 10 Ordering Information 86 11 Abbreviations and Acronyms 87 12 References ...

Page 5

... Pin Assignment VDD_VCO RF_P RF_N VDD_RF RF_TX_ALT_P RF_TX_ALT_N VDD_IF BIAS_R VDD_PADSA TX_ACTIVE GND EM260 Figure 1. EM260 Pin Assignment EM260 30 nSIF_LOAD 29 SIF_MOSI 28 SIF_MISO 27 SIF_CLK 26 nHOST_INT 25 RES 24 VDD_PADS 23 PTI_DATA 22 PTI_EN 21 nSSEL 120-1003-000D 5 ...

Page 6

... SPI Slave Select (Active Low) from Host to EM260. This signal must be connected to nSSEL (Pin 21) Reserved for future use, do not connect to any signal. I SPI Data, Master Out / Slave In (from Host to EM260) O SPI Data, Master In / Slave Out (from EM260 to Host) Power Pads supply (2.1 – 3.6V) I SPI Clock I ...

Page 7

... Power 41 GND Ground Description Link and Activity Signal Wake Interrupt Signal from Host to EM260 1.8V digital core supply 1.8V Synthesizer and Prescalar supply 24MHz crystal oscillator or left open for when using an external clock input on OSCA 24MHz crystal oscillator or external clock input 1 ...

Page 8

... EM260 2 Top-Level Functional Description Figure 2 shows a detailed block diagram of the EM260. PA select RF_TX_ALT_P,N PA RF_P,N LNA BIAS_R Bias OSCA HF OSC OSCB Internal RC-OSC VREG_OUT Regulator Chip manager The radio receiver is a low-IF, super-heterodyne receiver. It utilizes differential signal paths to minimize noise interference, and its architecture has been chosen to optimize co-existence with other devices within the 2 ...

Page 9

... In addition, the SIF module provides a non-intrusive programming and debug interface allowing for real-time application debugging. The EM260 exposes the Ember Serial API over the SPI, which allows application development to occur on a Host microcontroller of choice. In addition to the SPI, two additional signals, nHOST_INT and nWAKE, provide an easy-to-use handshake mechanism between the Host and the EM260 ...

Page 10

... Voltage on SIF_CLK, SIF_MISO, SIF_MOSI, nSIF_LOAD, nRESET, VREG_OUT Voltage on TX_ACTIVE, BIAS_R, OSCA, OSCB Storage temperature 3.2 Recommended Operating Conditions Table 3 lists the rated operating conditions of the EM260. Parameter Regulator input voltage (VDD_PADS) Core input voltage (VDD_24MHZ, VDD_VCO, VDD_RF, VDD_IF, VDD_PADSA, VDD_FLASH, VDD_SYNTH_PRE, VDD_CORE) Temperature range 3 ...

Page 11

... DC Electrical Characteristics Table 5 lists the DC electrical characteristics of the EM260. Parameter Regulator input voltage (VDD_PADS) Power supply range (VDD_CORE) Deep Sleep Current Quiescent current, including internal RC oscillator RX Current Radio receiver, MAC, and baseband (boost mode) Radio receiver, MAC, and baseband CPU, RAM, and Flash memory ...

Page 12

... EM260 3.5 Digital I/O Specifications Table 6 contains the digital I/O specifications for the EM260. The digital I/O power (named VDD_PADS) comes from three dedicated pins (pins 13, 19, and 24). The voltage applied to these pins sets the I/O voltage. Parameter Voltage supply Input voltage for logic 0 ...

Page 13

... IEEE 802.15.4) Linear RSSI range 3.6.2 Transmit Table 8 lists the key parameters of the integrated IEEE 802.15.4 transmitter on the EM260. All measurements data was collected with Ember’s Reference Design at 2440 MHz. The Typical Note: number indicates one standard deviation below the mean. ...

Page 14

... Error vector magnitude Carrier frequency error Load impedance PSD mask relative PSD mask absolute 3.6.3 Synthesizer Table 9 lists the key parameters of the integrated synthesizer on the EM260. Parameter Frequency range Frequency resolution Lock time Relock time Phase noise at 100kHz Phase noise at 1MHz ...

Page 15

... RSSI and CCA The EM260 calculates the RSSI over an 8-symbol period as well as at the end of a received packet. It utilizes the RX gain settings and the output level of the ADC within its algorithm. The EM260 RX baseband provides support for the IEEE 802.15.4-2003 required CCA methods summarized in Table 10. Modes 1, 2, and 3 are defined by the 802.15.4-2003 standard ...

Page 16

... PHY TX and RX packets (in a non-intrusive manner) between the MAC and baseband modules asynchronous 500kbps interface and cannot be used to inject packets into the PHY/MAC interface. The two signals from the EM260 are the frame signal (PTI_EN) and the data signal (PTI_DATA). The PTI is supported by InSight Desktop. ...

Page 17

... The EM260 stores non-volatile information necessary for network operation as well as 8 tokens available to the Host (see section 6.2.6, Tokens). The majority of internal tokens is only written when the EM260 performs a network join or leave operation. With security turned on, a 32-bit nonce counter token is set for every 4,096 messages sent ...

Page 18

... RAM Like the Flash memory, this RAM is also mapped to both the program and data-side address spaces. The EM260 supports a protection mechanism to prevent application code from overwriting system data stored in the RAM. To enable this, the RAM is segmented into 32-byte sections, each with a configurable bit that allows or denies write access when the EM260 is running in Application Mode ...

Page 19

... VDD_PADS POR assert 1.8V POR release 1.8V POR hysteresis 4.10 Clock Sources The EM260 integrates two oscillators: a high-frequency 24MHz crystal oscillator and a low-frequency internal 10kHz RC oscillator. 4.10.1 High-Frequency Crystal Oscillator The integrated high-frequency crystal oscillator requires an external 24MHz crystal with an accuracy of +/- 40ppm ...

Page 20

... Frequency variation with supply 4.11 Random Number Generator The EM260 allows for the generation of random numbers by exposing a randomly generated bit from the RX ADC. Analog noise current is passed through the RX path, sampled by the receive ADC, and stored in a regis- ter. The value contained in this register could be used to seed a software-generated random number. The EmberZNet stack utilizes these random numbers to seed the Random MAC Backoff and Encryption Key Genera- tors ...

Page 21

... Activity on a serial interface may also be configured to wake the EM260, though actual reception of data is not re-enabled until the EM260 has finished waking up. Depending on the speed of the serial data possible to finish waking up in the middle of a byte. Care must be taken to reset the serial interface between bytes and discard any garbage data before the rest ...

Page 22

... EM260 Instead of using the internal regulator, an external regulator may be used. The external regulator must be controlled by a GPIO from the Host microcontroller. 22 120-1003-000D ...

Page 23

... Physical Interface Configuration The EM260 supports both SPI Slave Mode 0 (clock is idle low, sample on rising edge) and SPI Slave Mode 3 (clock is idle high, sample on rising edge maximum SPI clock rate of 5MHz, as illustrated in Figure 3. The convention for the waveforms in this document is to show Mode 0. ...

Page 24

... Wait section, an interrupt-driven or polling-driven method is suggested for clocking the SPI as opposed to a DMA method. Since the EM260 can require up to 200 milliseconds to respond, as long as the Host keeps Slave Select active, the Host can perform other tasks while waiting for a Response. ...

Page 25

... Waking up the EM260 involves a simple handshaking routine as illustrated in Figure 5. This handshaking insures that the Host will wait until the EM260 is fully awake and ready to accept commands from the Host. If the EM260 is already awake when the handshake is performed (such as when the Host resets and the EM260 is already operating), the handshake will proceed as described below with no ill effects ...

Page 26

... Command Section. If the EM260 ever fails to respond during the Wait section valid for the Host to consider the EM260 unresponsive and to reset the EM260. Additionally, if nHOST_INT does not assert within 10ms of nWAKE asserting during the wake handshake, the Host can consider the EM260 unresponsive and reset the EM260 ...

Page 27

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

Page 28

... Special Response Bytes 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. 28 120-1003-000D Table 16. SPI Commands & Reponses ...

Page 29

... Slave Select returns to idle. By ignoring SPI traffic until idle, the EM260 will not begin receiving in the middle of a transaction. If the Host resets, in most cases it should reset the EM260 as well so that both devices are once again in the same state: freshly booted. Alternately, the Host can attempt to recover from the reset by recovering its previous state and resynchronizing with the state of the EM260 ...

Page 30

... Transaction Examples This section contains the following transaction examples: Obtaining the SPI Protocol Version EmberZNet Serial Protocol Frame—NOP Command EM260 Reset Three-Part Transaction: Wake, Get Version, Stack Status Callback 5.7.1 Obtaining the SPI Protocol Version 1. Activate Slave Select (nSSEL). ...

Page 31

... EZSP Frame Control Byte indicating a response with no overflow • 0x05 - EZSP Frame Type Byte indicating the NOP response • 0xA7 - Frame Terminator 8. Deactivate Slave Select. 5.7.3 EM260 Reset 1. nHOST_INT asserts. 2. Activate Slave Select (nSSEL). command NOP Figure 10. EM260 Reset Example EM260 120-1003-000D 31 ...

Page 32

... Receive the Error Byte and decode (0x02 is enumerated as RESET_POWERON). 8. Receive the Frame Terminator (0xA7). 9. Response 0x00 indicates the EM260 has reset and the Host should respond appropriately. 10. Deactivate Slave Select. 11. Since nHOST_INT does not assert again, there is no more data for the Host. ...

Page 33

... EZSP Frame Control Byte indicating a response with no overflow 0x19 EZSP Frame Type Byte indicating the emberStackStatusHandler response 0x91 EmberStatus EMBER_NETWORK_DOWN from emberStackStatusHandler 0xA7 Frame Terminator 24. Deactivate Slave Select. 25. Since nHOST_INT does not assert again, there is no more data for the Host. command callback 120-1003-000D EM260 33 ...

Page 34

... Physical Interface Configuration. 6.2 Conceptual Overview 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. ...

Page 35

... EM260 Description The number of packet buffers available to the stack. The maximum number of router neighbors the stack can keep track of. A neighbor is a node within radio range. The maximum number of datagram and sequenced messages the stack can have " ...

Page 36

... EM260 Value EZSP_CONFIG_DISCOVERY_CACHE_SIZE EZSP_CONFIG_STACK_PROFILE EZSP_CONFIG_SECURITY_LEVEL EZSP_CONFIG_MAX_TREE_DEPTH EZSP_CONFIG_MAX_ROUTER_CHILDREN EZSP_CONFIG_MAX_HOPS EZSP_CONFIG_MAX_END_DEVICE_CHILDREN (E) EZSP_CONFIG_INDIRECT_TRANSMISSION_TIMEOUT EZSP_CONFIG_RESERVED_ROUTING_ENTRIES EZSP_CONFIG_MOBILE_NODE_POLL_TIMEOUT EZSP_CONFIG_RESERVED_MOBILE_CHILD_ENTRIES EZSP_CONFIG_HOST_RAM EZSP_CONFIG_TX_POWER_MODE 36 120-1003-000D Min. Def. Max. Units RAM Cost entries hops children 4 0 300 3000 milli seconds 0 0 (C) entries quarter 0 seconds 0 0 (E) entries 255 bytes Description The number of entries in the discovery cache on a router ...

Page 37

... To avoid disrupting the operation of the network, only put the EM260 to sleep when it is not joined to a network or when it is joined as a sleeping end device. If the EM260 is joined as a sleeping end device, then it must poll its parent in order to receive messages. The Host controls the polling behavior using the command ...

Page 38

... Tokens preserve their values between reboots. Refer to section 4.6.2 for a description of the Simulated EEPROM and write cycle estimates. 6.2.7 RAM Some of the RAM on the EM260 can be reserved by the Host for its own use. The amount of space reserved is the EZSP_CONFIG_HOST_RAM can then read and write data using the will reduce the number of messages and callbacks that the EM260 can buffer ...

Page 39

... The current response was not truncated. Section 6.3.1 defines all the types used by the EM260 and section 6.3.2 defines all the structures. Section 6.3.3 enumerates all the named values for the different types. The subsequent sections list all the frames supported by the EM260, specifying the Frame ID, the command parameters and the response parameters. The list is divided into five sections: Section 6 ...

Page 40

... EM260 6.3.1 Type Definitions Type boolean EzspConfigId EzspConfigTxPowerMode EzspConfigStatus EzspPolicyId EzspDecisionId EmberStatus EmberEventUnits EmberNodeType EmberNetworkStatus EmberIncomingMessageType EmberBindingType EmberUnicastOption EmberNetworkScanType EmberJoinDecision EmberNodeId EmberPanId EmberEUI64 40 120-1003-000D Alias Description int8u True or false. int8u Identifies a configuration value. int16u Values for EZSP_CONFIG_TX_POWER_MODE. int8u Return type for configuration commands. ...

Page 41

... A binding can be used to send messages with any cluster ID, not just the one listed in the binding. A 64-bit identifier. This is either the destination EUI64 (for unicasts) or the 64-bit group address (for multicasts). An alias for zero, used for clarity. 0x00 An alias for one, used for clarity. 0x01 EM260 120-1003-000D 41 ...

Page 42

... EM260 EzspConfigId EZSP_CONFIG_PACKET_BUFFER_COUNT EZSP_CONFIG_NEIGHBOR_TABLE_SIZE EZSP_CONFIG_TRANSPORT_PACKET_COUNT EZSP_CONFIG_BINDING_TABLE_SIZE EZSP_CONFIG_TEMPORARY_BINDING_ENTRIES EZSP_CONFIG_TRANSPORT_CONNECTION_COUNT EZSP_CONFIG_ROUTE_TABLE_SIZE EZSP_CONFIG_DISCOVERY_TABLE_SIZE EZSP_CONFIG_DISCOVERY_CACHE_ENDPOINTS EZSP_CONFIG_DISCOVERY_CACHE_ENTRY_SIZE EZSP_CONFIG_DISCOVERY_CACHE_SIZE EZSP_CONFIG_STACK_PROFILE EZSP_CONFIG_SECURITY_LEVEL EZSP_CONFIG_MAX_TREE_DEPTH EZSP_CONFIG_MAX_ROUTER_CHILDREN EZSP_CONFIG_MAX_HOPS EZSP_CONFIG_MAX_END_DEVICE_CHILDREN 42 120-1003-000D The number of packet buffers available to the 0x01 stack. The maximum number of router neighbors the 0x02 stack can keep track of. A neighbor is a node within radio range ...

Page 43

... Enable both boost mode and the alternate 0x03 transmitter output. The command was successful. 0x00 Insufficient memory was available. 0x01 The value was out of bounds. 0x02 The configuration tag was not recognized. 0x03 Configuration values can no longer be modified. 0x04 EM260 120-1003-000D 43 ...

Page 44

... EM260 EzspPolicyId EZSP_TRUST_CENTER_POLICY EZSP_BINDING_MODIFICATION_POLICY EZSP_DATAGRAM_REPLIES_POLICY EZSP_POLL_HANDLER_POLICY EZSP_MESSAGE_CONTENTS_IN_CALLBACK_POLICY 44 120-1003-000D Controls trust center behavior. 0x00 Controls how external binding modification 0x01 requests are handled. Controls whether the Host supplies datagram 0x02 replies. Controls whether 0x03 pollHandler generated. Controls whether the message contents are ...

Page 45

... The EM260 will automatically send an empty reply (containing no payload) for every datagram received. EZSP_DATAGRAM_REPLIES_POLICY decision. The 0x21 EM260 will only send a reply if it receives a command from the Host. sendReply EZSP_POLL_HANDLER_POLICY default decision. 0x30 Do not inform the Host when a child polls. ...

Page 46

... EM260 EmberStatus EMBER_SUCCESS EMBER_ERR_FATAL EMBER_EEPROM_MFG_STACK_VERSION_MISMATCH EM- BER_INCOMPATIBLE_STATIC_MEMORY_DEFINITION S EMBER_EEPROM_MFG_VERSION_MISMATCH EMBER_EEPROM_STACK_VERSION_MISMATCH EMBER_NO_BUFFERS EMBER_SERIAL_INVALID_BAUD_RATE EMBER_SERIAL_INVALID_PORT EMBER_SERIAL_TX_OVERFLOW EMBER_SERIAL_RX_OVERFLOW EMBER_SERIAL_RX_FRAME_ERROR EMBER_SERIAL_RX_PARITY_ERROR EMBER_SERIAL_RX_EMPTY EMBER_SERIAL_RX_OVERRUN_ERROR EMBER_MAC_TRANSMIT_QUEUE_FULL EMBER_MAC_UNKNOWN_HEADER_TYPE EMBER_MAC_SCANNING EMBER_MAC_NO_DATA EMBER_MAC_JOINED_NETWORK EMBER_MAC_BAD_SCAN_DURATION EMBER_MAC_INCORRECT_SCAN_TYPE EMBER_MAC_INVALID_CHANNEL_MASK EMBER_MAC_COMMAND_TRANSMIT_FAILURE 46 120-1003-000D The generic 'no error' message. 0x00 The generic 'fatal error' message. 0x01 The manufacturing and stack token format in non- ...

Page 47

... Attempt 3 to initialize the Simulated EEPROM has 0x49 failed. This failure means one or both of the tokens TOKEN_MFG_NVDATA_VERSION or TO- KEN_STACK_NVDATA_VERSION were incorrect and the token system failed to properly reload default tokens and reset the Simulated EEPROM. An unknown flash token was specified. 0x4B EM260 as soon as 120-1003-000D 47 ...

Page 48

... EM260 EmberStatus EMBER_ERR_TOKEN_EXISTS EMBER_ERR_TOKEN_INVALID_SIZE EMBER_ERR_TOKEN_READ_ONLY EMBER_ERR_BOOTLOADER_TRAP_TABLE_BAD EMBER_ERR_BOOTLOADER_TRAP_UNKNOWN EMBER_ERR_BOOTLOADER_NO_IMAGE EMBER_TOO_MANY_CONNECTIONS EMBER_CONNECTION_OPEN EMBER_CONNECTION_FAILED EMBER_CONNECTION_CLOSED EMBER_CONNECTION_CLOSING EMBER_DELIVERY_FAILED EMBER_BINDING_INDEX_OUT_OF_RANGE EMBER_INVALID_BINDING_TERMINAL EMBER_INVALID_BINDING_INDEX EMBER_TERMINAL_HAS_MULTIPLE_BINDINGS EMBER_INVALID_CALL EMBER_COST_NOT_KNOWN EMBER_MAX_MESSAGE_LIMIT_REACHED 48 120-1003-000D Could not create new flash token because it 0x4C already exists. An incorrect size was specified when retrieving 0x4D token data. ...

Page 49

... The stack software has completed initialization 0x90 and is ready to send and receive packets over the air. The network is not operating. 0x91 The network has activity pending and should not 0x92 be shut down. The node has not joined a network. 0x93 An attempt to join a network failed. 0x94 EM260 120-1003-000D 49 ...

Page 50

... EM260 EmberStatus EMBER_INVALID_SECURITY_LEVEL EMBER_MOVE_FAILED EMBER_ORPHAN_SCAN_FAILED EMBER_NETWORK_BUSY EMBER_NODEID_INVALID EMBER_INVALID_ENDPOINT EMBER_BINDING_HAS_CHANGED EMBER_CHANNEL_NOT_CALIBRATED EMBER_STACK_AND_HARDWARE_MISMATCH EmberEventUnits EMBER_EVENT_INACTIVE EMBER_EVENT_MS_TIME EMBER_EVENT_QS_TIME EMBER_EVENT_MINUTE_TIME 50 120-1003-000D The chosen security level (the value of EM- 0x95 BER_SECURITY_LEVEL) is not supported by the stack. After moving, a mobile node's attempt to re- 0x96 establish contact with the network failed. ...

Page 51

... The node is an end device joined to a network 0x03 but its parent is not responding. The node is in the process of leaving its current 0x04 network. Datagram. 0x00 Datagram reply. 0x01 Sequenced message. 0x02 Multicast. 0x03 Shared multicast. 0x04 Multicast loopback. 0x05 Unicast. 0x06 Broadcast. 0x07 EM260 120-1003-000D 51 ...

Page 52

... EM260 EmberBindingType EMBER_UNUSED_BINDING EMBER_UNICAST_BINDING EMBER_AGGREGATION_BINDING EMBER_MULTICAST_BINDING EmberUnicastOption EMBER_UNICAST_OPTION_NONE EMBER_UNICAST_OPTION_APS_INDIRECT EMBER_UNICAST_OPTION_HAVE_SOURCE EMBER_UNICAST_OPTION_APS_RETRY EMBER_UNICAST_OPTION_ENABLE_ROUTE_DISCOVERY EMBER_UNICAST_OPTION_FORCE_ROUTE_DISCOVERY EMBER_UNICAST_OPTION_POLL_RESPONSE EmberNetworkScanType EMBER_ENERGY_SCAN EMBER_ACTIVE_SCAN EmberJoinDecision EMBER_HAS_KEY EMBER_SEND_KEY EMBER_DENY_JOIN EMBER_ASK_TRUST_CENTER 52 120-1003-000D A binding that is currently not in use. 0x00 A unicast binding whose 64-bit identifier is the 0x01 destination EUI64. A unicast binding whose 64-bit identifier is the 0x02 aggregator EUI64 ...

Page 53

... Configuration Frames Name: version Description: The command allows the Host to specify the desired EZSP version. This document describes version 1 of the protocol. The response provides information about the firmware running on the EM260. Command Parameters: int8u desiredProtocolVersion Response Parameters: int8u protocolVersion ...

Page 54

... EM260 Name: addEndpoint Description: Configures endpoint information on the EM260. The EM260 does not remember these settings after a reset. Endpoints can be added by the Host after the EM260 has reset. Sending any command other than , version getConfigurationValue longer be added and this command will respond with EZSP_CONFIG_INVALID_CALL. ...

Page 55

... Name: getPolicy Description: Allows the Host to read the policies used by the EM260 to make fast decisions. Command Parameters: EzspPolicyId policyId Response Parameters: EzspConfigStatus status EzspDecisionId decisionId 6.3.5 Utilities Frames Name: nop Description: A transaction which does nothing. The Host can use this to set the sleep mode or to check the status of the EM260 ...

Page 56

... Description: Sets a token (8 bytes of non-volatile storage) in the Simulated EEPROM of the EM260. Command Parameters: int8u tokenId int8u[8] tokenData Response Parameters: EmberStatus status Name: getToken Description: Retrieves a token (8 bytes of non-volatile storage) from the Simulated EEPROM of the EM260. Command Parameters: int8u tokenId Response Parameters: EmberStatus status int8u[8] tokenData Name: getMfgToken Description: Retrieves a manufacturing token (8 bytes of non-volatile storage) from the Flash Information Area of the EM260 ...

Page 57

... Name: setRam Description: Writes data supplied by the Host to RAM in the EM260. The amount of RAM available for use by the Host must be set using the setConfigurationValue Command Parameters: int8u startIndex int8u dataLength int8u[] data Response Parameters: EmberStatus status Name: getRam Description: Reads data from RAM in the EM260 and returns it to the Host. ...

Page 58

... EM260 Name: setTimer Description: Sets a timer on the EM260. There are 2 independent timers available for use by the Host. A timer can be cancelled by setting Command Parameters: int8u timerId int16u time EmberEventUnits units boolean repeat Response Parameters: EmberStatus status Name: getTimer Description: Gets information about a timer. The Host can use this command to find out how much longer it will be before a previously set timer will generate a callback ...

Page 59

... Description: Sends a serial message from the Host to the InSight debug system via the EM260. Command Parameters: int8u messageLength int8u[] messageContents Response Parameters: EmberStatus status Name: serialRead Description: Allows the Host to read a serial message from the InSight debug system via the EM260. Command Parameters: int8u length Response Parameters: int8u messageLength int8u[] messageContents Name: debugWrite Description: Sends a debug message from the Host to the InSight debug system via the EM260 ...

Page 60

... Name: startChannelCalibration Description: Start calibrating the specified channel. The calibration process takes several seconds to com- plete and the EM260 will be unresponsive until it is complete. The Host must not send another command until the EM260 indicates that calibration is complete, using the Command Parameters: ...

Page 61

... ID: 0x15 The manufacturer code for the local node. ID: 0x16 The new power descriptor for the local node. ID: 0x17 An EmberStatus value that indicates one of the following: suc- cessful initialization, EMBER_NOT_JOINED if the node is not part of a network, or the reason for failure. EM260 120-1003-000D 61 ...

Page 62

... EM260 Name: networkState Description: Returns a value indicating whether the node is joining, joined to, or leaving a network. Command Parameters: None Response Parameters: EmberNetworkStatus status Name: stackStatusHandler Description: A callback invoked when the status of the stack changes. If the status parameter equals EM- BER_NETWORK_UP, then the parameters. If any of the parameters are being stored in nonvolatile memory by the Host, the stored values should be updated ...

Page 63

... The channel on which the current error occurred. Undefined for the case of EMBER_SUCCESS. The error condition that occurred on the current channel. Value will be EMBER_SUCCESS when the scan has completed. ID: 0x1D An EmberStatus value indicating success or the reason for fail- ure. EM260 120-1003-000D 63 ...

Page 64

... EM260 Name: formNetwork Description: Forms a new network by becoming the coordinator. Command Parameters: EmberNetworkParameters parameters Response Parameters: EmberStatus status Name: joinNetwork Description: Causes the stack to associate with the network using the specified network parameters. It can take several seconds for the stack to associate with the local network. Do not send messages until the ...

Page 65

... Some networks use unsecured joining and distribute the key from the coordinator. Other networks require secure joining and accept only nodes that know the correct key. This value has no effect if the security level is 0. EM260 stack- command. 120-1003-000D 65 ...

Page 66

... EM260 Name: scanErrorHandler Description: This callback is invoked if an error occurs while attempting to . JoinNetwork This frame is a response to the Response Parameters: EmberStatus status Name: leaveNetwork Description: Causes the stack to leave the current network. This generates a indicate that the network is down. The radio will not be used until after sending a command ...

Page 67

... EmberEUI64 childEui64 EmberNodeType childType Name: trustCenterJoinHandler Description: The EM260 used the trust center behavior policy to decide whether to allow a new node to join the network. The Host cannot change the current decision, but it can change the policy for future decisions using the command. ...

Page 68

... EM260 Name: getNodeId Description: Returns the 16-bit node ID of the local node. Command Parameters: None Response Parameters: EmberNodeId nodeId Name: getNetworkParameters Description: Returns the current network parameters. Command Parameters: None Response Parameters: EmberStatus status EmberNodeType nodeType EmberNetworkParameters parameters Name: getParentChildParameters Description: Returns information about the children of the local node and the parent of the local node. ...

Page 69

... The EmberNodeType value for the child. ID: 0x2A An EmberStatus value indicating success or the reason for fail- ure. ID: 0x2B The index of a binding table entry. The contents of the binding entry. An EmberStatus value indicating success or the reason for fail- ure. EM260 . EMBER_NOT_JOINED index 120-1003-000D 69 ...

Page 70

... EM260 Name: getBinding Description: Gets an entry from the binding table. Command Parameters: int8u index Response Parameters: EmberStatus status EmberBindingTableEntry value Name: deleteBinding Description: Deletes a binding table entry. Command Parameters: int8u index Response Parameters: EmberStatus status Name: bindingIsActive Description: Indicates whether a binding table entry is active - that is, whether a connection open or any messages are en route from it ...

Page 71

... EmberNodeId nodeId Response Parameters: None Name: remoteSetBindingHandler Description: The EM260 used the external binding modification policy to decide how to handle a remote set binding request. The Host cannot change the current decision, but it can change the policy for future deci- sions using the command ...

Page 72

... EM260 Name: remoteDeleteBindingHandler Description: The EM260 used the external binding modification policy to decide how to handle a remote delete binding request. The Host cannot change the current decision, but it can change the policy for future decisions using the This frame is a response to the ...

Page 73

... ID: 0x36 The APS frame for the message. The message will be delivered to all nodes within the sender. A radius of zero is converted to EMBER_MAX_HOPS. Reserved for future use. This value is ignored by the EM260. The length of the messageContents The broadcast message. An EmberStatus value indicating success or the reason for fail- ure ...

Page 74

... EM260 Name: sendDatagram Description: Sends a datagram to the node and endpoint specified in a binding table entry. The status of the delivery will be reported by a Command Parameters: int8u bindingTableIndex int8u clusterId int8u messageTag int8u messageLength int8u[] messageContents Response Parameters: EmberStatus status 74 120-1003-000D ID: 0x37 callback. ...

Page 75

... ID: 0x38 The index of the binding table entry specifying the multicast group. The cluster ID to use. Reserved for future use. This value is ignored by the EM260. The message will be delivered to all nodes within this number of hops of the sender. A value of zero is converted to EM- BER_MAX_HOPS. ...

Page 76

... EM260 Name: openConnection Description: Opens a sequenced connection to a node. Command Parameters: int8u bindingTableIndex Response Parameters: EmberStatus status Name: connectionStatus Description: Returns the connection status of a binding table entry. Command Parameters: int8u bindingTableIndex Response Parameters: EmberStatus status 76 120-1003-000D ID: 0x3A The index of the binding table entry to which a connection will be opened ...

Page 77

... This error may be reported during the opening of a connection, while a connection is established or during the closing of a connection. EM- BER_INCOMING_SEQUENCED_MESSAGES_LOST - One or more sequenced messages have not been received on the connection and it has been determined they will never be received. EM260 120-1003-000D 77 ...

Page 78

... EM260 Name: sendSequenced Description: Sends a sequenced message over the connection associated with a specified binding table entry. Command Parameters: int8u bindingTableIndex int8u clusterId int8u messageTag int8u messageLength int8u[] messageContents Response Parameters: EmberStatus status Name: closeConnection Description: Closes a connection. Any sequenced messages previously sent on the connection will be delivered before the connection is closed ...

Page 79

... ID: 0x40 The value supplied by the Host in the command. emberSendSequenced Always returns EMBER_SUCCESS. ID: 0x41 EMBER_SUCCESS if the route request was successfully submitted to the transmit queue, and EMBER_ERR_FATAL otherwise. EM260 or emberSendDatagram parameter in bytes. messageCon emberSendDatagram 120-1003-000D 79 ...

Page 80

... EM260 Name: pollForData Description: Periodically request any pending data from our parent. Setting BER_EVENT_INACTIVE will generate a single poll. Command Parameters: int16u interval EmberEventUnits units int8u failureLimit Response Parameters: EmberStatus status Name: pollCompleteHandler Description: Indicates the result of a data poll to the parent of the local node. ...

Page 81

... The index of a binding that matches the message or 0xFF if there is no matching binding. If the incoming message is a datagram and the Host wishes to send a reply, this value must be supplied to the command. The length of the messageContents The incoming message. EM260 emberSendReply parameter in bytes. 120-1003-000D 81 ...

Page 82

... EM260 6.3.9 Alphabetical List of Frames Frame Name addEndpoint bindingIsActive calibrationCompleteHandler callback cancelMessage channelCalibrated childJoinHandler clearBindingTable closeConnection connectionStatus connectionStatusHandler createAggregationRoutes debugHandler debugWrite deleteBinding energyScanResultHandler formNetwork getBinding getBindingDestinationNodeId getChildData getConfigurationValue getEui64 getMfgToken getMillisecondTime getNetworkParameters getNodeId getParentChildParameters getPolicy getRam getRandomNumber getTimer getToken incomingMessageHandler invalidCommand ...

Page 83

... ID 0x1F 0x20 0x33 0x3F 0x21 0x1B 0x17 0x18 0x07 0x05 0x3A 0x22 0x43 0x42 0x44 0x32 0x31 0x08 0x4F 0x50 0x1C 0x51 0x36 0x37 0x25 0x38 0x39 0x3D 0x34 0x11 0x10 0x2B 0x30 0x53 0x14 EM260 120-1003-000D 83 ...

Page 84

... Sending Receiving 6.4.1 Joining 1) frame control joinNetwork command = 0x1F nodeType panId radioTxPower radioChannel useKey HOST -> EM260 frame control joinNetwork response = 0x1F status EM260 -> HOST Host waits for callback signal while EM260 tries to join the network. 3) frame control callback command = 0x06 84 120-1003-000D ...

Page 85

... HOST -> EM260 frame control = 0x80 (response frame, no overflow, not truncated) setBinding response = 0x2B status = 0x00 (EMBER_SUCCESS) EM260 -> HOST 6.4.3 Sending 1) frame control = 0x00 (command frame, don't sleep) ...

Page 86

... EM260 -> HOST 120-1003-000D = 0x00 (command frame, don't sleep) = 0x80 (response frame, no overflow, not truncated) = 0x00 (EMBER_INCOMING_DATAGRAM) = 0xABCD = 0x55 = 0x11 = 0x12 = 0x00 = 0xF0 = 0xC4 (-60) = 0x0001 = 0xFF ...

Page 87

... SIF_MOSI SIF_MISO Because the SIF module directly connects to the program and data memory buses within the EM260, it has access to the entire Flash and RAM blocks, as well as the on-chip registers. The maximum serial shift speed for the SIF interface is 48MHz. SIF interface accesses can be initiated even when the chip is in idle and deep sleep modes ...

Page 88

... EM260 8 Typical Application Figure 12 illustrates the typical application circuit for the EM260. This figure does not contain all decoupling capacitance required by the EM260. The Balun provides the impedance transformation from the antenna to the EM250 for both TX and RX modes. The harmonic filter provides additional suppression of the second harmonic, which increases the margin over the FCC limit ...

Page 89

... RESISTOR, 169 KOHM, 1%, 0402 RESISTOR, 100 KOHM, 5% O402 RESISTOR, 3.3 KOHM, 5% 0402 RESISTOR, 10 KOHM, 5%, 0402 EM260 SINGLE-CHIP ZIGBEE/802.15.4 SOLUTION CRYSTAL, 24.000MHZ, +/- 10PPM TOLERANCE, +/- 25PPM STABILITY, 18PF 85C 14 1 BLN1 BALUN, CERAMIC Table 23. Bill of Materials Manufacturer/Part No. <not specified> <not specified> <not specified> <not specified> ...

Page 90

... EM260 9 Mechanical Details The EM260 package is a plastic 40-pin QFN that is 6mm x 6mm x 0.9mm. A large ground pad in the bottom center of the package forms a 41 PCB ground plane. For more information, refer to the EM260 Reference Design. Figure 13 illustrates the package drawing. Top View ...

Page 91

... Ordering Information Use the following part numbers to order the EM260: EM260-RTR Reel, RoHS EM260-RTY Tray, RoHS To order parts, contact Ember at +1-617-951-0200, or send your inquiry by email to sales@ember.com. Details about our international distributors can be found on our Web site: www.ember.com. EM260 120-1003-000D 91 ...

Page 92

... EM260 11 Abbreviations and Acronyms Acronym/Abbreviation Meaning ACR Adjacent Channel Rejection AES Advanced Encryption Standard CBC-MAC Cipher Block Chaining—Message Authentication Code CCA Clear Channel Assessment CCM Counter with CBC-MAC Mode for AES encryption CCM* Improved Counter with CBC-MAC Mode for AES encryption ...

Page 93

... PTI Packet Trace Interface PWM Pulse Width Modulation RoHS Restriction of Hazardous Substances RSSI Receive Signal Strength Indicator SFD Start Frame Delimiter SIF Serial Interface SPI Serial Peripheral Interface UART Universal Asynchronous Receiver/Transmitter VCO Voltage Controlled Oscillator VDD Voltage Supply EM260 120-1003-000D 93 ...

Page 94

... Bluetooth Specification v1.2 (www.bluetooth.org/spec) 3. ZigBee Specification v1.1 (www.zigbee.org; document number 053474r07) 4. ZigBee Security Services Specification v1.0 (document number 03322r13) 5. Ember EM260 Reference Design (www.ember.com) © 2006 Ember Corporation. All rights reserved. The information in this document is subject to change without notice. This document is believed to be accu- rate and reliable, but the statements contained herein are presented without express or implied warranty ...

Related keywords