1. Set DC_PAUSE to 1, and there are several possibilities:
a) If it is currently in the RX state, it will immediately exit to the STBY state.
b) If it is currently in the TX state, it will exit to the STBY state after sending the set N packets(the
spectrum will be spurious if it exits immetiately).
c) If it is currently in the SLEEP state, it will exit to the STBY state after the sleep timer ends.
d) If it is currently in the TUNE state, it will go to the RX or TX state first, and then switch as the
described above.
2. No matter what kind of possibility, MCU can scan the CHIP_MODE_STA<3:0> register until the chip is
confirmed to have entered the STBY.
3. Reconfiguring the Duty-Cycle associated register will turn off the full-automatic mode(other registers can
also be configured). After completing the configuration, set DC_PAUSE to 0, or else it cannot enter
SLEEP.
4. Send the go_sleep command to let the configuration take effect, the system will stay at SLEEP and wait
for the MCU to continue.
Why does the chip wait until the TX operation is completed or the SLEEP timer is over to switch to STBY
after setting DC_PAUSE to 1? This is to allow the chip 100% guarantee to safely exit from the auto run mode.
Otherwise, the system may receive the command at any time and will exit at any time. This will not guarantee
the reliability. If the user sets a long sleep and does not want to wait that long before exiting, it is
recommended that the user exits in second way. The process is as follows:
1. Set CONF_RETAIN to 1, and if initialization is set, there is no need to do so again. Make sure
SLEEP_BYPASS_EN is set to 0.
2. Send the soft reset or the external reset.
3. Scan the CHIP_MODE_STA<3:0> register until the chip is confirmed to enter the SLEEP state.
4. Send the go_stby command immediately to switch the chip to the STBY mode.
5. Then configure, send go_sleep after completion.
This operation will not use the DC_PAUSE register because the MCU can be sure that the chip can send
the go_stby command after it is initialized to enter the SLEEP status. That is, when the MCU is unable to
confirm exactly what status the chip is in, it cannot send any go_* command to do the manual switching,
otherwise it does not guarantee the reliability and has the chance to crash.
So in general, it's OK to let users use the first method to exit. The second one is used when there is a
special requirement. It is important to note that the two mechanisms that exit from the full-automatic
Duty-Cycle mode must be operated only after the CMT2300A has entered the full-automatic Duty-Cycle mode,
otherwise an operation error occurs.
To Next Page
Loading...
