Getting Started with nRF9160 DK : Problem to connect DK to nrFcloud

[Jerome.]

Hello,

After following the steps of the tutorial : https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/getting-started-with-nrf9160-dk

I cannot connect my DK to nRF cloud
After following the step "Asset Tracker programming to DK" I have the following error in the logs:
***** Booting Zephyr OS v1.14.99-ncs2-rc2 *****
Flash region Domain License ***** Hardware exception *****
Current thread ID = 0x20001870
Faulting instruction address = 0x30100
Fatal fault in ISR! Spinning ...

Can you help me ?

[Øyvind]

Hello, 

Can you please give me some information on what version you are using? I.e. in command prompt give the output to the command "west status"

Kind regards,
Øyvind

[Jerome.]

Hello, 

I'm not sure you want this result

Result of command : west status 

=== status of nrf (nrf):
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)

modified: applications/asset_tracker/src/main.c
modified: subsys/spm/spm.c

Untracked files:
(use "git add <file>..." to include in what will be committed)

applications/asset_tracker/build_nrf9160_pca10090ns/
applications/nrf_desktop/build_nrf9160_pca10090/
applications/nrf_desktop/build_nrf9160_pca10090ns/
samples/bluetooth/central_bas/build_nrf9160_pca10090/
samples/bluetooth/central_bas/build_nrf9160_pca10090ns/
samples/bluetooth/throughput/build_nrf9160_pca10090/
samples/debug/ppi_trace/build_nrf9160_pca10090/
samples/nfc/record_text/build_nrf9160_pca10090/
samples/nfc/record_text/build_nrf9160_pca10090ns/
samples/nfc/tag_reader/build_nrf9160_pca10090/
samples/nfc/tag_reader/build_nrf9160_pca10090ns/
samples/nrf9160/Gpio/
samples/nrf9160/NRF9160/
samples/nrf9160/at_client/build_nrf9160_pca10090/
samples/nrf9160/at_client/build_nrf9160_pca10090ns/
samples/nrf9160/gps/build_nrf9160_pca10090/
samples/nrf9160/hello_world/
samples/nrf9160/mqtt_simple/build_nrf9160_pca10090/
samples/nrf9160/mqtt_simple/build_nrf9160_pca10090ns/
samples/nrf9160/secure_services/build_nrf9160_pca10090/
samples/nrf9160/secure_services/build_nrf9160_pca10090ns/
subsys/spm9/

no changes added to commit (use "git add" and/or "git commit -a")
=== status of fw-nrfconnect-zephyr (zephyr):
HEAD detached at refs/heads/manifest-rev
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)

modified: include/net/buf.h

no changes added to commit (use "git add" and/or "git commit -a")
=== status of nffs (modules\fs\nffs):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
=== status of segger (modules\debug\segger):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
=== status of fw-nrfconnect-mcuboot (mcuboot):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
=== status of fw-nrfconnect-mcumgr (modules\lib\mcumgr):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
=== status of fw-nrfconnect-tinycbor (modules\lib\tinycbor):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
=== status of nrfxlib (nrfxlib):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
=== status of cmock (test\cmock):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
=== status of unity (test\cmock\vendor\unity):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
=== status of mbedtls (mbedtls):
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean

[Øyvind]

Yes, this was exactly what I needed.  (Tip to next time is to use the Insert --> Insert Code)

You are currently working on the master branch of NCS which can cause issues. I was able to reproduce the issue. My solution was to checkout tag v0.4.0, and this is currently what we suggest customers use v0.4.0 until a new tag is released.

Before changing to tag v0.4.0, you should remove the untracked files that you have. If these are not important changes, you can use:

git clean -fd

To change to tag v0.4.0, please do the following:

cd ncs/nrf
git checkout master
git pull
git checkout v0.4.0
west update

Then try "Asset Tracker programming to DK" step one more time.

Kind regards,
Øyvind

[Jerome.]

Thanks for your help Øyvind.
It works now.

Kind regards, 

Jérôme

[Øyvind]

Good to hear! 

Cheers, 
Øyvind