ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Fri, 16 Feb 2024 13:26:46 GMT

Please see my answer here: RE: scan name filter in ble_app_uart_c example

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Fri, 16 Feb 2024 11:53:58 GMT

Yes, I tried it already (see my second post before your last answer).

Where can I find the BLE device name in the advertising data so I can manually compare the data?

I now added a logic so that when my firmware gets the NRF_BLE_SCAN_EVT_FILTER_MATCH event in scan_evt_handler it only connects to the device when the rssi is >= -55

case NRF_BLE_SCAN_EVT_FILTER_MATCH:
        {
        // When a filter is matched, it generates NRF_BLE_SCAN_EVT_FILTER_MATCH to the main application.
            NRF_LOG_INFO("NRF_BLE_SCAN_EVT_FILTER_MATCH");
            if ((last_adv_report.rssi >= -55) && (last_adv_report.rssi != NULL)) {
                //sd_ble_gap_scan_stop(); // 20240214
                NRF_LOG_INFO("rssi = %d dBm", last_adv_report.rssi);
                ble_scan_connect_with_target(&m_scan, &last_adv_report); // 20240214
            }
            break;
        }

For this I handle the BLE_GAP_EVT_ADV_REPORT in ble_evt_handler and save the adv_report from the advertising event.

case BLE_GAP_EVT_ADV_REPORT:
        {
            last_adv_report = p_gap_evt->params.adv_report;
            break;
        }

This is a workaround that helps now... But still I would like to make it work correctly with the BLE device name filter.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Mon, 12 Feb 2024 08:32:06 GMT

[quote user="tbuenger"]How is this possible? It leads me to believe that (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER) sets the filters in a way so only one of both filters have to match to start a connection. I guess the UUID filter matches with some device and so it starts the connection.[/quote]

Try to set the 'match_all' flag to 'true' in your nrf_ble_scan_filters_enable() call.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Fri, 09 Feb 2024 10:48:46 GMT

When I remove the battery from my test locking cylinder (should be the peripheral named "BT Test"), initialize the BLE device name with "BT Test" and use nrf_ble_scan_filters_enable(&m_scan, (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER), false); the program still gets NRF_BLE_SCAN_EVT_FILTER_MATCH and connects to a device.

How is this possible? It leads me to believe that (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER) sets the filters in a way so only one of both filters have to match to start a connection. I guess the UUID filter matches with some device and so it starts the connection.

How can I print the BLE device name on my segger embedded studio terminal directly from the advertisement, that matched my filters? Right now I only set m_target_periph_name and print that with NRF_LOG_INFO("m_target_periph_name: \"%s\"", m_target_periph_name);

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Fri, 09 Feb 2024 09:51:16 GMT

When I use scan_init() with (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER) with the following code:

static void scan_init(void)
{
    ret_code_t          err_code;
    nrf_ble_scan_init_t init_scan;

    memset(&init_scan, 0, sizeof(init_scan));

    init_scan.p_scan_param     = &m_scan_param;
    init_scan.connect_if_match = true;
    init_scan.conn_cfg_tag     = APP_BLE_CONN_CFG_TAG;

    err_code = nrf_ble_scan_init(&m_scan, &init_scan, scan_evt_handler);
    APP_ERROR_CHECK(err_code);

    ble_uuid_t uuid =
    {
        .uuid = BLE_UUID_SDCS_SERVICE,
        .type = BLE_UUID_TYPE_VENDOR_BEGIN,
    };
    err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_UUID_FILTER, &uuid);
    APP_ERROR_CHECK(err_code);

    if (ble_device_name_string_init == true)
    {
        if (strlen(ble_device_name_string) != 0)
        {
            err_code = nrf_ble_scan_filter_set(&m_scan,
                                              SCAN_NAME_FILTER,
                                              ble_device_name_string);
            APP_ERROR_CHECK(err_code);
        }
    } else {
        
        for(int i=0; i<BDN_STR_LEN; i++) {
            m_target_periph_name[i] = '\0';
        }
        m_target_periph_name[0] = 'B';
        m_target_periph_name[1] = 'T';
        m_target_periph_name[2] = ' ';
        m_target_periph_name[3] = 'T';
        m_target_periph_name[4] = 'e';
        m_target_periph_name[5] = 's';
        m_target_periph_name[6] = 't';

        if (strlen(m_target_periph_name) != 0)
        {
            NRF_LOG_INFO("m_target_periph_name: \"%s\"", m_target_periph_name);
            NRF_LOG_INFO("sizeof(m_target_periph_name): %d", (sizeof(m_target_periph_name)));
            NRF_LOG_INFO("strlen(m_target_periph_name): %d", (strlen(m_target_periph_name)));
            err_code = nrf_ble_scan_filter_set(&m_scan,
                                              SCAN_NAME_FILTER,
                                              m_target_periph_name);
            APP_ERROR_CHECK(err_code);
            if (err_code == 0) 
            {
                for (int i=0; i<BDN_STR_LEN; i++)
                {
                    ble_device_name_string[i] = '\0';
                }
                for (int i=0; i<strlen(m_target_periph_name); i++) {
                    ble_device_name_string[i] = m_target_periph_name[i];
                }
                ble_device_name_string_init = true;
            }
        } else {
            NRF_LOG_INFO("Please set a ble device name via UART.");
        }
    }

    if (is_connect_per_addr)
    {
       err_code = nrf_ble_scan_filter_set(&m_scan,
                                          SCAN_ADDR_FILTER,
                                          m_target_periph_addr.addr);
       APP_ERROR_CHECK(err_code);
    }
    
    err_code = nrf_ble_scan_filters_enable(&m_scan,
          (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER), false);
    APP_ERROR_CHECK(err_code);
}

