SES Compiler error for Thingy:91 asset_tracker - 'NRF_SPU' undeclared (first use in this function); did you mean 'NRF_SPU_S'?

[dkv]

I'm currently unable to build the asset_tracker for Thingy:91 on Segger Embedded Studio - using nrf9160_pca20035ns for the nRF Connect SDK Project

Do anyone have an idea why this occurs?

Br Dag

nRF Connect Options

[Didrik Rokhaug]

Hi.

I assume you are on the master branch?

Which commit are you using? I am able to build using 0a9d1b79.

From the picture, it looks like you are getting more errors than just the one, can you share the rest of them?

Best regards,

Didrik

[dkv]

I'm using ncs_tag v1.0.0 and the list of errors, all related to spm.c follows below.

[Didrik Rokhaug]

What compiler version are you using?

[dkv]

gcc-arm-none-eabi-7-2018-q2-update-win32-sha2 - as recommended in the Getting Started Assistant.

[Didrik Rokhaug]

Can you double-check which commit you are on in the nrf repo?

And run west update to make sure that the other repos are on the correct commit?

And what version of west do you have?

[dkv]

Executed some west-commands and the output was as follows - sorry for the crappy formating but I assume it holds the current ststus of the repos I have checked out

C:\nrfDev\ncs>west -V
West version: v0.6.3

C:\nrfDev\ncs>west list
nrf          nrf                          N/A                                      N/A

fw-nrfconnect-zephyr zephyr                       v1.14.99-ncs2                            github.com/.../fw-nrfconnect-zephyr

nffs         modules\fs\nffs              bc62a2fa9d98ddb5d633c932ea199bc68e10f194 github.com/.../nffs

segger       modules\debug\segger         6fcf61606d6012d2c44129edc033f59331e268bc github.com/.../segger

fw-nrfconnect-mcuboot mcuboot                      v1.3.99-ncs2                             github.com/.../fw-nrfconnect-mcuboot

fw-nrfconnect-mcumgr modules\lib\mcumgr           c8f675a5fa7f62106b9d913844bd5ed6e16ae69e github.com/.../fw-nrfconnect-mcumgr

fw-nrfconnect-tinycbor modules\lib\tinycbor         543ecb7c8662580ef803d59ceda7bd3b8a84a11b github.com/.../fw-nrfconnect-tinycbor

nrfxlib      nrfxlib                      v1.0.0                                   github.com/.../nrfxlib

cmock        test\cmock                   c243b9a7a7b3c471023193992b46cf1bd1910450 https://github.com/ThrowTheSwitch/cmock

unity        test\cmock\vendor\unity      031f3bbe45f8adf504ca3d13e6f093869920b091 https://github.com/ThrowTheSwitch/unity

mbedtls      mbedtls                      mbedtls-2.13.1                           github.com/.../mbedtls

C:\nrfDev\ncs>

Hope that this is what you asked for.

[dkv]

Well, I have banged my head on this for some hours already and I'm going to let it slide for now.

I've tried a lot of things - as deleting the source directory and re-run the procedure for cloning the repositories and re-running the python scripts - without any success. I actually got more problems after doing this...

You may close this issue, while I try to figure out how all of this is bundeled...

Br Dag 

[Didrik Rokhaug]

When I try to open the asset_tracker application in SES using v1.0.0, I can choose between nrf9160_pca20035_v0_2_2[ns] or nrf9160_pca20035_v0_3_0[ns], but not nrf9160_pca20035.

What do you get if you run git rev-parse HEAD in the nrf repo?

Are you able to build the project if you use the master branch?

Remember to run west update and check the "Clean Build Directory" checkbox when changing branch/tag/revision.

[dkv]

As mentioned, I have tried several different approches - the latest cloning the fw-nrfconnect-nrf onto my source dir, and the HEAD is e9f0bc0e3ebfab249d8906c12ad060418b16f238. v1.0-branch, and nrf-source directory is neamed fw-nrfconnect-nrf. Not nrf.

I tried all the [ns] variant you mention without any luck.

However, when I try to run the python scripts I'm faced with a lot of errors - some quite strange, like that Visual Studio 14 is missing...??

[Didrik Rokhaug]

Did you follow the "Getting Started Assistant" when installing NCS?

What python scripts are you talking about? The requirements files in {zephyr, nrf, mcuboot}/scripts/requirements.txt?