build doesn't recognize zephyr files

RE: build doesn't recognize zephyr files

Elfving — Wed, 21 Feb 2024 09:31:26 GMT

I am running into the same problem, which is good in a way. Then we know that this isn't really a symptom of there being anything wrong with your SDK.

[quote user="Raz_k"]

However, when i build with the nRF52840DK_nrf52840 it is able to build and flash(using J-link) successfully.

[/quote]

So you do have a DK on hand as well?

The nRF9160 doesn't have BLE capabilities, so you shouldn't build anything in the BLE fundamentals course for that SoC. Another thing is that the Thingies (Thingy91 and Thingy53) might be a bit harder to work with. I would recommend using a development kit (DK) instead. For parhaps a better breakdown of the difference between the two, see here.

[quote user="Raz_k"]But im having trouble understanding how to test the program, since im connected via J-link and there is no outputs in the viewer app. In addition the device doesnt recognize my USB data cable.[/quote]

Is this to the Thingy or the DK? The Thingy does not have an OB debugger, which might be the issue.

Regards,

Elfving

RE: build doesn't recognize zephyr files

Raz_k — Mon, 19 Feb 2024 15:01:00 GMT

When defining nRF52DK_nrf52832 I get the same errors.

However, when i build with the nRF52840DK_nrf52840 it is able to build and flash(using J-link) successfully.

But im having trouble understanding how to test the program, since im connected via J-link and there is no outputs in the viewer app. In addition the device doesnt recognize my USB data cable.

RE: build doesn't recognize zephyr files

Elfving — Mon, 19 Feb 2024 14:34:57 GMT

When building it for the "nRF52DK_nrf52832" though?

Regards,

Elfving

RE: build doesn't recognize zephyr files

Raz_k — Mon, 19 Feb 2024 14:30:34 GMT

I used the bme680 example and created it in the ncs directory, defined a thingy91_nrf52840 board.

But still the same errors:

Building bme680_nrf52
west build --build-dir c:/ncs/bme680_nrf52/build c:/ncs/bme680_nrf52