You can see I initialize m_target_periph_name with "BT Test". Normally this shouldn't be the default value. Normally I want my default value to be "BT Door" and input a desired BLE device name via UART but because we have multiple locking cylinders lying around in proximity I decided to initialize with "BT Test" for testing purposes now. I want to make sure the program filters correctly after BLE Name AND BLE Service UUID (not OR). I have set the ble device name on my test locking cylinder to "BT Test".

I am getting mode = 0x05 (hex) = 5 (decimal) ...

With NRF_BLE_SCAN_ALL_FILTER it was mode = 0x1F (hex) = 31 (decimal)

From the documentation I learned that (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER) enables NRF_BLE_SCAN_NAME_FILTER and NRF_BLE_SCAN_UUID_FILTER. This confused me because of the "|" operator (OR).

My collegue explained me that since both NRF_BLE_SCAN_UUID_FILTER and NRF_BLE_SCAN_NAME_FILTER are constants that contain number values, the bitwise OR works like a logical AND.

The last parameter in ble_scan_filters_enable(&m_scan, (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER), false); is called match_all in nrf_ble_scan.c/.h. I think this bool allows multiple filters to be set by a combination of constants like (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER). From my tests I notice that I have to set this to false.

When I use BLE device name "BT Test" and...

ble_scan_filters_enable(&m_scan, (NRF_BLE_SCAN_NAME_FILTER \| NRF_BLE_SCAN_UUID_FILTER), true);	can't connect
nrf_ble_scan_filters_enable(&m_scan, (NRF_BLE_SCAN_NAME_FILTER \| NRF_BLE_SCAN_UUID_FILTER), false);	can connect
nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_ALL_FILTER, true);	can't connect
nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_ALL_FILTER, false);	can connect

When I initialize BLE device name as "BT Door" and use...

ble_scan_filters_enable(&m_scan, (NRF_BLE_SCAN_NAME_FILTER \| NRF_BLE_SCAN_UUID_FILTER), true);	can't connect
nrf_ble_scan_filters_enable(&m_scan, (NRF_BLE_SCAN_NAME_FILTER \| NRF_BLE_SCAN_UUID_FILTER), false);	can connect
nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_ALL_FILTER, true);	can't connect
nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_ALL_FILTER, false);	can connect

In my admin phone app I can only see a "BT Test" device. So I am a bit confused why it can still connect even when I initialize with BLE device name "BT Door"... The firmware on my nRF52840 DK seems to connect to an unintended device in that case. I guess I have to adjust the filter further to give unique results by adding the BLE adress to the filter or add the RSSI and disable connect_if_match.

What do you think about this? If these are possible solutions I have to do some more research and decide which solution I want to realize.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 07 Feb 2024 14:15:48 GMT

Sorry I can't answer your question.

I wanted to see whether I can still find a matching peripheral by only using the UUID filter. It didn't work. From that I inferred that some of the changes I made to the scanning earlier today must have had some error.

I reverted some of the changes I made this morning:

- set .extended from true to false in m_scan_param

- reverted scan_start to what I had before:

static void scan_start(void)
{
    ret_code_t err_code;

    if (nrf_fstorage_is_busy(NULL))
    {
        m_memory_access_in_progress = true;
        return;
    }

    //ble_conn_state_init(); // 20240207

    NRF_LOG_INFO("Starting scan.");

    //sd_ble_gap_scan_stop(); // 20240207
    //err_code = sd_ble_gap_scan_start(&m_scan_param, &scan_buffer); // 20240207

    
    err_code = nrf_ble_scan_start(&m_scan);
    APP_ERROR_CHECK(err_code);
    

    err_code = bsp_indication_set(BSP_INDICATE_SCANNING);
    APP_ERROR_CHECK(err_code);
}

- in scan_init() I changed back to

err_code = nrf_ble_scan_filters_enable(&m_scan,
          NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER, false);

to see if I can still find something that way (all_filters_mode = false):

