RE: pc-ble-driver sd_ble_uuid_vs_add() returns NRF_ERROR_NO_MEM

Vidar Berg — Thu, 16 Sep 2021 06:11:36 GMT

We actually recommend trial and error to find the appropriate table size. That is, start with the default ATT table size and increase it until you no longer get the NO_MEM error. There are too many factors that determine the size of a service/characteristics to make it an easy calculation.

[quote user="Dave New"]At the moment I am adding 13 vendor specific characteristic UUIDs and 3 services[/quote]

Is it a requirement to have a different base UUIDs for each characteristic? Services and characteristics that belong together will typically share the same vendor specific base UUID.

RE: pc-ble-driver sd_ble_uuid_vs_add() returns NRF_ERROR_NO_MEM

Dave New — Wed, 15 Sep 2021 11:28:20 GMT

Thanks, that seems to work. Is there a recommended table size for a given UUID count? At the moment I am adding 13 vendor specific characteristic UUIDs and 3 services

RE: pc-ble-driver sd_ble_uuid_vs_add() returns NRF_ERROR_NO_MEM

Vidar Berg — Wed, 15 Sep 2021 09:01:42 GMT

Hello,

The attribute table size and the size of the vendor specific UUID buffer has to be configured on the application side through the ble_cfg_set() function.

Example:

/**@brief Function for setting configuration for the BLE stack.
 *
 * @return NRF_SUCCESS on success, otherwise an error code.
 */
static uint32_t ble_cfg_set(uint8_t conn_cfg_tag)
{
    const uint32_t ram_start = 0; // Value is not used by ble-driver
    uint32_t error_code;
    ble_cfg_t ble_cfg;

    // Configure the connection roles.
    memset(&ble_cfg, 0, sizeof(ble_cfg));

#if NRF_SD_BLE_API >= 6
    ble_cfg.gap_cfg.role_count_cfg.adv_set_count = BLE_GAP_ADV_SET_COUNT_DEFAULT;
#endif
    ble_cfg.gap_cfg.role_count_cfg.periph_role_count  = 0;
    ble_cfg.gap_cfg.role_count_cfg.central_role_count = 1;
    ble_cfg.gap_cfg.role_count_cfg.central_sec_count  = 0;

    error_code = sd_ble_cfg_set(m_adapter, BLE_GAP_CFG_ROLE_COUNT, &ble_cfg, ram_start);
    if (error_code != NRF_SUCCESS)
    {
        printf("sd_ble_cfg_set() failed when attempting to set BLE_GAP_CFG_ROLE_COUNT. Error code: "
               "0x%02X\n",
               error_code);
        fflush(stdout);
        return error_code;
    }

    memset(&ble_cfg, 0x00, sizeof(ble_cfg));
    ble_cfg.conn_cfg.conn_cfg_tag                 = conn_cfg_tag;
    ble_cfg.conn_cfg.params.gatt_conn_cfg.att_mtu = NRF_SDH_BLE_GATT_MAX_MTU_SIZE;

    error_code = sd_ble_cfg_set(m_adapter, BLE_CONN_CFG_GATT, &ble_cfg, ram_start);
    if (error_code != NRF_SUCCESS)
    {
        printf("sd_ble_cfg_set() failed when attempting to set BLE_CONN_CFG_GATT. Error code: "
               "0x%02X\n",
               error_code);
        fflush(stdout);
        return error_code;
    }

    memset(&ble_cfg, 0x00, sizeof(ble_cfg));
    ble_cfg.common_cfg.vs_uuid_cfg.vs_uuid_count = 10;

     error_code = sd_ble_cfg_set(m_adapter, BLE_COMMON_CFG_VS_UUID, &ble_cfg, ram_start);
    if (error_code != NRF_SUCCESS)
    {
        printf("sd_ble_cfg_set() failed when attempting to set BLE_COMMON_CFG_VS_UUID. Error code: "
               "0x%02X\n",
               error_code);
        fflush(stdout);
        return error_code;
    }   

    memset(&ble_cfg, 0x00, sizeof(ble_cfg));
    ble_cfg.gatts_cfg.attr_tab_size.attr_tab_size = 2816;
     error_code = sd_ble_cfg_set(m_adapter, BLE_GATTS_CFG_ATTR_TAB_SIZE, &ble_cfg, ram_start);
    if (error_code != NRF_SUCCESS)
    {
        printf("sd_ble_cfg_set() failed when attempting to set BLE_GATTS_CFG_ATTR_TAB_SIZE. Error code: "
               "0x%02X\n",
               error_code);
        fflush(stdout);
        return error_code;
    } 
    
    ...

Please try this and see if it helps.

[quote user=""]Doubled the stack size and heap size in the Keil options to __HEAP_SIZE=1024 __STACK_SIZE=4096[/quote]

You can leave this configuration as is. The connectivity FW does not use heap memory and the call stack is placed at the end of RAM anyway.

Best regards,

Vidar

Correction: Call stack is not placed at the end of RAM if you build with Keil but instead placed right above the globals. I.e. a stack overrun is guaranteed to overwrite global variables unlike FW built with GCC and therefore lead to undefined behavior. But 4096 bytes should be sufficient.