Converting ble_app_uart_c to support with multiple central connections

RE: Converting ble_app_uart_c to support with multiple central connections

Hieu — Wed, 21 Sep 2022 08:04:53 GMT

Hi Sudheer,

Great to know. I have suggested my first answer about the SoftDevice max link configuration as the answer to the original question this thread is about. If you don't mind, please verify it as the answer, or I can also do it later :D

Best regards,

Hieu

RE: Converting ble_app_uart_c to support with multiple central connections

A sudheer Kumar — Wed, 21 Sep 2022 04:37:42 GMT

Hi Hieu,

Thanks for your support, It's working fine for me after changing the values of Macros section placement according nrf52833 RAM size

Regards,

sudheer

RE: Converting ble_app_uart_c to support with multiple central connections

Hieu — Tue, 20 Sep 2022 13:59:43 GMT

Hi Sudheer,

One thing that stands out immediately is that the RAM start address should be 0x20005228 instead of 0x20005288.

If that is intentional on your part, notice that

x5288 + x1ADD8 = x20060. That is more than the 128kB of RAM you have on the nRF52833
There is no need to give the SoftDevice more RAM than it asks for
Your application is basically running out of RAM as is.

So please fix it. However, this is small and probably not what is causing you problem. Unfortunately I don't have the same issue using your main.c file on a nRF52832 with even smaller RAM. I assume you have just added some code to the application?

I recommend you to take a look at this discussion: Heap size .

If that doesn't help, please open a new ticket, and one of our Tech Support team will be happy to help you.

Best of luck,

Hieu

RE: Converting ble_app_uart_c to support with multiple central connections

A sudheer Kumar — Tue, 20 Sep 2022 09:05:26 GMT

Hi Hieu,

thanks for the replay,

- Your memory setting configuration, where you changed the RAM start address.

-please check the attached pic for Macro section placement

- Are you using only nRF52833 for this project?

- Yes, Actually we are planning nrf52833 for concurrent peripheral and central connections, for collecting and sharing the sensors(like Temperature, Humidity, etc.. ) data across the devices. always welcome if you have any advice.

sure, New ticket will open for further communication

Regards,

Sudheer

RE: Converting ble_app_uart_c to support with multiple central connections

Hieu — Tue, 20 Sep 2022 08:54:01 GMT

Hi Sudheer,

Glad to see you solved your original question.

Let's take a quick look at this next one. However, please know that if it is sufficiently different/complicated, I will have to request you to open a new ticket.

I need two information:

- Your memory setting configuration, where you changed the RAM start address.

- Are you using only nRF52833 for this project?

RE: Converting ble_app_uart_c to support with multiple central connections

A sudheer Kumar — Tue, 20 Sep 2022 04:50:36 GMT

Hi Hieu,

Yes, you are correct. NRF_SDH_BLE_CENTRAL_LINK_COUNT was 4 but NRF_SDH_BLE_TOTAL_LINK_COUNT was 1.

now I changed NRF_SDH_BLE_TOTAL_LINK_COUNT to 4 and build, while build it has been showing memory settings needs to change(please check the attached pic-error3).

Changed Section placement macros according to the attached pic, After changing section placement macros now it showing "heap is too large to fit in RAM1 memory segment".

kindly guide me to solve this memory related issue.

Regards,

sudheer

RE: Converting ble_app_uart_c to support with multiple central connections

Hieu — Mon, 19 Sep 2022 13:10:59 GMT

Hi Sudheer,

As you can see in that log, the assert happen at line 154 in your code, which is this section of code checking for Connecting Errors.

static void scan_evt_handler(scan_evt_t const * p_scan_evt)
{
    ret_code_t err_code;

    switch(p_scan_evt->scan_evt_id)
    {
         case NRF_BLE_SCAN_EVT_CONNECTING_ERROR:
         {
              err_code = p_scan_evt->params.connecting_err.err_code;
/* >>>>>>> */ APP_ERROR_CHECK(err_code);
         } break;

Another thing you can see is that the error code is 18, NRF_ERROR_CONN_COUNT.

From the name and context, you can guess, or confirm through the documentation, that this error indicates that you are connecting more than the application is configured to handle.

This analysis matches with your first screenshot, where the log indicates a successful first connection, and an error on the second connection attempt. However, it does not match with your second screenshot and typed out log... That bugs me a little.

For now, could you please double check the following sdk_config items if they have been updated to a suitable value?

NRF_SDH_BLE_TOTAL_LINK_COUNT
NRF_SDH_BLE_CENTRAL_LINK_COUNT

Best regards,

Hieu

RE: Converting ble_app_uart_c to support with multiple central connections

A sudheer Kumar — Mon, 19 Sep 2022 12:41:55 GMT

Hi Hieu,

please find the below information copied from the Debug terminal

<info> app_timer: RTC: initialized.
<info> app: BLE UART central example started.
<info> app: Connecting to target DACF341E3DD9
<error> app: ERROR 18 [NRF_ERROR_CONN_COUNT] at D:\DMD\NTL-Startopalogy\Central\nRF5_SDK_17.1.0_ddde560\examples\ble_central\ble_app_uart_c\main.c:154
PC at: 0x00030575
<error> app: End of error report

Regards,

Sudheer

RE: Converting ble_app_uart_c to support with multiple central connections

Hieu — Mon, 19 Sep 2022 12:35:34 GMT

Hi Sudheer,

Could you please give me the full 4th line?

My request for the Debug build is not to fix the issue. It's to get the error handling module to print out more information. But on your latest screenshot that information is clipped off by the small window.

Best regards,

Hieu

RE: Converting ble_app_uart_c to support with multiple central connections

A sudheer Kumar — Mon, 19 Sep 2022 12:05:59 GMT

Hi Hieu,

thanks for reply,

there is no breakpoints kept while debugging.

Just build and debugged with "Debug" option instead of "Release", but still facing the same issue.

please see the attached debug terminal output

Regards,

Sudheer

RE: Converting ble_app_uart_c to support with multiple central connections

Hieu — Mon, 19 Sep 2022 11:51:27 GMT

Hi Sudheer, welcome back.

I can see from the log that you are building for Release. Could you please try again but build with the Debug option? The log would give more helpful options then.

Please also double check if your setup is having any breakpoints. Your logs are somewhat similar to cases where users have problems due to an inadvertent breakpoint. Breakpoints will cause an application to crash when the application is using SoftDevice; that is due to how SoftDevice works.

Best regards,

Hieu