How to include Zephyr out of tree driver in modified nRF sample app?

RE: How to include Zephyr out of tree driver in modified nRF sample app?

Øivind — Tue, 28 Sep 2021 06:50:30 GMT

Correct me if I am mistaken, but Simon is handling that issue in the case you linked, so I will leave that to him.

My understanding is that this case is about the out-of-tree driver, so let's focus on that. Since you are having issues with SES, but not with building on the command line, are you able to build your application which implements the out-of-tree driver when using 'west' on the command line?

RE: How to include Zephyr out of tree driver in modified nRF sample app?

tedhavelka — Mon, 27 Sep 2021 18:27:23 GMT

Hello Oivind,

The error which I am seeing I have detailed in a separate post here: https://devzone.nordicsemi.com/f/nordic-q-a/80001/resolving-nrf9160-zephyr-app-build-error-offsets-c-obj-not-found.

A concerning matter I have found is that I am actually not, within Segger IDE able to compile nRF samples such as aws_iot or other samples. All samples fail with the same error:

Building 'zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj' from solution 'build' in configuration 'Common'
2> Checking 'offsets.c'
2> zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj does not exist.
2> Compiling 'offsets.c'

Because the error is the same across multiple samples and a personal project based on the same sdk-nrf v1.6.1 it seems to me this is an error in how Segger's "Open nRF Connect SDK Project..." menu option is working. The python script create_nordic_project.py is responsible for reading the contents of a sample application like `aws_iot`, and from those files building a couple of .emProject files for Segger, along with a new CMakeLists.txt file and some other build-supporting files in the given sample's build directory.

Something in this generated recipe, some include path or other configuration detail which `cmake` relies on to successfully build Zephyr is missing or different from the structure that's in place that `west` and a command line build process follow.

I can build all sample apps with `west` at the command line. But I can build no samples or other nRF + Zephyr apps when using Segger and its option "File > Open nRF Connect SDK Project...".

- Ted

RE: How to include Zephyr out of tree driver in modified nRF sample app?

Øivind — Mon, 27 Sep 2021 13:12:55 GMT

Hi,

I see that you had a case where you got help from Sigurd. I will read through that to try to better understand what you are trying to achieve.

What is the error that you are seeing when you try to compile your application?