Digi International的XBee PRO 900HP RF模组数据手册

需积分: 34 75 浏览量更新于2024-07-15 2 收藏 1.88MB PDF 举报

“XBee PRO 900HP 模块的数据手册提供了关于这款高功率射频模块的关键技术信息，包括其通信速率、通信距离、功耗以及不同的组网模式。” XBee PRO 900HP 模块是Digi International公司生产的一款高性能无线射频模块，适用于需要远距离通信和高功率需求的场景。该模块系列包括XBEE-PRO S3 和 XBEE-PRO S3B 型号，硬件版本为 S3 和 S3B 90002173_D，发布日期为2013年4月2日。 1. **模块特性**： - **通信速率**：XBee PRO 900HP 模块支持多种速率，具体取决于配置和应用。通常，它们可以提供高速串行通信，如UART和SPI接口，以适应不同速度的需求。 - **通信距离**：由于其高功率特性，XBee PRO 900HP 模块能够实现远距离无线通信。具体的通信距离会受到环境条件、天线类型和传输功率的影响。 - **功耗**：这些模块设计时考虑了低功耗，使其适合电池供电或能量受限的应用。功耗详细信息可在数据手册中找到，包括待机、传输和接收时的电流消耗。 - **组网模式**：XBee 模块支持多种网络拓扑结构，如点对点、星型、网状网络等，使得设备间可以灵活地建立连接和交换数据。 2. **全球兼容性**： - **Worldwide Acceptance**：XBee PRO 900HP 符合全球多个地区的无线电法规，可以在多个国家和地区合法使用，这使得它成为跨国项目或全球部署的理想选择。 3. **技术规格**： - **Serial Communications Specifications**：详细列出了模块的串行通信参数，包括UART（通用异步收发传输器）和SPI（串行外围接口）的具体设置，如波特率、数据位、停止位和奇偶校验。 - **UART**：提供了一个标准的串行接口，用于与微控制器或其他设备进行通信。 - **SPI**：支持主/从模式，允许高速数据传输，并可以与其他SPI兼容设备连接。 4. **GPIOs**： - **General Purpose Input/Output**：模块还配备了GPIO引脚，用户可以根据需要配置为输入或输出，用于控制外部设备或读取传感器数据。 5. **技术支持**： Digi International 提供了多种方式为客户和技术人员提供帮助，包括电话支持、在线支持服务和电子邮件联系。用户可以通过这些渠道获取技术咨询、故障排查和产品更新信息。通过深入阅读XBee PRO 900HP 模块的数据手册，开发者和系统集成者能够充分了解该模块的潜力，从而在设计无线通信解决方案时做出明智的决策。这份文档是理解模块功能、优化性能和确保合规性的关键参考资料。

XBee-PRO® 900HP/XBee-PRO® XSC RF Modules

Operation

Upon reset of any kind, the execution control begins with the bootloader.

If the reset cause is Power-On reset (POR), Pin reset (PIN), or Low Voltage Detect (LVD) reset (LVD)

the bootloader will not jump to the application code if the override bits are set to RTS(D7)=1,

DTR(D5)=0, and DIN(B0)=0. Otherwise, the bootloader writes the reset cause "NOTHING" to the

shared data region, and jumps to the Application.

Reset causes are defined in the file common. h in an enumeration with the following definitions:

typedef enum {

BL_CAUSE_NOTHING = 0x0000, //PIN, LVD, POR

BL_CAUSE_NOTHING_COUNT = 0x0001,//BL_Reset_Cause counter

// Bootloader increments cause every reset

BL_CAUSE_BAD_APP = 0x0010,//Bootloader considers APP invalid

} BL_RESET_CAUSES;

typedef enum {

APP_CAUSE_NOTHING = 0x0000,

APP_CAUSE_USE001 = 0x0001,

// 0x0000 to 0x00FF are considered valid for APP use.

APP_CAUSE_USE255 = 0x00FF,

APP_CAUSE_FIRMWARE_UPDATE = 0x5981,

APP_CAUSE_BYPASS_MODE = 0x4682,

APP_CAUSE_BOOTLOADER_MENU = 0x6A18,

} APP_RESET_CAUSES;

Otherwise, if the reset cause is a "watchdog" or other reset, the bootloader checks the shared memory

