Digi International Inc XBEEPRO2 Manual Do Utilizador
XBee®/XBee‐PRO® ZB RF Modules
© 2011 Digi International, Inc.
141
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.
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.
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.
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.
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.
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.
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.
Enabling GPIO 1 and 2
Most of the remaining sections in this chapter describe how to configure GPIO 1 and 2 to function correctly in
custom applications that run on the XBee and XBee-PRO modules. In order for GPIO pins 1 and 2 to be
configurable, the application must set the GPIO_CFG register to enable GPIO 1 and 2. Bits 4 - 7 in the
GPIO_CFG register control the functionality of various GPIO lines. The following table lists values for these bits
that enable GPIO 1 and 2. Other functionality is affected by these settings. See the EM250 datasheet from
Ember for a complete listing of functionality.
custom applications that run on the XBee and XBee-PRO modules. In order for GPIO pins 1 and 2 to be
configurable, the application must set the GPIO_CFG register to enable GPIO 1 and 2. Bits 4 - 7 in the
GPIO_CFG register control the functionality of various GPIO lines. The following table lists values for these bits
that enable GPIO 1 and 2. Other functionality is affected by these settings. See the EM250 datasheet from
Ember for a complete listing of functionality.
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