EM250-JMP-R Ember, EM250-JMP-R Datasheet - Page 22
![KIT JUMP START FOR EM250](/photos/14/10/141062/em250-jmp_board_1_sml.jpg)
EM250-JMP-R
Manufacturer Part Number
EM250-JMP-R
Description
KIT JUMP START FOR EM250
Manufacturer
Ember
Series
JumpStartr
Type
802.15.4/Zigbeer
Specifications of EM250-JMP-R
Frequency
2.4GHz
For Use With/related Products
EM250
Lead Free Status / RoHS Status
Contains lead / RoHS non-compliant
Other names
636-1001
EM250-JMP
EM250-JSK
EM250-JMP
EM250-JSK
EM250
4.7
22
Encryption Accelerator
120-0082-000I
4.6.2
The Ember stack reserves a section of Flash memory to provide Simulated EEPROM storage area for stack and
customer tokens. Therefore, the EM250 utilizes 8kB of upper Flash storage. This section of Flash is only acces-
sible when mapped to the Flash window in the data-side address space. Because the Flash cells are qualified
for up to 1,000 write cycles, the Simulated EEPROM implements an effective wear-leveling algorithm which ef-
fectively extends the number of write cycles for individual tokens.
4.6.3
The EM250 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,
starting at address 0x5000. 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 us-
ing the SIF interface to prevent accidental corruption or erasure. The EmberZNet stack reserves a small por-
tion of this space for its own use, but the rest is available to the application.
4.6.4
The EM250 integrates 5kB of SRAM. Like the Flash memory, this RAM is also mapped to both the program and
data-side address spaces. On the program side, the RAM is mapped to the top 2.5k words of the program ad-
dress space. The program-side mapping of the RAM is used for code when writing to or erasing the Flash mem-
ory. On the data side, the RAM is also mapped to the top of the address space, occupying the last 5kB, as
shown in Figure 3 and Figure 4.
Additionally, the EM250 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 EM250 is running in Application Mode. Read access is always al-
lowed to the entire RAM, and full access is always allowed when the EM250 is running in System Mode. The
EmberZNet stack intelligently manages this protection mechanism to assist in tracking down many common
application errors.
4.6.5
Table 40 provides a short description of all application-accessible registers within the EM250. Complete de-
scriptions are provided at the end of each applicable Functional Description section. The registers are mapped
to the data-side address space starting at address 0x4000. These registers allow for the control and configura-
tion of the various peripherals and modules. The registers may only be accessed as whole word quantities; at-
tempts to access them as bytes may result in undefined behavior. There are additional registers used by the
EmberZNet stack when the EM250 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 EM250 is running
in Application Mode.
The EM250 contains a hardware AES encryption engine that is attached to the CPU using a memory-mapped in-
terface. NIST-based CCM, CCM*, CBC-MAC, and CTR modes are implemented in hardware. These modes are de-
scribed 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 re-
quire security at the application level.
Simulated EEPROM
Flash Information Area (FIA)
RAM
Registers