RAM overflow migrating from ncs 2.2.0 to v2.4.4

RE: RAM overflow migrating from ncs 2.2.0 to v2.4.4

Amanda Hsieh — Mon, 02 Dec 2024 16:01:10 GMT

Happy to hear that. 🙂

RE: RAM overflow migrating from ncs 2.2.0 to v2.4.4

hugzy123 — Fri, 29 Nov 2024 12:49:33 GMT

Thanks, this worked.

RE: RAM overflow migrating from ncs 2.2.0 to v2.4.4

Amanda Hsieh — Mon, 11 Nov 2024 22:22:57 GMT

Hi,

[quote user="hugzy123"]Could this be an issue with including the multiprotocol child image?[/quote]

Yes.

Try to:
Enable CONFIG_ADD_MCUBOOT_MEDIATE_SIM_FLASH_DTS=y in the prj.con for "mcuboot_smp_ble_simultaneous" sample.

Remove the CONFIG_LOG_MINIMAL=y and CONFIG_LOG_MINIMAL=y in the child_image/mcuboot.conf.

Create the child_image/multiprotocol_rpmsg.conf and add the following configs to reduce the size of netcore image:

CONFIG_BT_MAX_CONN=2

# General
CONFIG_DEBUG=n
CONFIG_ASSERT=n
CONFIG_STACK_USAGE=n
CONFIG_THREAD_MONITOR=n
CONFIG_SERIAL=n
CONFIG_CONSOLE=n
CONFIG_PRINTK=n
CONFIG_UART_CONSOLE=n
CONFIG_BOOT_BANNER=n

RE: RAM overflow migrating from ncs 2.2.0 to v2.4.4

hugzy123 — Mon, 11 Nov 2024 12:07:55 GMT

When adding the thread config options to the example you provided I get RAM and FLASH sizing issues when compiling the network core (see below).

c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `text' will not fit in region `FLASH'

c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `noinit' will not fit in region `RAM'

c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `FLASH' overflowed by 26456 bytes

c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `RAM' overflowed by 12284 bytes

Could this be an issue with including the multiprotocol child image?

Steps to reproduce issue

1. Checkout v2.4.4 commit dadbc79f3abc6a2098546885958c3ce9e6286064 of the parent git repository "samples_for_nrf_connect_sdk".

2. Add multiprotocol config options to "mcuboot_smp_ble_simultaneous"
prj.conf

# Generic networking options
CONFIG_NETWORKING=y
CONFIG_ASSERT=y
CONFIG_ASSERT_NO_COND_INFO=y
# Enable OpenThread features set
CONFIG_OPENTHREAD_NORDIC_LIBRARY_MASTER=y
CONFIG_OPENTHREAD_SOURCES=y
CONFIG_NET_L2_OPENTHREAD=y
CONFIG_ADD_MCUBOOT_MEDIATE_SIM_FLASH_DTS=n #RAM fix

child_image/mcuboot.conf

CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAM=y

3. Compile "mcuboot_smp_ble_simultaneous" for *nrf5340dk_ns

Thanks,

RE: RAM overflow migrating from ncs 2.2.0 to v2.4.4

Amanda Hsieh — Thu, 07 Nov 2024 19:49:32 GMT

You can refer to the configs of this unofficial mcuboot_smp_ble_simultaneous sample.

RE: RAM overflow migrating from ncs 2.2.0 to v2.4.4

hugzy123 — Wed, 06 Nov 2024 10:41:20 GMT

Hi Amanda,

Thanks for your reply.

Adding CONFIG_ADD_MCUBOOT_MEDIATE_SIM_FLASH_DTS=n has helped with the RAM overflow issue, however, i'm still having some form of partition issues.

When I set the config option CONFIG_UPDATEABLE_IMAGE_NUMBER=2 for setting the ability to upgrade both application and network core, I get the following errors

C:/ncs/v2.4.4/bootloader/mcuboot/boot/zephyr/include/sysflash/sysflash.h:52:12: error: 'PM_MCUBOOT_SECONDARY_1_ID' undeclared (first use in this function); did you mean 'PM_MCUBOOT_SECONDARY_ID'?
   52 |            PM_MCUBOOT_SECONDARY_1_ID: \
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~
C:/ncs/v2.4.4/bootloader/mcuboot/boot/bootutil/src/bootutil_misc.c:161:35: note: in expansion of macro 'FLASH_AREA_IMAGE_SECONDARY'
  161 |         flash_area_get_id(fap) == FLASH_AREA_IMAGE_SECONDARY(image_index)) {
      |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~
C:/ncs/v2.4.4/bootloader/mcuboot/boot/bootutil/src/bootutil_misc.c: In function 'boot_find_status':
C:/ncs/v2.4.4/bootloader/mcuboot/boot/zephyr/include/sysflash/sysflash.h:45:12: error: 'PM_MCUBOOT_PRIMARY_1_ID' undeclared (first use in this function); did you mean 'PM_MCUBOOT_PRIMARY_ID'?
   45 |            PM_MCUBOOT_PRIMARY_1_ID :         \

Do you know what could be causing these errors?

I have managed to recreate the issue on my tfm_hello_world example attached below.
devzone.nordicsemi.com/.../8233.tfm_5F00_hello_5F00_world.zip

Thanks,

RE: RAM overflow migrating from ncs 2.2.0 to v2.4.4

Amanda Hsieh — Fri, 01 Nov 2024 13:51:16 GMT

Hi,

The overflow is likely in the bootloader because CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY selects the CONFIG_ADD_MCUBOOT_MEDIATE_SIM_FLASH_DTS symbol. Do you see the same if you add CONFIG_ADD_MCUBOOT_MEDIATE_SIM_FLASH_DTS=n to your project configuration? and also enable CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAM in the child_image/mcuboot.conf if you want to support the netcore updates with TFM.

-Amanda H.

RE: RAM overflow migrating from ncs 2.2.0 to v2.4.4

Amanda Hsieh — Thu, 31 Oct 2024 18:51:12 GMT

Hi,

I can reproduce the issue on nRF53DK with QSPI external flash, but still time to investigate the issue.

Regards,
Amanda H.