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

LAUNCHXL-CC1310: CC1310 would be frozen in deep sleep using Contiki-NG

YI DA ZHUANG
Prodigy 10 points
Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310

Hi everyone

This problem has bothered me over two months. It has asked in gitter of Contiki-NG, but no one has answers about it.

I need the mesh network in my application, so I choose Contiki-NG.

I built up a testing environment with 10 devices, and using star topology for a simple testing.

For achieving low power, the radio shall be turned off when it isn't needed. It will causes device to enter deep sleep.

Some of devices would be frozen after few days in my tests, and its VDDR dropped to 0V.

In SmartRF Flash Programmer, the devices could not be identified.

If I set the level of LPM to SLEEP, this problem will not appear.

Does anybody could tell me why cc1310 would be frozen or what situation would make VDDR become 0?

  • 0
    TI__Guru**** 317180 points

    I'm not familiar with contiki-NG and I therefore don't know which definition of power modes it uses. From the HW perspective the power modes are defined as:

    I would assume you get issues in standby. In standby the power system is duty cycled meaning that the level of VDDR is recharged at intervals. If you measure VDDR when in standby you will see this. Also see chapter 2 in https://www.ti.com/lit/pdf/swra478. If something happens with the recharge interval the recharge will fail and the VDDR will go to 0 (or worst case, VDDS) 

    One known cause for this is described as in advisory 06 in https://www.ti.com/lit/pdf/swrz062.

    - See if you see the same if you run the empty example from the SDK. This is to test with as simple SW as possible and verify that you don't have a HW issue. 

    - You probably have to simplify your application to the point where you don't see this and see which piece of code that causes this.