I am using nRF52 SDK v15.2.0, nRF SDK Mesh 3.0.0, and Segger v4.1.2.
I am trying to add the proxy service to the client node of the BLE_UART_COEXIST example. Has anyone here done this successfully?
ERROR 8 [NRF_ERROR_INVALID_STATE] is the error I get.
Hi.
Which function call gives you this error? It is hard to pin point the cause based on so little information.
Best regards,
Andreas
ble_softdevice_support.c:117 which is the ble_stack_init function from the mesh_main.
As far as I know the ble_stack_init, gap_params, conn_params functions need to be called twice; once for BLE_UART and once for Proxy service. Is this correct? I also noticed these three functions are different in the Mesh SDK compared to the 15.2 SDK. I feel like I am having some kind of storage conflict.
Thanks for the reply.
So, I should be able to just set MESH_FEATURE_GATT_PROXY_ENABLED 1 and set MESH_FEATURE_PB_GATT_ENABLED 1 to get the proxy service to work with the BLE_UART?
Hi again and happy new year.
I said something wrong in my previous reply, I've looked more close at the code and you can call gap_params_init and conn_params_init twice.
brinehart said:So, I should be able to just set MESH_FEATURE_GATT_PROXY_ENABLED 1 and set MESH_FEATURE_PB_GATT_ENABLED 1 to get the proxy service to work with the BLE_UART?
You should just set them in the nrf_mesh_config_core.h file
Best regards,
Andreas
Thanks again for your help. Here's what I have been getting.
ERROR 4 [NRF_ERROR_NO_MEM], mesh_adv.c:147 "Not enough memory to configure a new advertising handle. Update an existing advertising handle instead."
It looks like this has been solved in other cases and seems that this is where my problem is.
Hi.
The error NRF_ERROR_NO_MEM is because there is not enough memory to configure the advertising handle, you can check if you have the right start address atleast by following step 7 in this tutorial.
Best regards,
Andreas
I think the issue is something similar to this post about having multiple advertising sets. But still yet to confirm officially. Do you think this could be the culprit?
I think the issue is something similar to this post about having multiple advertising sets. But still yet to confirm officially. Do you think this could be the culprit?
Hi.
Well, it could be a problem, as there is always a limit of available memory. So you have to calculate that you have enough memory on the device compared to what you are using.
Best regards,
Andreas
Hello Andreas,
I am confident that is has something to do with both mesh_adv.c and ble_advertising.c calling sd_ble_gap_adv_set_configure . Would you be able to recreate this or assess the code to confirm or not?
Hi.
I don't think I can recreate it, because I don't know the steps you have done precisely. Regardless of this the error NRF_ERROR_NO_MEM is because you don't have enough memory when you configure your advertising handle. Have you checked this?
Best regards,
Andreas
I have checked the memory and you are right that I don't have it. Does that mean that it is not possible to run the proxy service with ble uart? Or is there anyway to advertise both these connectable services without conflict?
Hi.
You have to update your advertising set each time. Two advertising sets will give you NRF_ERROR_NO_MEM each time.
Here is some more information about how you can update the handle.
Best regards,
Andreas
