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.
Please refer to https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker/README.html#nrf9160-asset-tracker,
Could you observe in the terminal window that the board starts up in the Secure Partition Manager and that the application starts? This is indicated by output similar to the following lines:
SPM: prepare to jump to Non-Secure image
***** Booting Zephyr OS v1.13.99 *****
If not, what are the LEDs status?
There is no output in the terminal. In LTE Link Monitor, the UART indicator switches between red and yellow, and all other indicators are red (PDN is grey). When I flip the ON switch on the devkit, all four LEDs blink together one time and then immediately turn off and stay off.
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.
What operating system are you using?
Did you modify any config setting?
Please update to the latest with the following commands again.
git checkout master
git checkout v1.0.0
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.
I am using x64 Ubuntu 18.04.2 LTS. I have not changed any config settings. I performed the listed commands and attempted to open the project in SES again, but received the same errors.
I reported to the internal and wait for the update to you.
Now, all of the Nordic engineers that may have an answer to this seem to be on vacation at the moment (July is summer vacation season in Norway). I will follow up this one, but worst case we will have to wait until someone that knows returns from vacation.
It seems like we are experiencing the same issue, did the team come up with a solution?
Could you create a new support case and refer to this?
Please also provide the version of OS, SEGGER, modem, and NCS. Thanks.