Configurable UUID

RE: Configurable UUID

Bjørn Kvaale — Mon, 11 Mar 2019 13:58:39 GMT

siddhesh sawant Could you please create a new devzone case? Thank you.

RE: Configurable UUID

siddhesh sawant — Sat, 09 Mar 2019 12:26:23 GMT

i wanted to change the default UUID in ble_light_switch example? what should i do ? where i can find the default UUID

RE: Configurable UUID

endnode — Thu, 16 Nov 2017 08:59:35 GMT

Hard to say what you do wrong. Is normally pstorage_test_init function working? Where you place it normally? What error you get when you place it here? Or you just don't see the advertisement and that's your test? You don't need to answer these questions to me, these are just examples of questions you should ask yourself.

RE: Configurable UUID

milav — Thu, 16 Nov 2017 08:56:10 GMT

no....this the portion in which i initialized...

RE: Configurable UUID

endnode — Thu, 16 Nov 2017 08:54:28 GMT

Simple question: is pstorage already enabled/initialized?

RE: Configurable UUID

milav — Thu, 16 Nov 2017 08:52:55 GMT

but i am not able to read data from pstorage at time of ble_nus_init.

Here i send the snapshots of this function...

uint32_t ble_nus_init(ble_nus_t * p_nus, const ble_nus_init_t * p_nus_init) { uint32_t err_code; ble_uuid_t ble_uuid; ble_uuid128_t nus_base_uuid = NUS_BASE_UUID;

VERIFY_PARAM_NOT_NULL(p_nus);
VERIFY_PARAM_NOT_NULL(p_nus_init);

// Initialize the service structure.
p_nus->conn_handle             = BLE_CONN_HANDLE_INVALID;
p_nus->data_handler            = p_nus_init->data_handler;
p_nus->is_notification_enabled = false;

/**@snippet [Adding proprietary Service to S110 SoftDevice] */
// Add a custom base UUID.
err_code = sd_ble_uuid_vs_add(&nus_base_uuid, &p_nus->uuid_type);
VERIFY_SUCCESS(err_code);

ble_uuid.type = p_nus->uuid_type;
//ble_uuid.uuid = BLE_UUID_NUS_SERVICE;
	

	uint8_t *load_uuid;
	pstorage_test_init();
	UART_sendCString("pstorage_test_init\r\n");
	load_uuid = pstorage_test_load();
	
	UART_sendCString("pstorage_test_load\r\n");

	tag_uuid = (uint16_t)((load_uuid[0] << 8) | (load_uuid[1] & 0xFF));
	if(tag_uuid == 0xFFFF)
	{
			printf("ble_nus_init tag_uuid = 0\r\n");
			tag_uuid = 0x0000;
	}
	else
	{
		
		printf("Tag UUID is :- %d\r\n",tag_uuid);
	}
	ble_uuid.uuid = tag_uuid;


// Add the service.
err_code = sd_ble_gatts_service_add(BLE_GATTS_SRVC_TYPE_PRIMARY,
                                    &ble_uuid,
                                    &p_nus->service_handle);
/**@snippet [Adding proprietary Service to S110 SoftDevice] */
VERIFY_SUCCESS(err_code);

// Add the RX Characteristic.
err_code = rx_char_add(p_nus, p_nus_init);
VERIFY_SUCCESS(err_code);

// Add the TX Characteristic.
err_code = tx_char_add(p_nus, p_nus_init);
VERIFY_SUCCESS(err_code);

return NRF_SUCCESS;

} id.uuid = tag_uuid;

i can not get the interrupt from pstorage at time of load the data..

RE: Configurable UUID

endnode — Thu, 16 Nov 2017 08:47:13 GMT

Sure, you can do whatever you want with your pstorage;)

RE: Configurable UUID

milav — Thu, 16 Nov 2017 08:40:28 GMT

If we use the Pstorage for store the UUID....and we want to read the UUID at time of power of board.

so that the board advertise with new UUID.

so is this possible to read the UUID from pstorage in the time of service initialize?

RE: Configurable UUID

endnode — Mon, 13 Nov 2017 15:22:54 GMT

Well it doesn't matter where you store it, internal flash, external, UICR region, it's up to you where your app stores config data. Pstorage module should be enough. If you use it and you don't see the desired result then you simply have a bug in your project so test it properly, do UART or RTT tracing, do simple little steps and verify after each etc. This is nothing we could fix for you on forum.

RE: Configurable UUID

