• State Not Answered
  • Replies 3 replies
  • Subscribers 25 subscribers
  • Views 265 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 283957
Options

Nrf connect SDK memory mapping & logging

user106849

Hi, 

We're using Nordic Connect SDK V1.8.0 & nrf 52833 chip integrated on BL653 hardware & have some queries regarding logging SDK related data, following queries

  1. What are the data we are saving in SDK data. As per code we have found that we are saving SDK data in bt_mesh_prov for now.
    Does provisioning is holding only bt_mesh_prov data or it is also holding another info. Please provide info on this.

  2. Can we route the PATH of SDK data from Internal ROM to RAM.

  3. As per our finding we have 24KB size to save SDK data, In this space how much devices info we can save. If we wanted to modify this space, How we can do that.

Thank you,

Parents Reply Children
  • 0 in reply to user20690

    Hi Joakim, 


    Thanks for your response. 

    1. I wanted to know that what all the information SDK data includes and there memory size as well. 
    2. How the SDK is storing data about the provisioning and un-provisioning and other massage in SDK data partition?

    3. Can you please share SDK data Logging design document if you have to understand the process of storing provisioning and un-provisioning data and other logs in storage partition?

    4. How we can modify the SDK storage partition to some other reason and to external flash memory?

    5. What is min size required and max memory size requirement for SDK data logging?

  • 0 in reply to user113655

    Hi.

    Not sure if this is relevant anymore.

    But you can find all the data that is required by the provisioning process in the BLE Mesh Specification.

    The amount of data will depend on the application, LPN nodes, friend node etc.

    Br,
    Joakim

Related
Terms of service