nRF9160 Error building asset_tracker sample code

[jkase]

I'm trying to make a "simple" change to the asset_tracker project so that it will send the reporting data to my own server instead of the nRF cloud.  However, I am unable to build the provided asset_tracker code.  After many, many hours of work required to get the environment up and running, the following build error is displayed: 

...

Building ?spm/zephyr/spm_zephyr_prebuilt.elf? from solution ?build? in configuration ?Common?
1> Compiling ?empty_file.c?
1> Linking ?spm_zephyr_prebuilt.elf?
1> Memory region         Used Size  Region Size  %age Used
1>            FLASH:       48640 B        48 KB     98.96%
1>             SRAM:        5424 B        64 KB      8.28%
1>         IDT_LIST:          40 B         2 KB      1.95%
Building ?spm/zephyr/linker_pass_final.cmd? from solution ?build? in configuration ?Common?
1> Combining ?spm/zephyr/linker_pass_final.cmd?
Building ?spm/zephyr/CMakeFiles/spm_linker_pass_final_script_target? from solution ?build? in configuration ?Common?
Building ?spm/zephyr/spm_linker_pass_final_script_target? from solution ?build? in configuration ?Common?
Building ?spm/zephyr/isr_tables.c? from solution ?build? in configuration ?Common?
1> Combining ?spm/zephyr/isr_tables.c?
Building ?cmake_object_order_depends_target_spm_zephyr_final? from solution ?build? in configuration ?Common?
Building ?libspmsecureentries.a? from solution ?build? in configuration ?Common?
1> Compiling ?empty_file.c?
2> Compiling ?isr_tables.c?
Building ?spm/zephyr/zephyr.elf? from solution ?build? in configuration ?Common?
1> Linking ?zephyr.elf?
1> Post-link command 
Build failed


This occurs with both the original SEG Native 4.20a and the more recent SEG Native 4.30c .

The source is v1.1.0 .

I've tried the gnuarmemb version 7-2018-q2 as suggested in a different blog thread, but that causes errors in the compiling.  Version 8-2019-q3 seems to work better.

We intend to use the Thingy:91 for a customer and I need to get this resolved.

Thanks in advance,

--jeff

[jkase]

[Øyvind]

Hello Jeff, 
 
Did you follow the Getting Started Assistant in nRF Connect for Desktop, when installing NCS? From your screenshot, I see that you are using MacOS. Have you followed this tutorial?

This occurs with both the original SEG Native 4.20a and the more recent SEG Native 4.30c .

 What is SEG Native? Do you mean Segger Embedded Studio? If so, have you downloaded Segger Embedded Studio for ARM (Nordic Edition)?

However, I am unable to build the provided asset_tracker code. 

 Have you tried to build the asset_tracker without touching the sample? Did you try any other samples? 

Kind regards,
Øyvind

[jkase]

I followed the older nRF Connect for Desktop, which had several issues that needed to be clarified/corrected by a previous support ticket, and I've updated to the latest version and gone through that, as well.

Sorry, I don't know why I used the word Native.  The two versions I've tried are SEGGER Embedded Studio for ARM 4.20a and SEGGER Embedded Studio for ARM 4.30c .

I have not seen the nRF9160 DK do anything yet, although I've configured and been successful with the Thingy:91 .  If I can't build and modify the code, neither will be usable for our customers.

Thanks,

--jeff

[Øyvind]

jkase said:

I followed the older nRF Connect for Desktop, which had several issues that needed to be clarified/corrected by a previous support ticket, and I've updated to the latest version and gone through that, as well.

 Have you successfully been able to install NCS and download SEGGER Embedded Studio for ARM 4.30c via the Getting Started Assistant?

jkase said:

I have not seen the nRF9160 DK do anything yet, although I've configured and been successful with the Thingy:91

 Ok, what did you do with the Thingy:91? Have you updated the nRF9160 DK to latest modem FW and latest Asset Tracker application?

jkase said:

If I can't build and modify the code, neither will be usable for our customers.

 Let's take things one step at a time. 

