EM260-RCM-USART-R Ember, EM260-RCM-USART-R Datasheet - Page 28

• Manufacturer Part Number: EM260-RCM-USART-R
• Description: EM260 RCM BOARD
• Manufacturer: Ember
• Type: Transceiver, 802.15.4/ZigBeer

Specifications of EM260-RCM-USART-R

• Frequency: 2.4GHz
• For Use With/related Products: EM260
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 636-1025

5.6
120-0260-000J
Powering On, Power Cycling, and Rebooting
•
•
•
5.5.2
There are only five SPI Byte values,
condition occurs, any command sent to the EM260 will be ignored and responded to with one of these codes.
These special SPI Bytes must be trapped and dealt with. In addition, for each error condition the Error Byte
(instead of the Length Byte) is also sent with the SPI Byte.
When the Host powers on (or reboots), it cannot guarantee that the EM260 is awake and ready to receive
commands. Therefore, the Host should always perform the Wake EM260 handshake to guarantee that the
EM260 is awake. If the EM260 resets, it needs to inform the Host so that the Host can reconfigure the stack if
needed.
SPI Byte
will be
number 2. The version number can be a value from 1 to 63 (
SPI Status [0x0B]: Sending this command asks for the EM260 status. The response status byte will always
have the upper 2 bits set. In this current version, the status byte only has one status bit [0], which is set if
the EM260 is alive and ready for commands.
Bootloader Frame [0xFD]: This byte indicates that the current transaction is a Bootloader transaction and
there is more data to follow. This SPI Byte will cause the transaction to look like the full data format
illustrated in Figure 8. The byte immediately after this SPI Byte will be a Length Byte, and it is used to
identify the length of the Bootloader Frame. Refer to the EmberZNet Application Developer’s Guide (120-
4028-000) for more information on the bootloader. If the SPI Byte is
transaction size is four bytes.
EZSP Frame [0xFE]: This byte indicates that the current transaction is an EZSP transaction and there is
more data to follow. This SPI Byte will cause the transaction to look like the full data format illustrated in
Figure 8. The byte immediately after this SPI Byte will be a Length Byte, and it is used to identify the
length of the EZSP Frame. (The EZSP Frame is defined in the EZSP Reference Guide, 120-3009-000.) If the
SPI Byte is
Value
0x00
0x01
0x02
0x03
0x04
Special Response Bytes
0x82
0xFE
, since the version number corresponding to this set of Command-Response values is version
Error Message
EM260 Reset
Oversized EZSP
Frame
Aborted Transac-
tion
Missing Frame
Terminator
Unsupported SPI
Command
, it means the minimum transaction size is five bytes.
Table 16. Byte Values Used as Error Codes
0x00–0x04
Error Description
See section 5.6, Powering On, Power
Cycling, and Rebooting.
The command contained an EZSP
frame with a Length Byte greater than
133. The EM260 was forced to drop the
entire command.
The transaction was not completed
properly and the EM260 was forced to
abort the transaction.
The command was missing the Frame
Terminator. The EM260 was forced to
drop the entire command.
The command contained an unsup-
ported SPI Byte. The EM260 was forced
to drop the entire command.
Page 28
, ever used as error codes (see Table 16). When the error
0x81–0xBF
0xFD
).
, it means the minimum
Error Byte Description
The reset type. Refer to
Ember’s API documentation
discussing EmberResetType.
Reserved
Reserved
Reserved
Reserved
EM260