static void scan_init(void)
{
    ret_code_t          err_code;
    nrf_ble_scan_init_t init_scan;

    memset(&init_scan, 0, sizeof(init_scan));

    init_scan.p_scan_param     = &m_scan_param;
    init_scan.connect_if_match = true;
    init_scan.conn_cfg_tag     = APP_BLE_CONN_CFG_TAG;

    err_code = nrf_ble_scan_init(&m_scan, &init_scan, scan_evt_handler);
    APP_ERROR_CHECK(err_code);

    ble_uuid_t uuid =
    {
        .uuid = BLE_UUID_SDCS_SERVICE,
        .type = BLE_UUID_TYPE_VENDOR_BEGIN,
    };
    err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_UUID_FILTER, &uuid);
    APP_ERROR_CHECK(err_code);

    if (ble_device_name_string_init == true)
    {
        if (strlen(ble_device_name_string) != 0)
        {
            err_code = nrf_ble_scan_filter_set(&m_scan,
                                              SCAN_NAME_FILTER,
                                              //m_target_periph_name);
                                              ble_device_name_string);
            APP_ERROR_CHECK(err_code);
        }
    } else {
        
        for(int i=0; i<BDN_STR_LEN; i++) {
            m_target_periph_name[i] = '\0';
        }
        m_target_periph_name[0] = 'B';
        m_target_periph_name[1] = 'T';
        m_target_periph_name[2] = ' ';
        m_target_periph_name[3] = 'T';
        m_target_periph_name[4] = 'e';
        m_target_periph_name[5] = 's';
        m_target_periph_name[6] = 't';
        

        if (strlen(m_target_periph_name) != 0)
        {
            NRF_LOG_INFO("m_target_periph_name: \"%s\"", m_target_periph_name);
            NRF_LOG_INFO("sizeof(m_target_periph_name): %d", (sizeof(m_target_periph_name)));
            NRF_LOG_INFO("strlen(m_target_periph_name): %d", (strlen(m_target_periph_name)));
            err_code = nrf_ble_scan_filter_set(&m_scan,
                                              SCAN_NAME_FILTER,
                                              m_target_periph_name);
                                              //ble_device_name_string);
            APP_ERROR_CHECK(err_code);
            if (err_code == 0) 
            {
                for (int i=0; i<BDN_STR_LEN; i++)
                {
                    ble_device_name_string[i] = '\0';
                }
                for (int i=0; i<strlen(m_target_periph_name); i++) {
                    ble_device_name_string[i] = m_target_periph_name[i];
                }
                ble_device_name_string_init = true;
            }
        } else {
            NRF_LOG_INFO("Please set a ble device name via UART.");
        }
    }

    if (is_connect_per_addr)
    {
       err_code = nrf_ble_scan_filter_set(&m_scan,
                                          SCAN_ADDR_FILTER,
                                          m_target_periph_addr.addr);
       APP_ERROR_CHECK(err_code);
    }
    
    err_code = nrf_ble_scan_filters_enable(&m_scan,
          NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER, false);
    APP_ERROR_CHECK(err_code);
    
}

With all_filters_mode = false I can establish a connection:

With all_filters_mode = true I can't find anything.

When I try to debug code in nrf_ble_scan.c

[...]

#if (NRF_BLE_SCAN_NAME_CNT > 0)
    // Check the name filter.
    if (name_filter_enabled)
    {
        filter_cnt++;
        if (adv_name_compare(p_adv_report, p_scan_ctx))
        {
            filter_match_cnt++;

            // Information about the filters matched.
            scan_evt.params.filter_match.filter_match.name_filter_match = true;
            is_filter_matched = true;
        }
    }
#endif

[...]

#if (NRF_BLE_SCAN_UUID_CNT > 0)
    // Check the UUID filter.
    if (uuid_filter_enabled)
    {
        filter_cnt++;
        if (adv_uuid_compare(p_adv_report, p_scan_ctx))
        {
            filter_match_cnt++;
            // Information about the filters matched.
            scan_evt.params.filter_match.filter_match.uuid_filter_match = true;
            is_filter_matched = true;
        }
    }
#endif

[...]

I either run into NRF_BREAKPOINT_COND or I can not see the advertisement data:

I will continue to work on this on friday.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Wed, 07 Feb 2024 13:08:14 GMT

Thanks. 'NRF_BLE_SCAN_ALL_FILTER' did not show up in my search for some reason, so I assumed you had defined this symbol yourself. Anyway, do you see the same if you replace NRF_BLE_SCAN_ALL_FILTER with (NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER)?

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 07 Feb 2024 12:23:48 GMT

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Wed, 07 Feb 2024 12:17:53 GMT

Can you also post your definition of the NRF_BLE_SCAN_ALL_FILTER symbol?

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 07 Feb 2024 12:16:08 GMT

