nRF52 change device name

RE: nRF52 change device name

Sylvain — Wed, 02 May 2018 14:52:36 GMT

Ok, thank you for the answer ...

RE: nRF52 change device name

Mttrinh — Wed, 02 May 2018 13:43:05 GMT

That is because sd_ble_gap_device_name_set() is implemented in the softdevice.

We don't supply source code for our SoftDevices, just an API to interface with it as a part of our SDK.

RE: nRF52 change device name

Sylvain — Fri, 27 Apr 2018 09:38:55 GMT

Thanks for you answer.

I success to change the name on keeping the advertisement structure.

I don't understand why you say that's not possible to find the source code of the sd_ble_gap_device_name_set() function . The code should be somewhere even if it is an assembly code ...

RE: nRF52 change device name

Mttrinh — Fri, 27 Apr 2018 09:05:29 GMT

Hi,

You will get "N/A" if the name is not included or advertised. To include the name you have to set advdata.name_type to either BLE_ADVDATA_SHORT_NAME or BLE_ADVDATA_FULL_NAME in advertising_init(). and set the name by calling sd_ble_gap_device_name_set(). The sd_ble_gap_device_name_set() function will only set the GAP device name, this function is a softdevice function so you won't find the code for it.

I suggest you to have a look at the advertising_init() in any of the ble_peripheral examples in the SDK.

RE: nRF52 change device name

Sylvain — Wed, 25 Apr 2018 16:00:38 GMT

I use the SDK V14.2.0 ...

I agree I don't need to setup connection. But I set up the advertising and then start the advertising, so it's working fine.

I think my problem come from the fact that I don't pass the advertising data structure to the sd_ble_gap_adv_data_set () function.

I would like to know what the sd_ble_gap_device_name_set () function does. Do you know in which C file it is implemented?

Sylvain.

RE: nRF52 change device name

Mark — Wed, 25 Apr 2018 15:33:07 GMT

Again, not sure which SDK version you are using and I understand there are some slight variations so maybe I am missing something. However, I don't ever see a call to ble_advertising_init or an alternative.

You don't have to setup connections, but you have to tell the API what flags to set (commonly using ble_advertising_init) before you start advertising. Otherwise while you set the DEVICE_NAME in the API you never setup the advertising structure and initialized it before you advertised.

The fact that when you set the advertisement flags manually it works, only proves that point.

The comment on connect/disconnect or shutting off bluetooth was just to describe how the local BLE database gets updated on Android and iPhone devices, not specific to your code or your device functionality. Just covering details as I have seen many people waste significant time around names not updating simply because of the device cache.

RE: nRF52 change device name

Sylvain — Wed, 25 Apr 2018 14:47:26 GMT

1) My code is complete. In fact, I receive packets on the nRF Connect app

2) I don't understand why you talk about connect and disconnect. I'm in the Observer-Broadcaster scheme. So, no connection is required

RE: nRF52 change device name

Mark — Wed, 25 Apr 2018 14:23:28 GMT

Two quick points.

First: Your code appears incomplete for advertising. I'd suggest checking out one of the examples from the version SDK you are using. Maybe check: ble_peripheral/ble_app_uart or similar.

Second: When a BLE device is first seen by a device, e.g. Android or iPhone etc, the name is stored in a local database along with the mac id of the device. BLE does not update this name unless you connect and than disconnect from the device, OR you turn off bluetooth and then turn it back on clearing the local DB. Then on the next scan it will update the name. This is of course, assuming it is set properly from the advertising code.