offsets.h No such file or directory

[Mathi]

Hi, 

We have been using SDK version 2.1.1 and currently are in the process of migrating to SDK version 2.5.0.

Would be helpful to get some hint regarding what conditions can lead to the following error when building our application.

In file included from C:\ncs\v2.5.0\zephyr\include\zephyr\app_memory\app_memdomain.h:9,
from C:\ncs\v2.5.0\zephyr\include\zephyr\rtio\rtio.h:31,
from C:\ncs\v2.5.0\zephyr\include\zephyr\drivers\i2c.h:28,
from <our application.h>...
C:\ncs\v2.5.0\zephyr\include\zephyr\linker\linker-defs.h:26:10: fatal error: offsets.h: No such file or directory
26 | #include <offsets.h>
| ^~~~~~~~~~~

Thanks,

Mathi.

[Sigurd Hellesvik]

Hi,

Can you explain the steps you did to update to v2.5.0? Both for the SDK and the application.

Maybe most common is to forget to delete the build folder between versions.

Regards,
Sigurd Hellesvik

[Mathi]

Hi Sigurd,

Iam building an application that contains the child image mcuboot and hci_rpmsg.conf.
I use vscode to install the new version of the SDK and toolchain.
I can also confirm that the build error is seen only when upgrading from 2.4.2 to 2.5.0. i.e. 
In order to re-create the problem we tried to incrementally upgrade from 2.1.1 to 2.5.0..
i.e.
Upgrade from 2.1.1 to 2.3.0 ==> No build error related to offsets.h generation.
Upgrade from 2.3.0 to 2.4.0 ==> No build error related to offsets.h generation.
Upgrade from 2.4.0 to 2.4.1 ==> No build error related to offsets.h generation.
Upgrade from 2.4.1 to 2.4.2 ==> No build error related to offsets.h generation.
Upgrade from 2.4.2 to 2.5.0 ==> Build fails due to offsets.h generation.

Note: I always made sure to delete the build folder between versions.
Please let me know if you need further information.

Thanks,

Mathi.

[Mathi]

We don't enable CONFIG_RTIO in our configurations, but i do realize now that when the error occurs, the header file related to rtio seems to be getting included as a dependency, only in 2.5.0:
from C:\ncs\v2.5.0\zephyr\include\zephyr\rtio\rtio.h:31,

In either case, the problem still persists irrespective of whether CONFIG_RTIO is enabled or disabled.

[Sigurd Hellesvik]

Mathi said:

Yes, i set CONFIG_RTIO now and tried buiding a crypto sample application.

QuoteIt seems like the issue is related to i2c code. Can you try to see if you get the same from a sample using i2c?
For example from the I2C lesson in Devacademy?

[Bogdan Marinescu]

I can confirm that I see the same issue, but on 2.5.1. A clean build fails because offsets.h can't be found, but subsequent builds succeed.I don't have CONFIG_RTIO set.

[ryan_mulder_antrum]

I also am seeing the same issue on 2.5.1

When I dug into it a bit, it looked like zephyr's cmake was properly setting up the target for generating offsets.h, and that the library targets were setup to depend on it.

It made me suspect that ninja was the issue, but that's where I got stuck.

I have ninja version 1.10.1

[Sigurd Hellesvik]

ryan_mulder_antrum said:

When I dug into it a bit, it looked like zephyr's cmake was properly setting up the target for generating offsets.h, and that the library targets were setup to depend on it.

It made me suspect that ninja was the issue, but that's where I got stuck.

I have ninja version 1.10.1

How did you install the nRF Connect SDK and its toolchain?

How do you build you projects?

[TBing]

Is there any update on this issue?

FYI: Our project has two child images: MCUBOOT and HCI_RPMSG.

I agree with Bogdan's comment - this looks very much like a dependency/order issue. 

[Sigurd Hellesvik]

Hi Tonny,

We have a lot of users building projects with multiple child images without this error.
However, since multiple people in this ticket have the same issue, there is likely one thing in common that you do which causes the issue. If we can find out what that is, we can figure out if it is a bug or if there is something that you can do to fix the issue.

However, I do not yet know enough about the projects to know what this could be yet.

Here are some questions to things I suspect could impact this:

How did you install the nRF Connect SDK and its toolchain?
How did you add mcuboot and hci_rpmsg to your project?
Do you use sysbuild?

[TBing]

Hi Sigurd and thanks for your swift response.

- I installed the toolchain using the Toolchain Manager from nRF Connect for Desktop

- mcuboot and hci_rpmsg are added in the child_image folder to the application.

child_image\hci_rpmsg.conf
child_image\mcuboot
child_image\mcuboot\prj.conf
child_image\mcuboot\boards
child_image\mcuboot\boards\x_cpuapp.overlay

- We are not using sysbuild.

We are currently using SDK 2.1.1 and want to upgrade to 2.5.0 but hit the problem with offsets.h.

Upgrading to 2.4.x does not lead to the problem with offsets.h.

[Bogdan Marinescu]

Hi,

- I installed the toolchain manually. My project is a single application with its own west.yml that pulls in all the required dependencies, including NCS. The application has other dependencies that are compiled using cmake's add_subdirectory, I suspect this is part of the issue on my side (since the offsets.h issue appeared on one of these dependencies).
- mcuboot and hci_rpmsg were added automatically by the build system by setting the relevant configuration options in prj.conf.
- I don't use sysbuild.

[ryan_mulder_antrum]

Hi Sigurd,

- I installed the toolchain using the Toolchain Manager from nRF Connect for Desktop

- mcuboot is added via prj.conf with CONFIG_BOOTLOADER_MCUBOOT=y

- Not using hci_rpmsg

- Not using sysbuild

- Application has a west.yml for fetching one of our modules from git