AN811 - Silicon Labs

A N 8 11
S I 100 X / 1 0 1 X TO S I 106 X / 1 0 8 X W I R E L E S S MCU
T RANSITION G UIDE
1. Introduction
This document provides transition assistance from the Si100x/101x wireless MCU family to the Si106x/108x
wireless MCU family. The Si106x/108x represents a new generation of the wireless MCU (WMCU) family with
improved performance and flexibility combined with simplicity and cost efficiency. This document is an overview
comparison to highlight the main differences between these two WMCU families. It is highly recommended to read
the relevant device data sheets and application notes when converting a design from Si100x/101x to Si106x/108x.
2. Benefits of the Transition
The Si106x/108x offers significantly improved radio performance in almost all areas compared to the Si100x/101x.
Key among these are lower current in standby and active mode, overall improved link budget to 146 dB, and
improved phase noise and blocking performance. In addition, the Si106x/108x family has a highly configurable
modem and packet handler to support various application requirements as well as legacy modes of operation. The
Si106x/108x is packaged in a 5 mm x 6 mm QFN-36 package and so requires less board space than the
5 mm x 7 mm LGA-42 Si100x/101x. Customers will also benefit from the new development kits and WDS
improvements, which make it easier to evaluate RF performance and develop application code.
3. Type Comparison
Table 1 lists the Si100x/101x family members, key properties, and recommended replacement types from the
Si106x/108x family. Each replacement type contains the same CPU as the old type, combined with a new radio. In
most cases, there are two replacement types listed. One contains an EZRadioPRO radio (Si446x) for maximum
performance. The other contains an EZRadio radio (Si4455) with slightly limited features/performance and lower
cost. Additional differences in MCU GPIO availability and internal connections are described in Section “4.
Hardware Recommendations”
Table 1. WMCU Replacement Types
Old
WMCU Type
Contained
Radio
Min VDD
Flash Size
Max TX Power
Replacement
WMCU Type
Contained Radio
Si1000
Si443x
1.8 V 64 kB 20 dBm
Si1060
Si4463 EZRadioPRO
Si1001
Si443x
1.8 V 64 kB 20 dBm
Si1061
Si4463 EZRadioPRO
Si1002
Si443x
1.8 V 64 kB 20 dBm
Si1062
Si1064
Si4460 EZRadioPRO
Si4455 EZRadio
Si1003
Si443x
1.8 V 64 kB 20 dBm
Si1063
Si1065
Si4460 EZRadioPRO
Si4455 EZRadio
Si1004
Si443x
0.9 V 64 kB 13 dBm
Si1062
Si1064
Si4460 EZRadioPRO
Si4455 EZRadio
Si1005
Si443x
0.9 V 64 kB 13 dBm
Si1063
Si1065
Si4460 EZRadioPRO
Si4455 EZRadio
Rev. 0.1 12/13
Copyright © 2013 by Silicon Laboratories
AN811
AN811
Table 1. WMCU Replacement Types (Continued)
Old
WMCU Type
Contained
Radio
Min VDD
Flash Size
Max TX Power
Replacement
WMCU Type
Contained Radio
Si1010
Si443x
1.8 V 64 kB 20 dBm
Si1080
Si4463 EZRadioPRO
Si1011
Si443x
1.8 V 64 kB 20 dBm
Si1081
Si4463 EZRadioPRO
Si1012
Si443x
1.8 V 64 kB 20 dBm
Si1082
Si1084
Si4460 EZRadioPRO
Si4455 EZRadio
Si1013
Si443x
1.8 V 64 kB 20 dBm
Si1083
Si1085
Si4460 EZRadioPRO
Si4455 EZRadio
Si1014
Si443x
0.9 V 64 kB 13 dBm
Si1082
Si1084
Si4460 EZRadioPRO
Si4455 EZRadio
Si1015
Si443x
0.9 V 64 kB 13 dBm
Si1083
Si1085
Si4460 EZRadioPRO
Si4455 EZRadio
3.1. DC Characteristic Comparison
Since the MCUs used in both WMCU families are the same, the following comparison table contains only radio
related parameters.
Table 2. DC Characteristics Comparison
Si443x
Si4455/Si446x
Supply Voltage
1.8 to 3.6 V
1.8 to 3.6 V
Ambient Temperature
–40 to 85 °C
–40 to 85 °C
Shutdown Mode Current Consumption
15 nA
30 nA
Standby Mode Current Consumption
450 nA
50 nA
Ready Mode Current Consumption
800 µA
2 mA
Receive Mode Current Consumption
18.5 mA
10.7/13.7 mA
Shutdown To Receive Time
16.8 ms
30 ms/15 ms
Standby To Receive Mode Time
800 µs
460 µs
Ready To Receive Mode Time
200 µs
130 µs
Both radio families work over the same temperature ranges and supply voltages. Some types of both the new and
the old WMCU families allow operation from 0.9 V using the MCU’s built-in dc/dc converter. The majority of the
current consumption and transition times are significantly improved in the Si446x/Si4455 devices. Due to the
different configuration process, the Si4455 boots from shutdown to receive mode longer (30 ms) than the other
radios. However, the significantly improved standby mode current allows use of only the standby mode as low
power state, so there is no need to reboot. Faster turnaround times, lower active currents, and significantly lower
standby current consumption make the Si106x/108x family more desirable in battery-powered applications
compared to the Si100x/101x family.
2
Rev. 0.1
AN811
3.2. RF Parameters Comparison
Table 3. RF Parameters Comparison
Si443x
Si4460/Si4463
Si4455
142–175 MHz (4.7 Hz res.) 283 to 350 MHz (38.1 Hz res.)
283–350 MHz (9.5 Hz res.) 425 to 525 MHz (57.2 Hz res.)
850 to 960 MHz (114.4 Hz
420–525 MHz (14.3 Hz res.)
res.)
850–1050 MHz (28.6 Hz
res.)
Frequency
range
240 to 480 MHz
(156.25 Hz res.)
480 to 960 MHz
(312.5 Hz res.)
RX Channel
BW
2.6 to 620 kHz
1.1 to 850 kHz
40 to 850 kHz
–108 dBm (40 kbps, GFSK,
±20 kHz dev., BER<0.1%)
–110 dBm (40 kbps, GFSK,
+-20 kHz dev., BER<0.1%))
–108 dBm (40 kbps, GFSK,
±25 kHz dev., BER <0.1%)
–52 dBm
–75 dBm
–61 dBm
RX sensitivity
Blocking
1MHz Offset
The wider range of operating frequencies allows the Si446x family to be used in 169 MHz European ISM Bands
(proprietary, social alarm, or Wireless MBUS N mode applications). The narrower Receive channel filter, better
sensitivity, and excellent blocking performance make the Si446x more valuable in narrow-band applications (FCC
Part 90, ETSI Category 1, etc.). The Si4455 targets certain applications where the narrow band operation and the
full frequency coverage are not requirements.
Rev. 0.1
3
AN811
4. Hardware Recommendations
Due to the different package and pinout, it is necessary to modify the application printed circuit board when
transitioning from the Si100x/101x to the Si106x/108x. The following sections summarize the main differences and
provide guidelines for component selection.
4.1. Package and Pinout
The Si106x/108x is packaged in a 5 mm x 6 mm QFN-36 package and so requires less board space than the
5 mm x 7 mm LGA-42 packaged Si100x/101x. There are also differences in the pinout of the devices that is
summarized in the next table.
Table 4. Pinout Difference Summary
Si100x/101x
Si106x/108x
Available on some types
Not available
Connected to P1.4 or P1.3 internally
Connected to P1.3 internally
Available externally
Connected together internally
Radio general purpose IOs
3 radio GPIOs (digital signals or analog input for the internal ADC)
4 radio GPIOs (digital signals or
analog input for the internal
ADC)
ANT Pin
ANT pin can control the RF switch in
an antenna diversity application. It
helps to utilize the GPIOs for other
purposes.
The RF switch control functionality is available on all 4 GPIOs.
It provides flexibility for the HW
designer to select GPIOs for RF
switch control purposes that
result in the most optimal RF
layout.
This feature is not available
Available on some types.
TXRamp pin can be used to
control the TX ramp-up of the
front end module or provide bias
for the external transistor in a
high-output power design.
MCU P1.7 and P2.0-6
Radio NSS pin
Radio SDN pin and MCU GPIO
P0.7
TXRAMP Pin
VR_DIG Pin
Regulated output voltage of the radio No need for capacitor on output
digital LDO. Cannot be loaded exter- of internal LDO (so not available
externally).
nally. 1 µF decoupling capacitor needs
to be connected to this pin.
The following table compares the pinout of all devices. Pin functions that are available on every WMCU are not
listed. Signal names in parenthesis are connected inside the WMCU package and not available externally.
4
Rev. 0.1
AN811
Table 5. Pinout Comparison
Si1000/1/2/3
Si1004/5
Si1010/1/2/3
—
VBAT
—
—
GND/VBAT- —
—
DCEN
P0.7
Si1014/5
VBAT
Si1060/1
Si1080/1
—
Si1062/3
Si1082/3
Si1064/5
Si1084/5
VBAT
VBAT
GND/VBAT- —
GND/VBAT-
GND/VBAT-
—
DCEN
—
DCEN
DCEN
P0.7
P0.7
P0.7
(P0.7/SDN)
(P0.7/SDN)
(P0.7/SDN)
—
—
(P1.3/NSS)
(P1.3/NSS) (P1.3/NSS)
(P1.3/NSS)
(P1.3/NSS)
(P1.4/NSS)
(P1.4/NSS) P1.4
P1.4
P1.4
P1.4
P1.4
P1.7
P1.7
—
—
—
—
—
P2.0
P2.0
—
—
—
—
—
P2.1
P2.1
—
—
—
—
—
P2.2
P2.2
—
—
—
—
—
P2.3
P2.3
—
—
—
—
—
P2.4
—
—
—
—
—
—
P2.5
—
—
—
—
—
—
P2.6
—
—
—
—
—
—
—
—
—
—
GPIO_3
GPIO_3
GPIO_3
SDN
SDN
SDN
SDN
—
—
—
—
—
—
—
TXRAMP
TXRAMP
—
ANT_A
ANT_A
ANT_A
ANT_A
—
—
—
VDD_DIG
VDD_DIG
VDD_DIG
VDD_DIG
—
—
—
VR_DIG
VR_DIG
VR_DIG
VR_DIG
—
—
—
Rev. 0.1
5
AN811
4.2. Reference Design, Component Selection
The typical application circuit for the Si100x WMCU is shown in Figure 1, and the typical application circuit for the
Si106x/8x WMCU is shown in Figure 2.
Figure 1. Si100x Application Example
Figure 2. Si106x Application Example
The architecture of the Receive and Transmit frontends of both radios are similar; therefore, the matching network
topologies are the same in both application examples. Both radios can support different TX matching network
topologies. Refer to the following application notes for more details and comparisons of the different topologies:
AN627:
Si4060/Si4460/61 Low-Power PA Matching
Si4063/4463/64 TX Matching
AN693: Si4455 Low-Power PA Matching
The Si4455/Si446x can run on the same crystal as the Si443x. To utilize a lower-cost crystal in the application, the
Si4455/Si446x is designed to accommodate a wide range of crystal frequencies (25–32 MHz). Refer to “AN785:
Crystal Selection Guide for the Si4x6x RF ICs” for more details on crystal or TCXO selection for the Si4455/Si446x
devices.
AN648:
6
Rev. 0.1
AN811
5. Firmware Recommendations
5.1. Configuration Interface
The radios in both WMCU families can be configured through standard SPI interface, with up to 10 MHz clock
speed.
The SPI interfaces of the radio and MCU are connected internally in the WMCU package. The differences in
connection of the NSS and SDN signals (described in the previous chapter) has to be followed in the firmware also.
An Application Programming Interface (API) is designed for the radios in the Si106x/108x devices over the SPI
interface instead of using a register configuration approach like in the Si100x/101x. The major benefit of the API is
that the radio can execute complex commands and procedures with minimal MCU interaction. This approach helps
reduce the time-critical tasks of the MCU. However, using the API also has some drawbacks:
The command execution time
varies from command to command, and it may take more time than changing
a simple register in the case of very basic commands.
Retrieving status information from the chip requires the following process: issue a command that
addresses what information the MCU is asking for; wait for the radio to prepare the data (wait for the Clear
To Send Signal), and read the actual status information.
For time-critical information, the MCU can access the Fast Response Registers (RSSI, interrupt status, etc.) or use
dedicated HW commands (Transmit FIFO Write, Receive FIFO Read) as well. The complete list of commands and
their descriptions are provided in HTML documents in “EZRadioPRO API Documentation” and “EZRadio API
Documentation” zip files that are available on the Silicon Labs web site at www.silabs.com. The HTML format helps
to navigate more easily within the document. The open/collapse feature of the HTML document also helps to
highlight or hide desired or undesired details for easier readability.
5.2. Radio Power-On Sequence and Configuration
After waiting for the Power-On Reset, the radio in the Si100x/101x is ready to receive configuration commands.
The radio can be initialized by overwriting registers that need to be different than their default value. The value of
the registers needs to be defined by the user based on the data sheet; therefore there is a chance to overlook a
necessary setting that results in unwanted radio behavior.
For the radio in the Si106x/108x, an additional step of sending a power up command is required because the radio
needs to boot up before it is ready to receive configuration commands. Following the boot up, configuration
commands can be sent to the radio according to the desired radio parameters. The desired parameters are set on
a graphical interface of the WDS PC software, which means that configuration commands are generated by the
WDS rather than by the user.
The WDS provides the ability to pick-up predefined, tested radio settings for customers who are not familiar with
RF tradeoffs. The WDS also allows the flexibility to configure any desired radio configuration. The configuration
commands are generated by the WDS in the form of a config header file.
For the Si1064/5 and Si1084/5 devices, which have EZRadio radios, most of the configuration settings are
organized into an array. The consistency of the array is protected with CRC and the array is encoded to prevent bitby-bit changes and the possibility of missing an important configuration setting. The size of the configuration array
is 212 bytes, which need to be stored in the host MCU and may increase the code size compared to the other
WMCUs’ application code.
The configuration array stores all the settings that are typically set during initialization:
Radio
configuration: crystal parameters, frequency band, modulation format, data rate, etc.
content related settings: preamble, synchron word, CRC, etc.
Operation mode: packet-based communication or direct data reception on a GPIO
If the application requires a change in any of the above settings during run-time, then the radio needs to be reset
(toggling the SDN pin) and a new configuration array needs to be sent to the radio.
Packet
In addition to the configuration array, there are settings that can be changed even after the configuration array is
sent to the radio. These settings include fine-tuning parameters (e.g., crystal frequency fine tuning registers),
center frequency, channel spacing, packet content related or interrupt related settings.
Rev. 0.1
7
AN811
Turned off or in SDN state
Turned off or in SDN state
Apply VDD & set SDN=0
Apply VDD & set SDN=0
Power On Reset Power On Reset Max. 5ms
Ready to boot
Typ. 16ms
~15ms
Ready mode
Overwrite necessary registers for initialization
Send BOOT_UP command
Ready for
initiazitation
Send config array
and check
consistency
Radio is initialized
Radio is initialized
Si100x/101x radio initialization
Si106x/108x radio initialization
Figure 3. Radio Initialization Process for the WMCUs
For more information about the WDS and the configuration array, refer to the Programming Guides and Sample
Codes.
5.3. Typical Use Cases
Both WMCU families support the typical use cases: transmitting and receiving packets or transmitting and
receiving data in direct mode (when the data is available or provided through a GPIO instead of via the FIFO). Due
to the API interface of the radios in the Si106x/108x WMCUs, realizing the typical use cases is different than that
for the Si100x/101x WMCUs. The SPI low-layer driver and the high level application logic can be kept; the rest of
the application code needs to be changed.
Both radios have a programming guide with example codes summary showing how the radio needs to be used. In
addition to the improved radio operation, there are also major improvements in the example projects and the
Si106x/108x support tools as well:
The
Si100x/101x example codes are very basic, not partitioned, and therefore a bit difficult to change and
port them to another HW platform. The Si106x/108x example projects are built based on a driver set that is
well partitioned and beside the radio it supports all major peripherals of the evaluation boards too.
The radio configuration of the Si100x/101x example codes need to be configured manually. WDS has a
new feature for the Si106x/108x devices: it can generate example projects with customized radio settings
and packet configuration. The projects can be saved or opened in the Silicon Labs IDE for further FW
development, which reduces the possibility of misconfiguration of the radio and provides complete, tested
C source code for the given use case. It drastically reduces the development time.
For more details refer to the application notes, “AN692: Si4355/4455 Programming Guide” and “AN633:
Programming Guide for EZRadioPRO Si4x6x Devices” for more details on the example projects.
8
Rev. 0.1
AN811
5.4. RX Modem
Both radios use high-performance ADCs that allow channel filtering, image rejection, and demodulation to be
performed in the digital domain. The Si4455/Si446x has an improved digital modem; the differences are
summarized in Table 6.
Table 6. RX Modem Comparison
Specification
Si443x
Si446x
Si4455
Modulation Modes
2GFSK, 2FSK, OOK
2GFSK, 2FSK, 4GFSK, 4FSK,
GMSK, OOK
2GFSK, 2FSK, OOK
(G)FSK Data Rate
0.123–256 kbps
0.1–500 kbps
1.0-500 kbps
4(G)FSK Data Rate
N/A
0.2–1000 kbps
N/A
OOK Data Rate
0.123–40 kbps
0.1–120 kbps
0.5–120 kbps
RX Architecture
Fixed-IF (937.5 kHz)
Fixed-IF (Fxtal/64), zero-IF,
scaled-IF
Fixed-IF (Fxtal/64)
Image Calibration
N/A
Image calibration (IRCAL API command) is available to improve the
image rejection to more than 55 dB
in fixed-IF mode.
N/A
RSSI
Current RSSI can be
read from a register.
The current RSSI is available
through API call or Fast Response
Registers.
RSSI can be latched and stored
upon a system event (preamble/
synch word detection, etc.). For
more accurate RSSI reading, the
radio can average it for various bit
timings.
The radio can provide an interrupt if
the RSSI is changed by a programmable amount during packet reception to detect interfering signals.
The current RSSI is available through the
GET_MODEM_STATUS
API command. RSSI is
latched upon synch word
detection and the latched
value can be read through
Fast Response Register.
The radio can provide an
interrupt if the RSSI
exceeds a programmable
threshold value.
Preamble Detection
RX chain settles and
detect standard preamble (“0101”).
RX chain settles and detects stan- RX chain settles and detects
dard (up to 256 bytes) and custom standard (up to 256 bytes)
preamble pattern (up to 4 bytes).
preamble ("0101").
Rev. 0.1
9
AN811
Table 6. RX Modem Comparison (Continued)
Specification
Si443x
Si446x
Si4455
Automatic RX Hopping and Hop Table
N/A
This feature is intended for RX hopping where the device has to hop
from channel to channel and look
for packets.
It is fully-configurable through the
API interface, including hop table
and hop conditions.
N/A
Manual RX Hopping
N/A
It provides a fast turnaround time
(75 µs) from RX-to-RX that can be
utilized for frequency scanning algorithms.
N/A
The wider data rate and modulation format support make the Si446x more future proof. The extremely-configurable
RX modem makes it possible to design-in the Si446x for legacy product replacement.
Image calibration in fixed-IF mode allows the use of Si446x radios in ultra-narrow-band applications. Refer to
“AN790: Image Rejection and IQ Calibration” for more details on image calibration.
10
Rev. 0.1
AN811
5.5. Packet Handler
Both radios have built-in packet handlers that help to process the received data bits and construct the transmit
packets. Utilizing this feature offloads these time-consuming tasks from the host MCU and allows for the selection
of a simpler, lower-cost MCU.
The CRC and data-Whitening seeds and polynomials are more configurable in the Si446x than in the Si443x and
Si4455.
5.5.1. Receive Packet Handler
The Receive packet handler operation of the Si443x and Si4455 is very basic compared to that of the Si446x.
While the Si443x and Si4455 support only fixed or variable packet length mode operation with optional CRC,
Manchester coding, and data Whitening over the entire packet, the Si446x can be configured for a wide variety of
packet configurations by introducing the FIELD feature.
Config
0, 2, o r 4
Bytes
Con fig
0, 2, o r 4
Bytes
Con fig
0, 2, o r 4
B ytes
C RC Field 5 (op t)
Field 5 (opt)
Data
C RC Field 4 (op t)
Field 4 (opt)
Data
C RC Field 3 (op t)
Field 3 (opt)
Data
Con fig
C RC Field 2 (op t)
1-4 Bytes
F ield 2 (o pt)
Pkt Len gth or Data
Field 1
Header or Data
1-255 Bytes
C RC Field 1 (op t)
Preamble
Sync Word
FIELD is an entity within the packet where the CRC, Manchester coding, and data Whitening settings are fixed
within that entity. The FIELD feature is also mandatory if 4(G)FSK modulation is used. Up to five FIELDs can be
configured within a packet. One of the FIELDs can be of variable length, where the length byte must be present in
an earlier FIELD.
Con fig
0, 2, or 4
Bytes
0, 2, or 4
Bytes
Figure 4. Packet Handler Operation of the Si446x
5.5.2. Transmit Packet Handler
The Si443x can be configured for fixed or variable-length packet transmissions. In fixed packet length mode, the
radio transmits the preamble and the synch word automatically followed by the desired number of bytes from the
TX FIFO. The radio also automatically applies the selected CRC calculation, Manchester coding, or data Whitening
features over the entire packet.
In variable packet length mode, the operation is similar, but there is a length byte transmitted by the radio right after
the synchron word that determines how many bytes will be transmitted from the FIFO.
The Si4455 and Si446x do not have dedicated variable packet length mode operation. The entire packet has to be
filled into the FIFO as it desired to be transmitted, including the length byte on the proper location. Next, the
START_TX command has to be called with the packet length to initiate the packet transmission. The radio
transmits the preamble and the sync word automatically followed by the desired number of bytes from the FIFO
(defined as packet length in the START_TX command).
Rev. 0.1
11
AN811
5.6. Auxiliary Functions
Table 7 summarizes the auxiliary functions of the radios in the WMCUs:
Table 7. Auxiliary Functions
Radio auxiliary
function
Power On Reset
Low Battery Detect
Clock Out for MCU
Si100x
Si101x
Si1060/1/2/3
Si1080/1/2/3
Si1064/5
Si1084/5
Smart Reset
Simple Power On-Reset
Simple Power-On Reset
Battery voltage read
Battery voltage read
Low Battery Threshold Inter- Low Battery Threshold Interrupt
rupt
Battery voltage read
Low Battery Threshold
Interrupt
Derived from the XTAL
Derived from the XTAL
Not available
RSSI
Actual value during reception
RSSI Threshold Interrupt
Actual and latched value
during reception
RSSI Threshold Interrupt
Actual and latched value
during reception
RSSI Threshold Interrupt
Temperature Sensor
Available through the ADC
of the radio
Available through the ADC of
the radio
Available in the MCU
Wake Up Timer
Programmable, runs from
the 32 kHz RC oscillator
Has LDC RX feature
Programmable, runs from the
32 kHz oscillator
Has LDC RX and LDC TX
feature
Not available in the radio.
MCU can wake up the
radio using SmaRTClock
The Si106x/108x has a different radio power-on reset circuit with reduced Standby mode current consumption. It
cannot reset the radio upon rising edge of the supply voltage (called smart reset in Si100x/101x). Refer to the
Si106x/108x data sheet for more details on the radio power-on reset.
Note: If you wish to reset the radio from the host MCU, the SDN pin is intended to be used for that purpose.
The Radio Wake-up Timer (that can wake up the radio and the host MCU regularly to complete scheduled tasks)
has a new feature in the Si1060/1/2/3 and Si1080/1/2/3 devices. It not only provides Low Duty Cycle Reception
(LDC RX), but also Low Duty Cycle Transmission (LDC TX).
In the Si106x/108x devices, there is an 11-bit auxiliary ADC for measuring the battery voltage or an external
voltage over a GPIO. The Si1060/1/2/3 and Si1080/1/2/3 also has an internal temperature sensor. The ADC
utilizes SAR architecture and achieves 11-bit resolution. The Effective Number of Bits (ENOB) is 9 bits. This is an
improvement over the 8-bit SAR architecture of the Si100x/101x devices.
The RSSI can be read from a register in case of the Si100x/101x WMCUs, while it is in Receive mode. In the
Si106x/108x, the RSSI is accessible through the fast response register. In addition to being able to read the RSSI
any time during receive mode, Si106x/108x has a new feature to latch and store the RSSI value upon certain
conditions. This feature helps to offload the host MCU from time critical tasks:
If
a frequency scan algorithm needs to be designed that is based on RSSI measurements, then it is
recommended to latch the RSSI a few bits time later than the receiver has settled. This method provides a
fast way to measure the energy on all frequency channels.
If the application requires knowing the signal strength of the incoming packet, then it is recommended to
latch the RSSI upon preamble or synch word detection.
Both WMCU families can generate an interrupt if the RSSI exceeds a threshold any time during receive mode.
The Wake-up Timer, the Temperature sensor and the MCU Clock Output are not available in the Si1064/5 and
Si1084/5 devices, but the MCU SmaRTClock and Temperature sensor can be used instead. An example project is
available in WDS that implements the LDC mode in the host MCU.
12
Rev. 0.1
AN811
CONTACT INFORMATION
Silicon Laboratories Inc.
400 West Cesar Chavez
Austin, TX 78701
Tel: 1+(512) 416-8500
Fax: 1+(512) 416-9669
Toll Free: 1+(877) 444-3032
Please visit the Silicon Labs Technical Support web page:
https://www.siliconlabs.com/support/pages/contacttechnicalsupport.aspx
and register to submit a technical support request.
Patent Notice
Silicon Labs invests in research and development to help our customers differentiate in the market with innovative low-power, small size, analogintensive mixed-signal solutions. Silicon Labs' extensive patent portfolio is a testament to our unique approach and world-class engineering team.
The information in this document is believed to be accurate in all respects at the time of publication but is subject to change without notice.
Silicon Laboratories assumes no responsibility for errors and omissions, and disclaims responsibility for any consequences resulting from
the use of information included herein. Additionally, Silicon Laboratories assumes no responsibility for the functioning of undescribed features or parameters. Silicon Laboratories reserves the right to make changes without further notice. Silicon Laboratories makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does Silicon Laboratories assume any
liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation
consequential or incidental damages. Silicon Laboratories products are not designed, intended, or authorized for use in applications intended to support or sustain life, or for any other application in which the failure of the Silicon Laboratories product could create a situation where
personal injury or death may occur. Should Buyer purchase or use Silicon Laboratories products for any such unintended or unauthorized
application, Buyer shall indemnify and hold Silicon Laboratories harmless against all claims and damages.
Silicon Laboratories and Silicon Labs are trademarks of Silicon Laboratories Inc.
Other products or brandnames mentioned herein are trademarks or registered trademarks of their respective holders.
Rev. 0.1
13