EM260-USART-JMP-R Ember, EM260-USART-JMP-R Datasheet - Page 26

• Manufacturer Part Number: EM260-USART-JMP-R
• Description: KIT JUMP START FOR EM260
• Manufacturer: Ember
• Series: JumpStartr
• Type: 802.15.4/Zigbeer

Specifications of EM260-USART-JMP-R

• Frequency: 2.4GHz
• For Use With/related Products: EM260
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• Other names: 636-1004; EM260-JMP

EM260
5.3
26
SPI Protocol Timing
120-1003-000D
Figure 6 illustrates all critical timing parameters in the SPI Protocol. These timing parameters are a result of
the EM260’s internal operation and both constrain Host behavior and characterize EM260 operation. The
parameters shown are discussed elsewhere in this document. Note that Figure 6 is not drawn to scale, but is
instead drawn only to illustrate where the parameters are measured.
Table 15 lists the timing parameters of the SPI Protocol. These parameters are illustrated in Figure 6.
Parameter
t1 (a)
t1 (b)
t2
t3
t4
t5
t6
Missing Frame Terminator: Every Command and Response must be terminated with the Frame Terminator
byte. The EM260 will drop any Command that is missing the Frame Terminator. The EM260 will then imme-
diately provide the Missing Frame Terminator Error Response.
Long Transaction: A Long Transaction error occurs when the Host clocks too many bytes. As long as the
inter-command spacing requirement is met, this error condition should not cause a problem, since the
EM260 will send only 0xFF outside of the Response section as well as ignore incoming bytes outside of the
Command section.
Unresponsive: Unresponsive can mean the EM260 is not powered, not fully booted yet, incorrectly con-
nected to the Host, or busy performing other tasks. The Host must wait the maximum length of the Wait
section before it can consider the EM260 unresponsive to the Command section. This maximum length is
200 milliseconds, measured from the end of the last byte sent in the Command Section. If the EM260 ever
fails to respond during the Wait section, it is valid for the Host to consider the EM260 unresponsive and to
reset the EM260. Additionally, if nHOST_INT does not assert within 10ms of nWAKE asserting during the
wake handshake, the Host can consider the EM260 unresponsive and reset the EM260.
Description
Wake handshake, while 260 is awake
Wake handshake, while 260 is asleep
Wake handshake finish
Reset pulse width
Startup time
nHOST_INT deasserting after Command
Clock rate
Table 15. SPI Protocol Timing Parameters
Figure 6. SPI Protocol Timing Waveform
Min.
132
7.2
1.1
8
13
200
Typ.
133
7.3
1.2
250
35
Max.
140
7.5
25
1090
75
µs
ms
Unit
µs
µs
ms
µs
ns