EM260-RTR datasheet(26/50 Pages) SILICONIMAGE

26 / 50 page

EM260

120-0260-000M Rev 1.1

Page 26

Table 14 lists the timing parameters of the SPI Protocol. These parameters are illustrated in Figure 7.

Table 14. SPI Protocol Timing Parameters

Parameter

Description

Min.

Typ.

Max.

Unit

t1 (a)

Wake handshake, while 260 is awake

133

150

μs

t1 (b)

Wake handshake, while 260 is asleep

7.3

300

Wake handshake finish

1.1

1.2

μs

Reset pulse width

μs

t4 (a)

Startup time, entering application

250

1500

t4 (b)

Startup time, entering bootloader

2.5

7.5

nHOST_INT deasserting after Command

μs

Clock rate

200

Wait section

755

300000

μs

nHOST_INT deasserting after Response

130

800

μs

nHOST_INT asserting after transaction

800

μs

t10

Inter-command spacing

5.4

Data Format

The data format, also referred to as a command, is the same for both the Command section and the Response

section. The data format of the SPI Protocol is straightforward, as illustrated in Figure 8.

Figure 8. SPI Protocol Data Format

The total length of a command must not exceed 136 bytes.

All commands must begin with the SPI Byte. Some commands are only two bytes—that is, they contain the SPI

Byte and Frame Terminator only.

The Length Byte is only included if there is information in the Payload Frame and the Length Byte defines the

length of just the Payload Frame. Therefore, if a command includes a Payload Frame, the Length Byte can

have a value from 2 through 133 and the overall command size will be 5 through 136 bytes. The SPI Byte can

be a specific value indicating if there is a Payload Frame or not, and if there is a Payload Frame, then the

Length Byte can be expected.

The Error Byte is used by the error responses to provide additional information about the error and appears in

place of the length byte. This additional information is described in the following sections.

The Payload Frame contains the data needed for operating EmberZNet PRO. The EZSP Frame and its format

are explained in document UG100, EZSP Reference Guide. The Payload Frame may also contain the data

needed for operating the bootloader, which is called a Bootloader Frame. Refer to document UG103.6, Ember

Application Development Fundamentals: Bootloading, for more information on the bootloader.

The Frame Terminator is a special control byte used to mark the end of a command. The Frame Terminator

byte is defined as 0xA7 and is appended to all Commands and Responses immediately after the final data

byte. The purpose of the Frame Terminator is to provide a known byte the SPI Protocol can use to detect a

SPI Byte

Length or

Error

Payload Frame (Variable Length)

Frame

Terminator

EM260-RTR Folha de dados(PDF) 26 Page - Silicon image

EM260-RTR Folha de dados(HTML) 26 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

Folha de dados Download

Ligação URL