Are you able to build the asset tracker or samples without editing them? It is important that we have a baseline for where the issues start, i.e. we need to know where it's failing. What is the "simple change" you are trying to add? Have you set Zephyr Base and GNU ARM Toolchain directory in Segger Embedded Studio? (Under Tools -> Options -> nRF Connect)

The Asset Tracker is designed to be used with nRF Cloud, there are several settings that must be configured in order to use it with another server. My best suggestion is to start with the simple MQTT sample or the AWS FOTA sample, to use your own server.

 Kind regards,
Øyvind

[jkase]

The output I showed you is from SEG 4.30c, so yes, it's installed.

I am trying to build the sample source code for asset_tracker, with no modifications.  That results in the error listed.  If have not begun to modify the source, since I always like to build the sample and install it before I make changes.

All of the setup and configuration elements have been installed and verified.

I understand that I will need to make many changes to point to our server, but let's get the sample code running first.

Meanwhile, I've brought up an Ubuntu 18.04 server in Parallels, which I'm trying to get configured.  I'm at the "pip3 install --user west" step of the Clone the nRF Connect SDK process.  It runs without errors, but does not verify.  Where should west be installed?  There might be a path issue.

Thanks,

--jeff

[Øyvind]

jkase said:

The output I showed you is from SEG 4.30c, so yes, it's installed.

And to verify, does it say the following in the top of the window:
 

jkase said:

I am trying to build the sample source code for asset_tracker, with no modifications.  That results in the error listed.  If have not begun to modify the source, since I always like to build the sample and install it before I make changes.

 These are not errors, these are warnings. If you do get errors, it will say error and print in the output window of Segger Embedded Studio. If you do have any errors, please copy-paste from the output.

 

jkase said:

Meanwhile, I've brought up an Ubuntu 18.04 server in Parallels, which I'm trying to get configured.  I'm at the "pip3 install --user west" step of the Clone the nRF Connect SDK process.  It runs without errors, but does not verify.  Where should west be installed?  There might be a path issue.

I'm confused, are you working on Mac or Ubuntu? If you have installed in Mac, why do you need Ubuntu? It would be great if we can focus on one environment.

[jkase]

Yes, I'm running the 4.30c version from the nRF Connect SDK app, and yes it says that it's up to date.

There is a Package update available for "Nordic Semiconductor nRF CPU Support Package" Version 8.29 listed as something that could be installed.

The startup log ends with "SEGGER Embedded Studio is ready to use"

The build log I sent previously is the tail end of the log, after it's compiled all of the code and fails during the link.

The Ubuntu option is yet another thing I'm trying.  Parallels allows you to run multiple OSs simultaneously.  I assumed that it would be easier to install, but I'm getting stuck in that process, as well.

I would prefer to have the macOS version running natively, but I really need something to work as soon as possible, so I can start building the code.

Thanks,

--jeff

[jkase]

I've successfully built the asset_tracker in Ubuntu using Parallels.  It definitely took some work to get everything lined up and configured properly.  I have a properly-sized merged.hex file, which I will try to install.

In looking through the output on the macOs build, it's getting stuck with the following:

1> Post-link command 
Build failed

in my Ubuntu successful build, this is where these commands are run:

Building 'zephyr/mcuboot_primary_app.hex' from solution 'build' in configuration 'Common' 
1> Combining 'zephyr/mcuboot_primary_app.hex' 
1> Merged /home/parallels/Nordic/ncs/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/zephyr/zephyr.hex 

Any thoughts on what could be missing/going wrong?

Thanks,

--jeff

[Øyvind]

jkase said:

It definitely took some work to get everything lined up and configured properly

 Could you please elaborate on what was wrong/configured incorrectly? This is good feedback to our team working with the "Getting Started Assistant".

 

jkase said:

Any thoughts on what could be missing/going wrong?

It should not be any difference between macOS and Ubuntu with regards to the steps. Did you run "west update"? Are you certain that you configured macOS install correct, ref my question above?

-Øyvind