Build Configuration fails for SDK 2.2.0

Hi!

When using NRF Connect SDK 2.1.1 never had problem compiling the asset tracker example for the Thingy 91.

I'm now trying to switch to SDK 2.2.0 in combination with NRF Toolchain 2.2.0, but creating the build configuration fails. 

My settings for the project: 

- Freestanding application type

- SDK 2.2.0

- Toolchain 2.2.0

- Application template: asset_tracker_v2

And for the build configuration:

- Board: thingy91_nrf9160_ns

- Configuration: prj.conf

- Build after generating configuration: checked

- Enable debug options: checked


When I then click "Build Configuration" I do see an error "Makefile entry point not found", and the build configuration fails showing me this in the terminal:

[416/436] Linking C static library zephyr/kernel/libkernel.a
[417/436] Linking C executable zephyr/zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map 
: && ccache /opt/nordic/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc  -gdwarf-4 zephyr/CMakeFiles/zephyr_pre0.dir/misc/empty_file.c.obj -o zephyr/zephyr_pre0.elf  -fuse-ld=bfd  -Wl,-T  zephyr/linker_zephyr_pre0.cmd  -Wl,-Map=/Users/huubsmeitink/Documents/eMill/emill-embedded-software/test8/asset_tracker_v22/build/zephyr/zephyr_pre0.map  -Wl,--whole-archive  app/libapp.a  zephyr/libzephyr.a  zephyr/arch/common/libarch__common.a  zephyr/arch/arch/arm/core/aarch32/libarch__arm__core__aarch32.a  zephyr/arch/arch/arm/core/aarch32/cortex_m/libarch__arm__core__aarch32__cortex_m.a  zephyr/arch/arch/arm/core/aarch32/cortex_m/cmse/libarch__arm__core__aarch32__cortex_m__cmse.a  zephyr/arch/arch/arm/core/aarch32/mpu/libarch__arm__core__aarch32__mpu.a  zephyr/lib/libc/newlib/liblib__libc__newlib.a  zephyr/lib/posix/liblib__posix.a  zephyr/soc/arm/common/cortex_m/libsoc__arm__common__cortex_m.a  zephyr/boards/boards/arm/thingy91_nrf9160_ns/lib..__nrf__boards__arm__thingy91_nrf9160.a  zephyr/subsys/dfu/boot/libsubsys__dfu__boot.a  zephyr/subsys/net/libsubsys__net.a  zephyr/subsys/net/ip/libsubsys__net__ip.a  zephyr/subsys/net/lib/mqtt/libsubsys__net__lib__mqtt.a  zephyr/subsys/random/libsubsys__random.a  zephyr/drivers/clock_control/libdrivers__clock_control.a  zephyr/drivers/console/libdrivers__console.a  zephyr/drivers/gpio/libdrivers__gpio.a  zephyr/drivers/i2c/libdrivers__i2c.a  zephyr/drivers/led/libdrivers__led.a  zephyr/drivers/pwm/libdrivers__pwm.a  zephyr/drivers/sensor/adxl362/libdrivers__sensor__adxl362.a  zephyr/drivers/sensor/adxl372/libdrivers__sensor__adxl372.a  zephyr/drivers/sensor/bme680/libdrivers__sensor__bme680.a  zephyr/drivers/spi/libdrivers__spi.a  zephyr/drivers/watchdog/libdrivers__watchdog.a  zephyr/drivers/hwinfo/libdrivers__hwinfo.a  zephyr/drivers/flash/libdrivers__flash.a  zephyr/drivers/serial/libdrivers__serial.a  zephyr/drivers/entropy/libdrivers__entropy.a  zephyr/drivers/timer/libdrivers__timer.a  zephyr/drivers/pinctrl/libdrivers__pinctrl.a  modules/nrf/lib/nrf_modem_lib/lib..__nrf__lib__nrf_modem_lib.a  modules/nrf/lib/dk_buttons_and_leds/lib..__nrf__lib__dk_buttons_and_leds.a  modules/nrf/lib/at_monitor/lib..__nrf__lib__at_monitor.a  modules/nrf/lib/at_host/lib..__nrf__lib__at_host.a  modules/nrf/lib/at_cmd_parser/lib..__nrf__lib__at_cmd_parser.a  modules/nrf/lib/lte_link_control/lib..__nrf__lib__lte_link_control.a  modules/nrf/lib/modem_info/lib..__nrf__lib__modem_info.a  modules/nrf/lib/pdn/lib..__nrf__lib__pdn.a  modules/nrf/lib/fatal_error/lib..__nrf__lib__fatal_error.a  modules/nrf/lib/date_time/lib..__nrf__lib__date_time.a  modules/nrf/lib/hw_id/lib..__nrf__lib__hw_id.a  modules/nrf/lib/location/lib..__nrf__lib__location.a  modules/nrf/lib/modem_antenna/lib..__nrf__lib__modem_antenna.a  modules/nrf/lib/qos/lib..__nrf__lib__qos.a  modules/nrf/subsys/net/lib/nrf_cloud/lib..__nrf__subsys__net__lib__nrf_cloud.a  modules/nrf/subsys/net/lib/download_client/lib..__nrf__subsys__net__lib__download_client.a  modules/nrf/subsys/net/lib/fota_download/lib..__nrf__subsys__net__lib__fota_download.a  modules/nrf/subsys/caf/modules/lib..__nrf__subsys__caf__modules.a  modules/nrf/subsys/dfu/dfu_target/lib..__nrf__subsys__dfu__dfu_target.a  modules/nrf/subsys/fw_info/lib..__nrf__subsys__fw_info.a  modules/nrf/modules/tfm/zephyr/libtfm_api_nrf.a  modules/mcuboot/boot/bootutil/zephyr/libmcuboot_util.a  modules/trusted-firmware-m/libtfm_api.a  modules/cjson/libcjson.a  modules/hal_nordic/nrfx/libmodules__hal_nordic__nrfx.a  /opt/nordic/ncs/v2.2.0/nrfxlib/nrf_modem/lib/cortex-m33/hard-float/libmodem.a  modules/nrfxlib/nrfxlib/nrf_security/src/zephyr/libmbedtls_zephyr.a  -Wl,--no-whole-archive  zephyr/kernel/libkernel.a  zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj  -L"/opt/nordic/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/thumb/v8-m.main+fp/hard"  -L/Users/huubsmeitink/Documents/eMill/emill-embedded-software/test8/asset_tracker_v22/build/zephyr  -lgcc  zephyr/arch/common/libisr_tables.a  tfm/secure_fw/s_veneers.o  -no-pie  -Wl,--gc-sections  -Wl,--build-id=none  -Wl,--sort-common=descending  -Wl,--sort-section=alignment  -Wl,-u,_OffsetAbsSyms  -Wl,-u,_ConfigAbsSyms  -nostdlib  -static  -Wl,-X  -Wl,-N  -Wl,--orphan-handling=warn  -lm  -Wl,-lc  -L"/opt/nordic/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi"/lib/thumb/v8-m.main+fp/hard  -u_printf_float  -Wl,-lgcc  -lc  -specs=nano.specs  modules/nrfxlib/nrfxlib/nrf_security/src/libmbedcrypto.a  /opt/nordic/ncs/v2.2.0/nrfxlib/crypto/nrf_oberon/lib/cortex-m33/hard-float/liboberon_mbedtls_3.0.12.a  modules/nrfxlib/nrfxlib/nrf_security/src/libmbedcrypto_base.a  -mcpu=cortex-m33  -mthumb  -mabi=aapcs  -mfpu=fpv5-sp-d16  -mfloat-abi=hard  -mfp16-format=ieee  /opt/nordic/ncs/v2.2.0/nrfxlib/crypto/nrf_oberon/lib/cortex-m33/hard-float/liboberon_3.0.12.a  -lc && cd /Users/huubsmeitink/Documents/eMill/emill-embedded-software/test8/asset_tracker_v22/build/zephyr && /opt/nordic/ncs/toolchains/v2.2.0/Cellar/cmake/3.20.5/bin/cmake -E echo
/opt/nordic/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
/opt/nordic/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `FLASH' overflowed by 14492 bytes
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /opt/nordic/ncs/toolchains/v2.2.0/bin/cmake --build /Users/huub/Documents/eMill/emill-embedded-software/test8/asset_tracker_v22/build


I'm using a Mac, running Big Sur. 


I hope I'm just missing something, but I wouldn't know what since doing the same for SDK 2.1.1 doesn't give me any problems.

Parents
  • Hi Hubert,

    Thank you for contacting Devzone at NordicSemi.

    Can you please try following:

    1) try building the asset_tracker_v2 for nCS version 2.2.0 along with toolchain 2.2.0 without checking the "enable debug options"

    2) try building for 9160dk with same (without debug) options

    3) try building with previous version of nCS (for example 2.0.0) without (without debug) options and with different board.

    Let me know if it is successful or not or you find some other error.

    Regards,

    Naeem 

  • 1) try building the asset_tracker_v2 for nCS version 2.2.0 along with toolchain 2.2.0 without checking the "enable debug options"

    Still get the "makefile entry point not found" initially, but no more compile errors. So this seems to work.

    2) try building for 9160dk with same (without debug) options.

    Also still get the "makefile entry point not found" initially, but no more compile errors. So this seems to work too.

    3) try building with the previous version of nCS (for example 2.0.0) without (without debug) options and with a different board.

    What do you mean by a different board? Only the DK and the Thingy are supported for the asset tracker, right? I tried building it for the DK on version 2.0.0 with debug options enabled and this gave me no errors (except for the "makefile entry point not found"). 

    And, as I stated initially, building for the thingy 91 with debug options enabled on version 2.1.1 also gave me no problems. So it seems that enabled debug options on version 2.2.0 is causing the compilation errors.

  • hubert_11 said:
    So it seems that enabled debug options on version 2.2.0 is causing the compilation errors.

    Yes, and we have reported that internally.

Reply Children
No Data
Related