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

Getting started

The demo board would not connect (no second LED)

Since in Italy we only have NB-IoT, I guess I should recompile a more recent version of the demo application.

I have followed all steps in Getting Started Assistant but:

Even after registering Segger Embedded Studio, the Nordic version says I am not registered. The standard version of  Embedded Studio runs just fine with the same credentials.

When I try  "Open nrfConnect SDK Project" with:

  • C:/Projects/ncs/nrf/applications/asset_tracker/CMakeLists.txt
  • C:/Projects/ncs/zephyr/boards/arm/nrf9160_pca10090
  • nrf9160_pca10090
  • C:/Projects/ncs/nrf/applications/asset_tracker/build_nrf9160_pca10090

I get an error that asset_tracker.emProject is invalid. When i exit the window, an error marker is on the message(FATAL_ERROR... line:

execute_process(
  COMMAND
  ${PYTHON_EXECUTABLE}
  ${ZEPHYR_BASE}/scripts/kconfig/kconfig.py
  ${KCONFIG_ROOT}
  ${DOTCONFIG}
  ${AUTOCONF_H}
  ${PARSED_KCONFIG_SOURCES_TXT}
  ${merge_fragments}
  WORKING_DIRECTORY ${APPLICATION_SOURCE_DIR}
  # The working directory is set to the app dir such that the user
  # can use relative paths in ${IMAGE}CONF_FILE, e.g. CONF_FILE=nrf5.conf
  RESULT_VARIABLE ret
  )
if(NOT "${ret}" STREQUAL "0")
  message(FATAL_ERROR "command failed with return code: ${ret}")
endif()

  • Have you tried flashing over the newest firmware for the modem? 

    Maybe take a look at this thread and see if that helps

    https://devzone.nordicsemi.com/f/nordic-q-a/49264/unable-to-update-firmware-on-nrf9160

  • I have already downloaded and installed mfw_nrf9160_1.0.0.zip with nRF connect and got "Modem DFU completed successfully!", but I suspect that at this point I should reload the application; this is why I downloaded the development chain, but then I got stuck with the Nordic version of SES not recognizing the license, even after trying to get a new registration for a couple of times.

    If I try to use nRF Connect, all I get is:  Error: 'AT+CFUN=1 ' timed out

    I do not understand if mfw_nrf9160_1.0.0.zip is a sort of BIOS, after which I should have to add an application, or it already contains a modem application.

  • Hello,

    First of all, please ensure that you have the latest version of NCS v1.0.0. Following the latest version of Getting Started Assistant should yield the correct version.

    I get an error that asset_tracker.emProject is invalid. When i exit the window, an error marker is on the message(FATAL_ERROR... line:

     Please change board from nrf9160_pca10090 to nrf9160_pca10090ns. This should solve the issue when building the project. 

    Kind regards,
    Øyvind

  • I installed everything yesterday for the first time, so I think it is up to date.

    Today I no longer get the message about not being registered for Segger Embedded Studio.

    I changed the board to the ns version and I could compile; I also changed .config file as follows:

    # CONFIG_LTE_NETWORK_MODE_LTE_M is not set
    CONFIG_LTE_NETWORK_MODE_NBIOT=y

    The single LED now blinks forever, so the application seems to be running; I also tried a SIM from Vodafone (they say that their M2M SIMs are enabled for NB-IOT, also I would not take what Vodafone sales representatives say at face value), with the same result.

    I would like to test the board with LTE Link Monitor; is there some additional step after programming mfw_nrf9160_1.0.0.zip: I just get timeouts when issuing AT commands.

    I am doing everything with the PROG/DEBUG switch to nRF91.

    Also, from time to time SES starts failing to program the device; at this point also Segger tools fail and the only way to recover is revriting mfw_nrf9160_1.0.0.zip with nRF Connect; happened a couple of times this morning.

  • cmag said:
    I installed everything yesterday for the first time, so I think it is up to date.

     Yes, that should give you the latest version. 

    cmag said:
    I would like to test the board with LTE Link Monitor; is there some additional step after programming mfw_nrf9160_1.0.0.zip: I just get timeouts when issuing AT commands.

    Programming mfw_nrf9160_1.0.0.zip is a one-time thing, this updates the modem FW. With the latest version of Asset Tracker, you should be able to issue AT commands, but if you are not able to do so, please program AT_client sample and issue the AT+CFUN? command

    cmag said:
    Also, from time to time SES starts failing to program the device; at this point also Segger tools fail and the only way to recover is revriting mfw_nrf9160_1.0.0.zip with nRF Connect; happened a couple of times this morning.

     What kind of failure do you get? Can you describe the steps you use to program the device when it fails?

Related