Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Wed, 12 May 2021 10:25:01 GMT

Thanks Einar, it worked.

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Wed, 12 May 2021 09:31:16 GMT

Hi,

In this project you are using app_config.h (which takes presedence over sdk_config.h), wehre you have set NRF_SDH_BLE_VS_UUID_COUNT to 1. When I set this to 2 there is no error.

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Wed, 12 May 2021 08:38:03 GMT

V16

Source https://github.com/rmptxf/nrf52_ble_tester_project/tree/main/nRF5SDK/v16/projects/ble_peripheral/ble_app_tester

REF: www.youtube.com/watch

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Wed, 12 May 2021 08:34:53 GMT

Which SDK version is this for?

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Tue, 11 May 2021 09:57:14 GMT

devzone.nordicsemi.com/.../5556.ble_5F00_peripheral.zip

Using PCA10056-s140

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Tue, 11 May 2021 09:44:34 GMT

I see. Can you upload your complete project here so that I can have a look at it?

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Tue, 11 May 2021 09:29:04 GMT

following the below macro

***Try-2 Flash Macro***

FLASH_PH_START=0x0
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0x27000
FLASH_SIZE=0xd9000
RAM_START=0x20002ce0
RAM_SIZE=0x3d320

NRF_SDH_BLE_VS_UUID_COUNT Count value was 0(Zero) initially

I tried changing the value with 1, 2, 3, 10, 20(I tried them one by one individually

But all the time it was returning same error code.

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Tue, 11 May 2021 09:20:25 GMT

The first error is because you have configured app RAM start and size wrongly. Then you fixed that, and you get NRF_ERROR_NO_MEM returned from sd_ble_uuid_vs_add() add again. That means that you need to increase NRF_SDH_BLE_VS_UUID_COUNT

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Tue, 11 May 2021 09:13:30 GMT

After changing the RAM Size as follow

***OLD Flash Macro***
FLASH_PH_START=0x0
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0x27000
FLASH_SIZE=0xd9000
RAM_START=0x20002270
RAM_SIZE=0x3dd90
***Try-1 Flash Macro***
FLASH_PH_START=0x0
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0x27000
FLASH_SIZE=0xd9000
RAM_START=0x20001800
RAM_SIZE=0x3e800

I got the following error:

<info> app_timer: RTC: initialized.
<warning> nrf_sdh_ble: Insufficient RAM allocated for the SoftDevice.
<warning> nrf_sdh_ble: Change the RAM start location from 0x20001800 to 0x20002270.
<warning> nrf_sdh_ble: Maximum RAM size for application is 0x3DD90.
<error> nrf_sdh_ble: sd_ble_enable() returned NRF_ERROR_NO_MEM.
<error> app: Fatal error

***Try-2 Flash Macro***

FLASH_PH_START=0x0
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0x27000
FLASH_SIZE=0xd9000
RAM_START=0x20002ce0
RAM_SIZE=0x3d320

Still returns the same error code 4( NRF_ERROR_NO_MEM)

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Mon, 10 May 2021 11:52:59 GMT

Hi,

Sorry, I was multitasking a bit too much. Error code 4 is NRF_ERROR_NO_MEM, and from the API doc for sd_ble_uuid_vs_add() you see that it is returned if there are no more free slots for VS UUIDs. So you need to increase the NRF_SDH_BLE_VS_UUID_COUNT. Set this higher, and adjust the application RAM start address and size, as this will cause the SoftDevice RAM usage to increase slightly.

I am a bit surprised about what you write before, as this happens on the second base you add and you set it to 2, but you do not have full overview of you app and also add another bae UUID somewhere else (for instance if you incorporate a BLE service from the SDK that use a 128 bit UUID)?

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Mon, 10 May 2021 11:11:50 GMT

Hi Einar,

I was in debug build and error code = 0x00000004 call address 0x00028128

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Mon, 10 May 2021 11:05:22 GMT

Hi,

0 is NRF_SUCCESS so there must be something else. Looking at the log in your screenshot I see that you have not tested with a debug build. Please do that and let me know what the error code is.

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Mon, 10 May 2021 10:52:53 GMT

Ya I did them and the error is exactly on line where a I add the 2nd CUS BLE Service.

to be precise sd_ble_uuid_vs_add was returning the error code 4. which is from ble.h line 520.

// Add the Custom ble Service UUID
ble_uuid128_t base_uuid1 = CUS_SERVICE_UUID_BAS1;
err_code = sd_ble_uuid_vs_add(&base_uuid1, &p_cus->uuid_type);
NRF_LOG_INFO("003 %d", err_code);
if (err_code != NRF_SUCCESS)
{
return err_code;
}

And the error code was 0

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Mon, 10 May 2021 09:18:11 GMT

Hi,

Please make a debug build (if using SES, then just select the build target "Debug". If using another toolchain, then define "DEBUG" and "DEBUG_NRF" for the project. That way you will easily see in the log in which file, and which line number you got which error code. Which function call returns which error code?

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Fri, 07 May 2021 14:55:01 GMT

Hi Einar,

}

uint32_t ble_cus_init(ble_cus_t * p_cus, const ble_cus_init_t * p_cus_init)
{

    uint32_t                  err_code;
    ble_uuid_t                ble_uuid;
    ble_add_char_params_t     add_char_params;

/* Adding the service */

    // Initialize service structure.
    p_cus->evt_handler               = p_cus_init->evt_handler;
    p_cus->conn_handle               = BLE_CONN_HANDLE_INVALID;

    // Add the Custom ble Service UUID
    ble_uuid128_t base_uuid =  CUS_SERVICE_UUID_BASE;
    err_code =  sd_ble_uuid_vs_add(&base_uuid, &p_cus->uuid_type);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }
    
    ble_uuid.type = p_cus->uuid_type;
    ble_uuid.uuid = CUS_SERVICE_UUID;

    // Add the service to the database
    err_code = sd_ble_gatts_service_add(BLE_GATTS_SRVC_TYPE_PRIMARY, &ble_uuid, &p_cus->service_handle);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }


