• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 53 subscribers
  • Views 590 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC1101: Use of deprecated strobe command SAFC (0x37)?

Michael Connolly77
Prodigy 20 points
Part Number: CC1101
Other Parts Discussed in Thread: CC1100

I am working on debugging some legacy code which repeatedly sends strobe command 0x37 to its CC1101 radio.  This command is no longer listed in the CC1101 datasheet, but is defined in the source code's headers as SAFC, and I see in older versions of the CC1100 datasheet that it was once listed (removed in June 2006 - "References to SAFC strobe removed.")

I'm wondering what the effect, if any, of sending this strobe command would be on current CC1101 hardware.

Thanks!

  • 0
    TI__Guru* 86731 points

    Hi

    I have been digging through old internal documentation, and as far as I can see you cannot do any harm when using this command. However, the results was not as good as we hoped for, and we saw better results by doing the compensation manually, as described in the attached document.

    Siri

    DN015_Permanent_Frequency_Offset_Compensation.pdf

  • 0 in reply to Siri
    Prodigy 20 points

    Hi Siri,

    Thanks for writing back.  Do you know if the command will have any mode effects on the radio?  Is it valid at all times?  Does it have literally no effect, or just not 'much of one?'

    Thanks much,

    Michael

  • 0 in reply to Michael Connolly77
    TI__Guru* 86731 points
    I have not been able to dig up too much info about this. Since it is not longer documented I would off course remove it from the code. However, I have not found any reports indicating that something will go wrong if the command is being issued. The only thing I have been able to find is a report saying that doing the compensation manually gave better results. It might be that there has been timing issues with the command, so that if not issued at the correct time, no compensation has been done.