Build asset tracker for Thingy:91

[XavierN]

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

[Øyvind]

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

[XavierN]

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

[XavierN]

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

[Øyvind]

The Thingy:91 user guide states, GPS chapter
Note: GPS signals do not usually penetrate ceilings or other structures. For best GPS performance, Nordic Thingy:91 should be used outside in an open space, far from sources of interference and other structures that may block the signals.

[XavierN]

Ok I see, so for using the Thingy 91 inside a vehicle an external antenna is necessary? Any plans for supporting GNSS by the way?

[Øyvind]

You can place the Thingy on the dashboard under front window, this gives sufficient performance. 

GPS is only one of many satellite constellations, collectively referred to as GNSS or Global Navigation Satellite System. Can you please elaborate on what you mean?

[XavierN]

Yes of course, we would be interested in using multiple positioning systems, not only GPS, in particular Galileo and Glonass. For what we gather in the Thingy 91 specs only GPS is supported at the moment.

So my question would be if there are any plans to making the Thingy91 or its evolution capable of using multiple global positioning systems? I guess one always could build its own device based on the nRF9160 system and then add a GNSS compatible peripheral?

[Øyvind]

I have forwarded your question to the nRF91 team regarding GNSS. 

XavierN said:

I guess one always could build its own device based on the nRF9160 system and then add a GNSS compatible peripheral?

Yes, this is a valid solution.  

[XavierN]

Appreciate it, thank you.

[Øyvind]

Hello again, 

I'm sorry, there is currently no support or plans of support for GNSS. Your suggestion is currently the best solution.

Kind regards,
Øyvind

[XavierN]

Ok thank you for taking the time to look into it.

Xavier