EM260-RTR datasheet(28/50 Pages) SILICONIMAGE

28 / 50 page

EM260

120-0260-000M Rev 1.1

Page 28

will be 0x82, since the version number corresponding to this set of Command-Response values is version

number 2. The version number can be a value from 1 to 63 (0x81–0xBF).

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 document UG103.6, Ember Application Development

Fundamentals: Bootloading, for more information on the bootloader. If the SPI Byte is 0xFD, it means the

minimum 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 document UG100, EZSP Reference Guide.) If the SPI Byte is

0xFE

, it means the minimum transaction size is five bytes.

5.5.2

Special Response Bytes

There are only five SPI Byte values, 0x00–0x04, ever used as error codes (see Table 16). When the error

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.

Table 16. Byte Values Used as Error Codes

SPI Byte

Value

Error Message

Error Description

Error Byte Description

0x00

EM260 Reset

See section 5.6, Powering On, Power

Cycling, and Rebooting.

The reset type. Refer to API

documentation discussing

EmberResetType.

0x01

Oversized EZSP

Frame

The command contained an EZSP

frame with a Length Byte greater than

133. The EM260 was forced to drop the

entire command.

Reserved

0x02

Aborted

Transaction

The transaction was not completed

properly and the EM260 was forced to

abort the transaction.

Reserved

0x03

Missing Frame

Terminator

The command was missing the Frame

Terminator. The EM260 was forced to

drop the entire command.

Reserved

0x04

Unsupported SPI

Command

The command contained an

unsupported SPI Byte. The EM260 was

forced to drop the entire command.

Reserved

5.6

Powering On, Power Cycling, and Rebooting

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.

EM260-RTR 数据表(PDF) 28 Page - Silicon image

EM260-RTR 数据表(HTML) 28 Page - Silicon image

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

数据表下载

链接网址

EM260-RTR 数据表(PDF) 28 Page - Silicon image

EM260-RTR 数据表(HTML) 28 Page - Silicon image

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

数据表 下载

链接网址

数据表下载