Nrf9160dk lwm2m client

RE: Nrf9160dk lwm2m client

Øyvind — Fri, 11 Nov 2022 11:55:46 GMT

I am not able to reproduce this. I edited build configuration:

and unchecked Enable debug options

Then clicked build configuration, which ended with a complete build

....
Memory region         Used Size  Region Size  %age Used
           FLASH:      294492 B     409088 B     71.99%
            SRAM:      106712 B     211736 B     50.40%
        IDT_LIST:          0 GB         2 KB      0.00%
[435/443] Generating zephyr/tfm_nonsecure.hex
[436/443] Generating zephyr/mcuboot_primary_app.hex
[437/443] Generating zephyr/mcuboot_primary.hex
[438/443] Generating ../../zephyr/app_update.bin
sign the payload
[439/443] Generating ../../zephyr/dfu_application.zip
[440/443] Generating ../../zephyr/app_signed.hex
sign the payload
[441/443] Generating ../../zephyr/app_test_update.hex
sign the payload
[442/443] Generating ../../zephyr/app_moved_test_update.hex
[443/443] Generating zephyr/merged.hex

RE: Nrf9160dk lwm2m client

Hkhan7861 — Fri, 11 Nov 2022 10:14:08 GMT

HI, I have deleted the previous build and changed it to a build without debug options checked.

Executing task: nRF Connect: Build: lwm2m_clientt/build (active) 

