This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf_cloud_connect failed -111

I am attempting to do the LTE_Gateway example.  I have gotten all the code to build through Segger and upload to the DK.  The problem is when I'm watching the terminal for the 9160 it tries to boot but then it hits an error that says NRF_Cloud_Connect failed -111.

Here is a portion of the output of the trace.  Does anyone know what this error -111 means?


Secure Boot: configure peripherals
Secure Boot: MSP_NS 2002b1c0
Secure Boot: prepare to jump to Non-Secure image
***** Booting Zephyr OS v1.13.99-ncs1-4488-ga76f833d24 *****
Application started
LTE LC config ...
nrf_cloud_connect failed: -111

Parents
  • OK, so I finally answered my own question.  Apparently the connection was being refused because I had used all 10MB of data.  I must have left the card on over night with it sending GPS data and it used all 10MB.  It was strange because the cloud showed the 10MB as used but that is not what I saw in another spot (which is alluding me right now).  Anyways, I was able to top up the card with 10 more MB from the cloud site and immediately I could see it boot properly through the putty interface.

  • Ha! Good to know .. right now mine was working fine and I even experimented with different GPS locations but after attempting Uart over ble to cloud it seems not to work anymore. I restored the nRF52 to the released hex control file - Nordic, is that source not available? - but now I get the repeated reboot problem:

    Secure Boot: prepare to jump to Non-Secure image
    ***** Booting Zephyr OS v1.13.99-ncs2 *****
    Application started
    LTE LC config ...
    nrf_cloud_connect failed: 60
    ***** Booting Zephyr OS v1.13.99-ncs2 *****
    Secure Boot: configure flash
    Secure Boot: SPU: set region 0 as Secure
    

    My data usage is ok so far, at least. Update: Reprogramming with secure boot and application seems to have corrected the issue. Also all error numbers printed are printed as -ve for some reason, which is confusing at first (they are returned as -ERRORNUM).

    There may be a race hazard on the nRF91 and nRF52 startup causing one of the earlier reported errors, since if the nRF52 is not available there is a sync timeout

    k_sem_take failed with err -11

    Error -11 is not -11, it is 11 but reported as -11. Strange design ..

  • And indeed this is now reported in this post. What I hadn't realised - according to this post - is that the reset only affects nRF91 or nRF52, not both at the same time.

Reply Children
No Data
Related