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

Startup Troubles on Dev Kit

I was able one time to power up the nRF9160 dev kit and see it connect to the cellular network and to nRF Cloud. Since then, it will only blink LED3, which indicates that it can't connect. I would like to re-flash the firmware, but I'm totally lost in all the circular links in the documentation. I have used the nRF52832 dev kit extensively so I'm quite familiar with the process, but it appears the nRF9160 dev kti adds several more layers of complexity. I would like to be able to load a simple "hello world" application, and then build on that with my application source code. Please guide me to some concise documentation.

Parents Reply
  • That path is not in c:\arm_segger_embedded_studio_v420a_win_x64_nordic, and I cannot find the mentioned package in my folder.

    Do you have another SES version installed?

    If so, make sure that you are using the correct version (run the executable emStudio in the c:\arm_segger_embedded_studio_v420a_win_x64_nordic\bin folder).

    If that does not help, you might be able to solve the issue by running the other SES version and fixing the problem there, or by uninstalling the other SES version.

Children
  • We are going in circles. I am right back where I was two weeks ago.

    I have confirmed only one emStudio installed, via Windows Control Panel Programs and Features. I am running exactly that emStudio, in the recommended installation directory. Every time I open it, I get that same dialog box shown two messages above. Whether I answer yes or no, I then get the request to activate. I activate tho Nordic license (corrupting my legal company name because the box won't accept a comma in the company name), and the next time I open emStudio, I'm right back at the beginning of this paragraph.

    My client is getting impatient to see some results. So am I.

  • I am still working on a solution to the outdated package problem. In the meantime, if you press "yes to all", are you then able to open and build a sample project?

    That should make the license "stick", and there does not seem to be anything wrong with the hex files produced by SES after pressing "yes to all", so you would at least be able to start development while you are waiting for a permanent solution on the outdated package.

  • Still doesn't work. I'm working with David Martin, and we're still getting this:

  • Another possible clue: I get this error box:

    If I navigate to that specific file and dblclick, another instance of SES opens, and immediately gives me the same box again.

  • It still looks like the "GNU ARM Embedded Toolchain Directory" is wrong. I recreated your issue on a Windows 10 VM, by setting it to the path of SES, instead of the path of the ARM embedded toolchain. See pictures:

    If you change the "GNU ARM Embedded Toolchain Directory" option to the folder where you installed the ARM Embedded toolchain, then the error goes away, and you should be able to load and build the project. If you did not change the install directory in the ARM Embedded toolchain installer, the correct path should be C:\Program Files (x86)\GNU Tools Arm Embedded\7 2018-q2-update. I have attached pictures of the correct setup (on my VM), along with the content of the folder you should point to (when setting the path, only folders will be displayed, so you will not see the uninstaller):

    If you still cannot get it to work, please send pictures of the SES options window, and the folder pointed to by the "GNU ARM Embedded Toolchain Directory" option.

    Edit: Also, when opening a project, make sure that the "Clean Build Directory" checkbox is checked, to avoid risking using old settings.

Related