nrf7002dk - region `FLASH' overflowed

RE: nrf7002dk - region `FLASH' overflowed

Sigurd Hellesvik — Mon, 11 Sep 2023 11:49:52 GMT

In your log, I see multiple warnings like this:

warning: NORDIC_QSPI_NOR (defined at C:/nordicsemi/v2.3.0/nrf/Kconfig.nrf:97,
drivers/flash/Kconfig.nordic_qspi_nor:4) was assigned the value 'y' but got the value 'n'. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NORDIC_QSPI_NOR and/or look up
NORDIC_QSPI_NOR 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.

I suggest that you look into fixing these first.

You can do this by running "ninja menuconfig" inside "build/" or inside "build/mcuboot", depending on which image has the warning.

[quote user="Candela"]think it has to do with the XIP address warning [/quote]

Do you try to use XIP in your project?

RE: nrf7002dk - region `FLASH' overflowed

Candela — Mon, 11 Sep 2023 10:26:16 GMT

Hi Sigurd,

Finally, I have achieved to build succesfully the app deleting the partition manager file. Now the app fits on the nRF5340.

However, I think there is something wrong with the address mapping, because I can't load any new images by MCUMGR (it used to work before adding the WiFi configurations that caused the overflow), and, if I try to flash the hex file directly into the board, the BLE stops working (due to the hci image i guess...) I think it has to do with the XIP address warning on the last build log I uploaded.

I have also added the SPI configurations you propose.

Thank you!

Candela

RE: nrf7002dk - region `FLASH' overflowed

Sigurd Hellesvik — Mon, 11 Sep 2023 07:35:16 GMT

[quote user="Candela"]Nevertheless, the building process gets stuck into the step "Generating app_test_update.hex" many hours, without finishing the building process at all.[/quote]

I have never seen the build process freeze like that before.
Can you try to delete the build folder and rebuild?

"CONFIG_NORDIC_QSPI_NOR=y"

The nRF7002DK uses SPI for external flash, and not SPI: https://infocenter.nordicsemi.com/topic/ug_nrf7002_dk/UG/nrf7002_DK/hw_external_memory.html?cp=3_0_2_4_5

So you need to use the SPI driver instead.

Something along these lines:

CONFIG_NORDIC_QSPI_NOR=n
CONFIG_SPI=y
CONFIG_SPI_NOR=y
CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096

RE: nrf7002dk - region `FLASH' overflowed

Candela — Thu, 07 Sep 2023 10:47:06 GMT

Hi Sigurd,

Thank you a lot for your patience. Thanks to adding the overlay, I advanced into the building on the project. Nevertheless, the building process gets stuck into the step "Generating app_test_update.hex" many hours, without finishing the building process at all.

I've got a warning related to the mapping of the XIP partition during the building, I think it can be related. I am attaching the building log here.

Thank you for the support,

Candela

RE: nrf7002dk - region `FLASH' overflowed

Sigurd Hellesvik — Wed, 06 Sep 2023 13:10:59 GMT

You need to have an mcuboot.overlay, same as you have an oberlay for the board to enable external flash.
See this unofficial sample.

