User Manual

XBee®/XBee‐PRO®ZBRFModules
©2011DigiInternational,Inc. 140
SIF Firmware Updates
The XBee/XBee-PRO modules have a 2x5 SIF header that can be used with Ember's InSight tools to upload
firmware onto the modules. These tools include a USB device (USBLink) and Ethernet-enabled InSight Adapters.
Contact Ember for details.
Warning: If programming firmware through the SIF interface, be aware that uploading firmware through the
SIF header can potentially erase the XBee bootloader. If this happens, serial firmware updates will not work.
(The pinout for the SIF headers are shown in chapter 1.)
Writing Custom Firmware
The XBee/XBee-PRO module can be used as a hardware development platform for the EM250. Custom firmware
images can be developed around the EmberZNet 2.5.x and 3.x mesh stacks (for the EM250) and uploaded to the
XBee.
Warning: If programming firmware through the SIF interface, be aware that uploading firmware through the SIF
header can potentially erase the XBee bootloader. If this happens, serial firmware updates will not work.
Regulatory Compliance
XBee modules are FCC and ETSI certified for operation on all 16 channels. The EM250 output power can be
configured up to 3dBm with boost mode enabled.
XBee-PRO modules are certified for operation on 14 of the 16 band channels (channels 11 - 24). The scan
channels mask of XBee-PRO devices must be set in the application to disable the upper two channels (e.g.
0x01FFF800). The XBee-PRO contains power compensation circuitry to adjust the output power near 18dBm or
10dBm depending on the part number. For best results, the EM250 should be configured with an output power
level of 0dBm (or -2dBm if boost mode is enabled). The end product is responsible to adhere to these
requirements.
0x23
The bootloader encountered an error while
trying to parse the high byte of the CRC in the
XModem frame.
0x24
The bootloader encountered an error while
trying to parse the low byte of the CRC in the
XModem frame.
0x25
The bootloader encountered an error in the
sequence number of the current XModem
frame.
0x26
The frame that the bootloader was trying to
parse was deemed incomplete (some bytes
missing or lost).
0x27
The bootloader encountered a duplicate of the
previous XModem frame.
0x41 No .ebl header was received when expected.
0x42 Header failed CRC.
0x43 File failed CRC.
0x44 Unknown tag detected in .ebl image.
0x45 Invalid .ebl header signature.
0x46 Trying to flash odd number of bytes.
0x47 Indexed past end of block buffer.
0x48 Attempt to overwrite bootloader flash.
0x49 Attempt to overwrite SIMEE flash.
0x4A Flash erase failed.
0x4B Flash write failed.
0x4C End tag CRC wrong length.
0x4D Received data before query request/response
Hex Error Code Description