// Add the Custom ble Service UUID
    ble_uuid128_t base_uuid1 =  CUS_SERVICE_UUID_BAS1;
    err_code =  sd_ble_uuid_vs_add(&base_uuid1, &p_cus->uuid_type);
    NRF_LOG_INFO("003 %d", err_code);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }
/* Adding the service characteristics */

    // Add the buttons characteristic.

    uint8_t buttons_char_init_value [4] = {0};

    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid              = BUTTONS_STATES_CHAR_UUID;
    add_char_params.uuid_type         = p_cus->uuid_type;

    add_char_params.init_len          = 4;
    add_char_params.max_len           = 4;
    add_char_params.p_init_value      = buttons_char_init_value;

    add_char_params.char_props.read   = 1;
    add_char_params.char_props.notify = 1;
    add_char_params.char_props.write_wo_resp = 1;

    add_char_params.read_access       = SEC_OPEN;
    add_char_params.cccd_write_access = SEC_OPEN;

    err_code = characteristic_add(p_cus->service_handle,
                                  &add_char_params,
                                  &p_cus->buttons_states_char_handles);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }
    NRF_LOG_INFO("003 ");

    // Add the potentio characteristic.

    uint8_t pot_char_init_value [4] = {0};

    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid              = POTENTIO_LEVEL_CHAR_UUID;
    add_char_params.uuid_type         = BLE_UUID_TYPE_VENDOR_BEGIN;   //p_cus->uuid_typ2;

    add_char_params.init_len          = 4;// (in bytes)
    add_char_params.max_len           = 4;
    add_char_params.p_init_value      = pot_char_init_value;

    add_char_params.char_props.read   = 1;
    add_char_params.char_props.notify = 1;

    add_char_params.read_access       = SEC_OPEN;
    add_char_params.cccd_write_access = SEC_OPEN;

    err_code = characteristic_add(p_cus->service_handle,
                                  &add_char_params,
                                  &p_cus->potentio_level_char_handles);
    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }

    // Add the leds characteristic.

    uint8_t leds_char_init_value [2] = {0};

    memset(&add_char_params, 0, sizeof(add_char_params));
    add_char_params.uuid             = LEDS_STATES_CHAR_UUID;
    add_char_params.uuid_type        = BLE_UUID_TYPE_VENDOR_BEGIN;    //p_cus->uuid_typ3;

    add_char_params.init_len         = 2; // (in bytes)
    add_char_params.max_len          = 2;
   add_char_params.p_init_value      = leds_char_init_value;

    add_char_params.char_props.read  = 1;
    add_char_params.char_props.write = 1;

    add_char_params.read_access  = SEC_OPEN;
    add_char_params.write_access = SEC_OPEN;

    err_code = characteristic_add(p_cus->service_handle, 
                                  &add_char_params, 
                                  &p_cus->leds_states_char_handles);

    if (err_code != NRF_SUCCESS)
    {
        return err_code;
    }

    return NRF_SUCCESS;
}

When I try to add a base uuid 2nd time I getting a app: Fatal error.

I even changed number of vendor-specific UUID from 0-->2

#define NRF_SDH_BLE_VS_UUID_COUNT 2

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Tue, 04 May 2021 12:33:29 GMT

I see, that is peculiar. Then you must do as allready discussed in order to mimic this.

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Tue, 04 May 2021 08:16:02 GMT

Thanks Again, bellow is the protocol which I need to deploy in nrf52840

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Mon, 03 May 2021 09:24:34 GMT

Hi,