RE: nrf7002dk - region `FLASH' overflowed

Candela — Wed, 06 Sep 2023 07:07:12 GMT

Hi Sigurd,

Thank you for your answer and for the useful samples. I think I reached to build the app without flash overflow errors, but now, I get a compilation error related to the flash IDs. I think it might be because of using the external flash to store the MCUBOOT_SECONDARY partition. Is there any configuration am I missing?

prj.conf file:

# Drivers selection
CONFIG_GPIO=y
CONFIG_SERIAL=y
CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_WATCHDOG=n
CONFIG_ADC=n
CONFIG_PINCTRL=y
CONFIG_I2C=n
CONFIG_SPI=y
CONFIG_NRFX_SPIM2=y

CONFIG_REBOOT=y

# Power management
CONFIG_PM=n
 
# Interrupts
CONFIG_DYNAMIC_INTERRUPTS=y
CONFIG_UART_INTERRUPT_DRIVEN=n
CONFIG_IRQ_OFFLOAD=n

# Stacks and heaps
CONFIG_HEAP_MEM_POOL_SIZE=153640
CONFIG_MAIN_STACK_SIZE=2048
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
CONFIG_NET_TX_STACK_SIZE=2048
CONFIG_NET_RX_STACK_SIZE=2048
CONFIG_NET_MGMT_EVENT_STACK_SIZE=4096

# Memory protection
CONFIG_THREAD_STACK_INFO=n
CONFIG_THREAD_CUSTOM_DATA=n
CONFIG_FPU=n

# Wi-Fi
CONFIG_WIFI=y
CONFIG_WIFI_NRF700X=y
CONFIG_WPA_SUPP=y

CONFIG_KEY_MGMT_WPA2=y
CONFIG_SSID=""
CONFIG_PASSWORD=""

CONFIG_NET_CONFIG_PEER_IPV4_ADDR="192.168.1.201" 
# Board's IPv4 Address
CONFIG_NET_DHCPV4=y

# TCP
CONFIG_NEWLIB_LIBC=y
CONFIG_NETWORKING=y
CONFIG_POSIX_API=y

CONFIG_NET_IPV4=y
CONFIG_NET_TCP=y
CONFIG_NET_SOCKETS=y
CONFIG_POSIX_CLOCK=y
CONFIG_NET_TCP_WORKQ_STACK_SIZE=1024

# System settings
CONFIG_NEWLIB_LIBC_NANO=n


# Networking
CONFIG_NET_LOG=y
CONFIG_NET_IPV6=n
CONFIG_NET_UDP=y
CONFIG_NET_IF_UNICAST_IPV4_ADDR_COUNT=1
CONFIG_NET_MAX_CONTEXTS=10
CONFIG_NET_CONTEXT_SYNC_RECV=y

CONFIG_NET_PKT_RX_COUNT=16
CONFIG_NET_PKT_TX_COUNT=16
CONFIG_NET_MAX_CONN=10
CONFIG_NET_CONFIG_NEED_IPV4=n 
CONFIG_USERSPACE=n

# Below section is the primary contributor to SRAM and is currently
# tuned for performance, but this will be revisited in the future.
CONFIG_NET_BUF_RX_COUNT=80
CONFIG_NET_BUF_TX_COUNT=80
CONFIG_NET_CONTEXT_NET_PKT_POOL=y
CONFIG_NET_BUF_DATA_SIZE=128
CONFIG_NET_TC_TX_COUNT=0

CONFIG_INIT_STACKS=y
CONFIG_NET_L2_ETHERNET=y
CONFIG_NET_CONFIG_SETTINGS=y
CONFIG_NET_SOCKETS_POLL_MAX=4

# SNTP
CONFIG_SNTP=y

# Generate JSON message
CONFIG_JSON_LIBRARY=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_CJSON_LIB=y

# BLE configuration

CONFIG_BT=y
CONFIG_SETTINGS=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_GATT_DYNAMIC_DB=y

CONFIG_BT_DEVICE_NAME="Anchor"

# DFU over BLE
CONFIG_FLASH=y
CONFIG_IMG_MANAGER=y
CONFIG_FLASH_MAP=y

CONFIG_MCUMGR=y
CONFIG_MCUMGR_CMD_IMG_MGMT=y
CONFIG_MCUMGR_CMD_OS_MGMT=y
CONFIG_MCUMGR_SMP_BT=y
CONFIG_MCUMGR_SMP_BT_AUTHEN=n
CONFIG_MCUMGR_SMP_BT_CONN_PARAM_CONTROL=y

CONFIG_NORDIC_QSPI_NOR=y
#CONFIG_NORDIC_QSPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096
#CONFIG_NORDIC_QSPI_NOR_STACK_WRITE_BUFFER_SIZE=16
CONFIG_BOOTLOADER_MCUBOOT=y
#CONFIG_MCUBOOT_IMG_MANAGER=y


# Size optimizations
CONFIG_SIZE_OPTIMIZATIONS=y

mcuboot.conf file:

CONFIG_NORDIC_QSPI_NOR=y
CONFIG_BOOT_MAX_IMG_SECTORS=256
CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000

Build log on this link

Thank you,

Candela

RE: nrf7002dk - region `FLASH' overflowed