[6/94] Building C object CMakeFiles/app.dir/src/main.c.obj
FAILED: CMakeFiles/app.dir/src/main.c.obj
C:\ncs\toolchains\c57af46cb7\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -DKERNEL -DNRF52840_XXAA -DPICOLIBC_INTEGER_PRINTF_SCANF -DUSE_PARTITION_MANAGER=1 -D_FORTIFY_SOURCE=1 -D_POSIX_C_SOURCE=200809 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -IC:/ncs/v2.5.2/zephyr/include -Izephyr/include/generated -IC:/ncs/v2.5.2/zephyr/soc/arm/nordic_nrf/nrf52 -IC:/ncs/v2.5.2/zephyr/soc/arm/nordic_nrf/common/. -IC:/ncs/v2.5.2/nrf/include -IC:/ncs/v2.5.2/nrf/tests/include -IC:/ncs/v2.5.2/modules/hal/cmsis/CMSIS/Core/Include -IC:/ncs/v2.5.2/zephyr/modules/cmsis/. -IC:/ncs/v2.5.2/modules/hal/nordic/nrfx -IC:/ncs/v2.5.2/modules/hal/nordic/nrfx/drivers/include -IC:/ncs/v2.5.2/modules/hal/nordic/nrfx/mdk -IC:/ncs/v2.5.2/zephyr/modules/hal_nordic/nrfx/. -isystem C:/ncs/v2.5.2/nrfxlib/crypto/nrf_cc310_platform/include -fno-strict-aliasing -Os -imacros C:/ncs/bme680_nrf52/build/zephyr/include/generated/autoconf.h -fno-printf-return-value -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m4 -mthumb -mabi=aapcs -mfp16-format=ieee --sysroot=C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi -imacros C:/ncs/v2.5.2/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -ftls-model=local-exec -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=C:/ncs/bme680_nrf52=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/ncs/v2.5.2/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/ncs/v2.5.2=WEST_TOPDIR -ffunction-sections -fdata-sections --specs=picolibc.specs -std=c99 -MD -MT CMakeFiles/app.dir/src/main.c.obj -MF CMakeFiles\app.dir\src\main.c.obj.d -o CMakeFiles/app.dir/src/main.c.obj -c ../src/main.c
In file included from C:/ncs/v2.5.2/zephyr/include/zephyr/sys/util_macro.h:34,
from C:/ncs/v2.5.2/zephyr/include/zephyr/sys/atomic.h:16,
from C:/ncs/v2.5.2/zephyr/include/zephyr/kernel_includes.h:21,
from C:/ncs/v2.5.2/zephyr/include/zephyr/kernel.h:17,
from ../src/main.c:7:
../src/main.c: In function 'main':
C:/ncs/v2.5.2/zephyr/include/zephyr/sys/util.h:93:55: error: size of unnamed array is negative
93 | #define ZERO_OR_COMPILE_ERROR(cond) ((int) sizeof(char[1 - 2 * !(cond)]) - 1)
| ^
C:/ncs/v2.5.2/zephyr/include/zephyr/sys/util_internal.h:72:26: note: in definition of macro '__DEBRACKET'
72 | #define __DEBRACKET(...) __VA_ARGS__
| ^~~~~~~~~~~
C:/ncs/v2.5.2/zephyr/include/zephyr/sys/util_internal.h:64:9: note: in expansion of macro '__GET_ARG2_DEBRACKET'
64 | __GET_ARG2_DEBRACKET(one_or_two_args _if_code, _else_code)
| ^~~~~~~~~~~~~~~~~~~~
C:/ncs/v2.5.2/zephyr/include/zephyr/sys/util_internal.h:59:9: note: in expansion of macro '__COND_CODE'
59 | __COND_CODE(_XXXX##_flag, _if_1_code, _else_code)
| ^~~~~~~~~~~
C:/ncs/v2.5.2/zephyr/include/zephyr/sys/util_macro.h:180:9: note: in expansion of macro 'Z_COND_CODE_1'
180 | Z_COND_CODE_1(_flag, _if_1_code, _else_code)
| ^~~~~~~~~~~~~
C:/ncs/v2.5.2/zephyr/include/zephyr/device.h:279:9: note: in expansion of macro 'COND_CODE_1'
279 | COND_CODE_1(DT_HAS_COMPAT_STATUS_OKAY(compat), \
| ^~~~~~~~~~~
C:/ncs/v2.5.2/zephyr/include/zephyr/device.h:281:22: note: in expansion of macro 'ZERO_OR_COMPILE_ERROR'
281 | (ZERO_OR_COMPILE_ERROR(0)))
| ^~~~~~~~~~~~~~~~~~~~~
../src/main.c:14:42: note: in expansion of macro 'DEVICE_DT_GET_ONE'
14 | const struct device *const dev = DEVICE_DT_GET_ONE(bosch_bme680);
| ^~~~~~~~~~~~~~~~~
[15/94] Building C object zephyr/CMakeFiles/zephyr.dir/C_/ncs/v2.5.2/nrfxlib/crypto/nrf_cc310_platform/src/nrf_cc3xx_platform_mutex_zephyr.c.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'c:\ncs\bme680_nrf52\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

RE: build doesn't recognize zephyr files

Elfving — Mon, 19 Feb 2024 14:21:53 GMT

Just to make sure that there is nothing wrong with the SDK, toolchain, environment, etc., could you try simply building it for an nRF52DK?

[quote user="Raz_k"]So i switch the SWD to nrf 52 in my thingy91 and build using thingy91_nrf52840 board settings
[/quote]

I believe it actually should work for the nRF52840 on the Thingy91, though the nRF9160 itself does not have BLE capabilities, which might be reason why it failed - though from the error it doesn't seem like that is the main issue.

Regards,

Elfving

RE: build doesn't recognize zephyr files

Raz_k — Mon, 19 Feb 2024 14:14:33 GMT

Hey Elfving,

A little background:
My main goal is to advertise my BME sample sensor to the app and to be able to control the sensor activation using BLE, meaning nrf connect app for mobile.

Im using the thingy91. I tried to build it in an thingy91_nrf9160_ns board settings.
However i then saw that the exercise is suitable only to nrf52.

So i switch the SWD to nrf 52 in my thingy91 and build using thingy91_nrf52840 board settings
and it is still unable to build with the same errors as i mentioned before even after moved the directory to the path you mentioned.

Also, yes I checked the toolchain I'm using and it is exactly like you added in the your attached screenshot.

RE: build doesn't recognize zephyr files

Elfving — Mon, 19 Feb 2024 13:42:36 GMT

Could you try placing BLEexample/bt-fund/ in /ncs/, maybe there is something strange going on with the west workspace.

What HW are you building the sample for?

Could you check and make sure that you are using a corresponding newer toolchain?

Regards,

Elfving

RE: build doesn't recognize zephyr files

Raz_k — Sat, 17 Feb 2024 17:31:18 GMT

i removed NCS version 1.9. I and installed the newer version 2.5.2.

and still im unable to build:

* Executing task: nRF Connect: Build: blefund_less1_exer1/build (active)

Building blefund_less1_exer1
west build --build-dir c:/nordic/BLEexample/bt-fund/lesson1/blefund_less1_exer1/build c:/nordic/BLEexample/bt-fund/lesson1/blefund_less1_exer1

[4/74] Performing build step for 'mcuboot_subimage'
ninja: no work to do.
[14/74] Building C object zephyr/drivers/bluetooth/CMakeFiles/drivers__bluetooth.dir/hci/h4.c.obj
FAILED: zephyr/drivers/bluetooth/CMakeFiles/drivers__bluetooth.dir/hci/h4.c.obj
C:\ncs\toolchains\c57af46cb7\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -DKERNEL -DNRF52840_XXAA -DPICOLIBC_INTEGER_PRINTF_SCANF -DUSE_PARTITION_MANAGER=1 -D_FORTIFY_SOURCE=1 -D_POSIX_C_SOURCE=200809 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR_SUPERVISOR__ -D__ZEPHYR__=1 -IC:/ncs/v2.5.2/zephyr/subsys/bluetooth -IC:/ncs/v2.5.2/zephyr/include -Izephyr/include/generated -IC:/ncs/v2.5.2/zephyr/soc/arm/nordic_nrf/nrf52 -IC:/ncs/v2.5.2/zephyr/include/zephyr/posix -IC:/ncs/v2.5.2/zephyr/soc/arm/nordic_nrf/common/. -IC:/ncs/v2.5.2/zephyr/subsys/settings/include -IC:/ncs/v2.5.2/nrf/include -IC:/ncs/v2.5.2/nrf/tests/include -IC:/ncs/v2.5.2/modules/hal/cmsis/CMSIS/Core/Include -IC:/ncs/v2.5.2/zephyr/modules/cmsis/. -IC:/ncs/v2.5.2/modules/hal/nordic/nrfx -IC:/ncs/v2.5.2/modules/hal/nordic/nrfx/drivers/include -IC:/ncs/v2.5.2/modules/hal/nordic/nrfx/mdk -IC:/ncs/v2.5.2/zephyr/modules/hal_nordic/nrfx/. -IC:/ncs/v2.5.2/modules/crypto/tinycrypt/lib/include -IC:/ncs/v2.5.2/nrfxlib/softdevice_controller/include -isystem C:/ncs/v2.5.2/nrfxlib/crypto/nrf_cc310_platform/include -Wshadow -fno-strict-aliasing -Os -imacros C:/nordic/BLEexample/bt-fund/lesson1/blefund_less1_exer1/build/zephyr/include/generated/autoconf.h -fno-printf-return-value -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m4 -mthumb -mabi=aapcs -mfp16-format=ieee --sysroot=C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi -imacros C:/ncs/v2.5.2/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -ftls-model=local-exec -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=C:/nordic/BLEexample/bt-fund/lesson1/blefund_less1_exer1=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/ncs/v2.5.2/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/ncs/v2.5.2=WEST_TOPDIR -ffunction-sections -fdata-sections --specs=picolibc.specs -D_POSIX_THREADS -std=c99 -MD -MT zephyr/drivers/bluetooth/CMakeFiles/drivers__bluetooth.dir/hci/h4.c.obj -MF zephyr\drivers\bluetooth\CMakeFiles\drivers__bluetooth.dir\hci\h4.c.obj.d -o zephyr/drivers/bluetooth/CMakeFiles/drivers__bluetooth.dir/hci/h4.c.obj -c C:/ncs/v2.5.2/zephyr/drivers/bluetooth/hci/h4.c
In file included from C:/ncs/v2.5.2/zephyr/include/zephyr/toolchain/gcc.h:92,
from C:/ncs/v2.5.2/zephyr/include/zephyr/toolchain.h:50,
from C:/ncs/v2.5.2/zephyr/include/zephyr/kernel_includes.h:19,
from C:/ncs/v2.5.2/zephyr/include/zephyr/kernel.h:17,
from C:/ncs/v2.5.2/zephyr/drivers/bluetooth/hci/h4.c:12:
C:/ncs/v2.5.2/zephyr/include/zephyr/device.h:85:41: error: '__device_dts_ord_DT_CHOSEN_zephyr_bt_uart_ORD' undeclared here (not in a function)
85 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)
| ^~~~~~~~~
C:/ncs/v2.5.2/zephyr/include/zephyr/toolchain/common.h:132:26: note: in definition of macro '_DO_CONCAT'
132 | #define _DO_CONCAT(x, y) x ## y
| ^
C:/ncs/v2.5.2/zephyr/include/zephyr/device.h:85:33: note: in expansion of macro '_CONCAT'
85 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)
| ^~~~~~~
C:/ncs/v2.5.2/zephyr/include/zephyr/device.h:211:37: note: in expansion of macro 'DEVICE_NAME_GET'
211 | #define DEVICE_DT_NAME_GET(node_id) DEVICE_NAME_GET(Z_DEVICE_DT_DEV_ID(node_id))
| ^~~~~~~~~~~~~~~
C:/ncs/v2.5.2/zephyr/include/zephyr/device.h:228:34: note: in expansion of macro 'DEVICE_DT_NAME_GET'
228 | #define DEVICE_DT_GET(node_id) (&DEVICE_DT_NAME_GET(node_id))
| ^~~~~~~~~~~~~~~~~~
C:/ncs/v2.5.2/zephyr/drivers/bluetooth/hci/h4.c:74:44: note: in expansion of macro 'DEVICE_DT_GET'
74 | static const struct device *const h4_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_bt_uart));
| ^~~~~~~~~~~~~
[23/74] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/ncs/v2.5.2/modules/hal/nordic/nrfx/drivers/src/nrfx_clock.c.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'c:\nordic\BLEexample\bt-fund\lesson1\blefund_less1_exer1\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