region for the APP_RESET_CAUSE. If the reset cause is:

1."APP_CAUSE_NOTHING" or 0x0000 to 0x00FF, the bootloader increments the 

BL_RESET_CAUSES, verifies that it is still less than BL_CAUSE_BAD_APP, and jumps back to 

the application. If the Application does not clear the BL_RESET_CAUSE, it can prevent an 

infinite loop of running a bad application that continues to perform illegal instructions or 

watchdog resets.

2."APP_CAUSE_FIRMWARE_UPDATE", the bootloader has been instructed to update the

application "over-the-air" from a specific 64-bit address. In this case, the bootloader will 

attempt to initiate an Xmodem transfer from the 64-bit address located in shared RAM.

3."APP_CAUSE_BYPASS_MODE", the bootloader executes bypass mode. This mode passes the 

local UART data directly to the internal microcontroller allowing for direct communication with

the internal microcontroller.

The only way to exit bypass mode is to reset or power cycle the module.

If none of the above is true, the bootloader will enter "Command mode". In this mode, users can

initiate firmware downloads both wired and over-the-air, check application/bootloader version strings,

and enter Bypass mode.

Application version string

Figure 1 shows an "Application version string pointer" area in application flash which holds the pointer

to where the application version string resides. The application's linker command file ultimately

determines where this string is placed in application flash.

It is preferable that the application version string be located at address 0x8400 for MC9S08QE32 parts.

The application string can be any characters terminated by the NULL character (0x00). There is not a

strict limit on the number of characters in the string, but for practical purposes should be kept under

100 bytes including the terminating NULL character. During an update the bootloader erases the entire

application from 0x8400 on. The last page has the vector table specifically the redirected reset vector.

The version string pointer and reset vector are used to determine if the application is valid.

XBee-PRO® 900HP/XBee-PRO® XSC RF Modules

Application Interrupt Vector table and Linker Command File

Since the bootloader flash region is read-only, the interrupt vector table is redirected to the region

0xF1C0 to 0xF1FD so that application developers can use hardware interrupts. Note that in order for

Application interrupts to function properly, the Application's linker command file (*.prm extension)

must be modified appropriately to allow the linker to place the developers code in the correct place in

memory. For example, the developer desires to use the serial communications port SCI1 receive

interrupt. The developer would add the following line to the Codewarrior linker command file for the

project:

VECTOR ADDRESS 0x0000F1E0 vSci1Rx

This will inform the linker that the interrupt function "vSci1Rx()" should be placed at address

0x0000F1E0. Next, the developer should add a file to their project "vector_table.c" that creates an

array of function pointers to the ISR routines used by the application.

extern void _Startup(void);/* _Startup located in Start08.c */

extern void vSci1Rx(void);/* sci1 rx isr */

extern short iWriteToSci1(unsigned char *);

void vDummyIsr(void);

#pragma CONST_SEG VECTORS

