Unable to complete 'Getting Started with nRF9160 DK'

RE: Unable to complete 'Getting Started with nRF9160 DK'

Amanda Hsieh — Wed, 04 Dec 2019 11:49:15 GMT

Hi Matt,

Could you create a new support case and refer to this?

Please also provide the version of OS, SEGGER, modem, and NCS. Thanks.

-Amanda H.

RE: Unable to complete 'Getting Started with nRF9160 DK'

Matt Karaerik — Tue, 03 Dec 2019 23:57:16 GMT

Hi Amanda,

It seems like we are experiencing the same issue, did the team come up with a solution?

Matt Karaerik

RE: Unable to complete 'Getting Started with nRF9160 DK'

Jørgen Holmefjord — Mon, 15 Jul 2019 15:03:21 GMT

Have you made sure to set the correct paths in Segger Embedded Studio, as described in the Getting Started assistant?

Navigate to the folder where you extracted SEGGER Embedded Studio. In the bin subfolder, run emStudio.

Click Tools > Options and select the nRF Connect tab.

To load and build a project in SES, you must specify the following information:

Zephyr Base - the location of your cloned Zephyr repository (the full path to ncs/zephyr)
GNU ARM Embedded Toolchain Directory - the location of your GNU ARM Embedded Toolchain installation (for example, c:\gnuarmemb)

RE: Unable to complete 'Getting Started with nRF9160 DK'

joshua_thompson — Wed, 10 Jul 2019 13:38:44 GMT

Thanks for the quick reply. I will wait to hear back from you.

RE: Unable to complete 'Getting Started with nRF9160 DK'

Amanda Hsieh — Wed, 10 Jul 2019 13:34:03 GMT

Hi,

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.

-Amanda H.

RE: Unable to complete 'Getting Started with nRF9160 DK'

joshua_thompson — Wed, 10 Jul 2019 13:26:02 GMT

Hello,

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.

RE: Unable to complete 'Getting Started with nRF9160 DK'

Amanda Hsieh — Wed, 10 Jul 2019 09:02:17 GMT

Hi,

What operating system are you using?

Did you modify any config setting?

Please update to the latest with the following commands again.

cd ncs/nrf
git checkout master
git pull
git checkout v1.0.0
west update

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.

RE: Unable to complete 'Getting Started with nRF9160 DK'

joshua_thompson — Tue, 09 Jul 2019 13:14:44 GMT

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.

RE: Unable to complete 'Getting Started with nRF9160 DK'

Amanda Hsieh — Tue, 09 Jul 2019 06:33:17 GMT

Hi,

Please select board: nrf9160_pca10090ns

The application needs to build non-secure as described in the tutorial.

-Amanda H.

RE: Unable to complete 'Getting Started with nRF9160 DK'

joshua_thompson — Mon, 08 Jul 2019 14:38:17 GMT

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.

RE: Unable to complete 'Getting Started with nRF9160 DK'

joshua_thompson — Mon, 08 Jul 2019 14:32:38 GMT

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:

Loading solution asset_tracker.emProject
Executing load commands
cmake -GNinja -DBOARD=nrf9160_pca10090ns -DBOARD_DIR=/home/josh/Applications/nRFConnectSDK/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/home/josh/Applications/toolchain/gcc-arm-none-eabi-7-2018-q2-update -B/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns -H/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=/home/josh/Applications/SEGGER/arm_segger_embedded_studio_v418_linux_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Using application from '/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker'
Zephyr version: 1.14.99
-- Selected BOARD nrf9160_pca10090ns
-- Found west: /home/josh/.local/bin/west (found suitable version "0.5.8", minimum required is "0.5.6")
-- Cache files will be written to: /home/josh/.cache/zephyr
USING OUT OF TREE BOARD
-- Loading /home/josh/Applications/nRFConnectSDK/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090ns.dts as base
-- Overlaying /home/josh/Applications/nRFConnectSDK/zephyr/dts/common/common.dts
Parsing Kconfig tree in /home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/Kconfig
Loading /home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/zephyr/.config as base
Configuration written to '/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/zephyr/.config'
Including module: nrf in path: /home/josh/Applications/nRFConnectSDK/nrf
-- Using application from '/home/josh/Applications/nRFConnectSDK/nrf/samples/nrf9160/spm'
Zephyr version: 1.14.99
Changed board to secure nrf9160_pca10090 (NOT NS)
USING OUT OF TREE BOARD
-- Loading /home/josh/Applications/nRFConnectSDK/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090.dts as base
-- Overlaying /home/josh/Applications/nRFConnectSDK/zephyr/dts/common/common.dts
-- Overlaying /home/josh/Applications/nRFConnectSDK/nrf/samples/nrf9160/spm/nrf9160_pca10090.overlay

