readme.txt

nRF24E1 sample xBee development

/*****  Using MXI Files with the X-CTU  *****/

1. One MXI file must exist for each Module Type and Hex file combination.  Thus, if a firmware version will be programmed into both XBee and XBee-PRO modules, two MXI files must be created.

2. MXI files must have the same name as the corresponding hex file.


/*****  MXI Header Format  *****/
The fields in the MXI file determine the text that is viewed in the "Modem Configuration" tab of the X-CTU.

For example:
Original Text: [XBEE][XB24][W][1][100][0][0xFE][0][XBEE SMAC Sample App]
Field Breakdown:
[XBEE]  	- Modem Type Label (Modem: XBEE)
[XB24]  	- Modem Type as shown in drop-down "Modem" selection list
[W]		- Module Hardware Type (W-XBee, X-XBee-PRO)
[1]		- Software Compatibility Number (1)
[100]		- Firmware Version as shown in Version drop-down box
[0][0xFE][0]	- Required fields. Leave these values.
[-- t e x t --]	- Text displayed in the Function Set window


/*****  Example  *****/

1. Start with a Custom Application - "MyApp.hex"

2. Create MXI Files:
	"MyApp_XBee.mxi", "MyApp_XBP.mxi"

3. Rename/copy application to "MyApp_XBee.hex", "MyApp_XBP.hex"

4. Move hex and mxi files to \update\XBee subdirectory of XCTU installation.

5. After the mxi files are installed in the correct directory, open the X-CTU.  (The X-CTU must be restarted to read the new mxi files.)

6. The application can now be selected.