Home

EmberZNet

How does the emberSetEncryptionKey() function work?

Categories:

The emberSetEncryptionKey() function just sets the EEPROM token for the 128-bit key used for AES encrytion & decryption of data.  This value is loaded into the radio's registers so that it can be used by the hardware encrypt/decrypt engine to enforce security on incoming/outgoing packets.  The function takes a 16-byte array, which corresponds to the 128-bit shared network key in use.   Messages that don't match this key will be discarded by the radio.

How to use the ZigBee Device Object (ZDO)

Categories:

The ZDO (occupying Endpoint 0 of each node) is a stack-level entity defined by the ZigBee Networking Specification for use in network management and information gathering. This document explains how to make use of ZDO functionality in the EmberZNet stack and/or EZSP. An example is described as well.

How is the child table updated/managed?

Categories:
Who will/can remove old/unnecessary entries in a child table. When a sleepy end device executes emberNetworkLeave(), will the stack of its parent router node remove the entry for the device in the child table automatically? If the end device is gone without emberNetworkLeave(), will the parent node keep the entry forever or discard it with time-out? Or can/must the application program on the parent router node remove old/unnecessary entries in a child table?

Using the Simulated EEPROM

Categories:

This document describes how to use the Simulated EEPROM in the EM250, gives an overview of the internal design, and discusses design considerations. Revision E.

Attachment: 
application/pdf icon
120-5037-000_Simulated_EEPROM.pdf
« first‹ previous12
Syndicate content