void (* const vector_table[])(void) = /* Relocated Interrupt vector table */{

vDummyIsr,/* Int.no. 0 Vtpm3ovf (at F1C0)Unassigned */

vDummyIsr, /* Int.no. 1 Vtpm3ch5 (at F1C2) Unassigned */

vDummyIsr, /* Int.no. 2 Vtpm3ch4 (at F1C4) Unassigned */

vDummyIsr, /* Int.no. 3 Vtpm3ch3 (at F1C6) Unassigned */

vDummyIsr, /* Int.no. 4 Vtpm3ch2 (at F1C8) Unassigned */

vDummyIsr, /* Int.no. 5 Vtpm3ch1 (at F1CA) Unassigned */

vDummyIsr, /* Int.no. 6 Vtpm3ch0 (at F1CC) Unassigned */

vDummyIsr, /* Int.no. 7 Vrtc (at F1CE) Unassigned */

vDummyIsr, /* Int.no. 8 Vsci2tx (at F1D0) Unassigned */

vDummyIsr, /* Int.no. 9 Vsci2rx (at F1D2) Unassigned */

vDummyIsr, /* Int.no. 10 Vsci2err (at F1D4) Unassigned */

vDummyIsr, /* Int.no. 11 Vacmpx (at F1D6) Unassigned */

vDummyIsr, /* Int.no. 12 Vadc (at F1D8) Unassigned */

vDummyIsr, /* Int.no. 13 Vkeyboard (at F1DA) Unassigned */

vDummyIsr, /* Int.no. 14 Viic (at F1DC) Unassigned */

vDummyIsr, /* Int.no. 15 Vsci1tx (at F1DE) Unassigned */

vSci1Rx, /* Int.no. 16 Vsci1rx (at F1E0) SCI1RX */

vDummyIsr, /* Int.no. 17 Vsci1err (at F1E2) Unassigned */

vDummyIsr, /* Int.no. 18 Vspi (at F1E4) Unassigned */

vDummyIsr, /* Int.no. 19 VReserved12 (at F1E6) Unassigned */

vDummyIsr, /* Int.no. 20 Vtpm2ovf (at F1E8) Unassigned */

vDummyIsr, /* Int.no. 21 Vtpm2ch2 (at F1EA) Unassigned */

vDummyIsr, /* Int.no. 22 Vtpm2ch1 (at F1EC) Unassigned */

vDummyIsr, /* Int.no. 23 Vtpm2ch0 (at F1EE) Unassigned */

vDummyIsr, /* Int.no. 24 Vtpm1ovf (at F1F0) Unassigned */

vDummyIsr, /* Int.no. 25 Vtpm1ch2 (at F1F2) Unassigned */

vDummyIsr, /* Int.no. 26 Vtpm1ch1 (at F1F4) Unassigned */

vDummyIsr, /* Int.no. 27 Vtpm1ch0 (at F1F6) Unassigned */

XBee-PRO® 900HP/XBee-PRO® XSC RF Modules

vDummyIsr, /* Int.no. 28 Vlvd (at F1F8) Unassigned */

vDummyIsr, /* Int.no. 29 Virq (at F1FA) Unassigned */

vDummyIsr, /* Int.no. 30 Vswi (at F1FC) Unassigned */

_Startup /* Int.no. 31 Vreset (at F1FE) Reset vector */

};

