Flash overflow?

RE: Flash overflow?

Susheel Nuguru — Fri, 31 May 2024 04:19:54 GMT

That should not be, SW10 is only debug multiplexer switch. It does not behave the same way like your at my end with that switch.

What is the full version of the nrf9160DK you have? I am using PCA10090v1.1.0

RE: Flash overflow?

BenA — Thu, 30 May 2024 14:45:55 GMT

Hi Susheel - I had already tried this based on previous guidance in this thread

I think I might have found the issue... if I have SW10 on my 9160DK set to nRF91, I get the failure. When I switch it over to nRF52, it seems to work!

Why would this be? It doesn't make sense to me

Regards,

Ben

RE: Flash overflow?

Susheel Nuguru — Thu, 30 May 2024 10:46:05 GMT

It looks that you and me both were only flashing only nRf91 core and not the other core.

AS mentioned here in programming this sample, you need to change the switch and program HCI LPUART on nRF52 core to get a HCI response for the command. Right now it is timing out and creating a controlled hardfault exception.

We both overlooked the opcode in the error message and did not see that this hardfault was a controlled exception. The BLE team have taken the feedback to improve the logs to give little more informative message so that our first instinct is not to panic looking at the hardfault and focus more on the opcode that caused it.

Try flashing HCI LPUART code to nRF52 chip and you will see this problem goes away.

RE: Flash overflow?

Susheel Nuguru — Wed, 29 May 2024 11:12:50 GMT

One of my colleagues who is an expert in debugging this has offered to assist in this. He will try to reproduce and see if he can find more insights on why this is happening.

RE: Flash overflow?

BenA — Wed, 29 May 2024 06:54:25 GMT

Hi Susheel - thank you.

I am still having this issue - so please continue!

RE: Flash overflow?

Susheel Nuguru — Mon, 27 May 2024 12:25:12 GMT

BTW, if you have progressed away from this error then please let me know, so that I do not spend time on an issue that you already fixed.

RE: Flash overflow?

Susheel Nuguru — Mon, 27 May 2024 12:24:19 GMT

I can reproduce the error you mentioned.

I see that the faulting address on mine is 0x0001f458.

Doing and addr2line shows this

$ arm-none-eabi-addr2line -e E:\ncs\v2.6.0\nrf\samples\cellular\324344\build\zephyr\zephyr.elf -a 0x0001f458
0x0001f458
E:/ncs/v2.6.0/zephyr/subsys/bluetooth/host/hci_core.c:333 (discriminator 3)

This seems like a corrupt stack that means that the hardfault log info cannot be trusted.

I am trying to enable Thread Analyzer to see if it gives any more info than basic hardfault. Will be back to you soon.

RE: Flash overflow?

BenA — Mon, 13 May 2024 09:34:26 GMT

Hi - please see attached

devzone.nordicsemi.com/.../aws_5F00_iot_5F00_add_5F00_lte_5F00_ble_5F00_gateway_5F00_260_5F00_with_5F00_ble_5F00_scan-2.zip

RE: Flash overflow?

Susheel Nuguru — Fri, 10 May 2024 10:45:47 GMT

Can you please give me your project, so that I can test it at my end to see if I can get more debug data out?

RE: Flash overflow?

BenA — Wed, 08 May 2024 09:06:20 GMT

Hi - I included the four lines in pros.conf as instructed - but I don't seem to be getting any of the messages - I assume I would see them in the serial monitor?

RE: Flash overflow?

Susheel Nuguru — Wed, 08 May 2024 07:17:27 GMT

I requested you to enable the thread analyzer and monitor aswell, This should throw some logs onto the serial log terminal. Can you show me what the thread analyzer shows on each thread's stack usage? It is possible that sometime the neighboring rogue thread can cause a stack corruption in a well behaved thread.

RE: Flash overflow?

BenA — Tue, 07 May 2024 12:47:58 GMT

Hi - sorry for the delay

I tried again and made sure I clicked 'save to file' - it tells me that it to /build/zephyr/.config

I can verify that this worked by inspection of that file, and because VS Code says 'In build: 8192' if I try to add CONFIG_MAIN_STACK_SIZE manually to prj.conf

I still get the exact same error when I run the code!

RE: Flash overflow?

Susheel Nuguru — Thu, 02 May 2024 07:00:21 GMT

