ncs v2.5.0 linker error when setting CONFIG_BOOTLOADER_MCUBOOT

RE: ncs v2.5.0 linker error when setting CONFIG_BOOTLOADER_MCUBOOT

qrasmont — Tue, 12 Dec 2023 08:58:49 GMT

I started with the wifi provisioning sample in which I've added TWT negotiation based on the twt sample.

Adding CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000 did change the overflow error:

zephyr/zephyr_pre0.elf section `log_const_area' will not fit in region `FLASH'
.../zephyr_workspace/toolchains/7795df4459/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 142848 bytes

However upon doing more research I want to handle simultaneous DFU for the app + net core with external flash. So I'm completely changing my configuration (basing myself on this sample).

So I'm going to close this topic.

RE: ncs v2.5.0 linker error when setting CONFIG_BOOTLOADER_MCUBOOT

Amanda Hsieh — Mon, 11 Dec 2023 21:48:22 GMT

[quote user="qrasmont"]child_image refers to the network core of the nrf5340 correct ?[/quote]

Not really. child_image/mcuboot.conf only overwrites the configuration of mcuboot which is run on the app core. child_image/hci_rpmsg.cof would affect hci_rpmsg running on the netcore. See Permanent configuration changes to child images for more information.

[quote user="qrasmont"]Why is this option necessary ?[/quote]

CONFIG_MULTITHREADING=y is required when CONFIG_SPI=y is used in the mcuboot, so you'll get a lot of undefined references from the nrfx spim driver E.G. "undefined reference to `z_impl_k_sleep'". It will be enabled automatically if you are using the NCS Bluetooth samples.

Are you using the sample from NCS? If so, which one are you using?

[quote user="qrasmont"]"zephyr/zephyr_pre0.elf section `rodata' will not fit in region `FLASH'"[/quote]

Try to set CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000 in the child_image/mcuboot.conf to see if it can help or not.

-Amanda H.

RE: ncs v2.5.0 linker error when setting CONFIG_BOOTLOADER_MCUBOOT

qrasmont — Sat, 09 Dec 2023 16:40:01 GMT

Hi Amanda,

It did resolve the undefined references issue. child_image refers to the network core of the nrf5340 correct ?
Why is this option necessary ?

However my build sill fails, this time because of a flash layout issue.

"zephyr/zephyr_pre0.elf section `rodata' will not fit in region `FLASH'"

Is there more extensive documentation than this about setting up FOTA on the nrf5340 ?
Working on an nrf52 with the legacy SDK I to setup the bootloader myself to get DFU working so I'm bit confused by just having to set CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU and CONFIG_BOOTLOADER_MCUBOOT to get everything working.

Regarding the remaining issue:

The build memory summary:

Memory region         Used Size  Region Size  %age Used
           FLASH:      181352 B       256 KB     69.18%
             RAM:       59112 B        64 KB     90.20%
           SRAM1:          0 GB        64 KB      0.00%
        IDT_LIST:          0 GB         2 KB      0.00%

The generated partition.yml from the build:

EMPTY_0:
  address: 0xfe000
  end_address: 0x100000
  placement:
    after:
    - settings_storage
  region: flash_primary
  size: 0x2000
app:
  address: 0xc200
  end_address: 0x84000
  region: flash_primary
  size: 0x77e00
mcuboot:
  address: 0x0
  end_address: 0xc000
  placement:
    before:
    - mcuboot_primary
  region: flash_primary
  size: 0xc000
mcuboot_pad:
  address: 0xc000
  end_address: 0xc200
  placement:
    align:
      start: 0x4000
    before:
    - mcuboot_primary_app
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0xc000
  end_address: 0x84000
  orig_span: &id001
  - mcuboot_pad
  - app
  region: flash_primary
  sharers: 0x1
  size: 0x78000
  span: *id001
mcuboot_primary_app:
  address: 0xc200
  end_address: 0x84000
  orig_span: &id002
  - app
  region: flash_primary
  size: 0x77e00
  span: *id002
mcuboot_secondary:
  address: 0x84000
  end_address: 0xfc000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x4000
  region: flash_primary
  share_size:
  - mcuboot_primary
  size: 0x78000
otp:
  address: 0xff8100
  end_address: 0xff83fc
  region: otp
  size: 0x2fc
rpmsg_nrf53_sram:
  address: 0x20070000
  end_address: 0x20080000
  placement:
    before:
    - end
  region: sram_primary
  size: 0x10000
settings_storage:
  address: 0xfc000
  end_address: 0xfe000
  placement:
    align:
      start: 0x4000
    before:
    - end
  region: flash_primary
  size: 0x2000
sram_primary:
  address: 0x20000000
  end_address: 0x20070000
  region: sram_primary
  size: 0x70000

RE: ncs v2.5.0 linker error when setting CONFIG_BOOTLOADER_MCUBOOT

Amanda Hsieh — Fri, 08 Dec 2023 21:40:08 GMT

Hi,

Try to create child_image/mcuboot.conf with CONFIG_MULTITHREADING=y to the application.

Regards,
Amanda H.