Sigurd Hellesvik — Mon, 04 Sep 2023 11:47:02 GMT

[quote user="Candela"]child_image/mcuboot.conf file:[/quote]

From Multi Image builds docs, you only need to name it like this, and the build system will automatically find it.
So no need to make changes to CMakeLists.txt

When adding CONFIG_BOOTLOADER_MCUBOOT to your project configuration, ncs/bootloader/mcuboot/boot/zephyr/ will automatically be added as your bootloader child image.

[quote user="Candela"]

Taking a look into the post you link, I think I would need to add the child image using Zephyr modules, probably because of the use of a multicore architecture of nrf5340 microprocessor.

I've checked the multicore sample for nrf5340, where Zephyr modules are used to add a different configuration to the CPUNET core, but it is still not clear to me how to use them to add MCUBOOT configurations. Where can I find more info about it?

[/quote]

For now, we use the multi image build system instead of the coming Sysbuild feature in Zephyr.
From my knowledge, the nRF Connect SDK does not have full sysbuild support for MCUboot yet. Until that happens, I recommend that you do not use Zephyr modules for this.

Instead, do it in the multi-image way. See for example this example on how to configure child images.

Regards,
Sigurd Hellesvik

RE: nrf7002dk - region `FLASH' overflowed

Candela — Mon, 04 Sep 2023 11:36:26 GMT

Hi Sigurd,

I have tried your proposal, but I am still facing some issues. My setup is as follows:

child_image/mcuboot.conf file:

CONFIG_PM_PARITITON_SIZE_MCUBOOT=0x10000

CMakeLists.txt file:

cmake_minimum_required(VERSION 3.20.0)

set(PM_STATIC_YML_FILE ${CMAKE_CURRENT_SOURCE_DIR}/pm.yml)

find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})

project(blinky)

add_child_image(
    NAME mcuboot
    SOURCE_DIR ${CMAKE_CURRENT_LIST_DIR}/child_image
    DOMAIN CPUNET
    )
    
...

Doing so, I get the following building error, related to the PM_PARTITION_SIZE_MCUBOOT symbol:

C:/nordicsemi/Project_Workspace_Realease/Rel/Project_dfu/child_image/mcuboot.conf:1: warning: attempt to assign the value '0x10000' to the undefined symbol PM_PARITITON_SIZE_MCUBOOT

error: Aborting due to Kconfig warnings
Parsing C:/nordicsemi/v2.3.0/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration 'C:/nordicsemi/v2.3.0/nrf/boards/arm/nrf7002dk_nrf5340/nrf7002dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/nordicsemi/v2.3.0/bootloader/mcuboot/boot/zephyr/prj.conf'
Merged configuration 'C:/nordicsemi/v2.3.0/nrf/subsys/pcd/pcd.conf'
Merged configuration 'C:/nordicsemi/v2.3.0/nrf/subsys/bootloader/bl_override/override_external_mcuboot.conf'
Merged configuration 'C:/nordicsemi/v2.3.0/nrf/subsys/partition_manager/ext_flash_mcuboot_secondary.conf'
Merged configuration 'C:/nordicsemi/v2.3.0/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Merged configuration 'C:/nordicsemi/Project_Workspace_Realease/Rel/Project_dfu/child_image/mcuboot.conf'
Merged configuration 'C:/nordicsemi/Project_Workspace_Realease/Rel/Project_dfu/build/mcuboot/zephyr/misc/generated/extra_kconfig_options.conf'

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


-- Configuring incomplete, errors occurred!
CMake Error at C:/nordicsemi/v2.3.0/nrf/cmake/multi_image.cmake:433 (message):
  CMake generation for mcuboot failed, aborting.  Command: 1
Call Stack (most recent call first):
  C:/nordicsemi/v2.3.0/nrf/cmake/multi_image.cmake:163 (add_child_image_from_source)
  C:/nordicsemi/v2.3.0/nrf/modules/mcuboot/CMakeLists.txt:234 (add_child_image)


-- Configuring incomplete, errors occurred!
See also "C:/nordicsemi/Project_Workspace_Realease/Rel/Project_dfu/build/CMakeFiles/CMakeOutput.log".
See also "C:/nordicsemi/Project_Workspace_Realease/Rel/Project_dfu/build/CMakeFiles/CMakeError.log".
FATAL ERROR: command exited with status 1: 'C:\nordicsemi\toolchains\v2.3.0\opt\bin\cmake.EXE' '-DWEST_PYTHON=C:\nordicsemi\toolchains\v2.3.0\opt\bin\python.exe' '-Bc:\nordicsemi\Project_Workspace_Realease\Rel\Project_dfu\build' -GNinja -DBOARD=nrf7002dk_nrf5340_cpuapp -DNCS_TOOLCHAIN_VERSION:STRING=NONE -DCONF_FILE:STRING=c:/nordicsemi/Project_Workspace_Realease/Rel/Project_dfu/prj.conf '-Sc:\nordicsemi\Project_Workspace_Realease\Rel\Project_dfu'

Taking a look into the post you link, I think I would need to add the child image using Zephyr modules, probably because of the use of a multicore architecture of nrf5340 microprocessor.

Candela

RE: nrf7002dk - region `FLASH' overflowed

