Can I update the SoftDevice without touching the application?

RE: Can I update the SoftDevice without touching the application?

Hung Bui — Fri, 24 Mar 2017 11:38:00 GMT

When you update your softdevice, the application will be erase to give space for the new image of the softdevice. You will have to update the application back after you done with the softdevice.

Between minor versions of the softdevice, the application doesn't need to be modified to work with the new softdevice (with same major version).

We will try to keep the MBR unchanged alongside same softdevice in different major versions.

RE: Can I update the SoftDevice without touching the application?

endnode — Thu, 23 Mar 2017 18:02:03 GMT

Or update this question which you did, thx;)

RE: Can I update the SoftDevice without touching the application?

endnode — Thu, 23 Mar 2017 18:00:40 GMT

Oh, so your main question is to get strong statement from Nordic that Soft Device API will never change between minor version numbers? I suggest to do another question because your original "Can I update the SoftDevice without touching the application?" seems to be answered above.

RE: Can I update the SoftDevice without touching the application?

Elias — Thu, 23 Mar 2017 16:36:04 GMT

Telling me to test the combination is beside the point of my question. Of course I would test it, but there is only so much confidence I can gain from that as an application developer. I want to hear, from the perspective of someone who knows the machinations of the SoftDevice and its development process, how easy and flexible Nordic intends to make development after deployment of a product.

RE: Can I update the SoftDevice without touching the application?

endnode — Thu, 23 Mar 2017 13:51:18 GMT

MBR is typically not changing between any version of given SD and you are also not updating it OTA (that would be pretty dangerous if not impossible) so you should not worry. When it comes to Soft Device update only you can do it indeed (OTA DFU is in the end just erasing and rewriting some flash memory so you can do anything you want until you don't overwrite memory from which you are currently running the code - that's what makes MBR update difficult;) but you should test all combinations of your application code/binary versions and SD versions which you want to support before releasing it to the field. You will then find out if any API or SD size changed (which would break compatibility with your app).