C6, C7, C8RF balun/matching DC blocking capacitors
C9, C10Crystal loading capacitors
C11, C12, C13SMPS LC filter capacitor
L0RF choke inductor
L1, L2, L3, L9RF LC filter/matching inductors
L4, L5, L6RF balun/matching inductors
10/91Doc ID 022758 Rev 2
SPIRIT1Typical application diagram and pin description
Table 2.Description of the external components of the typical application diagram
(continued)
ComponentsDescription
L7, L8SMPS LC filter inductor
XTAL24, 26, 48, 52 MHz
Ta bl e 2 assumes to cover all the frequency bands using only four sets of external
components.
Doc ID 022758 Rev 211/91
PinoutSPIRIT1
4 Pinout
Table 3.Pinout description
PinNameI/ODescription
1GPIO_0I/OSee description of GPIOs below
2MISOOSPI data output pin
3MOSIISPI data input pin
4SCLKISPI clock input pin
5CSnISPI chip select
6XOUTO
7XINI
8VBATVDD+1.8 V to +3.6 V input supply voltage
9RXpI
10RXnI
11GND_PAGNDGround for PA
12TXORF output signal
13SMPS Ext2IRegulated DC-DC voltage input
14SMPS Ext1ODC-DC output pin
15SDNI
16VBATVDD+1.8 V to +3.6 V input supply voltage
17VREG
18GPIO3I/OGeneral purpose I/O that may be configured through the SPI
19GPIO2I/O
20GPIO1I/O
21GNDGNDExposed pad ground pin
(1)
VDDRegulated output voltage. A 100 nF decoupling capacitor is required
Crystal oscillator output. Connect to an external 26 MHz crystal or
leave floating if driving the XIN pin with an external signal source
Crystal oscillator input. Connect to an external 26 MHz crystal or to
an external source. If using an external clock source with no crystal,
DC coupling with a nominal 0.2 VDC level is recommended with
minimum AC amplitude of 400 mVpp
Differential RF input signal for the LNA. See application diagram for a
typical matching network
Shutdown input pin. 0-VDD V digital input. SDN should be = ‘0’ in all
modes except shutdown mode. When SDN =’1’ the SPIRIT1 is
completely shut down and the contents of the registers are lost
registers to perform various functions, including:
– MCU clock output
– FIFO status flags
– Wake-up input
– Battery level detector
– TX-RX external switch control
– Antenna diversity control
– Temperature sensor output
1. This pin is intended for use with the SPIRIT1 only. It cannot be used to provide supply voltage to other devices.
12/91Doc ID 022758 Rev 2
SPIRIT1Absolute maximum ratings and thermal data
5 Absolute maximum ratings and thermal data
Absolute maximum ratings are those values above which damage to the device may occur.
Functional operation under these conditions is not implied. All voltages are referred to GND.
Table 4.Absolute maximum ratings
PinParameterValueUnit
8,14,16Supply voltage and SMPS output -0.3 to +3.6 V
17DC voltage on VREG -0.3 to +1.4 V
1,3,4,5,15,18,19,20DC voltage on digital input pins -0.3 to +3.6 V
2DC voltage on digital output pins -0.3 to +3.6 V
11DC voltage on analog pins -0.3 to +3.6 V
6,7,9,10DC voltage on RX/XTAL pins -0.3 to +1.4 V
13DC voltage on SMPS Ext2 pin -0.3 to +1.4 V
12DC voltage on TX pin -0.3 to +3.6 V
T
STG
V
ESD-HBM
Storage temperature range-40 to +125 °C
Electrostatic discharge voltage ±1.0 KV
Table 5.Thermal data
SymbolParameterQFN20Unit
R
thj-amb
Thermal resistance junction-ambient45°C/W
Table 6.Recommended operating conditions
SymbolParameterMin.Typ.Max.Unit
V
BAT
T
Operating battery supply voltage1.833.6V
Operating ambient temperature range-4085°C
A
Doc ID 022758 Rev 213/91
CharacteristicsSPIRIT1
6 Characteristics
6.1 General characteristics
Table 7.General characteristics
SymbolParameterMin.Typ.Max.Unit
FREQFrequency range
Air data rate for each modulation scheme
Optional Manchester and 3 out of 6 encoding/decoding can be selected
2-FSK1
DR
GMSK (BT=1, BT=0.5)1500kBaud
GFSK (BT=1, BT=0.5)1500kBaud
MSK1500kBaud
OOK/ASK1250kBaud
6.2 Electrical specifications
6.2.1 Electrical characteristics
Characteristics measured over recommended operating conditions unless otherwise
specified. Typical values are referred to T
to a 50 Ohm antenna connector, via the reference design.
= 25 °C, V
A
150
300348MHz
387470MHz
779956MHz
= 3.0 V. All performance is referred
BAT
174MHz
-
500kBaud
-
14/91Doc ID 022758 Rev 2
SPIRIT1Characteristics
Table 8.Power consumption
SymbolParameterTest conditionsMin.Typ.Max.Unit
RX
(1)
(1)
(1)
(1)
(1)
(1)
2.5
650nA
950nA
400µA
4.5mA
9mA
21
22
19.5
21
6
6.5
7
7
nA
-
mA
I
BAT
1. See Table 17.
Supply current
Shutdown
Standby
Sleep
Ready (default mode)
Tu ni n g
(1)
TX
+11 dBm 169 MHz
(1)
TX
+11 dBm 315 MHz
(1)
TX
+11 dBm 433 MHz
(1)
TX
+11 dBm 868 MHz
(1)
TX
-8 dBm 169 MHz
(1)
TX
-8 dBm 315 MHz
(1)
TX
-7 dBm 433 MHz
(1)
TX
-7 dBm 868 MHz
6.2.2 Digital SPI
Table 9.Digital SPI input and output (SDO, SDI, SCLK, CSn, and SDN) and GPIO
SymbolParameterTest conditionMin.Typ.Max.Unit
Clock frequency10MHz
clk
Port I/O capacitance1.4pF
IN
Rise time
Fall time
Logic high level input
IH
voltage
T
T
f
C
RISE
FAL L
V
specification (GPIO_1-4)
0.1*VDD to 0.9*VDD,
CL=20 pF (low output
current programming)
0.1*VDD to 0.9*VDD,
CL=20 pF (high output
current programming)
0.1*VDD to 0.9*VDD,
CL=20 pF (low output
current programming)
0.1*VDD to 0.9*VDD,
CL=20 pF (high output
current programming)
VDD/2
+0.3
3.5
ns
2
5.5
ns
2.8
V
V
Logic low level input
IL
voltage
VDD/8
+0.3
V
Doc ID 022758 Rev 215/91
CharacteristicsSPIRIT1
Table 9.Digital SPI input and output (SDO, SDI, SCLK, CSn, and SDN) and GPIO
specification (GPIO_1-4) (continued)
SymbolParameterTest conditionMin.Typ.Max.Unit
IOH = -2.4 mA (-4.2 mA if
V
V
High level output voltage
OH
Low level output voltage
OL
high output current
capability is
programmed).
IOL = +2.4 mA (+4 mA if
high output current
capability is
programmed).
(5/8)*
VDD+
0.1
0.5V
6.2.3 RF receiver
Characteristics measured over recommended operating conditions unless otherwise
specified. All typical values are referred to T
= 25 °C, V
A
the RX signal. All performance is referred to a 50 Ohm antenna connector, via the reference
design.
Table 10.RF receiver characteristics
SymbolParameterTest conditionMin.Typ.Max.Unit
169.4-169.475 MHz, 433-435
RLReturn loss
CH
BW
Receiver channel bandwidth6800 kHz
MHz, 868-868.6 MHz, 310-320
MHz, 902-928 MHz
169MHz 2-FSK 1.2Kbps
(4 kHz dev. CH Filter=10kHz)
(1)
= 3.0 V, no frequency offset in
BAT
-10 dB
-117 dBm
V
169MHz GFSK (BT=0.5)
Sensitivity, 1% BER (according
to W-MBUS N mode
specification)
RX
SENS
Sensitivity, 1% PER (packet
length = 20 bytes) FEC
DISABLED
868 MHz GFSK 38.4 kbps
BT=1 (20kHz dev. CH BW=100
kHz), desired channel 3 dB
above the sensitivity limit, with
IQC correction.
@ 2 MHz offset, 868 MHz
GFSK 38.4kbps, desired
channel 3 dB above the
sensitivity limit
@ 10 MHz offset, 868 MHz
GFSK 38.4kbps, desired
channel 3 dB above the
sensitivity limit.
47dB
41dB
56dB
48dB
-42dBm
-40dBm
18/91Doc ID 022758 Rev 2
SPIRIT1Characteristics
Table 10.RF receiver characteristics (continued)
SymbolParameterTest conditionMin.Typ.Max.Unit
Below 1 GHz-58dBm
RX
SPUR
Spurious emissions (maximum
values according to ETSI EN
300 220-1)
Above 1 GHz up to 4 GHz for
frequency band < 470 MHz, up
to 6 GHz for frequency band >
-61dBm
470 MHz
1. Guaranteed in an entire single sub band. Reference design can be different for different application bands.
2. In OOK modulation, indicated value represents mean power.
3. Interferer is CW signal (as specified by ETSI EN 300 220 v1).
4. Blocker is CW signal (as specified by ETSI EN 300 220 v1)
6.2.4 RF transmitter
Characteristics measured over recommended operating conditions unless otherwise
specified. All typical values are referred to T
referred to a 50 Ohm antenna connector, via the reference design.
1. In ASK/OOK modulation, indicated value represents peak power.
46 + j36Ohm
25 + j27 Ohm
29 + j19 Ohm
34 - j7 Ohm
15 + j28 Ohm
42 - j15 Ohm
6.2.5 Crystal oscillator
Characteristics measured over recommended operating conditions unless otherwise
specified. All typical values are referred to T
= 25 °C, V
A
characteristics are referred to 915 MHz band.
Table 12.Crystal oscillator characteristics
SymbolParameterTest conditionsMin.Typ.Max.Unit
= 3.0 V. Frequency synthesizer
BAT
XTAL
F
TOL
Crystal frequency26MHz
F
Frequency tolerance
(1)
± 40ppm
100 Hz-90dBc/Hz
PN
XTAL
Minimum requirement on
external reference phase noise
mask (Fxo=26 MHz), to avoid
degradation on synthesizer
phase/noise
1 kHz-120dBc/Hz
10 kHz-135dBc/Hz
100 kHz-140dBc/Hz
1 MHz-140dBc/Hz
T
START
1. Including initial tolerance, crystal loading, aging, and temperature dependence. The acceptable crystal tolerance depends
on RF frequency and channel spacing/bandwidth.
2. Startup times are crystal dependent. The crystal oscillator transconductance can be tuned to compensate the variation of
crystal oscillator series resistance.
Startup time
(2)
V
=1.8 V100280300µs
BAT
Doc ID 022758 Rev 223/91
CharacteristicsSPIRIT1
Table 13.Ultra low power RC oscillator
SymbolParameterTest conditionsMin.Typ.Max.Unit
Calibrated RC oscillator
RC
Calibrated frequency
F
frequency is derived from
crystal oscillator frequency.
Digital clock domain 26 MHz
34.7kHz
-
RC
TOL
Frequency accuracy after
calibration
±1%
Table 14.N-Fractional ΣΔ frequency synthesizer characteristics
SymbolParameterTest conditionsMin.Typ.Max.Unit
F
RES
Frequency resolution-100Hz
10 kHz-100-97-94dBc/Hz
100 kHz-104-101-99dBc/Hz
PN
SYNTH
RF carrier phase noise
(915 MHz band)
200 kHz-105-102-100dBc/Hz
500 kHz-112-110-107dBc/Hz
1 MHz-120-118-116dBc/Hz
2 MHz-123-121-119dBc/Hz
TO
SET
CAL
TIME
PLL turn-on/hop time6080µs
PLL RX/TX settling time
TIME
PLL calibration time54µs
TIME
Settling time from RX to TX
and from TX to RX
8.5µs
6.2.6 Sensors
Characteristics measured over recommended operating conditions unless otherwise
specified. All typical values are referred to T
Table 15.Analog temperature sensor characteristics
= 25 °C, V
A
(1)
SymbolParameterTest conditionsMin.Typ.Max.Unit
T
T
SLOPE
V
TS-OUT
Error in temperatureAcross all the temperature range±2.5°C
ERR
Temperature coefficient2.5
Output voltage level0.92V
Buffered output (low output
impedance, about 400 Ohm)
T
Current consumption
ICC
Not buffered output (high output
impedance, about 100 kΩ)
1. The temperature readout is a trigger based function. Some processing time is allowed. So, start of conversion trigger ->
end of conversion status + read out register.
24/91Doc ID 022758 Rev 2
BAT
= 3.0 V.
600µA
10µA
mV/
°C
SPIRIT1Characteristics
Table 16.Battery indicator and low battery detector
(1)
SymbolParameterTest conditionsMin.Typ.Max.Unit
V
Battery level thresholds2.12.7V
BLT
Measured in slow battery
variation (static) conditions
1.535V
(inaccurate)
V
Brownout threshold
BOT
Measured in slow battery
variation (static) conditions
1.684V
(accurate)
BOT
1. For battery powered equipment, the TX does not transmit at a wrong frequency under low battery voltage conditions. It
either remains on channel or stops transmitting. The latter can of course be realized by using a lock detect and/or by
switching off the PA under control of the battery monitor. For testing reasons this control is enabled/disabled by SPI.
Brownout threshold hysteresis70mV
hyst
Doc ID 022758 Rev 225/91
Operating modesSPIRIT1
2%!$9
34!.$"9
3,%%0
2848,/#+
3(54$/7.
!-6
7 Operating modes
The SPIRIT1 is provided with a built-in main controller which controls the switching between
the two main operating modes: transmit (TX) and receive (RX).
In shutdown condition (the SPIRIT1 can be switched on/off with the external pin SDN, all
other functions/registers/commands are available through the SPI interface and GPIOs), no
internal supply is generated (in order to have minimum battery leakage), and hence, all
stored data and configurations are lost. From shutdown, the SPIRIT1 can be switched on
from the SDN pin and goes into READY state, which is the default, where the reference
signal from XO is available.
From READY state, the SPIRIT1 can be moved to LOCK state to generate the high
precision LO signal and/or TX or RX modes. Switching from RX to TX and vice versa can
happen only by passing through the LOCK state. This operation is normally managed by
radio control with a single user command (TX or RX). At the end of the operations above,
the SPIRIT1 can return to its default state (READY) and can then be put into a sleeping
condition (SLEEP state), having very low power consumption. If no timeout is required, the
SPIRIT1 can be moved from READY to STANDBY state, which has the lowest possible
current consumption while retaining FIFO, status and configuration registers. To manage the
transitions towards and between these operating modes, the controller works as a statemachine, whose state switching is driven by SPI commands. See Figure 3 for state diagram
and transition time between states.
Figure 3.Diagram and transition
The SPIRIT1 radio control has three stable states (READY, STANDBY, LOCK) which may be
defined stable, and they are accessed by the specific commands (respectively READY,
26/91Doc ID 022758 Rev 2
SPIRIT1Operating modes
STANDBY, and LOCKRX/LOCKTX), which can be left only if any other command is used. All
other states are transient, which means that, in a typical configuration, the controller
remains in those states, at most for any timeout timer duration. Also the READY and LOCK
states behave as transients when they are not directly accessed with the specific commands
(for example, when LOCK is temporarily used before reaching the TX or RX states).
Table 17.States
State/modeDigital LDOSPIXtalRF Synth.
SHUTDOWN
STANDBY
SLEEPOnOffOffOn350 µs350 µs
READY (Default)OnOnOffDon’t care110 µs110 µs
LOCKOnOnOnDon’t careNANA
RXOnOnOnDon’t care20 µsNA
TXOnOnOnDon’t careNA20 µs
OFF (register
contents lost)
ON (FIFO and
register
contents
retained)
OffOffOffOffNANA
OnOffOffOff320 µs320 µs
Wake-up
timer
Response time to
TXRX
Note:Response time SHUTDOWN to READY is ~1 ms.
READY state is the default state after the power-on reset event. In the steady condition, the
XO is settled and usable as the time reference for RCO calibration, for frequency synthesis,
and as the system clock for the digital circuits.
The TX and RX modes can be activated directly by the MCU using the TX and RX
commands, or automatically if the state machine wakes up from SLEEP mode and some
previous TX or RX is pending.
(a)
In LOCK state the synthesizer is in a locking condition
. If LOCK state is reached using
either one of the two specific commands (LOCKTX or LOCKRX), the state machine remains
in LOCK state and waits for the next command. This feature can be used by the MCU to
perform preliminary calibrations, as the MCU can read the calibration word in the
RCO_VCO_CALIBR_OUT register and store it in a non-volatile memory, and after that it
requires a further tuning cycle.
When TX is activated by the TX command, the state machine goes into TX state and
remains there until the current packet is fully transmitted or, in the case of direct mode TX,
TXFIFO underflow condition is reached or the SABORT command is applied.
a. LOCK state is reached when one of the following events occurs first: lock detector assertion or locking timeout
expiration.
Doc ID 022758 Rev 227/91
Operating modesSPIRIT1
After TX completion, the possible destinations are:
●TX, if the persistent-TX option is enabled in the PROTOCOL configuration registers
●PROTOCOL, if some protocol option (e.g. automatic re-transmission) is enabled
●READY, if TX is completed and no protocol option is in progress.
Similarly, when RX is activated by the RX command, the state machine goes into RX state
and remains there until the packet is successfully received or the RX timeout expires. In
case of direct mode RX, the RX stops when the RXFIFO overflow condition is reached or
the SABORT command is applied. After RX completion, the possible destinations are:
●RX, if the persistent-RX option is enabled in the PROTOCOL configuration registers
●PROTOCOL, if some protocol option (e.g. automatic acknowledgement) is enabled
●READY, if RX is completed and the LDCR mode is not active
●SLEEP, if RX is completed and the LDCR mode is active.
The SABORT command can always be used in TX or RX state to break any deadlock
condition and the subsequent destination depends on SPIRIT1 programming according to
the description above.
Commands are used in the SPIRIT1 to change the operating mode, to enable/disable
functions, and so on. A command is sent on the SPI interface and may be followed by any
other SPI access without pulling CSn high.
The complete list of commands is reported in Ta bl e 18 . Note that the command code is the
second byte to be sent on the MOSI pin (the first byte must be 0x80).
Table 18.Commands list
Command
code
0x60TXREADYStart to transmit
0x61RXREADYStart to receive
0x62READY
0x63STANDBYREADYGo to STANDBY
0x64SLEEPREADYGo to SLEEP
0x65LOCKRXREADY
0x66LOCKTXREADY
0x67SABORTTX, RXExit from TX or RX states and go to READY state
0x68LDC_RELOADAll
0x69
Command nameExecution stateDescription
SEQUENCE_UPDA
TE
STANDBY, SLEEP,
LOCK
All
Go to READY
Go to LOCK state by using the RX configuration of the
synthesizer
Go to LOCK state by using the TX configuration of the
synthesizer
Reload the LDC timer with the value stored in the
LDC_PRESCALER/COUNTER registers
Reload the packet sequence counter with the value
stored in the PROTOCOL[2] register.
0x6AAES EncAllStart the encryption routine
0x6BAES KeyAllStart the procedure to compute the key for decryption
0x6CAES DecAllStart decryption using the current key
28/91Doc ID 022758 Rev 2
SPIRIT1Operating modes
!-6
Table 18.Commands list (continued)
Command
code
0x6DAES KeyDecAllCompute the key and start decryption
0x70SRESAllReset
0x71FLUSHRXFIFOAllClean the RX FIFO
0x72FLUSHTXFIFOAllClean the TX FIFO
Command nameExecution stateDescription
The commands are immediately valid after SPI transfer completion (i.e. no need for any CSn
positive edge).
7.1 Reset sequence
SPIRIT1 is provided with an automatic power-on reset (POR) circuit which generates an
internal RESETN active (low) level for a time T
release threshold voltage V
(provided that SDN is low), as shown below. The same reset
RRT
pulse is generated after a step-down on the input pin SDN (provided that VDD>V
Figure 4.Power-on reset timing and limits
after the VDD reaches the reset
RESET
6$$NOMINAL
RRT
).
6
2%3%4.
3
6$$
T
The parameters V
RRT
and T
4
are fixed by design. At RESET, all the registers are
RESET
initialized to their default values. Typical and extreme values are reported in the following
table.
Doc ID 022758 Rev 229/91
Operating modesSPIRIT1
Table 1 9.POR param e ters
SymbolParameterCommentMin.Typ.Max.Unit
V
T
RESET
RRT
Reset startup threshold
voltage
Reset pulse width0.51.01.5ms
0.5V
Note:An SRES command is also available which generates an internal RESET of the SPIRIT1.
7.2 Timer usage
Most of the timers are programmable via R/W registers. All timer registers are made up of
two bytes: the first byte is a multiplier factor (prescaler); the second byte is a counter value.
MSBLSB
15PRESCALER87COUNTER0
Timer period= PRESCALER x CONTER x Tclk
For example, using a 26 MHz crystal oscillator (Tclk = 38 ns) and a PRESCALER of 27
(decimal), the COUNTER time base is about 1 µs.
Note:If the counter register value (prescaler register value) is 0, the related timer never stops
(infinite timeout), despite the value written in the prescaler register (counter register).
The available timers and their features are listed in the following table.
Note:For LDCR_COUNTER and LDCR_PRESCALER only, the effective number of cycles
counted is given by the value + 1 (e.g. counter=1 and prescaler=1 produces 2 x 2=4 counts,
counter=1 and prescaler=2 produces 2 x 3=6 counts, etc.).
7.3 Low duty cycle reception mode
The SPIRIT1 provides an operating mode, low duty cycle reception (LDCR), which is an
operating mode that allows operation with very low power consumption, while at the same
time keeping an efficient communication link. The LDCR mode is enabled by setting the
LDCR_MODE bit in the PROTOCOL registers.
30/91Doc ID 022758 Rev 2
SPIRIT1Operating modes
!#4)6% 3,%%0).' )$,%
475
4
)$,%
7AKE 5P
)NTERRUPT
39.#RECEIVED
)NTERRUPT
!-6
This mode is available for both the transmitter and receiver and it is designed to allow for at
most one sequence RX+TX or TX+RX.
The device provides a set of timers to efficiently handle low duty cycle reception (LDCR).
When LDCR is enabled the device runs on the 34.7 kHz RC oscillator keeping unused
blocks off.
LDCR is controlled essentially by the wake-up period (T
), which periodically wakes up
WU
the SPIRIT1 to perform a transmission or a reception.
In reception mode, it is also relevant to set up the RX timeout in order to minimize the
amount of time the SPIRIT1 waits for a packet during T
When setting T
, care should be taken when considering the analog settling time which is
WU
required before the radio becomes fully operative for transmission or reception (T
WU
.
in
IDLE
Figure 5).
Figure 5.LDCR mode timing
The T
this causes power waste. In order to minimize T
time can be longer than the minimum required to get analog circuits settling, and
IDLE
, the SPIRIT1 supports the runtime
IDLE
phasing of the internal wake-up timer, as follows:
●The value of the wake-up timer can be reloaded during runtime using the
LDCR_RELOAD command with the values written in the
LDCR_RELOAD_PRESCALER/COUNTER registers. In doing so, the counting can be
delayed or anticipated
●Alternatively, the wake-up timer can be automatically reloaded at the time the SYNC is
received. This option must be enabled on the PROTOCOL register and it is available
only for LDC mode in reception.
7.4 CSMA/CA engine
The CSMA/CA engine is a channel access mechanism based on the rule of sensing the
channel before transmitting. This avoids the simultaneous use of the channel by different
transmitters and increases the probability of correct reception of data being transmitted.
CSMA is an optional feature that can be enabled on the basis of user needs.
When CSMA is enabled, the device performs a clear channel assessment (CCA) before
transmitting any data. In SPIRIT1 implementation, CCA is based on a comparison of the
channel RSSI with a programmable static carrier sense threshold.
If the CCA finds the channel busy, a backoff procedure may be activated to repeat the CCA
process a certain number of times, until the channel is found to be idle. Each time that CCA
is retried, a counter (NB) is incremented by one, up to the upper limit (NB
).
max
Doc ID 022758 Rev 231/91
Operating modesSPIRIT1
When the limit is reached, an NBACKOFF_MAX interrupt request is raised towards the
MCU, to notify that the channel has been repeatedly found busy and so the transmission
has not been performed.
While in backoff, the device stays in SLEEP/READY state in order to reduce power
consumption.
CCA may optionally be persistent, i.e., rather than entering backoff when the channel is
found busy, CCA continues until the channel becomes idle or until the MCU stops it.
The thinking behind using this option is to give the MCU the possibility of managing the CCA
by itself, for instance, with the allocation of a transmission timer: this timer would start when
MCU finishes sending out data to be transmitted, and would end when MCU expects that its
transmission takes place, which would occur after a period of CCA.
The choice of making CCA persistent should come from trading off transmission latency,
under the direct control of the MCU, and power consumption, which would be greater due to
a busy wait in reception mode.
The overall CSMA/CA flowchart is shown in Figure 6, where T
cca
and T
are two of the
listen
parameters controlling the clear channel assessment procedure. Design practice
recommends that these parameters average the channel energy over a certain period
expressed as a multiple of the bit period (T
covering longer periods (T
). The measurement is performed directly by checking the
listen
) and repeat such measurement several times
cca
carrier sense (CS) generated by the receiver module.
32/91Doc ID 022758 Rev 2
30)COMMAND
48
."
3EEDRELOAD
#3-!?/.
3$.
3(54$/7.
2%!$9
3$.INTERNAL0/2
3ETTLING
ON2ESET
48SETTLING
48MODE
TRANSMITAPACKET
PERSISTENT
#3-!?0%23?/.
28MODE
CHANNELBUSY
#3
#3TIMEOUT
4
LISTEN
EXPIRATION
.O
9ES
9ES
2ESTART#ARRIER
3ENSETIMERS
9ES
NUMBEROFRETRIES
."."
MAX
3,%%0
.O
(AS"/WAIT
ELAPSED
"/RAND
."
§"5
."."
#3- !MODE
ENABLED
9ES
#3PERIOD
.O
4
CCA
EXPIRATION
.O
9ES
.O
9ES
.O
.O
9ES
#3-!
#3-!
2%!$9
!-6
SPIRIT1Operating modes
Figure 6.CSMA flowchart
To avoid any wait synchronization between different channel contenders, which may cause
successive failing CCA operations, the backoff wait time is calculated randomly between 0
and a contention window. The backoff time BO is expressed as a multiple of backoff time
units (BU). The contention window is calculated on the basis of the binary exponential
Doc ID 022758 Rev 233/91
Operating modesSPIRIT1
backoff (BEB) technique, which doubles the size of the window at each backoff retry (stored
in the NB counter):
BO= rand(0,2
NB
)×BU
The CSMA procedure is then controlled by the following parameters:
SEED_RELOAD: enables/disables the reload of the seed used by the backoff random
generator at the start of each CSMA procedure (at the time when the counter is reset, i.e.
NB=0). If this functionality is not enabled, the seed is automatically generated and updated
by the generator circuit itself.
CSMA_ON: enables/disables the CSMA procedure (11
th
bit of the PROTOCOL[1] register);
this bit is checked at each packet transmission.
CSMA_PERS_ON: makes the carrier sense persistent, i.e. the channel is continuously
th
monitored until it becomes free again, skipping the backoff waiting steps (9
bit of the
PROTOCOL[1] register); the MCU can stop the procedure with an SABORT command.
BU_COUNTER_SEED_MSByte/LSByte: these bytes are used to set the seed of the
pseudo-random number generator when the CSMA cycle starts (CSMA_CONFIG[3:2]
registers), provided that the SEED_RELOAD bit is enabled. Value 0 is not allowed, because
the pseudo-random generator does not work in that case.
(b)
BU_PRESCALER[5:0]: prescaler which is used to configure the backoff time unit
BU=BU_PRESCALER in Figure 6 (field of the CSMA_CONFIG[1] register).
CCA_PERIOD[1:0]: code which programs the T
time (expressed as a multiple of Tbit
cca
samples) between two successive CS samplings (field of the CSMA_CONFIG[1] register),
as follows:
●00 64×Tbit
●01 128×Tbit
●10 256×Tbit
●11 512×Tbit.
CCA_LENGTH[3:0]: configuration of T
= [1..15] x T
listen
cca
NBACKOFF_MAX[2:0]: max. number of backoff cycles.
b. Note that the backoff timer is clocked on the 34.7 kHz clock, because, in this case, the SPIRIT1 is in SLEEP
state, in order to reduce power consumption.
34/91Doc ID 022758 Rev 2
SPIRIT1Block description
8 Block description
8.1 Power management
The SPIRIT1 integrates a high efficiency step-down converter cascaded with LDOs meant
to supply both analog and digital parts. However, an LDO directly fed by the external battery
provides a controlled voltage to the data interface block.
8.2 Power-on-reset (POR)
The power-on-reset circuit generates a reset pulse upon power-up which is used to initialize
the entire digital logic. Power-on-reset senses V
8.3 Low battery indicator
The battery indicator can provide the user with an indication of the battery voltage level.
There are two blocks to detect battery level:
●Brownout with a fixed threshold as defined inTable 16: Battery indicator and low battery
detector
●Battery level detector with a programmable threshold as defined in Table 16: Battery
indicator and low battery detector.
BAT
voltage.
Both blocks can be optionally activated to provide the MCU with an early warning of
impending power failure. It does not reset the system, but gives the MCU time to prepare for
an orderly power-down and provides hardware protection of data stored in the program
memory, by preventing write instructions being executed.
The low battery indicatorr function is available in any of the SPIRIT1 operation modes. As
this function requires the internal bias circuit operation, the overall current consumption in
STANDBY, SLEEP, and READY modes is increased by 400 µA.
8.4 Voltage reference
This block provides the precise reference voltage needed by the internal circuit.
8.5 Oscillator and RF synthesizer
A crystal connected to XIN and XOUT is used to provide a clock signal to the frequency
synthesizer. The allowed clock signal frequency is either 24, 26, 48, or 52 MHz. As an
alternative, an external clock signal can be used to feed XIN for proper operation. In this
option, XOUT can be left either floating or tied to ground.
Since the digital macro cannot be clocked at that double frequency (48 MHz or 52 MHz), a
divided clock is used in this case. To enable the synthesizer reference signal divider by 2,
the bit-field REFDIV in the SYNTH_CONFIG register must be set.
The digital clock divider is enabled by default and must be kept enabled if the crystal is in the
(48 - 52) MHz range; if the crystal is in the (24 - 26) MHz range, then the divider must be
Doc ID 022758 Rev 235/91
Block descriptionSPIRIT1
disabled before starting any TX/RX operation. The safest procedure to disable the divider
without any risk of glitches in the digital clock is to switch into STANDBY mode, hence, reset
the bit-field PD_CLKDIV in the XO_RCO_TEST register, and then come back to the READY
state.
The integrated phase locked loop (PLL) is capable of synthesizing the frequencies in the
bands from 169.1 to 169.5, from 300 to 348 MHz, from 387 to 470 MHz, or from 779 to 956
MHz, providing the LO signal for the RX chain and the input signal for the PA in the TX
chain.
Frequency tolerance and startup times depend on the crystal used, although some tuning of
the latter parameter is possible through the GM_CONF field of the ANA_FUNC_CONF
registers.
Table 21.Programmability of trans-conductance at startup
GM_CONF[2:0]Gm at startup [ms]
00013.2
00118.2
01021.5
01125.6
10028.8
10133.9
11038.5
11143.0
Depending on the RF frequency and channel spacing, a very high accurate crystal or TCXO
can be required.
The RF synthesizer implements fractional sigma delta architecture to allow fast settling and
narrow channel spacing. It is fully integrated and uses a multi-band VCO to cover the whole
frequency range. All internal calibrations are performed automatically.
The PLL output frequency can be configured by programming the SYNT field of the SYNT3,
SYNT2, SYNT1, and SYNT0 registers and BS field of the SYNT0 register (see
Section 9.5.2). The user must configure these registers according to the effective reference
frequency in use (24 MHz, 26 MHz, 48 MHz, or 52 MHz). In the latter two cases, the user
must enable the frequency divider by 2 for the digital clock, in order to run the digital macro
at a lower frequency. The configuration bit for the digital clock divider is inside the
XO_RCO_TEST register (default case is divider enabled). In addition, the user can also
enable a divider by 2 applied to the reference clock. The configuration bit for the reference
clock divider is inside the SYNTH_CONFIG[1] register. The user must select a 3-bit word in
order to set the charge pump current according to the LO frequency variations, in order to
have a constant loop bandwidth. This can be done by writing the WCP field of the SYNT3
register, according to the following table:
36/91Doc ID 022758 Rev 2
SPIRIT1Block description
Table 2 2.CP word l ook-u p
Channel frequencyWCP [2:0]
169.1169.5011
290.3294000
294.3298.3001
298.3302.3010
302.4306.4011
306.4310.4100
310.4314.4101
314.4318.4110
318.4322.6111
322.6327.0000
327.0331.4001
331.4335.9010
335.9340.5011
340.5344.9100
344.9349.5101
349.5353.9110
353.9358.5111
387.0392.3000
392.3397.7001
397.7403.0010
403.0408.5011
413.8419.2101
419.2424.6110
424.6430.1111
430.1436.0000
436.0441.9001
441.9447.9010
447.9454.0011
454.0459.9100
459.9466.0101
466.0471.9110
471.9478.0111
774.0784.7000
784.7795.3001
Doc ID 022758 Rev 237/91
Block descriptionSPIRIT1
Table 22.CP word look-up (continued)
Channel frequencyWCP [2:0]
795.3806.0010
806.0817.0011
817.0827.7100
827.7838.3101
838.3849.2110
849.2860.2111
860.2872.0000
872.0883.8001
883.8895.8010
908.0919.8100
919.8932.0101
932.0943.8110
943.8956.0111
The SPIRIT1 is provided with an automatic and very fast calibration procedure for the
frequency synthesizer. If not disabled, it is performed each time the SYNTH is required to
lock to the programmed RF channel frequency (i.e. from READY to LOCK/TX/RX or from
RX to TX and vice versa). Calibration time is 54 µs.
After completion, the calibration word is used automatically by the SPIRIT1 and is stored in
the RCO_VCO_CALIBR_OUT[1:0] registers.
In order to get the synthesizer locked when the calibration procedure is not enabled, the
correct calibration words to be used must be previously stored in the
RCO_VCO_CALIBR_IN[2:0] registers using VCO_CALIBR_TX and VCO_CALIBR_RX
fields for TX and RX modes respectively.
The advantage of performing an offline calibration is that the LOCK/setting time is roughly
20 µs (using proper VCO_CALIBR_TX/RX register values).
If calibration is enabled, the LOCK/setting time is approximately 80 µs.
8.6 RCO: features and calibration
The SPIRIT1 contains a low power RC oscillator capable of generating 34.7 kHz with both
24 MHz and 26 MHz; the RC oscillator frequency is calibrated comparing it against the
digital domain clock divided by 692 or 750, respectively. The configuration bit, called 24_26
MHz_SELECT in the ANA_FUNC_CONF register, contains the information of the calibrator
about the frequency of the crystal under operation. If the digital domain clock is 25 MHz, the
setting of the configuration bit 24_26 MHz_SELECTwill calibrate the low power RC oscillator
according to the following table:
38/91Doc ID 022758 Rev 2
SPIRIT1Block description
Table 23.RC calibrated speed
Digital domain clock24_26MHz_SELECTRC calibrated speed
24 MHz 0 34.7 kHz
26 MHz 1 34.7 kHz
25 MHz 0 36.1 kHz
25 MHz 1 33.3 kHz
8.6.1 RC oscillator calibration
RC oscillator calibration is enabled when bit RCO_CALIBRATION is set in the
PROTOCOL[2] register (by default the calibration is enabled). The calibration words found
by the calibration algorithm are accessible in the RCO_VCO_CALIBR_OUT[1:0] registers
(fields RWT_OUT[3:0] and RFB_OUT[4:0],).
When the calibration is disabled, the frequency of the RC oscillator is set by a couple of
configuration words, namely RWT_IN[3:0] and RFB_IN[4:0], in the
RCO_VCO_CALIBR_IN[2:0] registers (fields RWT_IN[3:0] and RFB_IN[4:0]). RWT_IN[3:0]
can range from 0 up to 13 (decimal value) affecting the raw value of the frequency, while the
more accurate and fine control is up to RFB_IN[4:0] (ranging from 1 up to 31).
8.7 AFC
The SPIRIT1 implements an automatic frequency compensation algorithm to balance
TX/RX crystal frequency inaccuracies. The receiver demodulator estimates the centre of the
received data and compensates the offset between nominal and receiver frequency.
The tracking range of the algorithm is programmable and is a fraction of the receive channel
bandwidth. Frequency offset compensation is supported for 2-FSK, GFSK, and MSK
modulation.
When the relative frequency error between transmitter and receiver is less than half the
modulation bandwidth, the AFC corrects the frequency error without needing extra
bandwidth. When the frequency error exceeds BWmod/2, some extra bandwidth is needed
to assure proper AFC operation under worst-case conditions. The AFC can be disabled if
the TX/RX frequency misalignment is negligible with respect to the receiver bandwidth, for
example, when using a TCXO.
8.8 Receiver
The SPIRIT1 contains a low-power low-IF receiver which is able to amplify the input signal
and provide it to the ADC with a proper signal to noise ratio. The RF antenna signal is
converted to a differential one by an external balun, which performs an impedance
transformation also. The receiver gain can be programmed to accommodate the ADC input
signal within its dynamic range. After the down-conversion at IF, a first order filter is
implemented to attenuate the out-of-band blockers.
The SPIRIT1 contains an integrated PA capable of transmitting at output levels between -30
dBm to +11 dBm. The PA is single-ended and has a dedicated pin (TXOUT). The PA output
is ramped up and down to prevent unwanted spectral splatter. In TX mode the PA drives the
signal generated by the frequency synthesizer out to the antenna terminal. The output
power of the PA is programmable via SPI. Delivered power, as well as harmonic content,
depends on the external impedance seen by the PA. To obtain approval on ETSI EN 300
220, it is possible to program TX to send an unmodulated carrier.
The output stage is supplied from the SMPS through an external choke and is loaded with a
LC-type network which has the function of transforming the impedance of the antenna and
filter out the harmonics. The TX and RX pins are tied directly to share the antenna. During
TX, the LNA inputs are internally shorted to ground to allow for the external network
resonance, so minimizing the power loss due to the RX.
Figure 7.Shaping of ASK signal
8.10 Temperature sensors (TS)
The SPIRIT1 can provide an analog temperature indication as a voltage level, which is
available at the GPIO_0 pin. The voltage level V0 at room temperature (or any other useful
reference temperature) should be acquired and stored by the MCU in order to compensate
for the offset. The relationship between temperature and voltage is the following:
Equation 1
where V
Two output modes are available: buffered or not buffered (high output impedance, about 100
kΩ). The latter mode is the default one.
The TS function is available in every operating mode. When enabled, the internal logic
allows the switching on of all the necessary circuitry.
40/91Doc ID 022758 Rev 2
is the voltage at temperature T0.
0
SPIRIT1Block description
To enable the TS function, the user must perform the following operations:
●Set to 1 the TS bit in the ANA_FUNC_CONF[0] register
●Program as “Analog” (00) the GPIO_MODE field in the GPIO0_CONF register (other
fields are neglected)
●Optionally, enable the buffered mode (the EN_TS_BUFFER bit in the PM_CONFIG[2]
register).
As the TS function requires the internal bias circuit operation, the overall current
consumption in STANDBY, SLEEP, and READY modes is increased by 400 µA.
8.11 AES encryption co-processor
The SPIRIT1 provides data security support as it embeds an advanced encryption standard
(AES) core which implements a cryptographic algorithm in compliance with NIST FIPS 197.
Three registers are available to use the AES engine of SPIRIT1:
●AES_KEY_IN [15:0]: R/W type register (128-bit), used to provide the key to use
●AES_DATA_IN [15:0]: R/W type register (128-bit), used to provide the input to the AES
engine
●AES_DATA_OUT [15:0]: R type register (128-bit), used to retrieve the output of the AES
operation.
The core processes 128-bit data blocks using 128-bit keys.
The AES can be accessed in any of the SPIRIT1 operation modes.
To turn on the AES engine, the AES_ON bit in the ANA_FUNC_CONF[0] register must be
set.
Once the AES engine is on, it processes the operations according to the commands sent.
The SPIRIT1 engine provides 4 different operations:
1.Encryption using a given encryption key (AES Enc command). In this operation, the
MCU puts the encryption key into the AES_KEY_IN[15:0] register and the data to
encrypt into the AES_DATA_IN[15:0]. The MCU sends the AES Enc command and
when the AES_EOP (end of operation) is issued, the MCU can retrieve the data
encrypted from AES_DATA_OUT[15:0]
2. Decryption key derivation starting from an encryption key (AES Key command). In this
operation, the MCU puts the encryption key into AES_DATA_IN[15:0]. The MCU sends
the AES Key command and when the AES_EOP (end of operation) is issued, the MCU
can retrieve the decryption key from AES_DATA_OUT[15:0]
3. Data decryption using a decryption key (AES Dec command). In this operation, the
MCU puts the decryption key into the AES_KEY_IN[15:0] register and the data to
decrypt into AES_DATA_IN[15:0]. The MCU sends the AES Enc command and when
the AES_EOP (end of operation) is issued, the MCU can retrieve the data decrypted
from AES_DATA_OUT[15:0].
Data decryption using a decryption key (AES KeyDec command). In this operation, the MCU
puts the encryption key into the AES_KEY_IN[15:0] register and the data to decrypt into
AES_DATA_IN[15:0]. The MCU sends the AES Enc command and when the AES_EOP
(end of operation) is issued, the MCU can retrieve the data decrypted from
AES_DATA_OUT[15:0].
Doc ID 022758 Rev 241/91
Transmission and receptionSPIRIT1
9 Transmission and reception
9.1 PA configuration
The PA output power level can be configured by programming the PA_POWER[8:0] register
bank. The user can store up to eight output levels to provide flexible PA power ramp-up and
ramp-down at the start and end of a frequency modulation transmission as well as ASK
modulation shaping.
The power levels of the ramp are controlled by 7-bit words (PA_LEVEL_x, x=0÷7), according
to the following table:
Table 24.PA_level
[dBm]
P
PA_LEVEL_xComment
OUT
(170MHz)
0
1Maximum output power11
…
300
…
42-6
…
90Minimum level-34
91-127ReservedN/A
No output power: output stage in high impedance
mode and all circuits switched off.
-
The power ramping is enabled by the PA_RAMP_ENABLE bit. If enabled, the ramp starts
from the level defined by the word PA_LEVEL_0 and stops at the level defined by the word
PA_LEVEL_x, where x is the value of the 3-bit field PA_LEVEL_MAX_INDEX. So, a
maximum of 8 steps can be set up. Figure 8 describes the levels table and shows some
examples.
Each step is held for a time interval defined by the 2-bit field PA_RAMP_STEP_WIDTH. The
step width is expressed in terms of bit period units (T
/8=Tb/2). Therefore the PA ramp may last up to 4 Tb (about 3.3 ms if the bit rate is 1.2
The set of 8 levels is used to shape the ASK signal. In this case, the modulator works as a
counter that counts up when transmitting a one and down when transmitting a zero. The
counter counts at a rate equal to 8 times the symbol rate (in this case, the field
PA_RAMP_STEP_WIDTH is not used). The counter saturates at PA_LEVEL_MAX_INDEX
and 0 respectively. This counter value is used as an index of the Tab le 2 8 PA level to
associate the relevant POUT value. Therefore, in order to utilize the whole table,
PA_LEVEL_MAX_INDEX should be 7 when ASK is active. The real shaping of the ASK
signal is dependent on the configuration of the PA_LEVEL_x registers. Figure 8 shows
some examples of ASK shaping.
For OOK modulation, the signal is abruptly switched between two levels only, these are
PA_LEVEL_0 and PA_LEVEL_x, with x=PA_LEVEL_MAX INDEX.
The 2-bit CWC field in the PA_POWER register bank can be used to tune the internal
capacitive load of the PA (up to 3.6 pF in steps of 1.2 pF) in order to optimize the
performance at different frequencies.
9.2 RF channel frequency settings
RF channels can be defined using the CHSPACE and CHNUM registers.
Doc ID 022758 Rev 243/91
Transmission and receptionSPIRIT1
CHNUMCHSPACE
2
f
fff
15
XO
offsetbasec
⋅
⎟
⎠
⎞
⎜
⎝
⎛
⋅++=
18
XO
base
2
SYNT
2
D)*(B
f
=f
=
=
=
=
=
23rofehtwoldnab(961zHM,SB5)
61rof eht wol dnab zHM003( ot ,zHM843 SB )4
21rof eht elddim dnab zHM783( ot ,zHM074 SB )3
6rof eht hgih dnab morf( zHM977 ot ,zHM659 SB )1
B
very
{{
D
1 if REFDIV 0 (internal reference divider is disabled)
2 if REFDIV 1 (internal reference divider is enabled)
⎩
⎨
⎧
=
OFFSET_FC
2
f
f
18
XO
offset
⋅=
The channel center frequency can be programmed as:
Equation 2
This allows the setting of up to 256 channels with a programmable raster. The raster
granularity is about 793 Hz at 26 MHz and becomes about 1587 Hz at 52 MHz.
The actual channel spacing is from 793 Hz to 202342 Hz in 793 Hz steps for the 26 MHz
configuration and from 1587 to 404685 Hz in 1587 Hz steps for the 52 MHz configuration.
The base carrier frequency, i.e. the carrier frequency of channel #0, is controlled by the
SYNT0, SYNT1, SYNT2, and SYNT3 registers according to the following formula:
Equation 3
where:
●f
is the frequency of the XTAL oscillator (typically 24 MHz, 26 MHz, 48 MHz, or 52
XO
MHz)
●SYNT is a programmable 26-bit integer.
Equation 4
Equation 5
The offset frequency is a correction term which can be set to compensate the crystal
inaccuracy after e.g. lab calibration.
Equation 6
where:
●FC_OFFSET is a 12-bit integer (expressed as 2's complement number) set by the
FC_OFFSET[1:0] registers
Furthermore, the selection between VCOH (“high”) and VCOL (“low”) in the frequency
synthesizer according to the band selected and the VCO threshold is required.
44/91Doc ID 022758 Rev 2
SPIRIT1Transmission and reception
If the center frequency is below the frequency threshold for that frequency band, the VCO_L
must be selected by setting the bit 2 VCO_L_SEL field in the SYNTH_CONFIG register.
If the center frequency is above the frequency threshold for that frequency band, VCO_H
must be selected by setting the bit 1 VCO_ H _SEL field in the SYNTH_CONFIG register.
Table 25.Frequency threshold
Frequency threshold for each band (MHz)
Very low bandLow bandMiddle bandHigh band
161281250322562500430083334860166667
1. By default, the VCO_H is selected.
(1)
The user must make sure that actual frequency programming is inside the specified
frequency range. The accuracy of the offset is about 99 Hz for the 26 MHz reference and
about 198 Hz for the 52 MHz reference.
9.3 RX timeout management
In SPIRIT1, the RX state is specifically time monitored in order to minimize power
consumption. This is done by a RX timeout approach, which aborts the reception after T
timeout expiration. The timer used to control RX timeout is controlled by the registers
RX_TIMEOUT_PRESCALER and RX_TIMEOUT_COUNTER . However, to avoid the
reception to be interrupted during a valid packet, a number of options to stop the timeout
timer are available for the user. They are based on the received signal quality indicators (see
Section 9.7 for a full description of them):
●CS valid
●SQI valid
●PQI valid
RX
More specifically, both 'AND' or 'OR' boolean relationships among any of them can be
configured. This is done using the selection bit RX_TIMEOUT_AND_OR_SELECT in
PCKT_FLT_OPTIONS register. To choose which of the quality indicators should be taken
into account in the AND/OR Boolean relationship, the user should use the mask bits
available in the PROTOCOL[2] register.
The full true-table including any logical AND/OR among such conditions is reported in
When reception is aborted on timeout expiration, the packet is considered not valid and will
be discarded.
It is responsibility of the user to choose the proper boolean condition that suit its application.
In particular, it is required to include always SQI valid check, to avoid to stay in RX state for
unlimited time, if timeout is stopped but no valid SQI is detected (in such cases, the RX state
can be left using a SABORT command).
CS_TIMEOUT_MASK
SQI_TIMEOUT
_MASK
PQI_TIMEOUT_M
ASK
Description
Both RSSI AND SQI above
threshold
Both RSSI AND PQI above
threshold
Both SQI AND PQI above
threshold
RSSI OR SQI above
threshold
RSSI OR PQI above
threshold
SQI OR PQI above
threshold
It is also important to notice that, in case a packet is received, that the timeout is stopped by
some of the conditions in order to get an RX data ready interrupt, otherwise SPIRIT1 will
wait in RX mode for the RX timeout to expire anyway.
9.4 Intermediate frequency setting
The intermediate frequency (IF) is controlled by the register IF_OFFSET and can be set as
follow:
Equation 7
where f
The recommended IF value is 480 kHz resulting in IF_OFFSET setting as in the following
The following modulation formats are supported: 2-FSK, GFSK, MSK, OOK, and ASK. The
actual modulation format used is controlled by the MOD_TYPE field of the MOD0 register:
●MOD_TYPE =
–0 (00): 2-FSK
–1 (01): GFSK
–2 (10): ASK/OOK
–3 (11): MSK
In 2-FSK and GFSK modes, the frequency deviation is controlled by the FDEV register
With this solution the maximum deviation for the 26 MHz case is limited to about 355 kHz,
but this is still acceptable since the maximum useful deviation is about 125 kHz (MSK @ 500
kbps).
In GFSK mode the Gaussian filter BT product can be set to 1 or 0.5 by the field BT_SEL of
the MOD0 register.
In MSK mode, the frequency deviation is automatically set to ¼ of the data rate and the
content of the FDEV register is ignored.
The calculation done inside the modem assumes that the digital clock is equal to the
synthesizer reference. Hence, in the 52-MHz case the MSK can actually be configured by
setting the frequency deviation to ¼ of the data rate through the FDEV registers as for
normal 2-FSK. The same is true for GMSK mode, which can be configured by setting the
frequency deviation to ¼ of the data rate through the FDEV registers as for normal GFSK
with Gaussian filter BT equal to 1 or 0.5.
OOK and ASK
If MOD_TYPE = 2 and power ramping is enabled, then ASK is used; otherwise, if
MOD_TYPE = 2 and power ramping is disabled, then OOK is used.
When OOK is selected, a bit '1' is transmitted with the power specified by
PA_POWER[PA_LEVEL_MAX_INDEX], a bit '0' is transmitted with the power specified by
PA_POWER[0](normally set to PA off).
When ASK is selected, a bit '1' is transmitted with a power ramp increasing from
PA_POWER[0] to PA_POWER[PA_LEVEL_MAX_INDEX], a bit '0' is transmitted with a
power ramp decreasing from PA_POWER[PA_LEVEL_MAX_INDEX] to PA_POWER[0]. The
duration of each power step is 1/8 of the symbol time.
If more '1's are transmitted consecutively, the PA power remains at
PA_POWER[PA_LEVEL_MAX_INDEX] for all '1's following the first one; If more '0's are
transmitted consecutively, the PA power remains at PA_POWER[0] for all '0's following the
first one.
For test and measurement purposes the device can be programmed to generate a
continuous wave carrier without any modulation by setting the CW field of the MOD0
register. Be sure to use infinite timeout in RX mode to avoid the SPIRIT1 going back to
READY mode.
9.5.1 Data rate
The data rate is controlled by the MOD0 and MOD1 registers according to the following
formula:
Equation 9
where:
●DATARATE_M is an 8-bit integer ranging from 0 to 255
●DATARATE_E is a 4-bit integer ranging from 0 to 15
●f
The minimum data rate at f
MHz. Be advised that performance for such values is not guaranteed.
is the digital clock frequency (typically 26 MHz).
clk
= 26 MHz is about 25 Hz; the maximum data rate is about 1.6
clk
9.5.2 RX channel bandwidth
The bandwidth of the channel filter is controlled by the CHFLT_M and CHFLT_E fields of the
CHFLT register according to Ta bl e 2 8. The actual filter bandwidth for any digital clock
frequency can be obtained by multiplying the values in Ta bl e 2 9 by the factor f
The bandwidth values are intended as double-sided.
Table 28.CHFLT_M and CHFLT_E value for channel filter bandwidth (in kHz, for f
E=0E=1E=2E=3E=4E=5E=6E=7E=8E=9
M=0800.1450.9224.7112.356.128.014.07.03.51.8
M=1795.1425.9212.4106.253.026.513.36.63.31.7
M=2768.4403.2201.1100.550.225.112.66.33.11.6
M=3736.8380.8190.095.047.423.711.95.93.01.5
M=4705.1362.1180.790.345.122.611.35.62.81.4
M=5670.9341.7170.685.342.621.310.65.32.71.3
M=6642.3325.4162.481.240.620.310.15.12.51.3
M=7586.7294.5147.173.536.718.49.24.62.31.2
/26000000.
clk
= 26 MHz)
clk
M=8541.4270.3135.067.533.716.98.44.22.11.1
Doc ID 022758 Rev 249/91
Transmission and receptionSPIRIT1
Although the maximum TX signal BW should not exceed 750 kHz, the bandwidth of the
channel select filter in the receiver may need some extra bandwidth to cope with tolerances
in transmit and receive frequencies which depend on the tolerances of the used crystals.
9.6 Data coding and integrity check process
9.6.1 FEC
The device provides hardware support for error correction and detection.
Error correction can be either enabled or disabled according to link reliability and power
consumption needs. Convolutional coding with a rate=½ and k=4 is applied on the payload
and CRC before transmission (poly [13,17]). On the receiver side, error correction is
performed using soft Viterbi decoding.
To further improve error correction performance, a data interleaver is used when
convolutional coding is enabled. Data interleaving/de-interleaving is performed using a 4x4bit matrix interleaver.
To fill the entire matrix, at least 2 bytes of data payload are required (16 cells). In the
interleaver matrix, the encoded data bits are written along the rows and the sequence to
send to the modulator is obtained by reading the matrix elements along the columns of the
matrix. Consequently, in the de-interleaver, the received data from the demodulator are
written into the matrix along the columns, and sent to the FEC decoder reading them from
the rows of the de-interleaving matrix. Due to the size of the matrix, the overall data
transmitted must be an exact integer multiple of two, to fill the rows and columns of the
matrix. If necessary, the framer is able to add automatically extra bytes at the end of the
packet, so the number of bytes is an number.
FEC and interleaving are enabled/disabled together.
To enable FEC/INTERL, the field FEC_EN of PCKTCTRL1 must be set to ‘1’. When
FEC/INTERL is enabled, the number of transmitted bits is roughly doubled, hence the on-air
packet duration in time is roughly doubled as well. The data rate specified in Section 9.5.1
always applies to the on-air transmitted data.
A termination byte is automatically appended to set the encoder to the 0-state at the end of
the packet.
9.6.2 CRC
Error detection is implemented by means of cyclic redundancy check codes.
The length of the checksum is programmable to 8, 16, or 24 bits.
The CRC can be added at the end of the packet by the field CRC_MODE of the register
PCKCTRL1.
50/91Doc ID 022758 Rev 2
SPIRIT1Transmission and reception
AM03940v1
To ut
Tx
01
2
34
5
6
7
8
The following standard CRC polynomials can be selected:
●CRC mode = 1, 8 bits: the poly is (0x07) X
●CRC mode = 2, 16 bits: the poly is (0x8005) X
●CRC mode = 3, 16 bits: the poly is (0x1021) X
●CRC mode = 4, 24 bits: the poly is (0x864CFB)
24+X23+X18+X17+X14+X11+X10+X7+X6+X5+X4+X3
X
●CRC is calculated over all fields excluding preamble and synchronization word.
8+X2
16+X15+X2
16+X12+X5
+X+1
+1
+1
+X+1
9.6.3 Data whitening
To prevent short repeating sequences (e.g., runs of 0's or 1's) that create spectral lines,
which may complicate symbol tracking at the receiver or interferer with other transmissions,
the device implements a data whitening feature. Data whitening can optionally be enabled
by setting the filed WHIT_EN of the PCKTCTRL1 register to '1'. Data whitening is
implemented by a maximum length LFSR generating a pseudo-random binary sequence
used to XOR data before entering the encoding chain. The length of the LSFR is set to 9
bits. The pseudo-random sequence is initialized to all 1's.
Data whitening, if enabled, is applied on all fields excluding the preamble and the
synchronization words.
At the receiver end, the data are XOR-ed with the same pseudo-random sequence.
Whitening is applied according to the following LFSR implementation:
Figure 9.LFSR block diagram
It is recommended to always enable data whitening.
9.6.4 Data padding
If FEC is enabled then the total length of payload and CRC must be an even number (in
order to completely fill up the interleaver). If not, a proper filling byte is automatically inserted
in transmission and removed by the receiver. The total packet length is affected, and it is
configured automatically enabling the FEC.
Doc ID 022758 Rev 251/91
Transmission and receptionSPIRIT1
9.7 Packet handler engine
Before on-the-air transmission, raw data is properly cast into a packet structure. The
SPIRIT1 offers a highly flexible and fully programmable packet; the structure of the packet,
the number, the type, and the dimension of the fields inside the packet depend on one of the
possible configuration settings. Through a suitable register the user can choose the packet
configuration from three options: STack, WM-Bus, and Basic.
The current packet format is set by the PCK_FRMT field of the PCKTCTRL3 register. In
particular:
●0 Basic packet format
●2 MBUS packet format
●3 STack packet format.
The general packet parameters which can be set by the user are listed and described
hereafter. Some particular restrictions are possible depending on the selected packet
format.
9.7.1 STack packet
1-321-40-16 bit110-42 bit1 bit0-655350-3
Preamble SyncLength
Dest.
address
Source
address
Control Seq. No. NO_ACK PayloadCRC
Preamble (programmable field): the length of the preamble is programmable from 1 to 32
bytes by the PREAMBLE_LENGTH field of the PCKTCTRL2 register. Each preamble byte is
a '10101010' binary sequence.
Sync (programmable field): the length of the synchronization field is programmable (from 1
to 4 bytes) through dedicated registers. The synchronization word is programmable through
registers SYNC1, SYNC2, SYNC3, and SYNC4. If the programmed sync length is 1 then
only the SYNC1 word is transmitted; if the programmed sync length is 2 then only SYNC1
and SYNC2 words are transmitted and so on.
Length (programmable/optional field): the packet length field is an optional field that is
defined as the cumulative length of Address (2 bytes always), Control, and Payload fields. It
is possible to support fixed and variable packet length. In fixed mode, the field length is not
used.
Destination address (programmable field): When the destination address filtering is
enabled in the receiver, the packet handler engine compares the destination address field of
the packet received with the value of register TX_SOURCE_ADDR. If broadcast address
and/or multicast address filtering are enabled the packet handler engine compares the
destination address with the programmed broadcast and/or multicast address.
Source address (programmable field): is filled with the value of register
TX_SOURCE_ADDR. When source address filtering is enabled in the receiver, the packet
handler engine compares the source address received with the programmed source
address reference using the source mask address programmed.
The field ADDRESS_LEN of the PCKTCTRL4 register must be set always to 2.
52/91Doc ID 022758 Rev 2
SPIRIT1Transmission and reception
Control (programmable/optional field): is programmable from 0 to 4 bytes through the
CONTROL_LEN field of the PCKTCTRL4 register. Control fields of the packet can be set
using the TX_CTRL_FIELD[3:0] register.
Sequence number (programmable field): is a 2-bit field and contains the sequence number
of the transmitted packet. It is incremented automatically every time a new packet is
transmitted. In the receiver it is used (together with the CRC field) to detect if the received
packet is new or retransmitted. It can be re-loaded with the value in the
TX_SEQ_NUM_RELOAD[1:0] field of the PROTOCOL[2] register, by using the
SEQUENCE_UPDATE command.
NO_ACK (programmable field): 1 means for the receiver that the packet is not to be autoacknowledged. It is programmed by the bit field NACK_TX of the register PROTOCOL[2]. It
is important set to 0 this bit field in any other packet format.
Payload (programmable/optional field): the device supports both fixed and variable payload
length transmission from 0 to 65535 bytes.
On the transmitter, the payload length is always set as: PCKTLEN1 × 256 + PCKTLEN0.
On the receiver, if the field FIX_VAR_LEN of the PCKTCTRL2 register is set to 1, the
payload length is directly extracted from the received packet itself; if FIX_VAR_LEN is set to
0, the payload length is controlled by the PCKTLEN0 and PCKTLEN1 registers as the
transmitter.
In variable length mode, the width of the binary field transmitted, where the actual length of
payload is written, can be configured through the field LEN_WIDTH of the PCKTCTRL3
register according to the maximum length expected in the specific application.
Example 1
●If the variable payload length is from 0 to 31 bytes, then LEN_WIDTH = 5
●If the variable payload length is from 0 to 255 bytes, then LEN_WIDTH = 8
●If the variable payload length is from 0 to 65535 bytes, then LEN_WIDTH = 16.
CRC (programmable/optional field): There are different polynomials CRC: 8 bits, 16 bits (2
polynomials are available) and 24 bits. When CRC automatic filtering is enabled, the
received packet is discarded automatically when CRC check fails.
9.7.2 Wireless M-Bus packet (W M-BUS, EN13757-4)
The WM-BUS packet structure is shown in the figure below (refer to EN13757 for details
about sub-mode specific radio setting).
The preamble consists of a number of chip sequences '01' whose length depends on the
chosen sub-mode according to EN13757-4. The length can be programmed using the
MBUS_PRMBL_CTRL, from a minimum to a maximum dictated from the standard
specification.
Doc ID 022758 Rev 253/91
Transmission and receptionSPIRIT1
1st block, 2nd block, and optional blocks: can be defined by the user. The packet handler
engine uses the Manchester or the “3 out of 6” encoding for all the blocks according to the
defined sub-mode.
The postamble consists of a number of chip sequences '01' whose length depends on the
chosen sub-mode according to EN13757-4. The length can be programmed using the
MBUS_PSTMBL_CTRL, from a minimum to a maximum dictated from the standard
specification.
The sub-mode can be chosen setting the MBUS_SUBMODE[2:0] field of the MBUS_CTRL
register. There are 5 possible cases:
●Submode S1, S2 (long header) (MBUS_SUBMODE=0):
–Header length = MBUS_PRMBL_CTRL + 279 (in '01' bit pairs)
–Sync word = 0x7696 (length 18 bits)
●Submode S1-m, S2, T2 (other to meter) (MBUS_SUBMODE =1):
–Header length = MBUS_PRMBL_CTRL + 15 (in '01' bit pairs)
–Sync word = 0x7696 (length 18 bits)
●Submode T1, T2 (meter to other) (MBUS_SUBMODE =3):
–Header length = MBUS_PRMBL_CTRL + 19 (in '01' bit pairs)
–Sync word = 0x3D (length 10 bits)
●Submode R2, short header (MBUS_SUBMODE =5):
–Header length = MBUS_PRMBL_CTRL + 39 (in '01' bit pairs)
–Sync word = 0x7696 (length 18 bits).
●Submode N1, N2, short header:
–Header length = 8 (in '01' bit pairs)
–Sync word = 0xF68D (length 18 bits).
9.7.3 Basic packet
1-321-40-16 bit0-10-40-655350-3
PreambleSyncLengthAddressControlPayloadCRC
Preamble (programmable field): the length of the preamble is programmable from 1 to 32
bytes by the PREAMBLE_LENGTH field of the PCKTCTRL2 register. Each preamble byte is
a '10101010' binary sequence.
Sync (programmable field): the length of the synchronization field is programmable (from 1
to 4 bytes) through dedicated registers. The synchronization word is programmable through
registers SYNC1, SYNC2, SYNC3, and SYNC4. If the programmed sync length is 1, then
only SYNC word is transmitted; if the programmed sync length is 2 then only SYNC1 and
SYNC2 words are transmitted and so on.
Length (programmable/optional field): the packet length field is an optional field that is
defined as the cumulative length of Address, Control, and Payload fields. It is possible to
support fixed and variable packet length. In fixed mode, the field length is not used.
Destination address (programmable/optional field): when the destination address filtering
is enabled in the receiver, the packet handler engine compares the destination address field
of the packet received with the value of register TX_SOURCE_ADDR. If broadcast address
54/91Doc ID 022758 Rev 2
SPIRIT1Transmission and reception
and/or multicast address filtering are enabled, the packet handler engine compares the
destination address with the programmed broadcast and/or multicast address.
Control (programmable/optional field): is programmable from 0 to 4 bytes through the
CONTROL_LEN field of the PCKTCTRL4 register. Control fields of the packet can be set
using the TX_CTRL_FIELD[3:0] register.
Payload (programmable/optional field): the device supports both fixed and variable payload
length transmission from 0 to 65535 bytes.
On the transmitter, the payload length is always set as: PCKTLEN1 × 256 + PCKTLEN0.
On the receiver, if the field FIX_VAR_LEN of PCKTCTRL2 register is set to 1, the payload
length is directly extracted from the received packet itself; if FIX_VAR_LEN is set to 0, the
payload length is controlled by the PCKTLEN0 and PCKTLEN1 registers as the transmitter.
Furthermore, in variable length mode, the width of the binary field transmitted, where the
actual length of payload is written, must be configured through the field LEN_WIDTH of the
PCKTCTRL3 register according to the maximum length expected in the specific application.
Example 1
●If the variable payload length is from 0 to 31 bytes, then LEN_WIDTH = 5
●If the variable payload length is from 0 to 255 bytes, then LEN_WIDTH = 8
●If the variable payload length is from 0 to 65535 bytes, then LEN_WIDTH = 16.
CRC (programmable/optional field): There are different polynomials CRC: 8 bits, 16 bits (2
polynomials are available) and 24 bits. When the CRC automatic filtering is enabled, the
received packet is discarded automatically when the CRC check fails.
9.7.4 Automatic packet filtering
The following filtering criteria to automatically reject a received packet are supported:
●CRC filtering
●Destination address filtering
●Source address filtering
●Control field filtering.
Packet filtering is enabled by the AUTO_PCKT_FLT field of the PROTOCOL register and the
filtering criteria can be controlled by the PCK_FLT_OPT and PCK_FLT_GOALS registers.
Each filtering option works on the correct packet format according to Ta bl e 2 9.
●CRC: the received packet is discarded if CRC is not passed. To enable this automatic
filtering feature the bit field CRC_CHECK of the PCK_FLT_OPT register must be set.
●Destination address: this automatic filtering feature works on my address, broadcast
address and/or multicast address of the receiver.
–Destination vs. my address: the received packet is discarded if the destination
address received does not match the programmed my address of the receiver. My
address can be programmed for the receiver in the TX_SOURCE_ADDR register.
To enable this automatic filtering option the bitfield DEST_VS_SOURCE_ADDR of
the PCKT_FLT_OPTIONS register must be set.
–Destination vs. broadcast address: the received packet is discarded if the
destination address received does not match the programmed broadcast address
of the receiver. The broadcast address can be programmed for the receiver in the
BROADCAST register. To enable this automatic filtering option the bitfield
Doc ID 022758 Rev 255/91
Transmission and receptionSPIRIT1
DEST_VS_BROADCAST_ADDR of the PCKT_FLT_OPTIONS register must be
set.
–Destination vs. multicast address: the received packet is discarded if the
destination address received does not match the programmed multicast address
of the receiver. The multicast address can be programmed for the receiver in the
MULTICAST register. To enable this automatic filtering option the bitfield
DEST_VS_MULTICAST_ADDR of the PCKT_FLT_OPTIONS register must be
set.
More than one automatic filtering option can be enabled at the same time.
Source address: the received packet is discarded if the source address received does not
match the programmed source address reference through the source mask address (the
reference value used for the comparison is the reference one in AND bitwise with the source
mask). The source address reference can be programmed for the receiver in the
RX_SOURCE_ADDR register and the source address mask in the RX_SOURCE_MASK
register. To enable this automatic filtering option the bitfield SOURCE_FILTERING of the
PCKT_FLT_OPTIONS register must be set.
Control: the received packet is discarded if the control field received does not match the
programmed control reference through the control mask (the reference value used for the
comparison is the reference one in AND bitwise with the control mask). The control
reference can be programmed for the receiver in the CONTROLx_FIELD registers and the
control field mask in the CONTROLx_MASK registers. To enable this automatic filtering
option the bitfield CONTROL_FILTERING of the PCKT_FLT_OPTIONS register must be
set.
Table 29.Packet configuration
Destination address filteringOptionalNoOptional
Broadcast and multicast
addressing
Source address filteringOptionalNoNo
Custom filteringOptionalNoOptional
CRC filteringOptionalNoOptional
When a filtering mechanism is enabled the packet is signaled to the MCU only if the check is
positive, otherwise the packet is automatically discarded.
9.7.5 Link layer protocol
SPIRIT1 has an embedded auto-ACK and auto-retransmission available through the STack
packet format.
Automatic acknowledgment
Automatic acknowledgment is enabled on the receiver by setting the bitfield AUTO_ACK of
the PROTOCOL register. In this way, after the receiver receives a packet with success, it
sends an ACK packet only if the NO_ACK bit of the received packet is 1. This gives an
STackMBUSBasic
OptionalNoOptional
56/91Doc ID 022758 Rev 2
SPIRIT1Transmission and reception
opportunity for the transmitter to tell the receiver if the packet sent must be acknowledged or
not. The ACK request can be put in the packet (NO_ACK packet's bitfield at 1) by setting the
NACK_TX field of the PROTOCOL[2] register.
If the ACK request is ON (NO_ACK packet's bitfield at 1), the transmitter stays in RX state to
receive an ACK packet until the RX timeout, programmed with the
RX_TIMEOUT_PRESCALER and RX_TIMEOUT_COUNTER, expires.
If the transmitter does not receive any ACK packet when it must, the packet transmitted is
considered lost, and the TX_DATA_SENT in the IRQ_STATUS register remains at 0.
Automatic acknowledgment with piggybacking
The receiver can fill the ACK packet with data. To do so, the receiver must fill the TX FIFO
with the payload it must transmit and the bitfield PIGGYBACKING of PROTOCOL[1] register
must be set.
Automatic retransmission
If the transmitter does not receive the ACK packet, it can be configured to do another
transmission. This operation can be repeated up to 15 times. To configure how many times
this operation must be performed, the field NMAX_RETX of the PROTOCOL[2] register is
used.
9.8 Data modes
Direct modes are primarily intended to completely bypass all the framer/deframer
operations, in order to give the user maximum flexibility in the choice of frame formats,
controlled by the field TXSOURCE of the PCKTCTRL1 register. In particular:
TXSOURCE =
●0 - normal modes
●1 - direct through FIFO: payload bytes are continuously read from the TX FIFO and
transmitted without any processing (no preamble, no sync, no coding, etc.). It is the
responsibility of the microcontroller to avoid any underflow conditions on the TX FIFO.
●2 - direct through GPIO: payload bits are continuously read from one of the GPIO ports
and transmitted without any processing (no preamble, no sync, no coding, etc.). To
allow the synchronization of an external data source, a data clock signal is also
provided on one of the GPIO ports. Data are sampled by the device on the rising edge
of such clock signal; it is the responsibility of the external data source to provide a
stable input at this edge.
●3 - PN9 mode: a pseudo-random binary sequence is generated internally. This mode is
provided for test purposes only.
To improve flexibility, the entire packet related functions can be bypassed and the device can
operate in one of the following direct modes, controlled by the field RXMODE of
PCKTCTRL3. In particular:
Doc ID 022758 Rev 257/91
Transmission and receptionSPIRIT1
RXMODE =
●0 - normal modes
●1 - direct through FIFO: payload bytes are continuously received and written to the RX
FIFO without any processing (no preamble search, no sync, no decoding, etc.). It is the
responsibility of the microcontroller to avoid any overflow conditions on the RX FIFO.
●2 - direct through GPIO: payload bits are continuously written to one of the GPIO ports
without any processing (no preamble search, no sync, no decoding, etc.). To allow the
synchronization of an external data sink, a data clock signal is also provided on one of
the GPIO ports. Data are updated by the device on the rising edge of such clock signal
so the MCU must read it during falling edge of CLK.
9.9 Data FIFO
In the SPIRIT1 there are two data FIFOs, a TX FIFO for data to be transmitted and an RX
FIFO for the received data.
The length of both FIFOs is 96 bytes.
The SPI interface is used to read from the RX FIFO and write to the TX FIFO (see
Figure 10) starting from the address 0xFF.
58/91Doc ID 022758 Rev 2
SPIRIT1Transmission and reception
&)&/
&)&/ALMOSTFULL
THRESHOLD
&)&/ALMOSTEMPTY
THRESHOLD
!-6
Figure 10. Threshold of the linear FIFO
The FIFO has two programmable thresholds: FIFO almost full and FIFO almost empty.
The FIFO almost full event occurs when the data crosses the threshold from below to above.
The TX FIFO almost empty threshold can be configured using the field txaethr in the
FIFO_CONFIG[0] register. The RX FIFO almost empty threshold can be configured using
the field rxaethr in the FIFO_CONFIG[2] register.
The FIFO almost empty event occurs when the data crosses the threshold from above to
below. The TX FIFO almost full threshold can be configured using the field txafthr in the
FIFO_CONFIG[1] register. The RX FIFO almost full threshold can be configured using the
field rxafthr in the FIFO_CONFIG[3] register.
Another event occurs when the FIFO goes into overflow or underflow.
The overflow happens when the data in the FIFO are more than 96 bytes. The underflow
happens when the SPIRIT1 accesses the FIFO locations to read data, but there is no data
present.
Doc ID 022758 Rev 259/91
Transmission and receptionSPIRIT1
For example:
●If it reads from the RX FIFO more data than the actual number of bytes in it, the RX
FIFO underflow/overflow error occurs for an underflow event.
●If the SPIRIT1 receives a lot of data to fill the RX FIFO and exceeds the 96 bytes limit,
an RX FIFO underflow/overflow error occurs for an overflow event.
●If it sends more data than the actual number of bytes in the TX FIFO, the TX FIFO
underflow/overflow error occurs for an underflow event.
●If it writes more than 96 bytes in the TX FIFO, a TX FIFO underflow/overflow error
occurs for an overflow event.
An easy way to clean the FIFOs is to use the flush commands: FLUSHTXFIFO for the TX
FIFO and FLUSHRXFIFO for the RX FIFO.
The write TX FIFO operation needs an extra SPI transaction to write correctly the last byte
into the TX FIFO. Usually, this last SPI transaction is generated from the TX command sent
to transmit the data, otherwise a dummy SPI transaction must be done.
Using the auto-retransmission feature of the SPIRIT1 (packet format STack), if the packet is
more than 96 bytes, the packet must be reloaded into the TX FIFO by the MCU. However, if
the payload is 96 bytes or less, the SPIRIT1 handles the payload and it is not necessary to
reload the data into the TX FIFO at each retransmission.
●In addition, if the transmitter does not receive the ACK packet, the payload remains in
the TX FIFO. The user can decide to clean the TX FIFO or re-send the data again. If
the payload is more than 96 bytes, only the last part of the payload that fits the TX FIFO
remains in it.
9.10 Receiver quality indicators
The following quality indicators are associated to the received signal:
●Received signal strength indicator (RSSI)
●Link quality indicator (LQI)
●Preamble quality indicator (PQI)
●Synchronization quality indicator (SQI).
9.10.1 RSSI
The received signal strength indicator (RSSI) is a measurement of the received signal power
at the antenna measured in the channel filter bandwidth.
The measured power is reported in steps of half a dB from 0 to 255 and is offset in such a
way that -120 dBm corresponds to about 20.
RSSI reading is available after the reception of a packet in the RSSI_LEVEL register.
9.10.2 Carrier sense
The carrier sense functionality can be used to detect if any signal is being received, the
detection is based on the measured RSSI value. There are 2 operational modes for carrier
sensing: static and dynamic.
60/91Doc ID 022758 Rev 2
SPIRIT1Transmission and reception
When static carrier sensing is used (CS_MODE = 0), the carrier sense signal is asserted
when the measured RSSI is above the value specified in the RSSI_TH register and is deasserted when the RSSI falls 3 dB below the same threshold.
When dynamic carrier sense is used (CS_MODE = 1, 2, 3), the carrier sense signal is
asserted if the signal is above the threshold and a fast power increase of 6, 12, or 18 dB is
detected; it is de-asserted if a power fall of the same amplitude is detected.
The carrier sense signal is also used internally for the demodulator to start the AFC and
timing recovery algorithms and for the CSMA procedure (for this use it should be set to
cs_mode = 0).
The carrier sense function is controlled by the following parameters:
RSSI threshold: this parameter sets the minimum signal power above which the carrier
sense signal is asserted (RSSI_TH register).
CS mode: this parameter controls the carrier sense operational modes (RSSI_FLT register,
allowed values 0...3):
●CS_MODE = 0 static carrier sensing
●CS_MODE = 1 dynamic carrier sensing with 6 dB dynamic threshold
●CS_MODE = 2 dynamic carrier sensing with 12 dB dynamic threshold
●CS_MODE = 3 dynamic carrier sensing with 18 dB dynamic threshold.
9.10.3 LQI
The link quality indicator is a 4-bit value available through the LINK_QUALIF[0] register. Its
value depends on the noise power on the demodulated signal. The lower the value, the
noisier the signal. Be aware that comparing LQI values measured with different modulation
formats or data rate may lead to inconsistent results.
9.10.4 PQI
The preamble quality indicator (PQI) is intended to provide a measurement of the reliability
of the preamble detection phase.
This indicator counts the number of consecutive bit inversions in the received data stream.
The PQI ranges from 0 to 255. It is increased by 1 every time a bit inversion occurs, while it
is decreased by 4 every time a bit repetition occurs.
It is possible to set a preamble quality threshold in such a way that, if PQI is below the
threshold, the packet demodulation is automatically aborted at/after a timeout after the start
of RX.
If the preamble quality indicator check is enabled (field PQI_EN of the QI register set to '1'),
the running peak PQI is compared to a threshold value and the preamble valid IRQ is
asserted as soon as the threshold is passed. The preamble quality threshold is 4×PQI_TH
(PQI_TH = 0...15).
9.10.5 SQI
The synchronization quality indicator (SQI) is a measurement of the best correlation
between the received synchronization word and the expected one. The value representing a
perfect match is 8×SYNC_LENGTH.
Doc ID 022758 Rev 261/91
Transmission and receptionSPIRIT1
This indicator is calculated as the peak cross-correlation between the received data stream
and the expected synchronization word.
It is possible to set a synchronization quality threshold in such a way that, if SQI is below the
threshold, the packet demodulation is automatically aborted.
If the synchronization quality indicator check is enabled (field SQI_EN of the QI register set
to '1'), the running peak SQI is compared to a threshold value and the sync valid IRQ is
asserted as soon as the threshold is passed. The preamble quality threshold is equal to 8 ×
SYNC_LEN - 2xSQI_TH with SQI_TH = 0..3. When SQI_TH is 0, a perfect match is
required; when SQI_TH = 1, 2, 3 then 1, 2, or 3-bit errors are respectively accepted.
It is recommended to always enable the SQI check.
RX timeout mechanism
In order to reduce power consumption, a few automatic RX timeout modes are supported.
RX timeout applies both to normal receive mode and to the LDCR mode.
Infinite timeout: in this mode RX is stopped when the packet ends or the SABORT command
strobe is issued (default).
Carrier sense timeout: RX is aborted if the RSSI never exceeds a programmed threshold
within Trx timeout.
SQI timeout: in this mode RX is aborted if the synchronization quality indicator (SQI) never
exceeds a programmed threshold within Trx timeout.
PQI timeout: in this mode RX is aborted if the preamble quality indicator (PQI) never
exceeds a programmed threshold within Trx timeout.
The value of Trx timeout can be programmed ranging from ~1 µs to ~3 sec.
9.11 Antenna diversity
The device implements a switching based antenna diversity algorithm. The switching
decision is based on a comparison between the received power level on antenna 1 and
antenna 2 during the preamble reception.
The antenna switching function allows to control an external switch in order to select the
antenna providing the highest measured RSSI.
When antenna switching is enabled, the two antennas are repeatedly switched during the
reception of the preamble of each packet, until the carrier sense threshold is reached
(static carrier sense mode must be used). From this point on, the antenna with the highest
power is selected and switching is frozen. The switch control signal is available on GPIO and
in the MC_STATE[1] register.
The algorithm is controlled by the following parameters:
●AS_MEAS_TIME: this parameter controls the time interval for RSSI measurement
(ANT_SELECT_CONF register, allowed values 0...7). The actual measurement time is:
(c)
c. The user should make sure to provide a preamble sufficiently long to allow the algorithm to choose the final
antenna.
62/91Doc ID 022758 Rev 2
SPIRIT1Transmission and reception
XO
time_meas_AS
E
meas
f
2224
T
ChFlt
⋅⋅
=
Equation 10
●AS_ENABLE: this parameter enables the antenna switching function
In order to ensure good link reliability in an interference corrupted scenario, the device
supports frequency hopping, managed by the MCU; in particular, the SPIRIT1 supports
slow frequency hopping, meaning that the systems change frequency at a rate slower than
the information rate.
Depending on the desired blanking interval (the time during a hop), frequency hopping can
be done by performing the complete PLL calibration for each channel hop, or reading in the
suitable register calibration data calculated at startup and stored in the non-volatile memory
of the MCU. The former solution gives a long blanking interval but is more robust compared
with supply voltage and temperature variation. The latter provides a shorter blanking time
but is sensitive to voltage and temperature variation and requires memory space to store
calibration data for each channel involved in hopping.
Communication with the MCU goes through a standard 4-wire SPI interface and 4 GPIOs.
The device is able to provide a system clock signal to the MCU.
MCU performs the following operations:
●Program the SPIRIT1 in different operating modes by sending commands
●Read and write buffered data, and status information from the SPI
●Get interrupt requests from the GPIO pins
●Apply external signals to the GPIO pins.
10.1 Serial peripheral interface
The SPIRIT1 is configured by a 4-wire SPI-compatible interface (CSn, SCLK, MOSI, and
MISO). More specifically:
●CSn: chip select, active low
●SCLK: bit clock
●MOSI: data from MCU to SPIRIT1 (SPIRIT1 is the slave)
●MISO: data from SPIRIT1 to MCU (MCU is the master).
As the MCU is the master, it always drives the CSn and SCLK. According to the active SCLK
polarity and phase, the SPIRIT1 SPI can be classified as mode 1 (CPOL=0, CPHA=0),
which means that the base value of SCLK is zero, data are read on the clock's falling edge
and data are changed on the clock's rising edge. The MISO is in tri-state mode when CSn is
high. All transfers are done most significant bit first.
The SPI can be used to perform the following operations:
●Write data (to registers or FIFO queue)
●Read data (from registers or FIFO queue)
●Write commands.
When accessing the SPI interface, the two status bytes of the MC_STATE[1:0] registers are
sent to the MISO pin. The timing diagrams of the three operations above are reported below.
Figure 11. SPI “write” operation
64/91Doc ID 022758 Rev 2
SPIRIT1MCU interface
3#,+
#3N
-/3)
!
(EADER"YTE
$ATAREADFROM!DDRESS$ATAREADFROM!DDRESS
72
!#
$ONT#ARE
4RI3TATE
! ! ! ! ! !
!
3PIRIT-EMORY-AP!DDRESS
$ $ $ $ $ $ $ $$ $ $ $ $ $ $$
-)3/
3 3 3 3 3 3 33 3 3
3 3 3
33 3
3PIRIT3TATUSBITS
!-6
3#,+
#3N
-/3)
#
(EADER"YTE
72
!#
$ONT#ARE
4RI3TATE
# # #
# #
# #
3PIRIT#OMMAND#ODE
-)3/
3 3 3 3 3 3 33 3 3
3 3 3
33 3
3PIRIT3TATUSBITS
!-6
Figure 12. SPI “read” operation
Figure 13. SPI “command” operation
Concerning the first byte, the MSB is an A/C bit (Address/Commands: 0 indicates that the
following byte is an address, 1 indicates that the following byte is a command code), while
the LSB is a W/R bit (Write/Read: 1 indicates a read operation). All other bits must be zero.
Read and write operations are persistently executed while CSn is kept active (low), the
address being automatically incremented (burst mode).
Accessing the FIFO is done as usual with the read and write commands, by putting, as the
address, the code 0xFF. Burst mode is available to access the sequence of bytes in the
FIFO. Clearly, RX-FIFO is accessed with a read operation, TX-FIFO with a write operation.
Details of the SPI parameters are reported below.
Doc ID 022758 Rev 265/91
MCU interfaceSPIRIT1
Table 30.MCU clock vs. state
SymbolParameterMin.Typ.Max.Unit
f
SCLK
t
t
rise
t
t
t
t
SCLK frequency
CSn low to positive edge on SCLK2μs
sp
Clock rise timens
Clock fall timens
fall
Setup data (positive SCLK edge) to negative edge on
sd
SCLK
Hold data after negative edge on SCLKns
hd
Negative edge on SCLK to CSn highns
ns
10.2 Interrupts
In order to notify the MCU of a certain number of events an interrupt signal is generated on
a selectable GPIO. The following events trigger an interrupt to the MCU:
Table 31.Interrupts
BitEvents groupInterrupt event
0
1RX data discarded (upon filtering)
2TX data sent
MHz
--
ns
RX data ready
3Max. re-TX reached
4CRC error
5TX FIFO underflow/overflow error
Packet oriented
6RX FIFO underflow/overflow error
7TX FIFO almost full
8TX FIFO almost empty
9RX FIFO almost full
10RX FIFO almost empty
11Max. number of backoff during CCA
12
13Sync word detected
Signal quality related
Valid preamble detected
14RSSI above threshold (carrier sense)
66/91Doc ID 022758 Rev 2
SPIRIT1MCU interface
Table 31.Interrupts (continued)
BitEvents groupInterrupt event
15
16READY
17STANDBY state switching in progress
Wake-up timeout in LDCR mode
(2)
(1)
18Low battery level
19Power-on reset
20Brownout event
21LOCK
29Timer relatedRX operation timeout
30OthersAES end–of–operation
1. The interrupt flag n.15 is set (and consequently the interrupt request) only when the XO clock is available
for the state machine. This time may be delayed compared to the actual timer expiration. However, the real
time event can be sensed putting the end-of-counting signal on a GPIO output.
2. The interrupt flag n.16 is set each time the SPIRIT1 goes to READY state and the XO has completed its
setting transient (XO ready condition detected).
All interrupts are reported on a set of interrupt status registers and are individually
maskable. The interrupt status register must be cleared upon a read event from the MCU.
The status of all the interrupts is reported on the IRQ_STATUS[3:0] registers: bits are high
for the events that have generated any interrupts. The interrupts are individually maskable
using the IRQ_MASK[3:0] registers: if the mask bit related to a particular event is
programmed at 0, that event does not generate any interrupt request.
10.3 GPIOs
Device status related
The total number of GPIO pins is 4. Each pin is individually configurable.
Digital outputs can be selected from the following (see GPIOx_CONF register):
Table 32.Digital outputs
I/O
selection
0nIRQ (interrupt request, active low)
1POR inverted (active low)
2Wake-up timer expiration: ‘1’ when WUT has expired
3Low battery detection: ‘1’ when battery is below threshold setting
4TX data internal clock output (TX data are sampled on the rising edge of it)
5TX state indication: ‘1’ when the SPIRIT1 is transiting in the TX state
6TX FIFO almost empty flag
7TX FIFO almost full flag
8RX data output
Doc ID 022758 Rev 267/91
Output signal
MCU interfaceSPIRIT1
Table 32.Digital outputs (continued)
I/O
selection
9RX clock output (recovered from received data)
10RX state indication: ‘1’ when SPIRIT1 is transiting in the RX state
11RX FIFO almost full flag
12RX FIFO almost empty flag
13Antenna switch used for antenna diversity
14Valid preamble detected flag
15Sync word detected flag
16
17MCU clock
18TX or RX mode indicator (to enable an external range extender)
19VDD (to emulate an additional GPIO of the MCU, programmable by SPI)
20GND (to emulate an additional GPIO of the MCU, programmable by SPI)
21External SMPS enable signal (active high)
22Device in SLEEP or STANDBY states
23Device in READY state
24Device in LOCK state
RSSI above threshold (same indication as bit CS in the LINK_QUALIF[1]
register)
Output signal
25Device waiting for a high level of the lock-detector output signal
26
27Device waiting for a high level of the READY2 signal from XO
28Device waiting for timer expiration to allow PM block settling
29Device waiting for end of VCO calibration
30Device enables the full circuitry of the SYNTH block
31
Device waiting for timer expiration before starting to sample the lock-detector
output signal
Device waiting for a high level of the RCCAL_OK signal from the RCO
calibrator
All interrupts are reported on a set of interrupt status registers and are individually
maskable. The interrupt status register must be cleared upon a read event from the MCU.
The status of all the interrupts is reported on the IRQ_STATUS[3:0] registers: bits are high
for the events that have generated any interrupts. The interrupts are individually maskable
using the IRQ_MASK[3:0] registers: if the mask bit related to a particular event is
programmed at 0, that event does not generate any interrupt request.
Digital inputs can be selected from the following (see GPIOx_CONF register):
68/91Doc ID 022758 Rev 2
SPIRIT1MCU interface
Table 33.Digital inputs
I/O selectionInput signal
01 >> TX command
11 >> RX command
2TX data input for direct modulation
3Wake-up from external input (sensor output)
4External clock @ 34.7 kHz (used for DLC modes timing)
From 5 to 31Not used
The only available analog output is the temperature sensor, see Section 8.10.
10.4 MCU clock
SPIRIT1 can directly provide the system clock to the MCU in order to avoid the use of an
additional crystal. The clock signals for the MCU can be available on the GPIO pins. The
source oscillator can be the internal RCO or the XO depending on the active state. When
XO is active, it is the source clock (the RCO is not available in this condition).
In addition, different ratios are available and programmable through the MCU_CK_CONF
configuration register, as described in Tabl e 3 4.
In STANDBY state, no oscillator is available as the clock source. In order to allow the MCU
to better handle this event, and avoid a potential dead state situation, a dedicated procedure
is forecasted when the SPIRIT1 enters STANDBY state. A few extra clock cycles can be
provided to the MCU before actually stopping the clock (an interrupt is generated to notify
the MCU of this event).
The number of extra cycles can be programmed through the MCU_CK_CONF configuration
register to 0, 64, 256, or 512. The MCU can make use of these cycles to prepare to standby
or to switch on any auxiliary clock generator. The maximum transition time from READY to
STANDBY is then:
Equation 11
where f
is the digital clock frequency (typically 26 MHz).
clk
The transition to SLEEP state causes the MCU clock source to change from XO to RCO.
Similarly, when the SPIRIT1 exits SLEEP to any active state, the source is the XO. Both
these transitions are implemented in order to be glitch-free. This is guaranteed by
synchronizing both transitions, switching on the rising or falling edge of the RCO clock.
The clock provided to the MCU depends on the current state:
Table 35.MCU clock vs. state
StateSource oscillatorMCU clock
SHUTDOWNN/AN/A
STANDBYN/ATail
SLEEPRC OscRC/1 or RC/128
READY
TUNING
RX
TX
XTALXTAL/N
70/91Doc ID 022758 Rev 2
SPIRIT1Register table
11 Register table
This section describes all the registers used to configure the SPIRIT1. The description is
structured in sections according to the register usage.
SPIRIT1 has three types of registers:
●Read and write (R/W), which can be completely managed by SPI using READ and
WRITE operations
●Read-only (R)
●Read-and-reset (RR), is automatically cleared after a READ operation.
A further category of special registers collects the ones which cannot be categorized in any
of the three mentioned above R/W, R, or RR.
The fields named as “Reserved” must not be overridden by the user, otherwise, behavior is
not guaranteed.
of the PLL programmable
divider. See Equation 2 of
Section 7.1
SYNT[12:5], intermediate bits
of the PLL programmable
divider. See Equation 2 of
Section 7.1
SYNT[4:0], lowest bits of the
PLL programmable divider. See
Equation 2 of Section 7.1
Synthesizer band select. This
parameter selects the out-ofloop divide factor of the
synthesizer (B in Equation 2 of
Section 7.1).
1: 6 Band select factor for high
band
2: 8 Band select factor for high
band
3: 12 Band select factor for
middle band
4: 16 Band select factor for low
band
5: 32 Band select factor for very
low band
CHSPACE0x0C7:0CH_SPACING0xFCR/W
IF_OFFSET0x0D7:0IF_OFFSET0xA3R/W
7:4Reserved0
FC_OFFSET[1]0x0E
R/W
3:0FC_OFFSET[11:8]0
FC_OFFSET[0]0x0F7:0FC_OFFSET[7:0]0R/W
7Reserved0R/W
PA _P O W ER [ 8 ]0 x 1 0
6:0PA_LEVEL_7
000001
1
7Reserved0R/W
PA _P O W ER [ 7 ]0 x 1 1
6:0PA_LEVEL_6
000111
0
Channel spacing in steps of
/215 (~793 for fXO = 26 MHz,
f
XO
~732 for f
= 24 MHz).
XO
Intermediate frequency (see
Section 9.4)
Carrier offset in steps of
/218 and represented as 12
f
XO
bits 2-complement integer. It is
added / subtracted to the
carrier frequency set by the
SYNTx register. This register
can be used to set a fixed
correction value obtained e.g.
from crystal measurements.
1: LDC timer is reloaded with
the value stored in the
LDC_RELOAD registers
1: reload the back-off random
generator seed using the value
R/W
written in the
BU_COUNTER_SEED_MSByt
e / LSByte registers
1: CSMA channel access mode
enabled
1: CSMA persistent (no backoff) enabled
1: automatic packet filtering
mode enabled
Max. number of re-TX (from 0
to 15).
0: re-transmission is not
performed
1: field NO_ACK=1 on
transmitted packet
R/W
1: automatic acknowledgement
after correct packet reception
1PERS_RX0
0PERS_TX0
TIMERS[5]0x53
TIMERS[4]0x54
TIMERS[3]0x55
82/91Doc ID 022758 Rev 2
47:40RX_TIMEOUT_PRE
SCALER[7:0]
39:32RX_TIMEOUT_COU
NTER[7:0]
31:24LDC_PRESCALER[7
:0]
1: persistent reception enabled
1: persistent transmission
enabled
Prescaler value of the RX
TIMEOUT timer. When this
1R/W
0R/W
1R/W
timer expires the SPIRIT1 exits
RX state. Can be controlled
using the quality indicator (SQI,
LQI, PQI, CS).
Counter value of the RX
TIMEOUT timer. When this
timer expires the SPIRIT1 exits
RX state. Can be controlled
using the quality indicator (SQI,
LQI, PQI, CS)
Prescaler value of the LDC
wake-up timer. When this timer
expires the SPIRIT1 exits
SLEEP state.
wake-up timer. When this timer
expires the SPIRIT1 exits
SLEEP state.
Prescaler value of the LDC
reload timer. When this timer
expires the SPIRIT1 exits
SLEEP state. The reload timer
value is used if the SYNC word
is detected (by the receiver) or
if the LDC_RELOAD command
is used.
Counter part of the LDC reload
value timer. When this timer
expires the SPIRIT1 exits
SLEEP state. The reload timer
value is used if the SYNC word
is detected (by the receiver) or
if the LDC_RELOAD command
is used.
The MSB value of the counter
of the seed of the random
number generator used to
apply the BBE algorithm during
the CSMA algorithm
CSMA_CONFIG[2]0x657:0
CSMA_CONFIG[1]0x66
BU_COUNTER_SEE
D_LSByte
BU_PRESCALER[5:
7:2
0R/W
0]
000001
R/W
1:0CCA_PERIOD00
7:4CCA_LENGTH[3:0]0000
CSMA_CONFIG[0]0x67
3Reserved0
R/W
2:0NBACKOFF_MAX000Max. number of back-off cycles
TX_CTRL_FIELD[3]0x687:0TX_CTRL30R/W
TX_CTRL_FIELD[2]0x697:0TX_CTRL20R/W
TX_CTRL_FIELD[1]0x6A7:0TX_CTRL10R/W
TX_CTRL_FIELD[0]0x6B7:0TX_CTRL00R/W
The LSB value of the counter
seed of the random number
generator used to apply the
BBE algorithm during the
CSMA algorithm
The prescaler value used to
program the back-off unit BU
Used to program the T
(64 / 128 / 256 / 512 × T
Used to program the T
cca
bit
listen
time
)
time
Control field value to be used in
TX packet as byte n.3
Control field value to be used in
TX packet as byte n.2
Control field value to be used in
TX packet as byte n.1
Control field value to be used in
TX packet as byte n.0
In order to meet environmental requirements, ST offers these devices in different grades of
®
ECOPACK
packages, depending on their level of environmental compliance. ECOPACK
specifications, grade definitions, and product status are available at: www.st.com.
ECOPACK is an ST trademark.
Table 42.QFN20 (4 x 4 mm.) mechanical data
Dim.
Min.Typ.Max.
A0.800.901.00
A10.020.05
b0.180.250.30
D3.854.004.15
D22.552.702.80
E3.854.004.15
E22.552.702.80
e0.450.500.55
L0.300.400.50
ddd0.08
mm.
88/91Doc ID 022758 Rev 2
SPIRIT1Package mechanical data
7169619_F
Figure 14. QFN20 (4 x 4 mm.) dimension
Doc ID 022758 Rev 289/91
Revision historySPIRIT1
13 Revision history
Table 43.Document revision history
DateRevisionChanges
06-Feb-20121Initial release.
Update RF performance figures in the whole document.
26-Apr-20122
Changed pinout for pin 11.
Minor text changes.
90/91Doc ID 022758 Rev 2
SPIRIT1
Please Read Carefully:
Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the
right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any
time, without notice.
All ST products are sold pursuant to ST’s terms and conditions of sale.
Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no
liability whatsoever relating to the choice, selection or use of the ST products and services described herein.
No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this
document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products
or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such
third party products or services or any intellectual property contained therein.
UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS
OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS EXPRESSLY APPROVED IN WRITING BY TWO AUTHORIZED ST REPRESENTATIVES, ST PRODUCTS ARE NOT
RECOMMENDED, AUTHORIZED OR WARRANTED FOR USE IN MILITARY, AIR CRAFT, SPACE, LIFE SAVING, OR LIFE SUSTAINING
APPLICATIONS, NOR IN PRODUCTS OR SYSTEMS WHERE FAILURE OR MALFUNCTION MAY RESULT IN PERSONAL INJURY,
DEATH, OR SEVERE PROPERTY OR ENVIRONMENTAL DAMAGE. ST PRODUCTS WHICH ARE NOT SPECIFIED AS "AUTOMOTIVE
GRADE" MAY ONLY BE USED IN AUTOMOTIVE APPLICATIONS AT USER’S OWN RISK.
Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void
any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any
liability of ST.
ST and the ST logo are trademarks or registered trademarks of ST in various countries.
Information in this document supersedes and replaces all information previously supplied.
The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.