Hello CircuitDojo Community,
Are there any developers here in this forum who are working on Linux hosts, and running Nordic’s Segger IDE, with nRF project support? Have any developers encountered (and resolved) a build error involving “offsets.c.obj does not exist” when compiling nRF9160 cellular sample apps, such as
aws_iot when built in Segger Nordic version 5.60?
I am developing firmware for the Sparkfun Thing Plus nRF9160 development board. I’ve been working with Nordic’s sdk-nrf v1.6.1. To compile sample apps and my own small projects has largely gone smoothly, using
west and friends at a Linux shell prompt. In a new turn I am recently trying open and build the same projects in Segger. Nordic’s version of Segger IDE has an extra “open project” option under the top menu bar “File” option. I can create new Segger based projects directly from the sample apps in ~/projects/ncs/nrf/samples/nrf9160. At least I can do so as long as I point Segger to an nrf SDK version 1.6.1. Older and newer SDK releases fail early at Segger’s create project step.
Nordic’s sample apps as well as a personal project all fail to compile for the same error. DTS and Kconfig meta-compile steps appear to succeed. Many parts of Zephyr also appear to compile via ARM gcc cross-compiler, but somewhere a file fails to get built running the build in Segger (but succeeds via
west build . . .):
2> zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj does not exist.
I can provide the full build messages which Segger displays, but every single Zephyr based sample or app I’ve attempted to compile against nrf SDK v1.6.1 fails in this way.
Very little on other forums about this. Could only find a sole, 2018 Nordic Devzone post which mentions this particular error. And I’m blocked even earlier when trying to “open nRF Connect SDK Project” in Nordic’s Segger when the SDK is at any version other than 1.6.0 and 1.6.1. Segger says a script named
create_nordic_project.py is failing when I attempt to open an nRF Connect SDK project with Segger pointing to a non v1.6.1 SDK release.
Any help on this subtle build error greatly appreciated!