Sigurd Hellesvik — Fri, 01 Sep 2023 11:25:06 GMT

I suspect that this error could be related to MCUboot.
Try to create the folder child_image in your project, and put this in child_image/mcuboot.conf:

CONFIG_PM_PARITITON_SIZE_MCUBOOT=0x10000

RE: nrf7002dk - region `FLASH' overflowed

Candela — Thu, 31 Aug 2023 12:40:30 GMT

Sure! Find the complete log on this link

RE: nrf7002dk - region `FLASH' overflowed

Sigurd Hellesvik — Thu, 31 Aug 2023 12:30:14 GMT

[quote user="Candela"] but I still have no enough space for the bootloader and the application on the primary flash.[/quote]

Can you post the build log showing this?

RE: nrf7002dk - region `FLASH' overflowed

Candela — Thu, 31 Aug 2023 12:09:50 GMT

Hi,

I followed your recommendations, optimizing flash usage and using an external flash, and I got to reduce significativelly the flash usage. Nevertheless, I still have questions on how to add the mcuboot child image on the external flash. By now, I have used the partition manager to set the mcuboot_secondary region into the external flash, but I still have no enough space for the bootloader and the application on the primary flash. Do I need to move any other region to the external flash?

I am attaching the output partition manager report.

  external_flash (0x800000 - 8192kB):
+---------------------------------------------+
| 0x0: mcuboot_secondary (0xf4000 - 976kB)    |
| 0xf4000: external_flash (0x70c000 - 7216kB) |
+---------------------------------------------+

  flash_primary (0x100000 - 1024kB):
+-------------------------------------------------+
| 0x0: mcuboot (0xc000 - 48kB)                    |
+---0xc000: mcuboot_primary (0xf4000 - 976kB)-----+
| 0xc000: mcuboot_pad (0x200 - 512B)              |
+---0xc200: mcuboot_primary_app (0xf3e00 - 975kB)-+
| 0xc200: app (0xf3e00 - 975kB)                   |
+-------------------------------------------------+

  otp (0x2fc - 764B):
+------------------------------+
| 0xff8100: otp (0x2fc - 764B) |
+------------------------------+

  sram_primary (0x80000 - 512kB):
+-----------------------------------------------+
| 0x20000000: pcd_sram (0x2000 - 8kB)           |
| 0x20002000: sram_primary (0x6e000 - 440kB)    |
| 0x20070000: rpmsg_nrf53_sram (0x10000 - 64kB) |
+-----------------------------------------------+

 CPUNET flash_primary (0x40000 - 256kB):
+--------------------------------------------+
+---0x1000000: b0n_container (0x8800 - 34kB)-+
| 0x1000000: b0n (0x8580 - 33kB)             |
| 0x1008580: provision (0x280 - 640B)        |
+---0x1008800: app (0x37800 - 222kB)---------+
| 0x1008800: hci_rpmsg (0x37800 - 222kB)     |
+--------------------------------------------+

 CPUNET sram_primary (0x10000 - 64kB):
+-------------------------------------------+
| 0x21000000: sram_primary (0x10000 - 64kB) |
+-------------------------------------------+

Thanks!

Candela

RE: nrf7002dk - region `FLASH' overflowed

