compatibility of mesh-sdk2.2 upgrade to mesh-sdk-3.0

[jowei]

Hi Nordic:

I just got some confused when I did development between mesh-sdk-2.2 and mesh-sdk-3.0 examples today.

And finally I find a steps to produce an issue of compatibility between sdk-2.2 and 3.0:

 

- Program proxy_client of Mesh-sdk-2.2 to a nRF52 board, use nRF-Mesh APP to provision this device, and set a client publish address to 0xc001.

- Program this board of proxy_client of Mesh-sdk-3.0, do not click "erase all", just click "download" by segger studio.

- The board will get assert when boot up.

I think this result will happen too when doing DFU, because DFU is only re-program the application flash area, not erase nwk/opt/access/device-manage flash area.

So, is it possible that upgrade a device(already provsioned and configured) from sdk2.2 to sdk3 and boot up successfully?

Regards,

Joseph

[Bjørn Kvaale]

I think this result will happen too when doing DFU, because DFU is only re-program the application flash area, not erase nwk/opt/access/device-manage flash area.

 Why do you believe that the DFU only updates the application area & not the network/opt/access/device-manager flash area?

The way I understand it, when you do a DFU, you update the whole application. That means that the mesh stack, as well as your application will be updated. This is because the mesh stack is a part of the application build hex file.

So, is it possible that upgrade a device(already provsioned and configured) from sdk2.2 to sdk3 and boot up successfully?

 Yes, this is possible. Have you tried doing a DFU using our example? This documentation could also be helpful.