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

Unable to complete 'Getting Started with nRF9160 DK'

I have been going through the steps in this blog post: https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/getting-started-with-nrf9160-dk

I was able to complete everything up to Step 6 without fault, including updating the modem and flashing the hex file. After doing so, my DK, when powered on, very briefly flashes all four LEDs and then does not provide any further indications of any kind even after waiting extended periods of time. There are no errors or anything of that nature appearing in Segger emStudio. Any indications of similar experiences or potential causes would be much appreciated.

Thanks,

Josh

Parents Reply Children
  • Hello again,

    I have followed all the steps in that post, updating to the latest Programmer version, MFW v1.0.0, NCS v1.0.0, and SES v4.18. I was able to successfully update the modem firmware, but now when attempting to open the asset_tracker project in SES, I receive the following set of errors and I am unable to open the project:

    More guidance would be appreciated.

  • Hello,

    My last reply seems as though it did not post for some reason. Apologies if it appears twice. I have updated to SES 4.18, MFW 1.0.0, and NCS 1.0.0. I am able to update the modem firmware using the Programmer app, but when I attempt to open the asset_tracker project in SES to rebuild the hex files and flash them to the board, I get the following errors after hitting 'Open nRF Connect SDK Project' (very long logs so I have uploaded them with Ubuntu's paste service): https://paste.ubuntu.com/p/tT5tbh76wj/

    Any more guidance from this point would be appreciated.

  • Hello again,

    As you can see from the first 10 lines of the SES logs above, I did select nrf9160_pca10090ns. On line 18 it switches itself to the not NS board, but I followed exactly the steps in the tutorial and the initial lines of the logs do show the NS board being selected.

  • Hi, 

    What operating system are you using?

    Did you modify any config setting?

    Please update to the latest with the following commands again.  

    Right now we have some similar cases, but not sure the root cause is the same or not. Your information will be helpful to us. I am looking forward to your reply.

      

    -Amanda H.