Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Freezerohmatic — Thu, 30 Nov 2023 08:45:15 GMT

oh wheep ye who follow old examples blindly..... I think I've found the cause of this issue..

At some point I added CONFIG_BOOT_USE_MIN_PARTITION_SIZE=y

May my days of wasted time be helpful to other fools who are tricked by this simple line....

Thank you Amanda for entertaining my stupidity and sorry for your wasted time

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Freezerohmatic — Thu, 30 Nov 2023 07:20:05 GMT

Ah, no sorry, wrong board, that is for the NRF52840. Changed back to 0x4000 after changing back to 5340. I think this does confirm that there is something wrong in those board files.

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Freezerohmatic — Thu, 30 Nov 2023 07:09:16 GMT

So I update to 2.4.2 and now get this, using the default board files

warning: PM_PARTITION_SIZE_MCUBOOT (defined at
~/v2.4.2/nrf/modules/mcuboot/boot/zephyr/Kconfig:21,
~/v2.4.2/nrf/modules/mcuboot/boot/zephyr/Kconfig:26,
~/v2.4.2/nrf/modules/mcuboot/boot/zephyr/Kconfig:32) was assigned the value '0x10000'
but got the value '0x7c00'. See
docs.zephyrproject.org/.../kconfig.html and/or look up
PM_PARTITION_SIZE_MCUBOOT 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.

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Freezerohmatic — Thu, 30 Nov 2023 05:17:46 GMT

I still have this issue when pointing to the nRF5340DK. I can't find anything in the boards config file that has 0x4000. I did have to remove mx25r64 from reserved-memory to get things compiling

what is the default, I see 3 posabilities? Are you using 2.4.0?

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Amanda Hsieh — Mon, 27 Nov 2023 16:33:57 GMT

Hi,

Do you have the same issue while building the project for nRF5340DK?

0x4000 value is not the default for PM_PARTITION_SIZE_MCUBOOT. Do you assign it in the board configuration or somewhere? I have tried to create a nRF5340 custom board, but cannot reproduce the issue.

-Amanda H.

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Freezerohmatic — Mon, 27 Nov 2023 03:58:24 GMT

Hi Amanda,

The log "Warning" is (note I have removed the exact file reference with a ~)

warning: PM_PARTITION_SIZE_MCUBOOT (defined at
~/v2.4.0/nrf/modules/mcuboot/boot/zephyr/Kconfig:21,
~/v2.4.0/nrf/modules/mcuboot/boot/zephyr/Kconfig:26,
~/v2.4.0/nrf/modules/mcuboot/boot/zephyr/Kconfig:32) was assigned the value '0x10000'
but got the value '0x4000'. See
docs.zephyrproject.org/.../kconfig.html and/or look up
PM_PARTITION_SIZE_MCUBOOT 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.

Followed with

~/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'
~/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 40140 bytes
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

I also tried getting this working with the helloworld example with the same results.

Its a custom board using the nRF5340DK as a starting point

NCS 2.4.0

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Freezerohmatic — Fri, 10 Nov 2023 05:47:02 GMT

I'm currently on leave but I'll try this when I get back to the office.

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Amanda Hsieh — Mon, 06 Nov 2023 21:47:23 GMT

[quote user="Freezerohmatic"]I get an warning saying 0x10000 set but received 0x2000 or something similar to that[/quote]

Can you post the log?

Are you using nRF5340DK or the custom board?

Which NCS version are you using?

Please also post the content of prj.conf and mcuboot.conf if it's possible.

-Amanda H.

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Freezerohmatic — Mon, 06 Nov 2023 18:20:24 GMT

Hi Amanda,

I did try this, I get an warning saying 0x10000 set but received 0x2000 or something similar to that

RE: Issue when adding MCUBOOT. Overflow when added but application does not use even 20% of ROM when compiled without

Amanda Hsieh — Mon, 06 Nov 2023 15:46:21 GMT

Hi,

Seems you get a "FLASH overflowed" error from mcuboot, you can try to increase the mcuboot partition, which you can do by making a folder in your project called "child_image" (See Multi-image builds) and place mcuboot.conf there, where you put this line:

CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000

Please let me know this can help or not. Thanks.

Regards,
Amanda H.