This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Questions regarding firmware upgrade from Mesh v0.9.2 to Mesh v3.0.0 via BLE

Hi,

We are planning on upgrading the firmware on our device from Mesh v0.9.2 to Mesh v3.0.0 via BLE.

Specifically, our current stack uses:
- nRF5 SDK for Mesh v0.9.2
- nRF5 SDK v12.3.0
- S132 SoftDevice v3.0.0

We want to upgrade our devices to use:
- Mesh SDK v3.0.0
- nRF SDK v15.2.0
- Softdevice v6.1.0

Are there any known problems or pitfalls I should be aware of?
Is it better to have one single DFU package, or should I instead do multiple incremental update. (v0.9.2 => v1.0.0 => v2.2.0 => v3.0.0)

Best regards,
Thomas

Parents
  • Have you already written the FW for mesh SDK v3.0.0? From what you wrote, it seems you are not wondering about how to migrate from mesh sdk v0.9.2 to v3.0.0, right?

    If you just want to do a DFU via BLE, I would suggest you to update directly from v0.9.2 directly to v3.0.0. You will need to update the bootloader as well because you are updating the softdevice too. If you have not already taken a look at this blog post, I would suggest starting there. You will need to do a Bootloader + Softdevice + application DFU. You can create one zip file with all three (BL+SD+app) using the nrfutil pkg generate command.

Reply
  • Have you already written the FW for mesh SDK v3.0.0? From what you wrote, it seems you are not wondering about how to migrate from mesh sdk v0.9.2 to v3.0.0, right?

    If you just want to do a DFU via BLE, I would suggest you to update directly from v0.9.2 directly to v3.0.0. You will need to update the bootloader as well because you are updating the softdevice too. If you have not already taken a look at this blog post, I would suggest starting there. You will need to do a Bootloader + Softdevice + application DFU. You can create one zip file with all three (BL+SD+app) using the nrfutil pkg generate command.

Children
Related