Sigurd Hellesvik — Tue, 18 Jul 2023 08:00:20 GMT

Hi,

Enabling an SMP Server will split your available flash into two, effectively reducing available flash by half.
This is likely why you experience flash limitation errors.

To solve this, you got two options:

Reduce/optimize flash usage. See Memory footprint optimization, and disable features you do not need.
Add external flash. See External flash memory partitions. Remember to add this for the mcuboot child image as well

Regards,
Sigurd Hellesvik

RE: nrf7002dk - region `FLASH' overflowed

Candela — Tue, 18 Jul 2023 06:33:15 GMT

Hi Sigurd,

I'm attaching the complete build log with the Flash overflowed error, you can find it on this link

On the other hand, yes, I can reproduce the issue adding these three configurations to the smp_svr sample:

CONFIG_WIFI=y
CONFIG_WIFI_NRF700X=y
CONFIG_WPA_SUPP=y

Best regards,

Candela

RE: nrf7002dk - region `FLASH' overflowed

Sigurd Hellesvik — Fri, 14 Jul 2023 08:29:25 GMT

Hi,

I will continue to help with this case.

Can you upload your full build log as a .txt file?

Are you able to reproduce the issue if you add MCUboot to any of our samples?

Regards,
Sigurd Hellesvik

RE: nrf7002dk - region `FLASH' overflowed

AHaug — Thu, 13 Jul 2023 08:37:23 GMT

Hi Candela,

Thank you for providing this information. Just a heads up that I will be out of office for the few weeks, but this case will be handled by my colleague while I'm out of office. You will hear from them shortly w.r.t. what to do next!

Kind regards,
Andreas

RE: nrf7002dk - region `FLASH' overflowed

Candela — Wed, 12 Jul 2023 13:20:27 GMT

Hi Andreas,

After following the proposals on the blog to reduce the footprint, and adding some settings from the nRF Machine learning sample, I still have the same problem...

I'm attaching the Memory reports of my project before enabling the Bootloader configuration. Once I add it, I get the Flash overflowed.

ROM Memory report:

RAM Memory report:

Partitions Memory report:

Best regards,

Candela

RE: nrf7002dk - region `FLASH' overflowed

AHaug — Mon, 10 Jul 2023 12:07:06 GMT

Hi,

A few general thoughts and tips is the following

First steps would be to disable debug, which you've mentioned and logging.
The second step is to investigate Debunking misconceptions: A technical analysis of nRF5 SDK and nRF Connect SDK to see if there are anything you can use from this blog in your project to reduce its footprint
The third thing is to have a look at the nRF Machine learning sample to see how this application has optimized MCUboot w.r.t. memory

Could you also provide me with a memory report of your project? Either use the built in extension in VS Code or navigate to '<application location>/build' in command line and use 'nrfjprog partition_manager_report`?

Kind regards,
Andreas