Advertising restart after a disconnect event

RE: Advertising restart after a disconnect event

Yatekii — Tue, 24 Oct 2017 06:18:17 GMT

The BAS example is officially called like that, I didn't make the name ;) Ofc I followed the migration documents of SDK 14 but nut the ones of SDK 13. WIll try, thanks :) ble_advertising_on_ble_evt() is never called ... it's just defined in the SDK ...

RE: Advertising restart after a disconnect event

Joakim Jakobsen — Mon, 23 Oct 2017 09:33:18 GMT

I don't know what you mean by the BAS example, but did you take a look at the migration notes when porting your project? When porting from SDK12 to SDK14, it might be a good idea to look at the SDK13 migration document first, before migrating to SDK14.
You can take a look at how the advertising is handled for the BLE_GAP_EVT_DISCONNECTED by taking a look at ble_advertising_on_ble_evt() in the ble_advertising.c file.

RE: Advertising restart after a disconnect event

Yatekii — Thu, 19 Oct 2017 08:48:37 GMT

Hi Joakim

I am using a custom board. But that does not have any impact. As the LED just works fine :) (I adjusted the BSP variables) I used the BAS example and ported it from SDK 12 to SDK 14 (as I already started the project in SDK 12 and then decided to switch to 14 (which was a huge mistake due to various reasons (Mesh being one))). Of course I had a look for different changes and I checked the few I had (I did a git bisect) but I am afraid it's a problem from after the SDK 14 port. So I am not sure if I missed something or if it's a bug in the SDK 14. The question is: do I have to restart advertising on my own? Because I was kind of 100% sure I didn't with SDK 12. If so, why doesn't an advertising_start() work?

RE: Advertising restart after a disconnect event

Joakim Jakobsen — Thu, 19 Oct 2017 08:43:14 GMT

Hi Noah!
Are you using the nRF52 DK? What example are you using? And did you make any changes to the code, besides the advertising_start(false)?