• State Not Answered
  • Replies 6 replies
  • Subscribers 68 subscribers
  • Views 226 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 335351
Options

RAM overflow migrating from ncs 2.2.0 to v2.4.4

hugzy123

Hi,

I'm working on a project using MCUboot, TFM, and a network core app. We use MCUboot with an external flash module for OTA firmware updates.

Recently, we tried upgrading from ncs v2.2.0 to v2.4.4 but keep hitting a RAM overflow error when compiling the network core firmware.

arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `bss' 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 `RAM' overflowed

We first tried updating pm_static.yml for the new TFM requirements, then using partition manager to create partitions. Both approaches still gave the RAM overflow.

When migrating sdk, we compared the nRF5340 DK board file changes between v2.2.0 and v2.4.4 and applied relevant changes to our board files.

Attached is a modified "TFM - hello world" example with mcuboot, a network core image, and our custom board.

7317.tfm_hello_world.zip

Compiling this firmware with our board yields the error below when building the network core image.

: region `RAM' overflowed by 245896 bytes

However, compiling with the nRF5340 DK board file works fine.

I compared the generated partitions.yml from our custom board vs nRF5430 builds - all RAM partitions look identical. So I'm stumped on why we're getting RAM overflow.

Would anyone be able to give some pointers on what I'm missing?

Thanks,

  • 0 in reply to hugzy123

    Hi, 

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

    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

Related