Proxy node with BLE_UART coexist

RE: Proxy node with BLE_UART coexist

AndreasF — Mon, 21 Jan 2019 06:25:26 GMT

Hi.

Sorry, I forgot that you had posted that link already. But could you try to update the advertising set?

Best regards,

Andreas

RE: Proxy node with BLE_UART coexist

brinehart — Fri, 18 Jan 2019 17:47:05 GMT

If you scroll up 9 days prior you can see I have already suggested that link.

RE: Proxy node with BLE_UART coexist

AndreasF — Wed, 16 Jan 2019 13:06:33 GMT

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

RE: Proxy node with BLE_UART coexist

brinehart — Wed, 16 Jan 2019 05:37:11 GMT

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?

RE: Proxy node with BLE_UART coexist

AndreasF — Tue, 15 Jan 2019 08:17:25 GMT

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

RE: Proxy node with BLE_UART coexist

brinehart — Tue, 15 Jan 2019 00:45:46 GMT

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?

RE: Proxy node with BLE_UART coexist

AndreasF — Thu, 10 Jan 2019 12:38:17 GMT

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

RE: Proxy node with BLE_UART coexist

brinehart — Thu, 10 Jan 2019 01:44:24 GMT

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?

RE: Proxy node with BLE_UART coexist

AndreasF — Mon, 07 Jan 2019 07:22:32 GMT

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

RE: Proxy node with BLE_UART coexist

brinehart — Fri, 04 Jan 2019 14:59:38 GMT

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.

RE: Proxy node with BLE_UART coexist

AndreasF — Fri, 04 Jan 2019 09:30:01 GMT

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.

[quote user="brinehart"]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?[/quote]

You should just set them in the nrf_mesh_config_core.h file

Best regards,

Andreas

RE: Proxy node with BLE_UART coexist

brinehart — Wed, 02 Jan 2019 19:51:41 GMT

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?

RE: Proxy node with BLE_UART coexist

AndreasF — Sat, 29 Dec 2018 12:33:24 GMT

Hi.

Line 117 in ble_softdevice_support.c is a error check for the function call nrf_sdh_enable_request(), and if you get NRF_ERROR_INVALID_STATE, you can see below in the API that you have already enabled the SoftDevice when you are making the function call nrf_sdh_enable_request():

/**@brief   Function for requesting to enable the SoftDevice.
 *
 * This function issues a @ref NRF_SDH_EVT_ENABLE_REQUEST request to all observers that
 * were registered using the @ref NRF_SDH_REQUEST_OBSERVER macro. The observers may or
 * may not acknowledge the request. If all observers acknowledge the request, the
 * SoftDevice will be enabled. Otherwise, the process will be stopped and the observers
 * that did not acknowledge have the responsibility to restart it by calling
 * @ref nrf_sdh_request_continue when they are ready for the SoftDevice to change state.
 *
 * @retval  NRF_SUCCESS                 The process is started.
 * @retval  NRF_ERROR_INVALID_STATE     The SoftDevice is already enabled.
 */
ret_code_t nrf_sdh_enable_request(void);

You should not have to call ble_stack_init, gap_params_init, and conn_params_init twice.

Best regards,

Andreas

RE: Proxy node with BLE_UART coexist

brinehart — Fri, 28 Dec 2018 15:38:12 GMT

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.

RE: Proxy node with BLE_UART coexist

AndreasF — Fri, 28 Dec 2018 10:02:26 GMT

Hi.

Which function call gives you this error? It is hard to pin point the cause based on so little information.

Best regards,

Andreas