Building lwm2m_clientt
west build --build-dir c:\lwm2m_clientt\build c:\lwm2m_clientt

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base (cached)).
-- Application: C:/lwm2m_clientt
-- Cache files will be written to: C:/nordicsemi/v2.1.2/zephyr/.cache
-- Zephyr version: 3.1.99 (C:/nordicsemi/v2.1.2/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160_ns, Revision: 0.7.0
-- Found host-tools: zephyr 0.14.1 (C:/nordicsemi/toolchains/v2.1.2/opt/zephyr-sdk)
-- Found dtc: C:/nordicsemi/toolchains/v2.1.2/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: zephyr 0.14.1 (C:/nordicsemi/toolchains/v2.1.2/opt/zephyr-sdk)
-- Found BOARD.dts: C:/nordicsemi/v2.1.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns.dts
-- Found devicetree overlay: C:/lwm2m_clientt/boards/nrf9160dk_nrf9160_ns.overlay
-- Generated zephyr.dts: C:/lwm2m_clientt/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/lwm2m_clientt/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/lwm2m_clientt/build/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/lwm2m_clientt/build/zephyr/dts.cmake

warning: LIGHT_SENSOR_LIGHT_MEASUREMENT_MAX_VALUE (defined at
C:/lwm2m_clientt\src/sensors/Kconfig.light_sensor:14) was assigned the value '300' but got the value
''. Check these unsatisfied dependencies: LIGHT_SENSOR (=n), APP_LIGHT_SENSOR (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LIGHT_SENSOR_LIGHT_MEASUREMENT_MAX_VALUE
and/or look up LIGHT_SENSOR_LIGHT_MEASUREMENT_MAX_VALUE in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: LIGHT_SENSOR_COLOUR_MEASUREMENT_MAX_VALUE (defined at
C:/lwm2m_clientt\src/sensors/Kconfig.light_sensor:24) was assigned the value '300' but got the value
''. Check these unsatisfied dependencies: LIGHT_SENSOR (=n), APP_LIGHT_SENSOR (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LIGHT_SENSOR_COLOUR_MEASUREMENT_MAX_VALUE
and/or look up LIGHT_SENSOR_COLOUR_MEASUREMENT_MAX_VALUE in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: DFU_TARGET_FULL_MODEM (defined at
C:/nordicsemi/v2.1.2/nrf\subsys\dfu\dfu_target/Kconfig:72) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: DFU_TARGET_STREAM (=n), DFU_TARGET (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_DFU_TARGET_FULL_MODEM and/or look up
DFU_TARGET_FULL_MODEM in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: NRF_SECURITY_RNG (defined at C:/nordicsemi/v2.1.2/nrfxlib\nrf_security\Kconfig.legacy:316)
was assigned the value 'n' but got the value 'y'. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NRF_SECURITY_RNG and/or look up
Parsing C:/lwm2m_clientt/Kconfig
Loaded configuration 'C:/nordicsemi/v2.1.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns_defconfig'
Merged configuration 'c:/lwm2m_clientt/boards/nrf9160dk_nrf9160_ns.conf'
NRF_SECURITY_RNG in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: LWM2M_IPSO_LIGHT_CONTROL_INSTANCE_COUNT (defined at subsys/net/lib/lwm2m/Kconfig.ipso:152)
was assigned the value '4' but got the value ''. Check these unsatisfied dependencies:
LWM2M_IPSO_LIGHT_CONTROL (=n), LWM2M_IPSO_SUPPORT (=n), LWM2M (=n), NETWORKING (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LWM2M_IPSO_LIGHT_CONTROL_INSTANCE_COUNT
and/or look up LWM2M_IPSO_LIGHT_CONTROL_INSTANCE_COUNT in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: LWM2M_IPSO_ONOFF_SWITCH_INSTANCE_COUNT (defined at subsys/net/lib/lwm2m/Kconfig.ipso:235)
was assigned the value '2' but got the value ''. Check these unsatisfied dependencies:
LWM2M_IPSO_SUPPORT (=n), LWM2M (=n), NETWORKING (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LWM2M_IPSO_ONOFF_SWITCH_INSTANCE_COUNT
and/or look up LWM2M_IPSO_ONOFF_SWITCH_INSTANCE_COUNT in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: LWM2M_IPSO_PUSH_BUTTON_INSTANCE_COUNT (defined at subsys/net/lib/lwm2m/Kconfig.ipso:265)
was assigned the value '2' but got the value ''. Check these unsatisfied dependencies:
LWM2M_IPSO_PUSH_BUTTON (=n), LWM2M_IPSO_SUPPORT (=n), LWM2M (=n), NETWORKING (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LWM2M_IPSO_PUSH_BUTTON_INSTANCE_COUNT
and/or look up LWM2M_IPSO_PUSH_BUTTON_INSTANCE_COUNT in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: The choice symbol LWM2M_IPSO_ONOFF_SWITCH_VERSION_1_1 (defined at
subsys/net/lib/lwm2m/Kconfig.ipso:253) was selected (set =y), but no symbol ended up as the choice
selection. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LWM2M_IPSO_ONOFF_SWITCH_VERSION_1_1 and/or
look up LWM2M_IPSO_ONOFF_SWITCH_VERSION_1_1 in the menuconfig/guiconfig interface. The Application
Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of
the manual might be helpful too.


warning: LWM2M_IPSO_ONOFF_SWITCH (defined at subsys/net/lib/lwm2m/Kconfig.ipso:230) has direct dependencies LWM2M_IPSO_SUPPORT && LWM2M && NETWORKING with value n, but is currently being y-selected by the following symbols:
 - LWM2M_APP_ONOFF_SWITCH (defined at C:/lwm2m_clientt\src/lwm2m/Kconfig:22), with value y, direct dependencies y (value: y)
 - APP_ONOFF_SWITCH (defined at C:/lwm2m_clientt/Kconfig:21), with value y, direct dependencies BOARD_NRF9160DK_NRF9160_NS (value: y), and select condition BOARD_NRF9160DK_NRF9160_NS (value: y)

error: Aborting due to Kconfig warnings

CMake Error at C:/nordicsemi/v2.1.2/zephyr/cmake/modules/kconfig.cmake:293 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/nordicsemi/v2.1.2/zephyr/cmake/modules/zephyr_default.cmake:121 (include)
  C:/nordicsemi/v2.1.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/nordicsemi/v2.1.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
  CMakeLists.txt:9 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'c:\nordicsemi\toolchains\v2.1.2\opt\bin\cmake.EXE' '-DWEST_PYTHON=c:\nordicsemi\toolchains\v2.1.2\opt\bin\python.exe' '-Bc:\lwm2m_clientt\build' -GNinja '-Sc:\lwm2m_clientt'

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

RE: Nrf9160dk lwm2m client

Øyvind — Fri, 11 Nov 2022 09:13:15 GMT

Hassan, can you please try to disable debug options in your build configuration? Do you need these for testing the sample?

When you add a build configuration with this option checked, the following options are set:

CONFIG_DEBUG_OPTIMIZATIONS - This option limits the optimizations made by the compiler to only those that do not impact debugging.
CONFIG_DEBUG_THREAD_INFO - This option adds additional information to the thread object, so that the debugger can discover the threads. This will work for any debugger. Additional threads appear in the Call Stack View.

Enabling the debugging options will affect the application's memory usage.

From the nRF Connect for VS Code documentation on Enabling debugger

RE: Nrf9160dk lwm2m client

Hkhan7861 — Fri, 11 Nov 2022 06:56:52 GMT

Executing task: nRF Connect: Build: lwm2m_client3/build (active) 

Building lwm2m_client3
west build --build-dir c:\lwm2m_client3\build c:\lwm2m_client3 --pristine --board nrf9160dk_nrf9160_ns -- -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DBOARD_ROOT:STRING="c:/lwm2m_client2;c:/lwm2m_client3" -DCONFIG_DEBUG_OPTIMIZATIONS:STRING="y" -DCONFIG_DEBUG_THREAD_INFO:STRING="y" -DCONF_FILE:STRING="c:/lwm2m_client3/boards/nrf9160dk_nrf9160_ns.conf" -DDTC_OVERLAY_FILE:STRING="c:/lwm2m_client3/boards/nrf9160dk_nrf9160_ns.overlay"

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/lwm2m_client3
-- Found Python3: C:/nordicsemi/toolchains/v2.1.2/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter 
-- Cache files will be written to: C:/nordicsemi/v2.1.2/zephyr/.cache
-- Zephyr version: 3.1.99 (C:/nordicsemi/v2.1.2/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160_ns, Revision: 0.7.0
-- Found host-tools: zephyr 0.14.1 (C:/nordicsemi/toolchains/v2.1.2/opt/zephyr-sdk)
-- Found dtc: C:/nordicsemi/toolchains/v2.1.2/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: zephyr 0.14.1 (C:/nordicsemi/toolchains/v2.1.2/opt/zephyr-sdk)
-- Found BOARD.dts: C:/nordicsemi/v2.1.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns.dts
-- Found devicetree overlay: c:/lwm2m_client3/boards/nrf9160dk_nrf9160_ns.overlay
-- Generated zephyr.dts: C:/lwm2m_client3/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/lwm2m_client3/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/lwm2m_client3/build/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/lwm2m_client3/build/zephyr/dts.cmake

warning: LIGHT_SENSOR_LIGHT_MEASUREMENT_MAX_VALUE (defined at
C:/lwm2m_client3\src/sensors/Kconfig.light_sensor:14) was assigned the value '300' but got the value
''. Check these unsatisfied dependencies: LIGHT_SENSOR (=n), APP_LIGHT_SENSOR (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LIGHT_SENSOR_LIGHT_MEASUREMENT_MAX_VALUE
and/or look up LIGHT_SENSOR_LIGHT_MEASUREMENT_MAX_VALUE in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: LIGHT_SENSOR_COLOUR_MEASUREMENT_MAX_VALUE (defined at
C:/lwm2m_client3\src/sensors/Kconfig.light_sensor:24) was assigned the value '300' but got the value
''. Check these unsatisfied dependencies: LIGHT_SENSOR (=n), APP_LIGHT_SENSOR (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LIGHT_SENSOR_COLOUR_MEASUREMENT_MAX_VALUE
Parsing C:/lwm2m_client3/Kconfig
Loaded configuration 'C:/nordicsemi/v2.1.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns_defconfig'
Merged configuration 'c:/lwm2m_client3/boards/nrf9160dk_nrf9160_ns.conf'
Merged configuration 'C:/lwm2m_client3/build/zephyr/misc/generated/extra_kconfig_options.conf'
and/or look up LIGHT_SENSOR_COLOUR_MEASUREMENT_MAX_VALUE in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: DFU_TARGET_FULL_MODEM (defined at
C:/nordicsemi/v2.1.2/nrf\subsys\dfu\dfu_target/Kconfig:72) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: DFU_TARGET_STREAM (=n), DFU_TARGET (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_DFU_TARGET_FULL_MODEM and/or look up
DFU_TARGET_FULL_MODEM in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: NRF_SECURITY_RNG (defined at C:/nordicsemi/v2.1.2/nrfxlib\nrf_security\Kconfig.legacy:316)
was assigned the value 'n' but got the value 'y'. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NRF_SECURITY_RNG and/or look up
NRF_SECURITY_RNG in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: LWM2M_IPSO_LIGHT_CONTROL_INSTANCE_COUNT (defined at subsys/net/lib/lwm2m/Kconfig.ipso:152)
was assigned the value '4' but got the value ''. Check these unsatisfied dependencies:
LWM2M_IPSO_LIGHT_CONTROL (=n), LWM2M_IPSO_SUPPORT (=n), LWM2M (=n), NETWORKING (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LWM2M_IPSO_LIGHT_CONTROL_INSTANCE_COUNT
and/or look up LWM2M_IPSO_LIGHT_CONTROL_INSTANCE_COUNT in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: LWM2M_IPSO_ONOFF_SWITCH_INSTANCE_COUNT (defined at subsys/net/lib/lwm2m/Kconfig.ipso:235)
was assigned the value '2' but got the value ''. Check these unsatisfied dependencies:
LWM2M_IPSO_SUPPORT (=n), LWM2M (=n), NETWORKING (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LWM2M_IPSO_ONOFF_SWITCH_INSTANCE_COUNT
and/or look up LWM2M_IPSO_ONOFF_SWITCH_INSTANCE_COUNT in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: LWM2M_IPSO_PUSH_BUTTON_INSTANCE_COUNT (defined at subsys/net/lib/lwm2m/Kconfig.ipso:265)
was assigned the value '2' but got the value ''. Check these unsatisfied dependencies:
LWM2M_IPSO_PUSH_BUTTON (=n), LWM2M_IPSO_SUPPORT (=n), LWM2M (=n), NETWORKING (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LWM2M_IPSO_PUSH_BUTTON_INSTANCE_COUNT
and/or look up LWM2M_IPSO_PUSH_BUTTON_INSTANCE_COUNT in the menuconfig/guiconfig interface. The
Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices
sections of the manual might be helpful too.


warning: The choice symbol LWM2M_IPSO_ONOFF_SWITCH_VERSION_1_1 (defined at
subsys/net/lib/lwm2m/Kconfig.ipso:253) was selected (set =y), but no symbol ended up as the choice
selection. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LWM2M_IPSO_ONOFF_SWITCH_VERSION_1_1 and/or
look up LWM2M_IPSO_ONOFF_SWITCH_VERSION_1_1 in the menuconfig/guiconfig interface. The Application
Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of
the manual might be helpful too.


warning: LWM2M_IPSO_ONOFF_SWITCH (defined at subsys/net/lib/lwm2m/Kconfig.ipso:230) has direct dependencies LWM2M_IPSO_SUPPORT && LWM2M && NETWORKING with value n, but is currently being y-selected by the following symbols:
 - LWM2M_APP_ONOFF_SWITCH (defined at C:/lwm2m_client3\src/lwm2m/Kconfig:22), with value y, direct dependencies y (value: y)
 - APP_ONOFF_SWITCH (defined at C:/lwm2m_client3/Kconfig:21), with value y, direct dependencies BOARD_NRF9160DK_NRF9160_NS (value: y), and select condition BOARD_NRF9160DK_NRF9160_NS (value: y)

error: Aborting due to Kconfig warnings

CMake Error at C:/nordicsemi/v2.1.2/zephyr/cmake/modules/kconfig.cmake:293 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/nordicsemi/v2.1.2/zephyr/cmake/modules/zephyr_default.cmake:121 (include)
  C:/nordicsemi/v2.1.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/nordicsemi/v2.1.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:9 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'c:\nordicsemi\toolchains\v2.1.2\opt\bin\cmake.EXE' '-DWEST_PYTHON=c:\nordicsemi\toolchains\v2.1.2\opt\bin\python.exe' '-Bc:\lwm2m_client3\build' -GNinja -DBOARD=nrf9160dk_nrf9160_ns -DNCS_TOOLCHAIN_VERSION:STRING=NONE '-DBOARD_ROOT:STRING=c:/lwm2m_client2;c:/lwm2m_client3' -DCONFIG_DEBUG_OPTIMIZATIONS:STRING=y -DCONFIG_DEBUG_THREAD_INFO:STRING=y -DCONF_FILE:STRING=c:/lwm2m_client3/boards/nrf9160dk_nrf9160_ns.conf -DDTC_OVERLAY_FILE:STRING=c:/lwm2m_client3/boards/nrf9160dk_nrf9160_ns.overlay '-Sc:\lwm2m_client3'

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

Hi Øyvind

I must be doing something wrong in my setup then. Please point me in the right direction.

Kind regards,

Hassan

RE: Nrf9160dk lwm2m client

Øyvind — Thu, 10 Nov 2022 13:48:34 GMT

Hassan, I'm using nRF Connect SDK v2.1.2 from the Toolchain Manager. Created new application (freestanding) of the LwM2M client, built for nrf9160dk_nrf9160_ns

-Øyvind

RE: Nrf9160dk lwm2m client

Hkhan7861 — Thu, 10 Nov 2022 13:23:18 GMT

I had not changed anything. My device was also unplugged. I just redownloaded the toolchain as well. what toolchain are you using? The sample i'm using is the nrf9160 sample and im building nrf9160dk_nrf9160_ns. No configurations or anything else was changed.

Kind regards,

Hassan

RE: Nrf9160dk lwm2m client

Øyvind — Thu, 10 Nov 2022 12:35:47 GMT

Hello Hassan,

What configurations have you added to the project? Building the default sample for nrf9160dk_nrf9160_ns did not throw any error on my side.

Kind regards,
Øyvind