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()

Parents
  • 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 also tried a command copied from the Asset Tracker:

    AT%XSYSTEMMODE=0,1,0,0

     What does it return if you issue the command: 

    AT%XSYSTEMMODE?

     

    cmag said:
    AT+CLAC

    I can confirm that this does not work. It is a known bug. 

    Were you able to issue the AT+CFUN? command?

  • AT%XSYSTEMMODE?
    %XSYSTEMMODE: 0,1,0,0

    After startup, sometimes, after the usual blue dump ending with:

    :***** Booting Zephyr OS v1.14.99-ncs2 *****
    Application started
    LTE LC config ...

    I Get:

    AT+CESQ
    LTE LC config ...
    +CESQ: 99,99,255,255,255,255
    OK
    AT+CESQ
    +CESQ: 99,99,255,255,255,255
    OK
    AT+CESQ
    +CESQ: 99,99,255,255,255,69
    OK
    AT+CESQ
    +CESQ: 99,99,255,255,255,69
    OK
    nrf_cloud_connect failed: 22
    AT+CESQ

    And then:

    ***** Booting Zephyr OS v1.14.99-ncs2 *****
    Flash region Domain Permissions

    And it starts all over again

    There also is some sign of life (see attached image) with  the iBasis SIM.

    Since we only have NB-IoT and not LTE, I do not know what should happen next.

  • Is this all you get in the LTE Link Monitor output? You seem to be missing SPM. Have you flashed the correct .hex file: merged.hex. What version of SES are you using? Please ensure that you are using SES v4.18 and that Project zephyr/merged.hex is set to Active Project.

  • 2019-07-12T10_58_22.484Z-log.txt

    This is the full dump. After the initial blue part (boot?) I typed:

    AT
    OK
    AT
    OK
    AT+CFUN=1
    OK
    AT+CFUN?
    +CFUN: 1
    OK

    Then it started to do everything by itself and UART/MODEM/UICC/PDN became green; LTE was yellow (Using iBasis).

    I retried with Vodafone SIM and LTE stays gray. Signal is also weaker (2 marks instead of 3) so maybe iBasis is based on a different network.

    In this case the answer is:

    AT+CESQ
    +CESQ: 99,99,255,255,255,255

    Which makes me think that Vodafone lied when they said that any M2M SIM supports NB-IoT.

  • iBasis says:

    "We intend to have NB IoT within a month or two working in roaming mode as well."

    So Italy is not currently supported by their SIM.

    As for Vodafone, they confirmed today that their normal M2M SIMs do not support NB-IoT.

    They can sell us NB-IoT SIMs in lots of 250 pieces.

    I will try to ask other operators.

Reply Children
No Data
Related