Not sure if you have that much amount of RAM left to reserve for stack for main thread. I would normally increase it by 1024 or 2048 bytes at a time. Set to probably 8096 and not to 32k. Did you click on the "save to file" button on the top right corner?

RE: Flash overflow?

BenA — Tue, 30 Apr 2024 10:44:44 GMT

That doesn't seem to be working :-(

Is this the right place to set this?

RE: Flash overflow?

Susheel Nuguru — Mon, 29 Apr 2024 09:35:14 GMT

This seems like a hardfault on stack over on main thread. Have you tried to increase the CONFIG_MAIN_STACK_SIZE in your prj.conf?

If you are using or nRF extension on Visual Studio code you can see the GUI for KConfig and increase the value of the main stack to see if this issue gets solved.

Also, It is a good idea to enable the Thread_Analyzer while in development phase of your project to have.a good idea on the stack usage on threads you are using in your sofware delevelopment.

RE: Flash overflow?

BenA — Mon, 29 Apr 2024 08:27:06 GMT

Hi Susheel - thank you for the reply.

Is this what you need to see?:

ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:331
        command opcode 0x0c03 timeout with err -11
[00:00:10.267,791] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000002  r2/a3:  0x00000001
[00:00:10.267,791] <err> os: r3/a4:  0x0000014b r12/ip:  0x00000004 r14/lr:  0x00028e11
[00:00:10.267,822] <err> os:  xpsr:  0x41000000
[00:00:10.267,822] <err> os: Faulting instruction address (r15/pc): 0x00028e1c
[00:00:10.267,883] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.267,913] <err> os: Current thread: 0x20010ec0 (main)
[00:00:10.323,974] <err> fatal_error: Resetting system

Regards,

Ben

RE: Flash overflow?

Susheel Nuguru — Fri, 26 Apr 2024 10:57:03 GMT

It might help to get the current thread context that is calling the HCI functionality here.

Can you please enable the below in your prj.conf file, compile and rerun the firmware and give us the assert handler and serial logs details here? That will help understand the context more.

CONFIG_THREAD_ANALYZER=y
CONFIG_THREAD_NAME=y
CONFIG_THREAD_MONITOR=y
CONFIG_DEBUG_OPTIMIZATIONS=y

RE: Flash overflow?

BenA — Tue, 23 Apr 2024 14:29:32 GMT

Hi Michal - have you had a chance to get up-to-speed with this one yet?

Let me try and help by summarising

I am working on a project based on the AWS_IoT sample
- nRF9160 DK / nRF Connect SDK v2.6.0
I am trying to add BLE functionality to the sample
- I just need to be able to scan for BLE advertisements
I am now able to add the BLE via kconfig and compile the code
If I try to actually perform a BLE function (i.e. a scan), I get the following error:

ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:331

Regards,
Ben

RE: Flash overflow?

Michal — Tue, 16 Apr 2024 07:48:54 GMT

Hello Ben,

I took over the case since my colleague is currently unavailable, but it will take me a bit to understand the background and the issue.

Sorry for the delays and thank you for your patience.

Best regards,

Michal

RE: Flash overflow?

BenA — Wed, 10 Apr 2024 14:33:47 GMT

Hi - do you get the same issue if you build/run this code?

I know that the hci_lpuart is successfully running on the nRF52, as I can run other BLE apps (i.e. a project I've made based on LTE-BLE gateway sample)

RE: Flash overflow?

BenA — Fri, 05 Apr 2024 14:33:09 GMT

Hi - yes, I've built and flashed the hci_lpuart sample to the nRF52 - but I'm still getting the same issue:

*** Booting nRF Connect SDK d96769faceca ***
[00:00:00.253,631] <inf> aws_iot_sample: The AWS IoT sample started, version: v1.0.0
Initialising BLE
ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:331
        command opcode 0x0c03 timeout with err -11
[00:00:10.264,129] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x00000002
[00:00:10.264,160] <err> os: r3/a4:  0x2000d4a0 r12/ip:  0x00000010 r14/lr:  0x0001f625
[00:00:10.264,160] <err> os:  xpsr:  0x41000000
[00:00:10.264,160] <err> os: Faulting instruction address (r15/pc): 0x0001f630
[00:00:10.264,221] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.264,251] <err> os: Current thread: 0x20010b90 (unknown)
[00:00:10.320,587] <err> fatal_error: Resetting system

