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

Build asset tracker for Thingy:91

Hello, I am trying to build the asset tracker reference app for my newly acquired Thingy:91.

I went through the instructions to get the toolchain and SEGGER IDE up and running

Then I Select "open nrf connect SDK project" and select:

CMakeLists.txt: $BASEDIR/ncs/nrf/applications/asset_tracker/CMakeLists.txt

Board Directory: $BASEDIR/ncs/nrf/boards/arm/nrf9160_pca20035

But I am getting the error:

`kconfiglib.KconfigError: $BASEDIR/ncs/nrf/boards/arm/nrf9160_pca20035/Kconfig.defconfig:53: couldn't parse 'default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_Z_CODE_PARTITION))': macro expanded to blank string`

I see that this config parameter DT_CHOSEN_Z_CODE_PARTITION is not present in the nrf9160DK Kcondif.defconfig file but I don't know how to configure it or to which value.

Also, I see that the Thingy:91 board dir is out of tree, any chances that it will be added soon?

Thank you.

Xavier

Parents
  • Hello Xavier, 

    What instructions did you follow? 

    In SES, have you configured the Zephyr base address? (Tools -> Options -> nRF Connect)

    Did you run "west update" after "west init"?

    cd <sourcecode_root>
    mkdir ncs
    cd ncs
    west init -m https://github.com/NordicPlayground/fw-nrfconnect-nrf
    west update


    Kind regards,

    Øyvind

  • Hello,

    I followed the instructions in the "Getting Started Assistant" from the nrf Connect SDK app.

    I actually found the problem, when filling in the form after "File -> open nrf Connect SDK Project" i should have chosen "nrf9160_pca20035ns", it defaults to the one without the "ns" and that was wrong.

    So my next question now that I can build it is: I only have the Thingy:91, I don't have the nrf9160 DK board, I found the instructions on how to install my merged.hex file using the Thingy:91 connected to the USB port. But is it possible to debug the application? At least to get the "printk" statements somewhere?

    Thank you.

    Xavier

  • Hi Xavier,

    XavierN said:
    So my next question now that I can build it is: I only have the Thingy:91, I don't have the nrf9160 DK board, I found the instructions on how to install my merged.hex file using the Thingy:91 connected to the USB port. But is it possible to debug the application? At least to get the "printk" statements somewhere?

    Using the LTE Link Monitor, you are able to see printk statements when connected via USB. In the LTE Link Monitor you will see the Thingy:91 in the device list as PCA20035

    There is, unfortunately, no possibility to debug via USB on the Thingy:91, you can only do application firmware updates. For debugging, you will need an nRF9160 DK or J-Link device supporting Arm Cortex-M33.

    Kind regards,
    Øyvind

  • I see, thank you!

    I have had the thingy 91 running the firmware it came with for a couple of hours, admittedly indoors but close to a window, and I can't get a GPS Fix to show in the nrf CLoud site, the other sensors are sending data. Is this expected? How can improve the GPS performance or get a fix at all?

    Xavier

Reply Children
Related