Skip to Navigation
Home
  • Company
    • Quick Facts
    • Board of Directors
    • Management Team
    • Press Releases
    • News Coverage
    • Newsletter
    • Careers
    • Articles
    • Ember Chronology
    • Contact Us
  • Products
    • ZigBee Chips
    • ZigBee Software
    • ZigBee Development Tools
    • Documentation
  • Buy
    • Digi-Key (Online)
    • Distributors
  • Applications
    • AMI & AMR
    • Integrated Home Automation
    • Building Automation
    • Others
  • ZigBee
    • About ZigBee
    • Ember & ZigBee
    • ZigBee FAQ
    • Download Specifications
    • ZigBee Events
  • Partners
  • Support
    • Training
  • Events
Home › FAQs

Tools : ISD, ISA FAQs

All Frequently Asked Questions (FAQs), organized by category.

Click "here":http://portal.ember.com/faq/new to view only the most recent entries.

Where can I download the latest release of InSight Desktop, xIDE, or the EmberZNet stack?

All official software releases and documentation are available from the software area of this web site.

All developers who have a current maintenance contract (depending on your purchase details) should have access. If you do not have access to this area of the site please contact your FAE, sales representative, or distributor.

Why does port 4901 on the InSight Adapter show bad data?

When connected to the InSight Adapter via telnet to port 4901, but my prints and the EM250 answers are gibberish, just like you get when you are connected with the wrong baud rate. How do I change the baud rate?

Try first:

You must configure the InSight Adapter baud rate to match the baud rate configured in the application -- this is because the InSight Adapter is just a translator between serial and telnet.
How do I compile my EM250 application with the debug stack?

Note: this topic is also covered in application note 5018.

In order to compile an EM250 application with the debug stack, you need to do the following items:

How to decode EmberNet files in InSight Desktop? Why is my EmberNet trace file no longer readable in InSight Desktop?

The basic problem is that InSight Desktop files store information about the type of network being decoded. In ISD versions prior to 1.1.4, this information was not always stored correctly. Fortunately, there is an identified workaround to the problem. If you find that an EmberNet file will not properly decode in InSight Desktop, try the following steps:

 

1) Unzip the trace file (.wb or .isd). You may need to change the file extension to .zip so that Windows can properly handle the file type.

Where can I find the USB driver I need to access the settings on my Insight Adapter via USB cable?
Where can I find the USB driver I need to access the settings on my Insight Adapter via USB cable?

The Insight Adapter USB driver is not shipped with the Development Kit or the Jump Start Kit.  It can be found on FTDI's website at http://www.ftdichip.com/Drivers/VCP.htm.

This USB driver is required when using the USB port on the Insight Adapter to access the administrative port.

How do I make the USB driver choose a lower com port?

For development with the EM260 serial, I am using Cygwin for my host. As I plug in my USB to serial device, it keeps showing up at an increasingly higher COM port. How do I clean out the old COM port information?

From your Windows machine, begin the regedit program (start->run->regedit). Search for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Ports and clean out all the lower COM port entries.

In the InSight Desktop transactions pane, what do P#, M#, and E# refer to?

In the InSight Desktop transactions pane, what do P#, M#, and E# refer to?

P# refers to the total number of transmissions, including 802.15.4 layer ACKs, in the transaction.

M# refers to the total number of MAC and NWK layer retries.

E# refers to the total number of end to end retries.

Note that the retries do not include the original packet. So, if an APS message is sent one hop away and that node has been removed from the network, E# + M# + 1 (for the original transmission) = P#.

Solving general programming/connection problems with the SIF Adapter / ISA
I am having trouble programming my EM250/EM260 with an ISA, what can I do? I am having trouble connecting to my EM250/EM260 with my ISA, how do I resolve this? I am seeing that the SIF shift register is not functioning correctly. What can I do?

 

InSight Desktop is having a hard time discovering my InSight Adapters. What can I try?

I just installed InSight Desktop on my PC and my InSight Adapters seem to be working, but I can't see any of my InSight Adapters. Why? I used to be able to discover my InSight Adapters, but for some reason, I can no longer discover them. What is the issue?

With regard to discovering your adapters, some things to try:

Why does App builder show 112kB as maximum flash available?

Total flash space of em250 is 128kB. However, a fixed block of 8kB flash is used by Simulated EEPROM, and 8kB is reserved for DATA segment storage, so total flash available for CODE segments, as shown in App builder, is 112kB.

Why does my firmware upload to an Ember chip sometimes hang at 0% or finish and do nothing?

When using InSight Desktop , you may notice the upload progress bar stalled at 0% during an upload of firmware to an Ember device, or perhaps that the upload succeeded but the chip is not responsive in any way (not even a NodeInfo trace when capture is started).

