
A N 6 3 3
74
Rev. 0.7
10.14. Packet Reception with Manual Hopping Capability
The purpose of the standard packet reception with manual hopping feature example code is to demonstrate how
the radio can receive packets in FIFO mode and how rapidly it scans frequency channels to search for signals.
Once the device is configured into the RX state, it automatically starts hopping through the pre-configured channels
on different frequencies. The RX_HOP API command provides the fastest method for hopping from one channel to
another channel but it requires more management by the host MCU. Using the RX_HOP command, the turn-
around time is 75 µs. The timing is faster with this method than using either the START_RX or
RX_HOP_CONTROL (automatic hopping) API commands because one of the calculations required for the
synthesizer calibrations is offloaded from the radio chip. The arguments of the RX_HOP command are calculated
by the Wireless Development Suite. They must be stored by the host that provides them for the radio.
Figure 55. General Working Mechanism of the Manual RX Hopping
Since the host MCU has to provide the pre-calculated synthesizer arguments for the radio, such as the integer
divide and fractional number of the fractional-N PLL, the host MCU needs to handle manually how much time the
radio will spend in channels searching for signals. In every channel, the radio waits for the sync word detected
successfully. If the timer supervised by host MCU expires without detecting the synch word then the host MCU will
control the radio to hop to the next frequency channel manually. Once the correct bytes of sync word are received,
the receiver stays on the channel in order to receive the payload of the packet and to fill it into the RX FIFO. The
radio will not make a decision on staying on a channel or hopping to the next one automatically. There are not any
configurable hop conditions for that purpose. The host MCU is responsible for determining whether to continue
hopping or to stay on a particular channel. The MANUAL_RX_HOP_CHANNEL_X_INPUT_ARGS directive
imported to the application in the “radio_config.h” header file as project specific setting contains the input
arguments for the RX_HOP API command for one dedicated frequency channel. It determines the values of
FREQ_CONTROL_INTE, FREQ_CONTROL_FRAC2, FREQ_CONTROL_FRAC1, FREQ_CONTROL_FRAC API
properties and VCO_CNT1 and VCO_CNT0 properties.
Summary of Contents for EZRADIOPRO Si4060
Page 24: ...AN633 24 Rev 0 7 Figure 20 Supply Current versus Time Diagram from Shutdown to RX State...
Page 67: ...AN633 Rev 0 7 67 Figure 48 Variable Length Packet Reception Flowchart...
Page 69: ...AN633 Rev 0 7 69 Figure 50 Packet Matching Reception Flowchart...
Page 73: ...AN633 Rev 0 7 73 Figure 54 Packet Reception with Automatic RX Hopping Flowchart...
Page 75: ...AN633 Rev 0 7 75 Figure 56 Packet Reception with Manual Rx Hopping...
Page 80: ...AN633 80 Rev 0 7 Figure 62 Long Packet Transmission Workflow...
Page 81: ...AN633 Rev 0 7 81 Figure 63 Long Packet RX Flowchart...