milav — Mon, 13 Nov 2017 15:19:54 GMT

i want to change ....this bit in UUID..

//ble_uuid.uuid = BLE_UUID_NUS_SERVICE;

ble_uuid.uuid = tag_uuid;

RE: Configurable UUID

milav — Mon, 13 Nov 2017 15:18:23 GMT

external flash or internal flash?

I also loaded data in pstorage.... and restart the chip as softreset..

but the logic was not work....

RE: Configurable UUID

endnode — Mon, 13 Nov 2017 15:12:27 GMT

But as I said it looked better to me to just store new UUID in flash and reboot whole chip where it would init GATT Server with correct new UUIDs once it boots next time.

RE: Configurable UUID

endnode — Mon, 13 Nov 2017 15:11:36 GMT

If you want to change GATT handles on the stack (meaning delete some) you need to disable BLE stack. I cannot tell you what one-liner call does that, look into SDK, look into examples, search on the forum.

RE: Configurable UUID

milav — Mon, 13 Nov 2017 15:08:05 GMT

Thank You...

let me explain in more details...the flow is like....

UART_setup();
ble_init() { // Initialize. APP_TIMER_INIT(APP_TIMER_PRESCALER, APP_TIMER_OP_QUEUE_SIZE, false); //uart_init();

buttons_leds_init(&erase_bonds); ble_stack_init(); gap_params_init(); services_init(); advertising_init(); conn_params_init(); }

uint32_t ble_advertise() { uint32_t err_code;

 	err_code = ble_advertising_start(BLE_ADV_MODE_FAST);
 	APP_ERROR_CHECK(err_code);

 return err_code;

}

now in re advertise which function i call..?

please explain me....

RE: Configurable UUID

endnode — Mon, 13 Nov 2017 15:02:55 GMT

Nom that's not the correct way, you cannot call BLE init once you already did it. You need to reset the whole chip or to disable Soft Device and enable it again. I also suspect that these BLE_INIT and BLE_ADVERTISE boxes are some high level function call which really are in your code. If so then please understand that I have no clue what these blackboxes do and so I cannot advice on sequence or parameters of these functions.

RE: Configurable UUID

milav — Mon, 13 Nov 2017 14:58:36 GMT

I do this same thing....let me explain......my code flow as following.....

UART Setup();
BLE_INIT();
BLE_ADVERTISE();

from Central send new UUID to peripheral. after receiving the new UUID .....

call sd_ble_gap_disconnect() function. and again i restart the advertising..

BLE_INIT();
BLE_ADVERTISE();

is this correct way?

please correct me if i m wrong...

Thank You.

RE: Configurable UUID

endnode — Mon, 30 Oct 2017 12:39:36 GMT

But "standard" way how to implement this with current Nordic SD would be:

Let some default UUID (saying "I'm unpersonalized device of yours").
Once master connects and is allowed to modify/personalize it assigns new UUID.
Devices must disconnect. GATT Server saves new configuration and reboots.
As soon as GAP Peripheral/GATT Server boots it uses new UUID to populate GATT Server differently then before and it's ready to be used as you intended.

If you are fine with that disconnection you have your solution. Otherwise go with different BLE stack.

RE: Configurable UUID

endnode — Mon, 30 Oct 2017 12:36:23 GMT

UUID shouldn't be identifier of particular device but it should be class of devices (= providers of specific kind of service). Devices are identified by MAC and if you don't want or cannot use it then you should define your own proprietary identifier (and place it to your APP data e.g. in Manufacturer Specific AD element of ADV/SCAN_RSP data). But back to the technical side of your proposed solution: Nordic (G)ATT Server API supports only adding Services/Characteristics not hiding or deleting so I'm afraid you will either need to go with different stack (Zephyr might be good choice because if it doesn't support this you may implement it yourself) or change your solution or try to get some more help from Nordic (maybe they have such feature in a back log but I don't see any indication of that from outside).

RE: Configurable UUID

milav — Mon, 30 Oct 2017 09:32:05 GMT

is there any chance to configure the UUID which i describe as in Question?

the actual case is like this...

there are ten BLE enabled board which are advertise. we give...10 different the serial number so that in central we have a choice to select any one of them Using Different UUID.

RE: Configurable UUID

endnode — Mon, 30 Oct 2017 07:37:08 GMT

The only way how to change GATT Server objects with Nordic Soft Device is to "restart" it (typically softreset of the chip is faster way). UUIDs are assumed to be static identifiers.