warning: MBEDTLS_TLS_VERSION_1_2 (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:24) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_TLS_VERSION_1_2.html (which is
updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_KEY_EXCHANGE_RSA_ENABLED (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:69)
was assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_KEY_EXCHANGE_RSA_ENABLED.html
(which is updated regularly from the master branch). See the 'Setting configuration values' section
of the Board Porting Guide as well.

warning: MBEDTLS_CIPHER_AES_ENABLED (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:178) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_CIPHER_AES_ENABLED.html (which
is updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_AES_ROM_TABLES (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:182) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_AES_ROM_TABLES.html (which is
updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_CIPHER_DES_ENABLED (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:190) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_CIPHER_DES_ENABLED.html (which
is updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_CIPHER_CBC_ENABLED (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:215) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_CIPHER_CBC_ENABLED.html (which
is updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_MAC_MD5_ENABLED (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:238) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_MAC_MD5_ENABLED.html (which is
updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_MAC_SHA1_ENABLED (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:242) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_MAC_SHA1_ENABLED.html (which
is updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_MAC_SHA256_ENABLED (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:246) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_MAC_SHA256_ENABLED.html (which
is updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_SHA256_SMALLER (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:250) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_SHA256_SMALLER.html (which is
updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

warning: MBEDTLS_CTR_DRBG_ENABLED (defined at ext/lib/crypto/mbedtls/Kconfig.tls-generic:272) was
assigned the value 'y' but got the value 'n'. You can check symbol information (including
dependencies) in the 'menuconfig' interface (see the Application Development Primer section of the
manual), or in the Kconfig reference at
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_MBEDTLS_CTR_DRBG_ENABLED.html (which
is updated regularly from the master branch). See the 'Setting configuration values' section of the
Board Porting Guide as well.

/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/spm/zephyr/.config:32: warning: attempt to assign the value 'n' to the undefined symbol CLOUD_API

/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/spm/zephyr/.config:353: warning: attempt to assign the value 'n' to the undefined symbol SOC_SERIES_LPC55XXX

/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/spm/zephyr/.config:687: warning: attempt to assign the value 'y' to the undefined symbol SERIAL_SUPPORT_ASYNC

/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/spm/zephyr/.config:760: warning: attempt to assign the value 'n' to the undefined symbol MINIMAL_LIBC_LL_PRINTF

/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/spm/zephyr/.config:778: warning: attempt to assign the value 'n' to the undefined symbol UPDATEHUB
Parsing Kconfig tree in /home/josh/Applications/nRFConnectSDK/zephyr/Kconfig
Loading /home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/spm/zephyr/.config as base

Error: Aborting due to non-whitelisted Kconfig warning '/home/josh/Applications/nRFConnectSDK/nrf/ap
plications/asset_tracker/build_nrf9160_pca10090ns/spm/zephyr/.config:32: warning: attempt to assign
the value 'n' to the undefined symbol CLOUD_API'. Note: If this warning doesn't point to an actual
problem, you can add it to the whitelist at the top of
/home/josh/Applications/nRFConnectSDK/zephyr/scripts/kconfig/kconfig.py.

CMake Error at /home/josh/Applications/nRFConnectSDK/zephyr/cmake/kconfig.cmake:200 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /home/josh/Applications/nRFConnectSDK/zephyr/cmake/app/boilerplate.cmake:529 (include)
  ../../samples/nrf9160/spm/CMakeLists.txt:3 (include)


-- Configuring incomplete, errors occurred!
See also "/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/CMakeFiles/CMakeOutput.log".
See also "/home/josh/Applications/nRFConnectSDK/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/CMakeFiles/CMakeError.log".
Project load failed
Reported error: solution load command failed (1)

More guidance would be appreciated.

RE: Unable to complete 'Getting Started with nRF9160 DK'

Amanda Hsieh — Thu, 04 Jul 2019 10:55:13 GMT

Hi,

Please follow this post update firmware on nrf9160 and toolchain.

Amanda H.

RE: Unable to complete 'Getting Started with nRF9160 DK'

joshua_thompson — Wed, 03 Jul 2019 14:26:31 GMT

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.

RE: Unable to complete 'Getting Started with nRF9160 DK'

Amanda Hsieh — Wed, 03 Jul 2019 13:08:05 GMT

Hi,

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 *****
Application started

If not, what are the LEDs status?

-Amanda