store user data with mesh ?

[atrons]

Both Devzone and Mesh SDK 5.0 are mentioned that store user data in mesh should using flash manager.

But read the source code of the mesh SDK , the mesh SDK already called flash_manager_init() function in deep backtrace of nrf_mesh_enable.

it is obviously NOT a object oriented designed flash manager.(a large number of static global variable defined in the module). I can not create new instance anymore. so I have to insert our user defined application data into SDK level data process? using like mesh_config_entry_set/get API , instead of user own database?

I am also very very strange , does Nordic mesh SDK was designed by other company? Nrf-mesh SDK looks re-implemented another full sets of driver and looks abandon NRF-SDK at all? e.g. flash/uart/gpio drivers are totally different with NRF-SDK, and obvious more obscure and junior. Point out the flash manager, the state machine use static global variables is a very very bad architecture design.

Could anyone tell me how to store application user data in mesh in a correct way?

[Mttrinh]

Hi,

To store user data, you can use mesh configuration module, which is a key-value persistent storage. More information can be found here: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v5.0.0/md_doc_user_guide_modules_mesh_config.html?cp=7_2_2_4_3 

Please look at Enocean Example as an example of how to use mesh configuration module: https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/master/examples/enocean_switch/src/main.c#L162

Please note that the first free file id is defined by MESH_OPT_FIRST_FREE_ID: https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/master/mesh/core/include/mesh_opt.h#L67

Flash manager used as a backend for the mesh configuration module. So that the you don't need to access flash manager API directly.