xIDE

This document discusses the typical steps in starting a debugging session for an EM250 application.

As always, make sure that the Insight Adapter is connected to the network and that all connectors are firmly attached.

1. Be sure that the Emulator setting in the build options for your project target point to the current IP address of the InSight Adapter [ISA] you’re going to be using for the debug session.
2. Change the preprocessor options to add DISABLE_WATCHDOG.

This article explains various techniques for minimizing flash memory consumption for EmberZNet applications developed on the EM250 platform.

NOTE1: This How-To article describes Flash memory conservation techniques. If it is RAM you are concerned about, there are a number of configuration parameters that are variable by the application’s CONFIGURATION_HEADER file and can affect the amount of static memory used by the EmberZNet stack. Please consult the Reducing RAM usage on the EM250 article.

NOTE: All of the issues below are fixed in xIDE 2.1.1.

Problem: Auto-discovery of InSight Adapters (“ISAs” or “SIF Pods”) by TCP broadcast doesn’t detect any adapters.*
Tracked by Ember as: Case 10603
Workaround: Add the ISA manually by specifying its IP address or hostname (if you have an /etc/hosts alias or a DNS server entry to resolve the hostname automatically to an IP).

If xIDE refuses to start the IDE and instead reports an error dialog explaining that it was unable to locate your license file, this is usually a sign that either your license is not in the correct folder or has expired. As far as troubleshooting the first of these two causes:

• The expected location for the license file is in the “licence” (note the British spelling) subdirectory of the folder where “xIDE for EM250” was installed. By default, this installation is rooted at C:\Program Files\Ember\xIDE_EM250, but you may have changed it to a custom location during installation.

NOTE: This FAQ is written circa EmberZNet 3.3.0. As you read this, keep in mind that if you are referencing a future or past version of EmberZNet, libraries offered and their exact naming conventions may be slightly different.

As EM250 users will note, in the “build” subdirectory of the EmberZNet installation, there are a number of supplied libraries, each with their own subdirectory (with a “library” substring) containing the *.xap library file. Most of these libraries come in a couple of varieties, indicated by these suffixes:

The XAP2b architecture doesn’t really have “libraries” in the traditional sense, since the “object” code produced by the compiler is really just assembly code, and the “linkage” that occurs is

Because xIDE for EM250 is a development toolchain consisting of compiler, linker, assembler, deadstripper, and other components, each with their own version.

Alarm Messages

Alarm messages are stored for an unlimited time by the parent in dedicated memory for delivery to a hibernating sleepy child.

Alarm messages can be unicast or broadcast with the following APS data (defined in ember-types.h):

• Profile ID: EMBER_PRIVATE_PROFILE_ID.
• Endpoint: the source and destination endpoints are ignored.
• Cluster ID: EMBER_BROADCAST_ALARM_CLUSTER, EMBER_UNICAST_ALARM_CLUSTER, or EMBER_CACHED_UNICAST_ALARM_CLUSTER