Getting own bluetooth address of device

RE: Getting own bluetooth address of device

shenzn — Tue, 01 Aug 2017 08:44:41 GMT

Thanks a lot, Hung Bui! I have found mistake in my source code. There is no any problem in sd_ble_gap_addr_get() It works fine now

RE: Getting own bluetooth address of device

Hung Bui — Mon, 31 Jul 2017 16:02:01 GMT

Yes it should properly. I don't know how you test, but we haven't got any report like what you described. My quick test in the ble_app_proximity showed the above result, the address in the advertising match with the address i got when calling sd_ble_gap_addr_get(). Check the image above.

RE: Getting own bluetooth address of device

shenzn — Mon, 31 Jul 2017 13:08:05 GMT

When it advertising I see different addresses by peer_addr = &p_ble_evt->evt.gap_evt.params.connected.peer_addr; But I want to know my own address without looking for that address on another side of communication chain. The problem is that sd_ble_gap_addr_get() returns incorrect address. Different which I see during advertising. Hung Bui, Did you try the sd_ble_gap_addr_get() function? Does it work correct?

RE: Getting own bluetooth address of device

Hung Bui — Mon, 31 Jul 2017 12:52:37 GMT

Can you use a phone or PC to check the address ? Try, for example, to let 2 devices advertising at the same time, and find the address, they should have different address.

RE: Getting own bluetooth address of device

shenzn — Fri, 28 Jul 2017 17:24:20 GMT

Sure, the sd_ble_gap_addr_get() has not return the same address. But it does in my case. I did like you say and check When it advertises I see unique address but if I use the mentioned function I am not able to get that address. So that function returns all the time the same value on different chips. So I am wondering if is it buggy function or me doing something wrong? If any way to check it?

RE: Getting own bluetooth address of device

Hung Bui — Fri, 28 Jul 2017 14:42:44 GMT

It doesn't sound very right that all chip returns same address. The default address should match with the 48bit DEVICEADDR in the FICR. Could you try to test with any ble peripheral example in the SDK ? Simply add sd_ble_gap_addr_get() call in and check the address. It should match with address when advertising. You can use PC or a Phone to check the address of the advertiser.

RE: Getting own bluetooth address of device

shenzn — Fri, 28 Jul 2017 12:23:48 GMT

I do not know which type of address is used (resolvable or static). How to check it?

RE: Getting own bluetooth address of device

shenzn — Fri, 28 Jul 2017 12:16:57 GMT

Thanks for the answer Hung Bui! In my case the sd_ble_gap_addr_get() function gets all the same value (0x04 0x00 0x20 0xE5 0x08 0x00) for different nFR52832 chips. That is why I have asked about that thing. If any other way to get the unique bluetooth address? And why sd_ble_gap_addr_get() function returns the same value for different chips in my case? Thanks!

RE: Getting own bluetooth address of device

Hung Bui — Fri, 28 Jul 2017 11:21:45 GMT

Hi Shenzn,

Do you use resolvable random address ? Or you simply use the static random address comes as the default with the chip ?

If you use the static random address, you can just call sd_ble_gap_addr_get() to get the address. It should not be the same for all chips. Each chip should have different address in the FICR.

If you use resolvable random address ( requires you to use _opt command to set) then it's not much point of getting that address because it will change over time.

Could you let me know what is the use of own_addr in your case ?