void vDummyIsr(void){

for(;;){

if(iWriteToSci1("STUCK IN UNASSIGNED ISR\n\r>"));

}

The interrupt routines themselves can be defined in separate files. The "vDummyIsr" function is used

in conjunction with "iWritetoSci1" for debugging purposes.

Bootloader Menu Commands

The bootloader accepts commands from both the local UART and OTA. All OTA commands sent must be

Unicast with only 1 byte in the payload for each command. A response will be returned to the sender. All

Broadcast and multiple byte OTA packets are dropped to help prevent general OTA traffic from being

interpreted as a command to the bootloader while in the menu.

Bypass Mode - "B"

The bootloader provides a “bypass” mode of operation that essentially connects the freescale mcu to

the internal microcontroller’s serial UART. This allows direct communication to the internal

microcontroller’s radio for the purpose of firmware and radio configuration changes. Once in bypass

mode, the X-CTU utility can change modem configuration and/or update module’s firmware. Bypass

mode automatically handles any baud rate up to 115.2kbps. Note that this command is unavailable

when module is accessed remotely.

Update Firmware - "F"

The "F" command initiates a firmware download for both wired and over-the-air configurations.

Depending on the source of the command (received via Over the Air or local UART), the download will

proceed via wired or over-the-air respectively.

Adjust Timeout for Update Firmware - "T"

The "T" command changes the timeout before sending a NAK by Base-Time*2^(T). The Base-Time for

the local UART is different than the Base-Time for Over the Air. During a firmware update, the

bootloader will automatically increase the Timeout if repeat packets are received or multiple NAKs for

the same packet without success occur.

Application Version String - "A"

The "A" command provides the version of the currently loaded application. If no application is present,

"Unkown" will be returned.

Bootloader Version String - "V"

The "V" command provides the version of the currently loaded bootloader. The version will return a

string in the format BLFFF-HHH-XYZ_DDD where FFF represents the Flash size in kilo bytes, HHH is the

hardware, XYZ is the version, and DDD is the preferred XMODEM packet size for updates. Double the

preferred packet size is also possible, but not guaranteed. For example "BL032-2B0-023_064" will take

64 byte CRC XMODEM payloads and may take 128 byte CRC XMODEM payloads also. In this case, both

64 and 128 payloads are handled, but the 64 byte payload is preferred for better Over the Air

reliability.

Bootloader Version BL032-2x0-025_064 only operates at 9600 baud on the local UART as well as

communications to the internal microcontroller. A newer version of the Bootloader BL032-2x0-033_064

or newer BL032-2B0-XXX_064 has changed the baud rate to 115200 between the Programmable and

XBee-PRO® 900HP/XBee-PRO® XSC RF Modules

the internal microcontroller. The internal module is also set to 115200 as the default baud rate. The

default rate of the programmable local UART is also set to 115200, however, the local UART has an

auto baud feature added to detect if the UART is at the wrong baud rate. If a single character is sent, it

will automatically switch to 115200 or 9600 baud.

Firmware Updates

Wired Updates

A user can update their application using the bootloader in a wired configuration with the following

steps:

a. Plug XBee programmable module into a suitable serial port on a PC.

b. Open a hyperterminal (or similar dumb terminal application) session with 115200 baud, no par-

ity, and 8 data bits with one stop bit.

c. Hit Enter to display the bootloader menu.

d. Hit the "F" key to initiate a wired firmware update.

e. A series of "C" characters Will be displayed within the hyperterminal window. At this point,

select the "transfer->send file" menu item. Select the desired flat binary output file.

f. Select "Xmodem" as the protocol.

g. Click "Send" on the "Send File" dialog. The file will be downloaded to the XBee Programmable

module. Upon a successful update, the bootloader will jump to the newly loaded application.

Over-The-Air updates

A user can update their application using the bootloader in an “over-the-air” configuration with the

following steps…(This procedure assumes that the bootloader is running and not the application. The

internal microcontroller baud rate of the programmable module must be set to 115200 baud. The

bootloader only operates at 115200 baud between the Radio and programmable bootloader. The

application must be programmed with some way to support returning to the bootloader in order to

support Over the Air (OTA) updates without local intervention.)

a. Open a hyperterminal session to the host module with no parity, no hardwareflow control, 8

data bits and 1 stop bit. (The host module does not have to operate at the same baud rate as the

remote module.) For faster updates and less latency due to the UART, set the host module to a

faster baud rate. (i.e. 115200)

b. Enter 3 pluses "+++" to place the module in command mode. (or XCTU’s “Modem Configura-

tion” tab can be used to set the correct parameters)

c. Set the Host Module destination address to the target module’s 64 bit address that the host

module will update (ATDH aabbccdd, ATDL eeffgghh, ATCN, where aabbccddeeffgghh is the hexa-

decimal 64 bit address of the target module).

d. Hit Enter and the bootloader command menu will be displayed from the remote module. (Note

that the option "B" doesn't exist for OTA)

e. Hit the "F" key to cause the remote module to request the new firmware file over-the-air.

f. The host module will begin receiving "C" characters indicating that the remote module is

requesting an Xmodem CRC transfer. Using XCTU or another terminal program, Select "XMODEM"

file transfer. Select the Binary file to upload/transfer. Click Send to start the transfer. At the con-

clusion of a successful transfer, the bootloader will jump to the newly loaded application.

Output File Configuration

BKGD Programming

P&E Micro provides a background debug tool that allows flashing applications on the MC9S08QE parts

through their background debug mode port. By default, the Codewarrior tool produces an "ABS"

output file for use in programming parts through the background debug interface. The programmable

XBee from the factory has the BKGD debugging capability disabled. In order to debug, a bootloader

剩余146页未读，继续阅读

一方灯火

粉丝: 442
资源: 11

Digi International的XBee PRO 900HP RF模组数据手册

XBeePRO数据手册

XBEE PRO S3B 900HP 点对点通信配置和测试报告

XBee-Pro S3B 900HP 中文手册

XBEE XBEE-PRO模块基本试验手册

XBee3 zigbee3.0模块数据手册（中文）.pdf

Xbee pro900HP-User Guide.pdf

Digi XBee PRO S2B ZigBee RF 模块数据手册

XBEE PRO S2B数据手册

XBee-PRO900HP DigiMesh RF 模块用户指南

Digi International的ZigBee XBee®/XBee-PRO® ZB RF 模块手册

最新资源