EM260-RTR Ember, EM260-RTR Datasheet - Page 18

• 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

EM260
4.7
4.8
4.9
18
Encryption Accelerator
Reset Detection
Power-on-Reset (POR)
120-1003-000D
Conversely, if for every 9 times the nonce counter is set (36,864 messages have been sent) an App token is set
once. A very rough estimate for the total number of times the App token can bet set is approximately 80,000.
These estimates would typically increase if the EM260 is kept closer to room temperature, since the 1,000
guaranteed write cycles of the Flash is for across temperature.
4.6.3
The EM260 also includes a separate 1024-byte FIA that can be used for storage of data during manufacturing,
including serial numbers and calibration values. This area is mapped to the data side of the address space.
While this area can be read as individual bytes, it can only be written to one word at a time, and may only be
erased as a whole. Programming of this special Flash page can only be enabled using the SIF interface to
prevent accidental corruption or erasure. The EmberZNet stack reserves a small portion of this space for its
own use, but the rest is available to the application. See section 6.2.6, Tokens, for more information.
4.6.4
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. Read access is always allowed to the entire RAM,
and full access is always allowed when the EM260 is running in System Mode. The EmberZNet stack intelli-
gently manages this protection mechanism to assist in tracking down many common application errors.
4.6.5
The registers are mapped to the data-side address space. These registers allow for the control and configura-
tion of the various peripherals and modules. There are additional registers used by the EmberZNet stack when
the EM260 is running in System Mode, allowing for control of the MAC, baseband, and other internal modules.
These system registers are protected from being modified when the EM260 is running in Application Mode.
The EM260 contains a hardware AES encryption engine that is attached to the CPU using a memory-mapped
interface. NIST-based CCM, CCM*, CBC-MAC, and CTR modes are implemented in hardware. These modes are
described in the IEEE 802.15.4-2003 specification, with the exception of CCM*, which is described in the
ZigBee Security Services Specification 1.0. The EmberZNet stack implements a security API for applications
that require security at the application level.
The EM260 contains multiple reset sources. The reset event is logged into the reset source register, which lets
the CPU determine the cause of the last reset. The following reset causes are detected:
Each voltage domain (1.8V Digital Core Supply VDD_CORE and Pads Supply VDD_PADS) has a power-on-reset
(POR) cell.
Power-on-Reset
Watchdog
PC rollover
Software reset
Core Power Dip
Flash Information Area (FIA)
RAM
Registers