An alternative to DFU + BLE using a single bank

[_lumac]

Hi Mate,

Like most of the other tickets in this thread, I have a large application and need to DFU it using Bluetooth. I know nrf connect is not compatible with the single bank for Bluetooth, but let's discuss other approaches:

1. As with nRF5, is it possible to define a partition just for the Bluetooth stack and add a bit more space for the application banks?
2. In a scenario where you only use Bluetooth for DFU. Create a small partition for it and a large partition for the application (asymmetrically). In your main application, jump (swap by user command) to DFU app, which starts the overwrite process and, once complete, run the new image on the larger partition. Is this possible in order to emulate the single bank? 
3. Is there any possibility of having a single bank in nrf connect or something close to that (using Bluetooth, of course)?

Best regards

Luis

[Menon]

Hello,

I know it can be a bit frustrating, but in BLE OTA DFU, the device writes the new firmware to a separate area of memory (the secondary slot). After the update, the device switches to this secondary slot and verifies its integrity. If the new firmware is valid, the device continues using it; otherwise, it reverts to the old firmware. With a single bank, there's no separate space to store the new firmware during the update process. I apologize if you already know this, but I wanted to explain why single-bank DFU is not supported.

Additionally, I personally don't recommend using our old nRF5 SDK, as it is in maintenance mode and no further development will be made

Kind Regards,

Abhijith