While debugging I noticed that I only need to call nrf_ble_scan_filters_enable() once.

Now I only use

err_code = nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_ALL_FILTER, true);
APP_ERROR_CHECK(err_code);

In debug I can see the followin scan_filters:

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 07 Feb 2024 10:54:39 GMT

Hello,

after a bit more testing and improving the general logic a bit further, the code now runs without errors.

The problem I have now is that I can't find the advertising peripheral device when I filter with UUID and BLE device name. Generally I can't find the peripheral when scanning with the BLE device name.

I think I should be able to check the name filter operation in adv_name_compare() in nrf_ble_scan.c but when I set a breakpoint inside that function, the debugger never seems to reach that breakpoint.

Since I want to filter by UUID and BLE device name I coded it like this:

main.c:

#define BLE_GAP_SCAN_BUFFER_EXTENDED_MIN (255)

#define BDN_STR_LEN 9

[...]

static ble_gap_scan_params_t const m_scan_param =
{
    .active        = 0x01,
#if (NRF_SD_BLE_API_VERSION > 7)
    .interval_us   = NRF_BLE_SCAN_SCAN_INTERVAL * UNIT_0_625_MS,
    .window_us     = NRF_BLE_SCAN_SCAN_WINDOW * UNIT_0_625_MS,
#else
    .interval      = NRF_BLE_SCAN_SCAN_INTERVAL,
    .window        = NRF_BLE_SCAN_SCAN_WINDOW,
#endif // (NRF_SD_BLE_API_VERSION > 7)
    .filter_policy = BLE_GAP_SCAN_FP_WHITELIST,
    .timeout       = SCAN_DURATION_WITELIST,
    .scan_phys     = BLE_GAP_PHY_1MBPS,
    .extended      = true,
};

static uint8_t scan_buffer_data[BLE_GAP_SCAN_BUFFER_EXTENDED_MIN];

static ble_data_t scan_buffer = {
    scan_buffer_data,
    BLE_GAP_SCAN_BUFFER_MIN
};

static char m_target_periph_name[BDN_STR_LEN];
static char ble_device_name_string[BDN_STR_LEN];
static bool ble_device_name_string_init = false;
static bool is_connect_per_addr = false;

[...]

static void scan_start(void)
{
    ret_code_t err_code;

    if (nrf_fstorage_is_busy(NULL))
    {
        m_memory_access_in_progress = true;
        return;
    }

    ble_conn_state_init(); // 20240207

    NRF_LOG_INFO("Starting scan.");

    sd_ble_gap_scan_stop(); // 20240207
    err_code = sd_ble_gap_scan_start(&m_scan_param, &scan_buffer); // 20240207

    /*
    err_code = nrf_ble_scan_start(&m_scan);
    APP_ERROR_CHECK(err_code);
    */

    err_code = bsp_indication_set(BSP_INDICATE_SCANNING);
    APP_ERROR_CHECK(err_code);
}

[...]

static void scan_init(void)
{
    ret_code_t          err_code;
    nrf_ble_scan_init_t init_scan;

    memset(&init_scan, 0, sizeof(init_scan));

    init_scan.p_scan_param     = &m_scan_param;
    init_scan.connect_if_match = true;
    init_scan.conn_cfg_tag     = APP_BLE_CONN_CFG_TAG;

    err_code = nrf_ble_scan_init(&m_scan, &init_scan, scan_evt_handler);
    APP_ERROR_CHECK(err_code);

    ble_uuid_t uuid =
    {
        .uuid = BLE_UUID_SDCS_SERVICE,
        //.type = BLE_UUID_TYPE_BLE, // fuer BT SIG UUIDs
        .type = BLE_UUID_TYPE_VENDOR_BEGIN, // fuer herstellerspezifische 128 bit UUIDs
    };
    err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_UUID_FILTER, &uuid);
    APP_ERROR_CHECK(err_code);

    if (ble_device_name_string_init == true)
    {
        if (strlen(ble_device_name_string) != 0)
        {
            err_code = nrf_ble_scan_filter_set(&m_scan,
                                              SCAN_NAME_FILTER,
                                              //m_target_periph_name);
                                              ble_device_name_string);
            APP_ERROR_CHECK(err_code);
        }
    } else {
        
        for(int i=0; i<BDN_STR_LEN; i++) {
            m_target_periph_name[i] = '\0';
        }
        m_target_periph_name[0] = 'B';
        m_target_periph_name[1] = 'T';
        m_target_periph_name[2] = ' ';
        m_target_periph_name[3] = 'T';
        m_target_periph_name[4] = 'e';
        m_target_periph_name[5] = 's';
        m_target_periph_name[6] = 't';
        

        if (strlen(m_target_periph_name) != 0)
        {
            NRF_LOG_INFO("m_target_periph_name: \"%s\"", m_target_periph_name);
            NRF_LOG_INFO("sizeof(m_target_periph_name): %d", (sizeof(m_target_periph_name)));
            NRF_LOG_INFO("strlen(m_target_periph_name): %d", (strlen(m_target_periph_name)));
            err_code = nrf_ble_scan_filter_set(&m_scan,
                                              SCAN_NAME_FILTER,
                                              m_target_periph_name);
                                              //ble_device_name_string);
            APP_ERROR_CHECK(err_code);
            if (err_code == 0) 
            {
                for (int i=0; i<BDN_STR_LEN; i++)
                {
                    ble_device_name_string[i] = '\0';
                }
                for (int i=0; i<strlen(m_target_periph_name); i++) {
                    ble_device_name_string[i] = m_target_periph_name[i];
                }
                ble_device_name_string_init = true;
            }
        } else {
            NRF_LOG_INFO("Please set a ble device name via UART.");
        }
    }

    if (is_connect_per_addr)
    {
       err_code = nrf_ble_scan_filter_set(&m_scan,
                                          SCAN_ADDR_FILTER,
                                          m_target_periph_addr.addr);
       APP_ERROR_CHECK(err_code);
    }

    err_code = nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_NAME_FILTER, true);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_UUID_FILTER, true);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_ALL_FILTER, true);
    APP_ERROR_CHECK(err_code);
}

