• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 221 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC1110-CC1111: Changes in silicon with different Chip versions

Luka234
Prodigy 240 points
Part Number: CC1110-CC1111

Is there a document with provided info about changes introduced with different chip versions (register 0xDF37 VERSION)?

In particular I'm interested in the Sleep Timer. Are there any differences regarding issues around Sleep Timer (slowing down by 128 if entering sleep or changing EVENT0 on 32kHz edge)?

  • 0
    TI__Guru 56590 points

    Hello Luka,

    I believe we only have the errata note:

    CC1110Fx/CC1111Fx Errata Note (Rev. C)

    Which revisions are you working on?

  • 0 in reply to Eirik V
    Prodigy 240 points

    Hello Eirik,

    There is no mention of chip versions in errata.

    We have versions 3 and 4 in our products.

  • 0 in reply to Luka234
    TI__Guru 56590 points

    Hello Luka,

    I am not familiar with the issue you describe for the Sleep Timer, can you explain?

  • 0 in reply to Eirik V
    Prodigy 240 points

    Hello Eirik,

    It is a known issue but not described in errata. You can find multiple instances in forum with that issue.

    For example you can see response from Siri in: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/p/388171/1370573 

    In short - Sleep Timer can slow down by a factor of 128 and only reset can bring Sleep Timer back to normal.

    I need more data regarding that issue. We have more than 20000 devices in the field. Recently some devices are returned as not working and we found that some of them have 128x Sleep Timer slow down issue (I will refer to that issue as "128x state"). We followed all requirements described in the datasheet, errata and forum.

    I'm unable to reproduce "128x state" even when on purpose trying to change EVENT0 and/or entering PM2 on a 32kHz edge. We must know exactly what is happening in order to know how big a problem do we have with devices in the field and how to proceed/fix it.

    • What are the conditions for the chip to enter "128x state"?
    • Can we have example source code which will always (or most likely) put a chip in "128x state"?
    • Is there a difference with different chip revisions regarding "128x state"?

    Best regards

  • 0 in reply to Luka234
    Prodigy 240 points

    Hello Eirik,

    I'm still unable to reproduce "128x state" on test device. Do you have any new information regarding this issue? It is high priority on our side and I don't have any idea where to proceed next. 

    Best regards