This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/CC1352R: EasyLink_getRssi() documentation

Part Number: CC1352R

Tool/software: Code Composer Studio

Can anyone shed some light on the behavior of EasyLink_getRssi()?

I either get a good value or -128 (RF_GET_RSSI_ERROR_VAL). The documentation isn't entirely helpful as to why it does not work sometimes.

Side question: since EasyLink_getRssi() returns a EasyLink_Status, shouldn't that be something other than success when the rssi value it sets is clearly not valid?

What I am ultimately trying to do is assess the noisyness of the environment. Maybe there is a better way to go about this. I'd like to periodically sample the rssi without actually sending or receiving. I'm using EasyLink_transmitCcaAsync() and trying to assess the optimum EASYLINK_CS_RSSI_THRESHOLD_DBM

  • Hello spanky,

    see page 1919 from the technical reference guide:

    CMD_GET_RSSI is an immediate command that takes no parameters, and therefore, can be used as a
    direct command.
    On reception, the radio CPU reads the RSSI from an underlying receiver. The RSSI is returned in result
    byte 2 (bit 23–16) of CMDSTA (see Figure 25-5). The RSSI is given on signed form in dBm. If no RSSI is
    available, this is signaled with a special value of the RSSI (−128, or 0x80).
    If no radio operation command is running, the radio CPU returns the result ContextError in CMDSTA.
    Otherwise, the radio CPU returns DONE along with the RSSI value.
  • So when I get a -128 from EasyLink_getRssi(), then how do I get the RSSI? is EasyLink_getRssi() just whatever the last recent receive saw?
  • Hello Spanky,

    Yes, this is correct if you see a -128, just assume the last reading you saw.

    Regards,
    AB