• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 75 subscribers
  • Views 1652 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 225523
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

About OTA of Mesh 3.10

listenYes

Hi

I have some question about OTA .

1.The nRF SDK hvae twos way for OTA:single bank and dual bank;The nRF Mesh 3.10 too?Because my firmware maybe very large,so I want to use single bank.The Mesh 3.10 can also support the single bank OTA?

2.Because theOTA way was one-to-one for nRF SDK,the Mesh OAT must be one-to-one?If so,upgrade all device must spend a lot of time.would like to one-to-more what should I do?can be implement MESH OTA? Such as upgrade all light node at the same time through the mesh network.

Parents
  • 0

    Hi,

    Mesh DFU and nRF5 SDK DFU are two different things. I recommend you look at the documentation about the Mesh DFU procotol here. To summarize:

    Mesh DFU supports two modes

    • background DFU, that transfers the new firmware in the background while the application is running, when the transfer is done the application then flash the new firmware when ready.
    • bootloader DFU, in which only the mesh bootloader is running (no application running).

    The Mesh DFU protocol use relay of data to neighboring devices when performing an update. Both the passive mesh devices and the devices receiving a transfer will relay all data packets, this method is much faster than passing the entire DFU transfer to each device individually (one-to-one).

    But because of the throughput concerns in mesh we recommend using background DFU when possible, so your mesh network does not have to have a downtime while performing an update. If you find out you don't have enough flash available you can of course perform a bootloader DFU.

    Best Regards,

    Marjeris

Reply
  • 0

    Hi,

    Mesh DFU and nRF5 SDK DFU are two different things. I recommend you look at the documentation about the Mesh DFU procotol here. To summarize:

    Mesh DFU supports two modes

    • background DFU, that transfers the new firmware in the background while the application is running, when the transfer is done the application then flash the new firmware when ready.
    • bootloader DFU, in which only the mesh bootloader is running (no application running).

    The Mesh DFU protocol use relay of data to neighboring devices when performing an update. Both the passive mesh devices and the devices receiving a transfer will relay all data packets, this method is much faster than passing the entire DFU transfer to each device individually (one-to-one).

    But because of the throughput concerns in mesh we recommend using background DFU when possible, so your mesh network does not have to have a downtime while performing an update. If you find out you don't have enough flash available you can of course perform a bootloader DFU.

    Best Regards,

    Marjeris

Children
Related
Terms of service