I have a custom nRF52840 design, I'm actually using a ublox BMD-340-A-R module on a custom board. I have a working application with BLE peripheral, I2C sensors, USB CDC, LoRaWan and some RS485 interfaces. I am using NCS 2.5.2. The application is working as intended and I now want to add mcuboot for OTA DFU firmware updates. In the application I have console and logging disabled as I am using the UARTs for the RS485 interfaces so they are not available (practically all pins are in use).
Now, I've tried to add mcuboot by adding CONFIG_BOOTLOADER_MCUBOOT=y in prj.conf and a child_image/mcuboot.conf (shown below). If I connect to the device using nRFConnect App I can see that DFU service is available. If I press the DFU icon and load the app_distribution.zip it appears as if the file is uploaded (I get the transfer speed chart and the progress goes on to 100%) but right after the upload when the progress switches to "Validating..." the nRF52 reboots and gets stuck somewhere. If I power cycle the board the device comes back up but it is on the original firmware.
I'm not very familiar with mcuboot so I'm not sure what to check or try. Below are all of the file the I think are relevant.
prj.conf:
child_image/mcuboot.conf:
pm_static.yml (copied from partition.yml)