Merging ble_app_blinky_c with mesh ligth_switch_server fails on sending composition data on configuration process (NRF_ERROR_NO_MEM).

[EdenCandelas]

Im working on merging blinky_c with light_switch_server. Took the blinky example as starting point then merge the mesh code accorging the Coexistence with nRF5 SDK BLE functionality.

The issue is the same showed on this post, but I adder more logs to locate where it is exactly failing. This is the scenario:

Applications starts correctly.

When a provisioner finds the device it starts the provisioning process, it goes correctly, got a node addreess( tested this with a DK board as provisioner,  another DK board as client and a DK running my merging code, also performed this step using the interactive python demo).

Then is receives the composition_data_get, tries to process it, but fails on sending the packet.

I added log to config_server.c and access.c to trackdown the issue. It leads to the nrf_mesh_packet_send() returning a 0x04 (NRF_ERROR_NO_MEM).

According to the api reference it is caused by a lack of memory to send the packet.

My guess is that something is mesing on the sdk_config or the nrf_mesh_config_app but not shure.

On nrf_mesh_config_app.h the

ACCESS_MODEL_COUNT is set to 3

ACCESS_MODEL_COUNT is set to 1

In the app there is the config_model, health_model and simple_on_off model.

I will appreciate any hints o solutions that you can provide me.

Regards.

Edén.

 

[Jui-Chou (Rick) Chung]

Hello Eden,

Excuse us for the late reply.

Would you please modify the "heap size" in the "project setting" and check if it works?

 

Since the heap size default setting in the ble_app_blinky_c is "0", but sending composition data needs to use SAR transaction, which needs heap. There is a note in the bottom of mesh SDK release note: 

The transport SAR uses +malloc()+ to allocate buffers for SAR transactions. 
This behaviour can be overridden using +transport_sar_mem_funcs_set()+, 
otherwise +__HEAPSIZE+ needs to be defined.

Hope this can do help :)

[EdenCandelas]

Thanks for your reply.

You answer fixed the problem, I was able to get the composition data

and configure the device in order to perform the example on the configuration demo.