Why do I keep getting " CRC Failed " status in InSight Desktop captures?

CRC failures can occur for a few reasons, such as:

Received a packet that had bit errors, so CRC did not pass
Solution: Not much you can do here, since bit errors are a natural occurrence when there is excessive noise or very weak signals or frequent packet collisions on the medium.

What TCP/UDP ports are required for the InSight Adapter to operate with InSight Desktop?

For customers that wish to access InSight Desktop (ISD) or InSight Adapter (ISA) functionality through a firewall it is important to make sure that all required TCP/UDP ports are open for communications.

Where is the RFEval plugin in ISD 2.0? How should I perform RF Evaluation testing?

The RFEval plugin of InSight Desktop was removed as of InSight Desktop 2.0 for several reasons:

  • It did not meet Ember’s standards for quality
  • The plugin was designed for use with Ember’s RF Evaluation Kit (which has been discontinued) rather than the development kit hardware.
  • The plugin tests only MAC layer functionality, which is not representative of the performance achieved in a multi-hop, mesh network.

For evaluating RF performance in ZigBee networks, please use the new and improved RF Evaluation Firmware, designed by Ember partner Global Edge Software (GES), which can be f

Why does em2xx_load (or em2USBLoad) keep saying "Shift Register All 0's" or "LOADB stuck low"?

At times customers have reported seeing unexpected output from the EM2xx Utilities (em2xx_load/patch/read) or their EM2USB counterparts, where the output contains a repeated message like:

 XAP2= DbgEna Shift register is all 0's
 XAP2= Stop Shift register is all 0's
 XAP2= DbgEna Shift register is all 0's
 XAP2= Reset Shift register is all 0's
Shift register is all 0's
Shift register is all 0's
Shift register is all 0's

…or something like this:

 XAP2= DbgEna LOADB stuck low
 XAP2= Stop LOADB stuck low
 XAP2= Reset LOADB stuck low
 XAP2= Issuing SW_RESET

Why can't I get any serial data in/out of InSight Desktop Console's Serial 1 tab?

The functionality of the serial stream on the Serial 1 tab has some hardware and software dependencies on the embedded side, so while you may suspect problems on the PC side, your computer’s setup probably doesn’t have anything to do with the problems in this case…

In order to use the Serial 1 tab through InSight Desktop Console, the following steps must be met (no specific order):

  • Firmware running on Ember node needs to be built with serial driver support (app/util/serial/serial.c) and Serial Port 1 should be initialized (via emberSerialInit()) in the software.
  • Firmware on node
Can I use the ISA3 (for EM35x) with EM250 / EM260 chips? What about the original ISA and EM35x chips?

As the interfaces and pinouts and protocols are quite different between
the EM2xx chipset (which uses the 16-bit XAP2b architecture and the proprietary SIF debug/programming protocol from CCL) and the EM3xx chipset (which uses the 32-bit ARM Cortex-M3 architecture and the more standardized JTAG and SerialWire debug/programming protocols), there’s no compatibility (in either direction) between the development tools from one
platform and the devices/chips from the other platform.

Currently, the ISA3 (EM3xx-era ISA) is the only device that can be used to program
EM3xx chips, and the ISA [

Where is the EUI64 stored on the device? How can I read or set the current EUI64 of a device?


What is the description of the fields in the Radio Info EM250 event detail in InSight Desktop?

The RadioInfoEM250 fields, used with the EM250 and EM260 chips, break down as follows:

  • CRC: The 16-bit CRC (cyclical redundancy check) checksum for the received packet. This is used to detect bit errors in the reception. The value here is the actual CRC calculated by the receiver radio, which replaces the CRC appended by the transmitter, and if the values are equal then the “CRC Pass” flag is marked true.
  • Raw LQI: The raw (unconverted) LQI data about the received packet. This is measured by the receiver and appended to the packet data as part of the reception process.

Search

FAQs

  • All (166)
  • Software : Embedded (65)
  • Software : Networking (70)
  • Hardware : Design (22)
  • Hardware : Manufacturing (10)
  • Tools : Dev Boards (2)
  • Tools : ISD, ISA (21)
  • Tools : xIDE (6)
  • Tools : Other (7)
  • ZigBee (1)
  • Change Notification (0)
Primary links
  • Developer Blog
  • Documentation
    • Release Notes
  • Contributed Software
  • FAQs
  • Change Notifications
  • Training
Portal
  • My Account
  • Search
User login
  • Request new password

Company | Products | Buy | Applications | ZigBee | Partners | Support | Events | Contact Us

©2007-2008 Ember Corporation | All rights reserved | Privacy