• State Verified Answer
  • Locked Locked
  • Replies 13 replies
  • Subscribers 74 subscribers
  • Views 2942 views
  • Users 0 members are here
Attachments (6) Download All
Nordic Case Info
  • Case ID: 276928
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF9160 goes to sleep and becomes stuck in idle task

NelsonGoncalves

Hello,

I am using the Nordic SDK at v1.5.0, to create an application that runs on the Nordic nRF9160. 

In the typical use case scenario, my application is mains powered and once per day is contacted by our remote TCP client, for a readout or sensor data.

However I noticed that when left unattended, after about 1h30 ~2h it appears to go into some sort of power saving (or sleep ?) mode, enters the Zephyr idle task and remains there.

It is also not reachable by our remote client.

I have disabled all power saving options for the modem part, so I do not understand why or how this could be occuring. As far as I can tell, there are no power related registers on the user CPU of the nRF9160 that can be configured to prevent this sleep mode.

So my question is, how can I prevent the application from going into power saving (or sleep) mode ? 

Thanks in advance,

 Nelson Gonçalves

  • 0 in reply to Didrik Rokhaug

    Hi,

    Have you had any success reproducing the POLLIN with NCS v1.7.0?

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Hello Didrik,

    Sorry for the late reply. I am now busy with another project, and I could not yet test the POLLIN in v1.7.0

    I will try to do it this week and report back. Sorry again for the delay.

    BR,

    Nelson

  • 0 in reply to NelsonGoncalves

    Hello Didrik,

    I changed my test application a little, to fix the issues that you pointed out, and also I build it using NCS v1.7.0. 

    I left the application running for about 6h30, and the listening socket was always on. It seems that whatever issue was occurring, it got fixed in v1.70.

    For the record, this is the setup on which I tested:

    • nRF9160 SoC
    • HW revision: nRF9160 SICA B0A
    • FW version (modem): 1.3.0
    • NCS v1.7.0

    With this setup, running this demo application 6886.tcp_listen.zip, I never had any connectivity issues. There is a small TCL test client in the ZIP file, which I used to connect to the server running on the nRF9160, throughout the day.

    The longest period without any communication between the client and the server was 3hrs, and again there were no connectivity issues. It seems moving to v1.7.0 fixed the issue.

Related
Terms of service