plus i tried in 1.9.1 version to remove the /zephyr/ path in the include, but it didnt help.

RE: build doesn't recognize zephyr files

Elfving — Fri, 16 Feb 2024 12:31:39 GMT

Hello again,

Ah yes. I see that you are running it in NCS version 1.9. I think the newer versions are the ones that are tested/supported with this course. Try NCS NCS 2.4.0 and above. There are a few changes made inbetween these NCS versions, and 1.9 is starting to get old. If you have a larger ongoing project I would understand if you stick to one NCS version for a longer period of time, but for learning NCS and BLE I would recommend upgrading to the latest NCS versions.

When it comes to the issue itself, it seems that you need to write #include </sys/printk.h> in NCS1.9, not #include <zephyr/sys/printk.h>. But nevermind that, just install a newer version.

Regards,

Elfving

RE: build doesn't recognize zephyr files

Raz_k — Thu, 15 Feb 2024 14:49:45 GMT

Hey Elfving,

Yes i am able to build and flash an example of BME sample sensor, that is located in C:\bme680

and its CMakeList.txt is:

# SPDX-License-Identifier: Apache-2.0

cmake_minimum_required(VERSION 3.20.0)

find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})

project(bme680)

FILE(GLOB app_sources src/*.c)

target_sources(app PRIVATE ${app_sources})

i tried to include the same librarys that where unable to include and build in the original issue file:

#include <zephyr/sys/printk.h>

#include <zephyr/sys/byteorder.h>

#include <zephyr/kernel.h>

#include <zephyr/drivers/gpio.h>

#include <soc.h>

#include <zephyr/bluetooth/bluetooth.h>

#include <zephyr/bluetooth/hci.h>

#include <zephyr/bluetooth/conn.h>

#include <zephyr/bluetooth/uuid.h>

#include <zephyr/bluetooth/gatt.h>

but i get the same errors as i mentioned before.

RE: build doesn't recognize zephyr files

Elfving — Thu, 15 Feb 2024 10:33:08 GMT

Hello,

That is odd. Are you able to simply build a default sample from the SDK?

Regards,

Elfving