sdk_config.h:

// <e> NRF_BLE_SCAN_FILTER_ENABLE - Enabling filters for the Scanning Module.
//==========================================================
#ifndef NRF_BLE_SCAN_FILTER_ENABLE
#define NRF_BLE_SCAN_FILTER_ENABLE 1
#endif
// <o> NRF_BLE_SCAN_UUID_CNT - Number of filters for UUIDs. 
#ifndef NRF_BLE_SCAN_UUID_CNT
#define NRF_BLE_SCAN_UUID_CNT 1
#endif

// <o> NRF_BLE_SCAN_NAME_CNT - Number of name filters. 
#ifndef NRF_BLE_SCAN_NAME_CNT
#define NRF_BLE_SCAN_NAME_CNT 1
#endif

// <o> NRF_BLE_SCAN_SHORT_NAME_CNT - Number of short name filters. 
#ifndef NRF_BLE_SCAN_SHORT_NAME_CNT
#define NRF_BLE_SCAN_SHORT_NAME_CNT 0
#endif

// <o> NRF_BLE_SCAN_ADDRESS_CNT - Number of address filters. 
#ifndef NRF_BLE_SCAN_ADDRESS_CNT
#define NRF_BLE_SCAN_ADDRESS_CNT 0
#endif

// <o> NRF_BLE_SCAN_APPEARANCE_CNT - Number of appearance filters. 
#ifndef NRF_BLE_SCAN_APPEARANCE_CNT
#define NRF_BLE_SCAN_APPEARANCE_CNT 0
#endif

// </e>

sdcs_c.h:

/**@brief   Macro for defining a ble_sdcs_c instance.
 *
 * @param   _name   Name of the instance.
 * @hideinitializer
 */
#define BLE_SDCS_C_DEF(_name)                                                                        \
static ble_sdcs_c_t _name;                                                                           \
NRF_SDH_BLE_OBSERVER(_name ## _obs,                                                                 \
                     BLE_SDCS_C_BLE_OBSERVER_PRIO,                                                   \
                     ble_sdcs_c_on_ble_evt, &_name)

/** @brief Macro for defining multiple ble_sdcs_c instances.
 *
 * @param   _name   Name of the array of instances.
 * @param   _cnt    Number of instances to define.
 * @hideinitializer
 */
#define BLE_SDCS_C_ARRAY_DEF(_name, _cnt)                 \
static ble_sdcs_c_t _name[_cnt];                          \
NRF_SDH_BLE_OBSERVERS(_name ## _obs,                     \
                      BLE_SDCS_C_BLE_OBSERVER_PRIO,       \
                      ble_sdcs_c_on_ble_evt, &_name, _cnt)


/** @brief  Maximum number of RR intervals to be decoded for each SDCS notifications (any extra RR intervals are ignored).
 *
 * This define should be defined in the sdk_config.h file to override the default.
 */
#ifndef BLE_SDCS_C_RR_INTERVALS_MAX_CNT
#define BLE_SDCS_C_RR_INTERVALS_MAX_CNT 20
#endif

#define SDCS_BASE_UUID {0x9F, 0xDC, 0x9C, 0x81, 0xFF, 0xFe, 0x94, 0x89, 0xE5, 0x11, 0x94, 0x9D, 0x00, 0xED, 0xCB, 0x5D} // little endian

#define BLE_UUID_SDCS_SERVICE   0xED00
#define SDCS_SERVICE_UUID_TYPE BLE_UUID_TYPE_VENDOR_BEGIN // 0x02 /**< UUID type for the Nordic UART Service (vendor specific). */