RE: Flash overflow?

Hieu — Fri, 05 Apr 2024 12:29:02 GMT

Hi Ben,

[quote user="BenA"]

I can successfully build the project you shared. I tried adding simple BLE scanning, but I'm getting the following error:

ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:331

I guess this is another configuration I need to set somewhere?

[/quote]

Have you flashed the HCI application onto the nRF52840 device on the DK? If not, that would be the problem. The design is that the nRF9160 will run only the BLE Host application, and the nRF52840 will run the BLE Controller application.

Please refer to the documentation of the LTE BLE Gateway sample for more information.

[quote user="BenA"]

On another note - I don't quite understand how you've added the BLE to the config - as kconfig parameters such as CONFIG_BT=y are in a separate .conf file.

I added them to the main prj.conf for the purposes of this build - but am I missing something? How to I tell it to also read lte_ble_gateway.conf?

[/quote]

You guessed right. The other .conf file can be included in the build.

If you are building from the command line with west, refer to this guide: Application Development — Zephyr Project documentation (nRF Connect SDK) (nordicsemi.com).

If you are building with the nRF Connect for VS Code Extension, you can specify additional .conf file to be included in a build configuration:

You might also want to know that the nRF Connect SDK also include a solution for different "build types" that makes use of different .conf files. However, that's not what I am using here.

RE: Flash overflow?

BenA — Thu, 04 Apr 2024 17:11:40 GMT

Thanks Hieu,

I can successfully build the project you shared. I tried adding simple BLE scanning, but I'm getting the following error:

ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:331

I guess this is another configuration I need to set somewhere?

On another note - I don't quite understand how you've added the BLE to the config - as kconfig parameters such as CONFIG_BT=y are in a separate .conf file.

I added them to the main prj.conf for the purposes of this build - but am I missing something? How to I tell it to also read lte_ble_gateway.conf?

devzone.nordicsemi.com/.../aws_5F00_iot_5F00_add_5F00_lte_5F00_ble_5F00_gateway_5F00_260_5F00_with_5F00_ble_5F00_scan.zip

RE: Flash overflow?

Hieu — Tue, 02 Apr 2024 22:20:37 GMT

Hi Ben,

Sorry for the long wait. We have had the Easter holiday.

From your build log, the failure happened during the application compilation, but I can't see any further what the problem could be.

Here is my project. I used nRF Connect SDK v2.6.0, but there shouldn't be much difference. Please let me know if you need v2.5.2 specifically.

devzone.nordicsemi.com/.../aws_5F00_iot_5F00_add_5F00_lte_5F00_ble_5F00_gateway_5F00_260.zip

RE: Flash overflow?

BenA — Tue, 02 Apr 2024 09:04:43 GMT

Here is the full build output:

 *  Executing task: nRF Connect: Generate config nrf9160dk_nrf9160_ns for /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo 

