XBee‐PRO®900HP/XBee‐PRO®XSCRFModules
©2014DigiInternationalInc. 92
Verifying the New Application
For an uploaded application to function correctly every single byte from the .ebin file must be properly
transferred to the GPM. To guarantee that this is the case GPM VERIFY functions exist to ensure that all bytes
are properly in place. The FIRMWARE_VERIFY function reports whether or not the uploaded data is valid. The
FIRMWARE_VERIFY_AND_INSTALL command will report if the uploaded data is invalid. If the data is valid it
will begin installing the application. No installation will take place on invalid data.
Installing the Application
When the entire .ebin file has been uploaded to the GPM of the target node a
FIRMWARE_VERIFY_AND_INSTALL command can be issued. Once the target receives the command it will
verify the .ebin file loaded in the GPM. If it is found to be valid then the module will install the new firmware.
This installation process can take up to 8 seconds. During the installation the module will be unresponsive to
both serial and RF communication. To complete the installation the target module will reset. AT parameter
settings which have not been written to flash (using the WR command) will be lost.
Things to Remember
• The firmware upgrade process requires that the module resets itself. Because of this reset
parameters which have not been written to flash will be lost after the reset. To avoid this,
write all parameters with the WR command before doing a firmware upgrade. Packet routing
information will also be lost after this reset. Route discoveries will be necessary for DigiMesh
unicasts involving the upgraded node as a source, destination, or intermediate node.
• Because explicit API Tx frames can be addressed to a local node (accessible via the SPI or
UART) or a remote node (accessible over the RF port) the same process can be used to update
firmware on a module in either case.
0
384 128 384 to 511
1
0 128 512 to 639
1
128 128 640 to 767
-
---
-
---
-
---
107
0 54784 to 54911
107
128 54912 to 55039
107
256 101 55040 to 55140
GPM_BLOCK_NUM
GPM_START_INDEX GPM_NUM_BYTES .ebin bytes
To Next Page
Loading...
Need help?
General