#define BLE_UUID_SDCS_PIPE_CHARACTERISTIC 0xED20

#define BLE_CLIENT_CHARACTERISTIC_CONFIG_UUID {{0x00, 0x00, 0x29, 0x02, 0x00, 0x00, 0x10, 0x00, 0x80, 0x00, 0x00, 0x80, 0x5f, 0x9b, 0x34, 0xfb}}

[...]

Please help.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Fri, 26 Jan 2024 11:26:08 GMT

Ok, I found out my firmware uses the BSP BLE Button Module... This module fires the BSP_EVENT_SLEEP event when BLE is not connected and Button 1 is released (This was case in my program).

In my main.c I handled the BSP_EVENT_SLEEP the following way:

case BSP_EVENT_SLEEP:
            NRF_LOG_INFO("BSP_EVENT_SLEEP");
            nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_SHUTDOWN_GOTO_SYSOFF);
            break;

This lead to my program going to sleep.

Now I commented those lines of code and it solved my problem 🙂

Thanks for helping me figuring this out!

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Wed, 24 Jan 2024 15:56:56 GMT

No worries. I'll leave this thread open.

[quote userid="104738" url="~/f/nordic-q-a/107563/error-4-nrf_error_no_mem-after-nrf_ble_scan_filter_set/465856"]I checked the code further and found out, that the error is caused in main()[/quote]

This is a different assert check. The crash log pointed to the assert here: C:\nRF5_SDK_17.0.2_d674dde\components\libraries\pwr_mgmt\nrf_pwr_mgmt.c:418

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 24 Jan 2024 15:42:18 GMT

Hello Vidar.

Sorry, I closed this ticket by excident...

I checked the code further and found out, that the error is caused in main()

[...]

