can MCUBOOT be built without Secure_Boot

[dev_99_b]

I am using NRF52833 and trying to setup DFU specifically for OTA.

As experienced in other threads the size limitations are there

Secure_Boot builds creating slot partitions of 240kB

MCUBOOT with Secure_Boot seems that it would limit to 192kB  It wont build as it currently triggers an error I am having trouble with.

MCUBOOT will not build by itself with  CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

it seems to specifically include CONFIG_BUILD_S1_VARIANT=y  and including this variant requires CONFIG_SECURE_BOOT=y

which brings me back to including both bootloaders

edit:  setting CONFIG_BUILD_S1_VARIANT=n and trying my best to field child_image conf and overlay.  it does create a build with the partition manager only including partitions for bootload mcuboot and settings without the full layout that gets created with config_secure_boot=y but it  seems to fail to find partition slots correctly on compilation.

am using current NCS 2.6.0

thanks for helping me to navigate this issue!

[dev_99_b]

thanks! I will check out the guide more fully.

I was able to fix my main issue "error: 'PM_MCUBOOT_PRIMARY_1_ID"  with RE: how to implement simultaneous dfu on 5340 ncs2.4 without external flash 

now I have an error   File "C:\NCS\v2.6.0\nrf\scripts\partition_manager.py", line 393, in dynamic_partitions_size
    size = total_size - sum([req['size'] for name, req in reqs.items() if 'size' in req.keys() and name != dp])
TypeError: unsupported operand type(s) for +: 'int' and 'str'

which in one thread people seem to have previously fixed perhaps with the deprecated option CONFIG_PCD=y which seems to already be getting set with CONFIG_PCD_APP=y

and in another thread that issue is referenced here  RE: NVS Settings subsys custom partition placement in getting created by a other CONFIG option that gets rolled in.

[Sigurd Hellesvik]

Did you get anything from the guide?

What is your end goal here?
(I am trying to get an overview)