Building edge-plus-iot-demo
west build --build-dir /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo --pristine --board nrf9160dk_nrf9160_ns --no-sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE -DBOARD_ROOT=/Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo
-- CMake version: 3.20.5
-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/opt/python@3.9/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/benaskem/Library/Caches/zephyr
-- Zephyr version: 3.4.99 (/opt/nordic/ncs/v2.5.2/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: nrf9160dk_nrf9160_ns, Revision: 0.14.0
-- Found host-tools: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/20d68df7e5/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/ncs/v2.5.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns.dts
-- Found devicetree overlay: /opt/nordic/ncs/v2.5.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns_0_14_0.overlay
-- Found devicetree overlay: /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/boards/nrf9160dk_nrf9160_ns.overlay
-- Found devicetree overlay: /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/boards/nrf9160dk_nrf9160_ns_0_14_0.overlay
-- Generated zephyr.dts: /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/zephyr/dts.cmake

warning: Experimental symbol TFM_EXPERIMENTAL is enabled.


warning: Experimental symbol NET_CONNECTION_MANAGER is enabled.

Parsing /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/Kconfig
Loaded configuration '/opt/nordic/ncs/v2.5.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns_defconfig'
Merged configuration '/Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/prj.conf'
Merged configuration '/Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/boards/nrf9160dk_nrf9160_ns.conf'
Configuration saved to '/Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/zephyr/.config'
Kconfig header saved to '/Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/opt/python@3.9/bin/python3.9 (found version "3.9.6") found components: Interpreter 
Changed board to secure nrf9160dk_nrf9160 (NOT NS)

=== child image mcuboot -  begin ===
loading initial cache file /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/mcuboot/child_image_preload.cmake
Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/ncs/v2.5.2/bootloader/mcuboot/boot/zephyr
-- CMake version: 3.20.5
-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/opt/python@3.9/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/benaskem/Library/Caches/zephyr
-- Zephyr version: 3.4.99 (/opt/nordic/ncs/v2.5.2/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: nrf9160dk_nrf9160, Revision: 0.14.0
-- Found host-tools: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/20d68df7e5/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/ncs/v2.5.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts
-- Found devicetree overlay: /opt/nordic/ncs/v2.5.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_0_14_0.overlay
-- Found devicetree overlay: /opt/nordic/ncs/v2.5.2/bootloader/mcuboot/boot/zephyr/app.overlay
-- Generated zephyr.dts: /Users/benaskem/Documents/nrF_Connect_SDK/git/edge-plus-iot-demo/build/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/benaskem/Documents/nrF_Connect_SDK/git/edge-plus-iot-demo/build/mcuboot/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/benaskem/Documents/nrF_Connect_SDK/git/edge-plus-iot-demo/build/mcuboot/zephyr/dts.cmake
Parsing /opt/nordic/ncs/v2.5.2/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration '/opt/nordic/ncs/v2.5.2/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_defconfig'
Merged configuration '/opt/nordic/ncs/v2.5.2/bootloader/mcuboot/boot/zephyr/prj.conf'
Merged configuration '/opt/nordic/ncs/v2.5.2/nrf/modules/mcuboot/tfm.conf'
Merged configuration '/opt/nordic/ncs/v2.5.2/nrf/modules/mcuboot/fih_low_enable.conf'
Merged configuration '/opt/nordic/ncs/v2.5.2/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Merged configuration '/Users/benaskem/Documents/nrF_Connect_SDK/git/edge-plus-iot-demo/build/mcuboot/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to '/Users/benaskem/Documents/nrF_Connect_SDK/git/edge-plus-iot-demo/build/mcuboot/zephyr/.config'
Kconfig header saved to '/Users/benaskem/Documents/nrF_Connect_SDK/git/edge-plus-iot-demo/build/mcuboot/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
MCUBoot bootloader key file: /opt/nordic/ncs/v2.5.2/bootloader/mcuboot/root-ec-p256.pem
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/benaskem/Documents/nrF_Connect_SDK/git/edge-plus-iot-demo/build/mcuboot
=== child image mcuboot -  end ===

CMake Warning at /opt/nordic/ncs/v2.5.2/nrf/modules/mcuboot/CMakeLists.txt:320 (message):
  

          ---------------------------------------------------------
          --- WARNING: Using default MCUBoot key, it should not ---
          --- be used for production.                           ---
          ---------------------------------------------------------
          



CMake Warning at /opt/nordic/ncs/v2.5.2/zephyr/CMakeLists.txt:1958 (message):
  __ASSERT() statements are globally ENABLED


CMake Warning at /opt/nordic/ncs/v2.5.2/nrf/cmake/partition_manager.cmake:79 (message):
  

          ---------------------------------------------------------------------
          --- WARNING: Using a bootloader without pm_static.yml.            ---
          --- There are cases where a deployed product can consist of       ---
          --- multiple images, and only a subset of these images can be     ---
          --- upgraded through a firmware update mechanism. In such cases,  ---
          --- the upgradable images must have partitions that are static    ---
          --- and are matching the partition map used by the bootloader     ---
          --- programmed onto the device.                                   ---
          ---------------------------------------------------------------------
          

Call Stack (most recent call first):
  /opt/nordic/ncs/v2.5.2/zephyr/cmake/modules/kernel.cmake:247 (include)
  /opt/nordic/ncs/v2.5.2/zephyr/cmake/modules/zephyr_default.cmake:138 (include)
  /opt/nordic/ncs/v2.5.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /opt/nordic/ncs/v2.5.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:9 (find_package)


Dropping partition 'nonsecure_storage' since it is empty.
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build
-- west build: building application
[1/449] Preparing syscall dependency handling

[1/182] Preparing syscall dependency handling

[11/182] Generating include/generated/version.h
-- Zephyr version: 3.4.99 (/opt/nordic/ncs/v2.5.2/zephyr), build: 4b5ef270413a
[182/182] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       31254 B        48 KB     63.59%
             RAM:       16368 B        88 KB     18.16%
        IDT_LIST:          0 GB         2 KB      0.00%
[13/449] Generating include/generated/version.h
-- Zephyr version: 3.4.99 (/opt/nordic/ncs/v2.5.2/zephyr), build: 4b5ef270413a
[14/449] Generating ../../tfm/CMakeCache.txt
CMake Warning at cmake/version.cmake:22 (message):
  Actual TF-M version is not available from Git repository.  Settled to
  v1.8.0
Call Stack (most recent call first):
  CMakeLists.txt:22 (include)


-- Found Git: /opt/nordic/ncs/toolchains/20d68df7e5/bin/git (found version "2.37.3") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/opt/python@3.9/bin/python3.9 (found version "3.9.6") found components: Interpreter 
CMake Deprecation Warning at /opt/nordic/ncs/v2.5.2/zephyr/cmake/modules/FindDeprecated.cmake:121 (message):
  'PYTHON_PREFER' variable is deprecated.  Please use Python3_EXECUTABLE
  instead.
Call Stack (most recent call first):
  /opt/nordic/ncs/v2.5.2/zephyr/cmake/modules/python.cmake:16 (find_package)
  /opt/nordic/ncs/v2.5.2/zephyr/cmake/modules/user_cache.cmake:30 (include)
  /opt/nordic/ncs/v2.5.2/zephyr/cmake/modules/extensions.cmake:5 (include)
  /opt/nordic/ncs/v2.5.2/nrf/subsys/nrf_security/tfm/CMakeLists.txt:36 (include)


-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/opt/python@3.9/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/benaskem/Library/Caches/zephyr
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/tfm
[205/209] Linking C executable bin/tfm_s.axf
Memory region         Used Size  Region Size  %age Used
           FLASH:      129932 B     261632 B     49.66%
             RAM:       52788 B        88 KB     58.58%
[24/449] Performing install step for 'tfm'
-- Install configuration: "MinSizeRel"
[109/449] Building C object CMakeFiles/app.dir/src/ble.c.obj
In file included from ../src/ble.c:2:
../src/edge.h:52:25: warning: 'key_handle' defined but not used [-Wunused-variable]
   52 | static psa_key_handle_t key_handle;
      |                         ^~~~~~~~~~
../src/edge.h:50:16: warning: 'm_decrypted_text' defined but not used [-Wunused-variable]
   50 | static uint8_t m_decrypted_text[NRF_CRYPTO_EXAMPLE_AES_MAX_TEXT_SIZE];
      |                ^~~~~~~~~~~~~~~~
../src/edge.h:49:16: warning: 'm_encrypted_text' defined but not used [-Wunused-variable]
   49 | static uint8_t m_encrypted_text[NRF_CRYPTO_EXAMPLE_AES_MAX_TEXT_SIZE];
      |                ^~~~~~~~~~~~~~~~
../src/edge.h:45:16: warning: 'm_plain_text' defined but not used [-Wunused-variable]
   45 | static uint8_t m_plain_text[NRF_CRYPTO_EXAMPLE_AES_MAX_TEXT_SIZE] = {
      |                ^~~~~~~~~~~~
[116/449] Building C object CMakeFiles/app.dir/src/main.c.obj
In file included from ../src/main.c:13:
../src/edge.h:52:25: warning: 'key_handle' defined but not used [-Wunused-variable]
   52 | static psa_key_handle_t key_handle;
      |                         ^~~~~~~~~~
../src/edge.h:50:16: warning: 'm_decrypted_text' defined but not used [-Wunused-variable]
   50 | static uint8_t m_decrypted_text[NRF_CRYPTO_EXAMPLE_AES_MAX_TEXT_SIZE];
      |                ^~~~~~~~~~~~~~~~
../src/edge.h:49:16: warning: 'm_encrypted_text' defined but not used [-Wunused-variable]
   49 | static uint8_t m_encrypted_text[NRF_CRYPTO_EXAMPLE_AES_MAX_TEXT_SIZE];
      |                ^~~~~~~~~~~~~~~~
../src/edge.h:45:16: warning: 'm_plain_text' defined but not used [-Wunused-variable]
   45 | static uint8_t m_plain_text[NRF_CRYPTO_EXAMPLE_AES_MAX_TEXT_SIZE] = {
      |                ^~~~~~~~~~~~
[435/449] Linking C executable zephyr/zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map 
: && ccache /opt/nordic/ncs/toolchains/20d68df7e5/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  -T  zephyr/linker_zephyr_pre0.cmd  -Wl,-Map=/Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/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/picolibc/liblib__libc__picolibc.a  zephyr/lib/libc/common/liblib__libc__common.a  zephyr/soc/soc/arm/common/cortex_m/libsoc__arm__common__cortex_m.a  zephyr/boards/arm/nrf9160dk_nrf9160/libboards__arm__nrf9160dk_nrf9160.a  zephyr/subsys/random/libsubsys__random.a  zephyr/subsys/bluetooth/common/libsubsys__bluetooth__common.a  zephyr/subsys/bluetooth/host/libsubsys__bluetooth__host.a  zephyr/subsys/dfu/boot/libsubsys__dfu__boot.a  zephyr/subsys/net/libsubsys__net.a  zephyr/subsys/net/l2/offloaded_netdev/libsubsys__net__l2__offloaded_netdev.a  zephyr/subsys/net/ip/libsubsys__net__ip.a  zephyr/subsys/net/lib/mqtt/libsubsys__net__lib__mqtt.a  zephyr/subsys/net/lib/http/libsubsys__net__lib__http.a  zephyr/subsys/net/conn_mgr/libsubsys__net__conn_mgr.a  zephyr/drivers/bluetooth/libdrivers__bluetooth.a  zephyr/drivers/clock_control/libdrivers__clock_control.a  zephyr/drivers/console/libdrivers__console.a  zephyr/drivers/entropy/libdrivers__entropy.a  zephyr/drivers/flash/libdrivers__flash.a  zephyr/drivers/gpio/libdrivers__gpio.a  zephyr/drivers/hwinfo/libdrivers__hwinfo.a  zephyr/drivers/pinctrl/libdrivers__pinctrl.a  zephyr/drivers/serial/libdrivers__serial.a  zephyr/drivers/timer/libdrivers__timer.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/hw_id/lib..__nrf__lib__hw_id.a  modules/nrf/lib/modem_antenna/lib..__nrf__lib__modem_antenna.a  modules/nrf/subsys/nrf_security/src/zephyr/libmbedtls_zephyr.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/net/lib/aws_jobs/lib..__nrf__subsys__net__lib__aws_jobs.a  modules/nrf/subsys/net/lib/aws_fota/lib..__nrf__subsys__net__lib__aws_fota.a  modules/nrf/subsys/net/lib/aws_iot/lib..__nrf__subsys__net__lib__aws_iot.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.5.2/nrfxlib/nrf_modem/lib/nRF9160/soft-float/libmodem.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/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/thumb/v8-m.main/nofp"  -L/Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/zephyr  -lgcc  zephyr/arch/common/libisr_tables.a  tfm/secure_fw/s_veneers.o  -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  -Wl,-no-pie  -DPICOLIBC_INTEGER_PRINTF_SCANF  modules/nrf/subsys/nrf_security/src/libmbedtls.a  modules/nrf/subsys/nrf_security/src/libmbedx509.a  modules/nrf/subsys/nrf_security/src/libmbedcrypto.a  /opt/nordic/ncs/v2.5.2/nrfxlib/crypto/nrf_oberon/lib/cortex-m33/soft-float/liboberon_mbedtls_3.0.13.a  modules/nrf/subsys/nrf_security/src/libmbedcrypto_base.a  -mcpu=cortex-m33  -mthumb  -mabi=aapcs  -mfp16-format=ieee  /opt/nordic/ncs/v2.5.2/nrfxlib/crypto/nrf_oberon/lib/cortex-m33/soft-float/liboberon_3.0.13.a  --specs=picolibc.specs  -lc  -lgcc && cd /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build/zephyr && /opt/nordic/ncs/toolchains/20d68df7e5/Cellar/cmake/3.20.5/bin/cmake -E true
/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/zephyr_pre0.elf section `text' will not fit in region `FLASH'
/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `FLASH' overflowed by 119504 bytes
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /opt/nordic/ncs/toolchains/20d68df7e5/bin/cmake --build /Users/benaskem/Documents/nRF_Connect_SDK/git/edge-plus-iot-demo/build

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