On low flash devices like nrf51822 FLASH_AREA_IMAGE_1 equal to FLASH_AREA_IMAGE_0 is improbable, which means dual bank is likewise improbable and as a result we've talked previously about how to shrink FLASH_AREA_IMAGE_1 down to a stub.
However, my current understanding is newtmgr/imagemgr implementation is dual bank, wherein the application saves received bytes into COREDUMP_FLASH_AREA (ie FLASH_AREA_IMAGE_1) and reboots allowing bootloader (apps/boot) to safely make the swap. I don't believe theres a good way to do a single bank receive from within the running application, which would mean this has to be moved into the bootloader, which means it need to share access to nimble, which means a bootloader fork that includes splitty, nimble, newtmgr, imagemgr. Im somewhat unclear if the 'loader' app can/should also serve as the 'bootloader', or if it was intended that a separate bootloader would also be present in addition to loader and application? Thoughts on this architecture, am I missing anything?
