MacOS SDK 1.1 linking problems

[Slava B.]

Hi,

All was working on SDK 1.0. Now I have SDK 1.1 and new Segger and new nRF Connect and gnuarmbemb (I had a new computer, so did set up everything from scratch)

2> Compiling ‘isr_tables.c’
1> Remove /Users/slava/work/nordic/ncs/nrf/samples/nrf9160/gps/build_nrf9160_pca10090ns/spm/zephyr/zephyr.elf
1> Linking ‘zephyr.elf’
1> Post-link command 
Build failed

However, using west directly is working fine:

➜  gps git:(d3130d77) ✗ west build --board=nrf9160_pca10090ns -d build_nrf9160_pca10090ns
-- west build: build configuration:
       source directory: /Users/slava/work/nordic/ncs/nrf/samples/nrf9160/gps
       build directory: /Users/slava/work/nordic/ncs/nrf/samples/nrf9160/gps/build_nrf9160_pca10090ns
       BOARD: nrf9160_pca10090ns (origin: CMakeCache.txt)
-- west build: building application
[0/1] Re-running CMake...
-- Using application from '/Users/slava/work/nordic/ncs/nrf/samples/nrf9160/gps'
Zephyr version: 2.0.99
...
...
-- Build files have been written to: /Users/slava/work/nordic/ncs/nrf/samples/nrf9160/gps/build_nrf9160_pca10090ns
[167/295] Linking C executable spm/zephyr/spm_zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:         32 KB        48 KB     66.67%
            SRAM:        5424 B        64 KB      8.28%
        IDT_LIST:          40 B         2 KB      1.95%
[289/295] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      113980 B       976 KB     11.40%
            SRAM:       19644 B       128 KB     14.99%
        IDT_LIST:         120 B         2 KB      5.86%
[295/295] Generating zephyr/merged.hex
Merged /Users/slava/work/nordic/ncs/nrf/samples/nrf9160/gps/build_nrf9160_pca10090ns/spm/zephyr/zephyr.hex
Merged /Users/slava/work/nordic/ncs/nrf/samples/nrf9160/gps/build_nrf9160_pca10090ns/zephyr/zephyr.hex

Not sure where to look anymore or how to get more precise and details error mesage...

[Heidi]

Hi!

I don't understand what you're having issues with. Using west directly works fine, but what is it you're trying that doesn't work?

Best regards,

Heidi

[Slava B.]

Heidi, yes as John mentioned this is a build log from Segger. Cannot build any solution in Segger after upgrading everything

[Heidi]

I see now, sorry about that. What version of GNU Arm Embedded Toolchain are you using?

[Slava B.]

I am using gcc-arm-none-eabi-8-2019-q3-update-mac as per the Getting Started guide

[Heidi]

And you are using v4.20 of SES?

The log you posted doesn't seem to have the error message itself.

Could you post the whole log (try cleaning and rebuilding)? Sometimes it helps to re-import the project (delete the original build folder, or choose another build folder).

 

[Slava B.]

Hi, I am using version 4.30c which is a version that downloads following a link in a Getting Started guide.

I did clean a directory and re-build and re-imported the solution and everything. But I never was able to achieve the full log. This is as full as it gets.

[Otso Jousimaa]

Hello, 

I have the same setup (Mac OS, SDK1.1, SES 4.30c) and and I get the same error.

[Heidi]

Hi!

Please update nrf to master and run west update:

git checkout master
git pull
west update

And then make sure that the requirements are successfully installed:

cd <sourcecode_root>\ncs
pip3 install -r zephyr\scripts\requirements.txt
pip3 install -r nrf\scripts\requirements.txt
pip3 install -r mcuboot\scripts\requirements.txt

Delete the build folder for the sample you are running and double-check the correct paths when opening the project. Board Name should be "nrf9160_pca10090ns".

Make sure these paths are correct:

Also, please check which nrfjprog version you have (nrfjrprog -v in a terminal). 

Best regards,

Heidi

[John]

Heidi, please advise which version of nrfjprog we should have please. In addition git checkout master may not help a lot as we need to be using the most stable release of the Asset Tracker code which I understand is v1.1.0

Please advise if you are able to compile the code after using the getting started guide with a clean install on MAC OS.

[Heidi]

You should have version 10.5.0 of nrfjprog.

John said:

In addition git checkout master may not help a lot as we need to be using the most stable release of the Asset Tracker code which I understand is v1.1.0

Yes, I agree. I'm not recommending using master for development, just for debugging purposes to see if the error goes away when on the master branch.

John said:

Please advise if you are able to compile the code after using the getting started guide with a clean install on MAC OS.

Someone in the department is looking into it, as this seems to be a problem several users are having. I'll let you know when I have an update.