• State Verified Answer
  • Replies 2 replies
  • Subscribers 73 subscribers
  • Views 395 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 250885
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Corresponds to mesh

cbe9

Hello

Currently, there are systems that operate with peripherals developed with nRF52832, SDK v.12.2.0. I have a question about supporting this for meshes.

1. Are you aware that you need to change the SDK to nRF5 SDK for Mesh if you support mesh?
2. How much do you think the usage of ROM and RAM will increase?

Parents
  • +1

    Hi,

    If you have an existing BLE project and want to add e.g. Bluetooth mesh to that, then you will need to develop the new firmware using e.g. nRF5 SDK for Mesh, yes. Similarly, if you want to use Thread or Zigbee you would need to use the nRF5 SDK for Thread and Zigbee.

    nRF5 SDK for Mesh is used together with nRF5 SDK (but you need to upgrade to a later version of it.) nRF5 SDK for Thread and Zigbee is based off of nRF5 SDK, but there as well a newer version of the nRF5 SDK.

    Regarding Flash and RAM requirements, the nRF5 SDK for Mesh has only limited compatibility with the nRF52810 due to the smaller amount of Flash and RAM on that device. (No logging, no DFU, must compile with optimization for space.) In other words, our Bluetooth mesh examples fits on a device with 192 kB Flash and 24 kB RAM when optimized for size, including the SoftDevice and required parts from the nRF5 SDK. Your functionality specific to the application then comes on top of that.

    Regards,
    Terje

  • 0 in reply to tesc

    Thank you very much. It was very helpful.

Reply Children
No Data
Related
Terms of service