https://devzone.nordicsemi.com/f/nordic-q-a/14593/firmware-update-for-serialization-scenarioFrom what I can see the scenario where you have a serialized app running from a separate CPU and how to do firmware update on that is not discussed anywhere on the Nordic site and I am trying to get some ideas so I will not find myself duplicating a loten-USTelligent Community 13Mon, 20 Jun 2016 12:26:47 GMThttps://devzone.nordicsemi.com/thread/55700?ContentTypeID=1Mon, 20 Jun 2016 12:26:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d7bbc303-c6b5-4df2-a588-b897f09ee4cbHung Bui<p>Hi Catalin,</p> <p>I afraid that there is not much work has been done regarding having DFU for the connectivity chip in serialization set-up.</p> <p>DFU process requires a bootloader. It&#39;s not possible or I would say pretty complicated to integrate the DFU functionality into the main connectivity application.</p> <p>The closest we have is the SPI bootloader that you can have a look <a href="https://github.com/NordicSemiconductor/nrf51-dfu-spi-slave">here</a>.</p> <p>I am not fully understand what you mentioned here: <em>&quot;however the very quick move from 2.0.0 to 2.0.1 raises the valid question if we would not be much better on the longer term having a very clean upgrade path in the Nordic circuit too&quot;</em></p> <p>Could you explain a little bit more?</p><div style="clear:both;"></div>