This is the same with Bluetooth 4.x and 5.x, and the SoftDevice API for this is mostly the same for a long time. What you want to do should be possible, but as it is not a normal approach it is not as elegant as you could hope. Essentially, you need to do as I wrote before, which is to add a base for each UUID, and a service UUID and a characteristic using that base. This is exactly what the code snippet you have included here does. Then you could duplicate this for all your different bases.

Do you know why the UUIDs are like this in the first place in the old product you are using? Could it be a misunderstanding somewhere? Could you check with nRF Connect for desktop and do a service discovery of the old product and copy--paste here just so we see to double-check?

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Fri, 30 Apr 2021 14:21:48 GMT

Thanks again Einar, I want to use such UUID because our old products, It's having such PS and PC's as below

UUID: 0x455449424C5545544845524DB87AD700 (in ASCII = ETIBLUETHERM¸z×)

Slot No.	Private Characteristic Name	Characteristic UUID	Property
1&2	Sensor 1 Reading	0x455449424C5545544845524DB87AD701	Read & Notify
3&4	Sensor 2 Reading*	0x455449424C5545544845524DB87AD703	Read & Notify
5&6	Command/ Notifications	0x455449424C5545544845524DB87AD705	Read/Write & Notify
7	Sensor 1 Settings	0x455449424C5545544845524DB87AD707	Read/Write
8	Sensor 2 Settings*	0x455449424C5545544845524DB87AD708	Read/Write
9	Instrument Settings	0x455449424C5545544845524DB87AD709	Read/Write
10	Trim Settings	0x455449424C5545544845524DB87AD70A	Read/Write

This is with BLE 4.1 and Now we are updating to BLE5.0 thus I also want to follow the same above protocol for all my Private Services and Private Characteristics. If I'm developing from scratch we can use new standards but here have have to follow this to support some custom developed native apps.

I kindly request you to review this possibility.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

-If I use

// Add the Custom ble Service UUID
ble_uuid128_t base_uuid = CUS_SERVICE_UUID_BASE;
err_code = sd_ble_uuid_vs_add(&base_uuid, &p_cus->uuid_type);
if (err_code != NRF_SUCCESS)
{
return err_code;
}

ble_uuid.type = p_cus->uuid_type;
ble_uuid.uuid = CUS_SERVICE_UUID;

// Add the service to the database
err_code = sd_ble_gatts_service_add(BLE_GATTS_SRVC_TYPE_PRIMARY, &ble_uuid, &p_cus->service_handle);

for each UUID it will be abed as PS

But I want to add PC

/* Adding the service characteristics */

// Add the buttons characteristic.

uint8_t buttons_char_init_value [4] = {0};

memset(&add_char_params, 0, sizeof(add_char_params));
add_char_params.uuid = BUTTONS_STATES_CHAR_UUID;
add_char_params.uuid_type = p_cus->uuid_type;

add_char_params.init_len = 4;
add_char_params.max_len = 4;
add_char_params.p_init_value = buttons_char_init_value;

add_char_params.char_props.read = 1;
add_char_params.char_props.notify = 1;

add_char_params.read_access = SEC_OPEN;
add_char_params.cccd_write_access = SEC_OPEN;

err_code = characteristic_add(p_cus->service_handle,
&add_char_params,
&p_cus->buttons_states_char_handles);

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Fri, 30 Apr 2021 13:42:02 GMT

No, that is not possible using the SoftDevice. You will need to add each base UUID with sd_ble_uuid_vs_add(), and then refer to each base when you use your UUID's (which will all have different base).

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Sivashankar — Fri, 30 Apr 2021 13:34:32 GMT

Hi Einar,

Thanks for your response, Is there a way where i can define each PC UUID full 128bit and PS UUID as below.

#define ETI_SVC_UUID { 0x00, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_SEN1_UUID { 0x01, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \

0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_COM_NOT_UUID { 0x05, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_SEN1_SET_UUID { 0x07, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_INS_SET_UUID { 0x09, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_TRM_SET_UUID { 0x0a, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
0x42, 0x49, 0x54, 0x45 }

CS_SERVICE_UUID_128(ETI_SERVICE0, ETI_SVC_UUID),

/* To the BLE transfer */

/* Sensor 1 Reading in Service 1 */
CS_CHAR_UUID_128(ETI_SEN1_READING_CHAR0, // attidx_char
ETI_SEN1_READING_VAL0, // attidx_val
ETI_CHAR_SEN1_UUID, // uuid
PERM(RD, ENABLE) | PERM(NTF, ENABLE), // perm
sizeof(app_env_cs.to_air_buffer), // length
app_env_cs.to_air_buffer, // data
NULL),

RE: Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

Einar Thorsrud — Fri, 30 Apr 2021 12:38:21 GMT

Hi,

Why do you want to change that? This is essentially the same question as in this old post. As the UUID format is standardized, doing it like you suggest means you will need a separate base for each UUID, where the base is incremented by one for each UUID. It will work, but it is a bit odd.