• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 621 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.

CC1310: Stuck in standby mode

Andreas Urke
Expert 1480 points
Part Number: CC1310


We have a rare issue where our cc1310 does not recover after going into standby mode. However the issue does not appear in either of these two cases:

1. CC1310 is revision A

2. It is the first run after flashing

We are early in our investigation, but I wanted to query first here if these two quite distinct outliers give any pointers as to where we should start looking? Especially the "first run" is puzzling, I know there is a halt-in-boot flag set in that circumstance, any other differences which could impact this?

  • 0
    TI__Guru**** 317180 points

    - Does CC1310 always end up in the stuck in standby mode if you are not in any of the corner cases? 

     -Do you run from an external 32 kHz tal and if so, have you verified that this works? 

    I assume that the debugger is connected in the "It is the first run after flashing" case? If so, the CC1310 does not go to standby since the JTAG is active. 

    How do you know that the chip is stuck in standby? 

  • 0 in reply to TER
    Expert 1480 points

    > - Does CC1310 always end up in the stuck in standby mode if you are not in any of the corner cases? 

    Not sure if I understand your question...it is 100 % reproducible.The cc1310 always works if in any of the corner cases (if it is a rev. A or if it is first after flashing). On the other hand it always get stuck if this is not the case (if it is a rev. B and it is not first after flashing).

    >  -Do you run from an external 32 kHz tal and if so, have you verified that this works? 

    Yes we do, and thanks for hint, we will verify its operation when cc1310 is stuck (as mentioned this is a rare issue, typically cc1310 operates fine in and out of standby mode).

    > I assume that the debugger is connected in the "It is the first run after flashing" case? If so, the CC1310 does not go to standby since the JTAG is active. 

    Yes. Thanks, I was not aware of the JTAG impacting the power modes - that explains this corner case. Any thoughts on the remaining rev. A corner case?

    > How do you know that the chip is stuck in standby? 

    Just a simple printout when going in and out of it

  • 0 in reply to Andreas Urke
    TI__Guru**** 317180 points

    How do you know that it's stuck in standby based on a printout, do you know for sure that  the print will be performed before/ after standby? 

    Could you also check the VDDR and DCOUPL voltages when you are stuck? 

  • 0 in reply to TER
    TI__Guru**** 317180 points

    Any update? 

  • 0 in reply to TER
    Expert 1480 points

    Sorry, and thanks for following up. Since it is quite rare we have not been able to prioritize, will see if we can measure those voltages soon.

    I had printouts right before going into standby, and right after. So obviously not bullet-proof, it was just part of our preliminary investigation.

  • 0 in reply to Andreas Urke
    TI__Guru**** 317180 points

    Any further update or should I close this one? 

  • 0 in reply to TER
    Expert 1480 points

    Hi, when we get stuck, the VDDR and DCOUPL drops to 0 V

  • 0 in reply to Andreas Urke
    TI__Guru**** 317180 points

    - What is the current consumption in this state? 

    - Does this also happens if you run the empty example (unmodified) from the SDK?

    - Could advisory 12 in  http://www.ti.com/lit/er/swrz062d/swrz062d.pdf case something?

    Are you sure that VDDS is above 1.8V at all times? 

  • 0 in reply to TER
    TI__Guru**** 317180 points

    Any update?