// Enter main loop.
    for (;;)
    {
        if (uart_started == true)
        {
            uint8_t cr;
            while (app_uart_get(&cr) != NRF_SUCCESS);
            
[...]

by the call of app_uart_get(&cr).

Inside of app_uart_get(uint8_t * p_byte) the first command is ASSERT(p_byte).

This is defined in nrf_assert.h

#ifdef _lint
#define ASSERT(expr)                                                          \
if (expr)                                                                     \
{                                                                             \
}                                                                             \
else                                                                          \
{                                                                             \
    while (1);                                                                \
}
#else //_lint
#define ASSERT(expr)                                                          \
if (NRF_ASSERT_PRESENT)                                                       \
{                                                                             \
    if (expr)                                                                 \
    {                                                                         \
    }                                                                         \
    else                                                                      \
    {                                                                         \
        assert_nrf_callback((uint16_t)__LINE__, (uint8_t *)__FILE__);         \
    }                                                                         \
}

#endif

In debug I found that p_byte got a value of 0x00004001 and *p_byte is 0x80.

I don't understand why this is a problem but it is a problem. I think it is a problem with app_uart_fifo.

Do you have any idea what could be the issue here?

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Wed, 24 Jan 2024 14:01:02 GMT

I understand.

This assert is triggered if you attempt to enter the system OFF mode while debugging the application. Also, note that asserts are only enabled in the 'Debug' build configuration. This might explain why you have not encountered the error before.

[quote userid="104738" url="~/f/nordic-q-a/107563/error-4-nrf_error_no_mem-after-nrf_ble_scan_filter_set/465821"]How can I investigate this "system off" assertion in debug?[/quote]

You can start by looking for references to "sleep", "SYSOFF", "nrf_pwr_mgmt_shutdown", etc in your code.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 24 Jan 2024 13:54:40 GMT

Sadly I am not allowed to upload the whole project because it has confidential code. I can only post general code here... I asked my collegue about this earlier already but he doesn't allow it. I think I can share some more parts from my main.c... I have to ask my collegue about this. How can I investigate this "system off" assertion in debug? I am using Segger Embedded Studio for ARM 5.42a

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Wed, 24 Jan 2024 13:49:52 GMT

I saw it, but it is only displaying a portion of the callback, and I'm not sure what else, if anything, is included in the callback. I'm trying to understand where and when your application will try to enter system off. Can you upload your whole project instead?

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 24 Jan 2024 13:47:04 GMT

You can see the code for the button callback in the 4th post in this topic. Basicly the button only stops the scanning by calling nrf_ble_scan_stop() and then sets uart_started = true... see:

case BSP_EVENT_KEY_0:
        {   
            nrf_ble_scan_stop();
            
            NRF_LOG_INFO("Button 1 pressed.");
            //nrf_gpio_pin_toggle(LED_4); 
            NRF_LOG_INFO("Please enter a new #encryption_key and/or $ble device name: ");
            uart_receive();
            break;
        }

After uart_started got set to true, the firmware should run the code for uart processing by running the code in the if query in main().This already worked when my device had established a BLE connection.Now I try to run into this code before I got a working BLE connection.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Wed, 24 Jan 2024 13:36:14 GMT

Please post the code for your button callback.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 24 Jan 2024 13:32:33 GMT

The error appears right after I press the button. From the log I can see that the program starts reading input via UART but then it seems to get the error immediately. I didn't type anything in putty and I didn't get this problem before I changed the scanning. The difference is, that now I try to receive input via uart before my device has established a working BLE connection to SDCS and before I had the connection and then I initiated uart input processing.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Wed, 24 Jan 2024 13:25:02 GMT

[quote user="tbuenger"]Now I'm getting this error:[/quote]

This assertion is raised because the program attempts to enter System OFF mode (deep sleep) while the chip is in debug interface mode. I'm not sure where or when your application will try to enter sleep.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 24 Jan 2024 12:49:27 GMT

Some more information for clarification:

In my uart_receive() I only set uart_started = true...

The real logic for processing uart is in my main():

int main(void)
{
    // Initialize.
    log_init(); // uses UART
    timer_init();
    //bsp_board_init(BSP_INIT_LEDS);
    power_management_init();
    buttons_leds_init(&erase_bonds);
    //gpio_init();
    uart_started = false;
    uart_init(); // uses UART
    ble_stack_init();
    gatt_init();
    peer_manager_init();
    db_discovery_init();
    //hrs_c_init();
    sdcs_c_init();
    bas_c_init();
    scan_init();

    NRF_LOG_INFO("SDCS client started.");

    scanning_start(&erase_bonds);  

    // Enter main loop.
    for (;;)
    {
        if (uart_started == true)
        {
            uint8_t cr;
            while (app_uart_get(&cr) != NRF_SUCCESS);
            while (app_uart_put(cr) != NRF_SUCCESS);
            
            if (uart_receive_index < UART_RECEIVE_MAX_LENGTH)
            {
                uart_receive_data[uart_receive_index++] = cr;
            }
            
            if (uart_receive_index >= UART_RECEIVE_MAX_LENGTH ||
                cr == 0xD) // Enter
              //cr == 0x20) // Spacebar
            {
                NRF_LOG_INFO("\r\nExit UART.\r\n");
                //printf(" \r\nExit UART.\r\n");
                
                /*
                NRF_LOG_INFO("received data [line 1]: %x %x %x %x", uart_receive_data[0], uart_receive_data[1], uart_receive_data[2], uart_receive_data[3]);
                NRF_LOG_INFO("received data [line 2]: %x %x %x %x", uart_receive_data[4], uart_receive_data[5], uart_receive_data[6], uart_receive_data[7]);
                NRF_LOG_INFO("received data [line 3]: %x %x %x %x", uart_receive_data[8], uart_receive_data[9], uart_receive_data[10], uart_receive_data[11]);
                NRF_LOG_INFO("received data [line 4]: %x %x %x %x", uart_receive_data[12], uart_receive_data[13], uart_receive_data[14], uart_receive_data[15]);
                */
                
                uart_started = false;
                // determine length of input string
                if (cr == 0xD) {
                    uart_receive_length = (uart_receive_index -1);
                } else {
                    uart_receive_length = uart_receive_index;
                }
                NRF_LOG_INFO("uart_receive_length: 0x%x = %d", uart_receive_length, uart_receive_length);

[...]
// then I have some code which checks the input strings
[...]

                if (name_length != 0) {
                    NRF_LOG_INFO("name_length: %d", name_length);
                    if (name_length > BDN_STR_LEN)
                    {
                        NRF_LOG_INFO("Entered BLE name is too long! Max BLE name is %d characters!", BDN_STR_LEN);
                    } else { 
                        if (name_length < 1) {
                            NRF_LOG_INFO("Entered BLE name is too short!");
                        } else {
                            for (int i=0; i<BDN_STR_LEN; i++) {
                                ble_device_name_string[i] = ' ';
                            }
                            for (int i=0; (i<name_length && i<BDN_STR_LEN); i++) {
                                ble_device_name_string[i] = input_string[(i+name_begin_index)];
                            }
                            NRF_LOG_INFO("ble_device_name_string: %s", ble_device_name_string);
                            
                            // Remove all filters.
                            ret_code_t err_code;
                            err_code = nrf_ble_scan_all_filter_remove(&m_scan);
                            APP_ERROR_CHECK(err_code);

                            ble_uuid_t uuid =
                            {
                                .uuid = BLE_UUID_SDCS_SERVICE,
                                //.type = BLE_UUID_TYPE_BLE, // for BT SIG UUIDs
                                .type = BLE_UUID_TYPE_VENDOR_BEGIN, // for vendor specific 128 bit UUIDs
                            };
                            err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_UUID_FILTER, &uuid);
                            APP_ERROR_CHECK(err_code);

                            err_code = nrf_ble_scan_filter_set(&m_scan,
                                              SCAN_NAME_FILTER,
                                              ble_device_name_string);
                            APP_ERROR_CHECK(err_code);

                            if (is_connect_per_addr)
                            {
                                err_code = nrf_ble_scan_filter_set(&m_scan,
                                                         SCAN_ADDR_FILTER,
                                                         m_target_periph_addr.addr);
                                APP_ERROR_CHECK(err_code);
                            }
                            
                            err_code = nrf_ble_scan_filters_enable(&m_scan,NRF_BLE_SCAN_ALL_FILTER,true); // alle gesetzten filter muessen zutreffen
                            input_valid = true;
                        }
                    }
                }

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Wed, 24 Jan 2024 12:09:29 GMT

Hello Vidar,

thanks for your advice. I adjusted my program accordingly and it helped. Now I'm working on the next step and got a different problem:

When I disconnected after changing the filters, I noticed that my device always connected to a SDCS device (SDCS = Secure Data Container Service... It's our own BLE service). That lead me to believe that it didn't use the name filter correctly but only established the connection based on the UUID.

I then changed

err_code = nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_NAME_FILTER | NRF_BLE_SCAN_UUID_FILTER, false);

err_code = nrf_ble_scan_filters_enable(&m_scan,NRF_BLE_SCAN_ALL_FILTER,true);

I also added nrf_ble_scan_stop(); to the beginning of my Button event code:

case BSP_EVENT_KEY_0:
        {   
            nrf_ble_scan_stop();
            
            NRF_LOG_INFO("Button 1 pressed.");
            //nrf_gpio_pin_toggle(LED_4); 
            NRF_LOG_INFO("Please enter a new #encryption_key and/or $ble device name: ");
            uart_receive();
            break;
        }

Now I'm getting this error:

<info> app_timer: RTC: initialized.
<info> app: SDCS client started.
<info> app: Starting scan.
<info> app: Button 1 pressed.
<info> app: Please enter a new #encryption_key and/or $ble device name: 
<info> app: 
UART started.

<error> app: ERROR 3735928559 [Unknown error code] at C:\nRF5_SDK_17.0.2_d674dde\components\libraries\pwr_mgmt\nrf_pwr_mgmt.c:418
PC at: 0x0002744B
<error> app: End of error report

I think I need to improve the connection handling e.g. only start the authentication process, when I have an active connection... Or only start UART input when my device is ready... Any tips on how and where I should add some of these required if queries to improve firmware stability? Please help.

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

Vidar Berg — Fri, 19 Jan 2024 11:43:13 GMT

Hello Tobias,

Each time you call nrf_ble_scan_filter_set(), a new name is added to the filter. The number of names allocated for this filter is determined by the NRF_BLE_SCAN_NAME_CNT symbol in your sdk_config.h header and NRF_ERROR_NO_MEM is returned when you exceed this number.

A solution can be to call nrf_ble_scan_all_filter_remove() before adding the new name filter.

Best regards,

Vidar

RE: ERROR 4 [NRF_ERROR_NO_MEM] after nrf_ble_scan_filter_set()

tbuenger — Fri, 19 Jan 2024 11:35:33 GMT

Debug log:

<info> app_timer: RTC: initialized.
<info> app: SDCS client started.
<info> app: Starting scan.
<info> app: NRF_BLE_SCAN_EVT_FILTER_MATCH
<info> app: Connected. m_conn_handle: 0x0
<info> app: GATT ATT MTU on connection 0x0 changed to 247.
<info> app: BLE_GATTC_EVT_EXCHANGE_MTU_RSP
<info> app: Data length for connection 0x0 updated to 251.
<info> app: SDCS discovered.
<info> app: BLE Device Name: BT Door
<info> app: Waiting for Button press...
<info> app: Button 1 -> set new ble device name ($name) and/or encryption key (#key) via uart
<info> app: Button 2 -> start authentication
<info> app: Button 3 -> remote access open door request
<info> ble_sdcs_c: Configuring CCCD. CCCD Handle = 14, Connection Handle = 0
<info> app: BLE_GATTC_EVT_WRITE_RSP, gatt_status: 0x0
<info> app: BLE_GATT_HVX_NOTIFICATION
<info> app: Button 1 pressed.
<info> app: Please enter a new encryption_key: 
<info> app: 
UART started.

<info> app: 
Exit UART.

<info> app: uart_receive_length: 0x13 = 19
<info> app: name_length: 7
<info> app: ble_device_name_string (0 - 4): B T   T e
<info> app: ble_device_name_string (5 - 8): s t    
<error> app: ERROR 4 [NRF_ERROR_NO_MEM] at C:\nRF5_SDK_17.0.2_d674dde\examples\ble_central\ble_app_sdcs_c\main.c:1836
PC at: 0x00029F41
<error> app: End of error report