Problem with SEGGER and nrf connect

Question

Hi, 
 Last week I bought two NRF9160 DK. I downloaded the nrf connect on pc and then i followed the steps carefully from this webpage https://devzone.nordicsemi.com/nordic/b/cellular-iot-guides/posts/getting-started-with-nrf9160-dk 
 But (working on two windows 10 pro computers) I have issue when I followed this in the assistant : 
 
 In Segger, after specifying Zephyr Base and GNU ARM Embedded Toolchain Directory , I opened nrF connect SDK project and followed the steps as above in the image... But unfortunately I have this error as in the image shows below :

It normally should be easy to work with your software but it's not that easy due to the bugs in the updated version and that the updated version is not compatible with SEGGER. 
 Besides all of this, there is not really help on the internet... 
 I really regrets buying your products, nothing is working.

Øyvind · Accepted Answer

Hello there, I'm sorry you feel this way, but I hope that we can help you to realize that this is a great product. 
 First of all, you must be aware that nRF9160 is a more advanced device compared to our nRF52 device. This is why we need to have Zephyr OS . 
 Secondly, did you try using board name nRF9160_pca10090ns ? There is a bug in the Getting Started Assistant v0.9.2, that shows nRF9160_pca10090 instead of nRF9160_pca10090ns. When you choose nRF9160_pca10090 you will get the error message that you got. Both the Getting Started Guide in our blog and the Getting Started Guide from the NCS v0.4.0 documentation uses the nRF9160_pca10090ns board name. 
 The reason for why we have both nRF9160_pca10090 and nRF9160_pca10090ns has to do with the complexity of the nRF9160. It is a Cortex-M33 MCU with TrustZone. From the NCS documentation : 
 " The M33 TrustZone divides the MCU into secure and non-secure domains. When the MCU boots, it always starts executing from the secure area, which in this case is the Secure Partition Manager . 
 To use any of the nRF9160 samples, you must first compile and flash the Secure Partition Manager sample. It provides a reference implementation of a Secure Partition Manager firmware. This firmware is required to set up the nRF9160 DK so that it can run user applications in the non-secure domain. 
 Note that the Secure Partition Manager sample is automatically included in the build for the nrf9160_pca10090ns board." 
 I hope this helps with your issue, and don't hesitate to ask if you get any more. 
 Good luck! 
 Kind regards, Øyvind

Problem with SEGGER and nrf connect

Top Replies