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.

CC1310: How to mitigate Advisory 09

Part Number: CC1310


Hi,

I am wondering what the proper way to mitigate Advisory 09 is. The errata document is quite light on details, and I was hoping you could elaborate a bit.

  1. What is meant by "If a CC1310 device operates in continuous receive mode for a long period of time"? Are we talking seconds, minutes, days?
  2. What workaround is implemented in SDK v2.20.00.38? Our radio-facing code operates by directly writing to the radio core registers, and it sounds like the suggestion is to turn the receiver off and on again in our case. The device I'm working on should always be listening, so this is not really an acceptable solution, especially when I don't know how often the receiver degradation occurs.

thanks,
Fredrik

  • Hi Fredrik

    The bug described in advisory 09 is caused by the receiver having received a correlation peak from noise or another packet that is higher than what you get from your sync word.

    Since the algorithm searches for the best peak, your sync word will not be accepted.

    Restarting RX will reset the correlator threshold, but if you get a high correlation peak right after RX has been restarted, you might still not be able to receive anything until your next restart of RX.

    If you have good sync word (good autocorrelation properties) it is possible to disable this feature looking for the best peak.

    This can be done by using the following override:

    HW_REG_OVERRIDE(0x5108  , 0x007F)

    The fix that is implemented in the SDK is an updated patch that makes sure that best peak tracker resets whenever a packet is rejected

    BR

    Siri

  • Thank you for the detailed answer, I appreciate it.