Unable to build blinky project outside SDK folder

RE: Unable to build blinky project outside SDK folder

Suhas_MS — Tue, 08 Mar 2022 13:28:20 GMT

Hello,

I know this Q&A thread has been idle for a long time, but I have found a solution for the issue and it's working in Windows Operating System.

Run the following commands. (Even for windows, keep Posix path names)

setx ZEPHYR_BASE "C:/nrfZephyrSDK/nrf"

west config --system zephyr.base C:/nrfZephyrSDK/zephyr
west config --system zephyr.base-prefer configfile
west config --system manifest.path C:/nrfZephyrSDK/nrf
west config --system manifest.file west.yml
west config --system build.board_warn false

west config --global zephyr.base C:/nrfZephyrSDK/zephyr
west config --global zephyr.base-prefer configfile
west config --global manifest.path C:/nrfZephyrSDK/nrf
west config --global manifest.file west.yml
west config --global build.board_warn false

- Suhas

RE: Unable to build blinky project outside SDK folder

Albrecht Markus Schellenberger — Wed, 29 Sep 2021 13:07:50 GMT

Hello Suhas,

[quote user="Suhas_MS"]Please let me know how I can establish the out-of -tree application repository properly.[/quote]

I will demonstrate this based on the Hello World sample on an Ubuntu distribution. The installation path of the nRF Connect SDK is "$HOME/ncs", resulting in:

~$ echo $ZEPHYR_BASE
/home/user/ncs/zephyr

In addition to all other required tools, the variable has to point to the right Zephyr within your build environment.

Now I just copy the hello_world folder from "$HOME/ncs/zephyr/samples/hello_world" to a different location, e.g. "$HOME/_work/outoftree/".

From there, I run:

~/_work/outoftree/hello_world$ west build -b nrf9160dk_nrf9160ns

-- west build: generating a build system

...

...

-- west build: building application

[1/171] Preparing syscall dependency handling

[6/171] Performing build step for 'spm_subimage'

[1/216] Preparing syscall dependency handling

[209/216] Linking C executable zephyr/zephyr_prebuilt.elf

[216/216] Linking C executable zephyr/zephyr.elf

Memory region Used Size Region Size %age Used

FLASH: 64 KB 64 KB 100.00%

SRAM: 11808 B 64 KB 18.02%

IDT_LIST: 0 GB 2 KB 0.00%

[163/171] Linking C executable zephyr/zephyr_prebuilt.elf

[170/171] Linking C executable zephyr/zephyr.elf

Memory region Used Size Region Size %age Used

FLASH: 28940 B 960 KB 2.94%

SRAM: 6528 B 178968 B 3.65%

IDT_LIST: 0 GB 2 KB 0.00%

[171/171] Generating zephyr/merged.hex

Regards,

Markus

RE: Unable to build blinky project outside SDK folder

Suhas_MS — Wed, 29 Sep 2021 06:41:53 GMT

Hello Markus,

I have already tried this approach and this downloads the whole SDK again to my workspace.

I need to implement an application out of the SDK directory as given in -

Workflow 2: Out-of-tree application repository

This approach will help us maintain the application only with our repository and decouple it with NRF SDK. That is the reason why I have added ZYPHER_BASE to my CMakelists.txt

but this approach doesn't seem to work.

Please let me know how I can establish the out-of -tree application repository properly.

Thank You.

- Suhas

RE: Unable to build blinky project outside SDK folder

Albrecht Markus Schellenberger — Tue, 28 Sep 2021 19:03:20 GMT

Hello Suhas,

[quote user="Suhas_MS"]I need a freestanding application.[/quote]

Got you!

You might want to have a look at the section Adding your own code in the NCS documentation. I will provide you with an example based on Workflow 4: Application as the manifest repository.

In the root folder of your freestanding Blinky sample, create a file named west.yml containing the following:

# Example application-specific west.yml, using manifest imports.
manifest:
  remotes:
    - name: ncs
      url-base: https://github.com/nrfconnect
  projects:
    - name: nrf
      repo-path: sdk-nrf
      remote: ncs
      revision: v1.6.1
      import: true
  self:
    path: blinky_app

path should be the root folder name of the Blinky sample, which in this case “blinky_app”. NCS version to be used in this example will be v1.6.1, but this can be changed to basically any other version.

Now, in your workspace folder where “blinky_app” is the manifest repository, run the following command:

west init -l blinky_app

followed by:

west update

When finished, you should have a full nRF Connect SDK repository within your workspace. Switching to “blinky_app”, you can now run the build command:

west build -b thingy91_nrf9160ns

followed by:

west flash --erase

I hope this will help you.

Regards.

Markus

RE: Unable to build blinky project outside SDK folder

Suhas_MS — Tue, 28 Sep 2021 14:57:36 GMT

Yes I have installed nRF Connect SDK according to the guideline. This can be confirmed because, the application compiles correctly inside the SDK.

I need a freestanding application.

the west command will not build anything,

PS C:\Users\Suhas\eclipse-workspace\blinky> west build -b thingy91_nrf9160ns
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: error: argument <command>: invalid choice: 'build' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate')
PS C:\Users\Suhas\eclipse-workspace\blinky>

thank you.

-suhas

RE: Unable to build blinky project outside SDK folder

Albrecht Markus Schellenberger — Tue, 28 Sep 2021 14:03:47 GMT

Hello Suhas,

have you installed the nRF Connect SDK according to this guideline and performed all steps?

Is there a reason why you are using this build command?

cmake -B build -GNinja -DBOARD=thingy91_nRF9160_ns

Normally, we recommend to use this one instead:

west build -b thingy91_nrf9160ns

Regards,

Markus