iOS compatibillity with SDK13

RE: iOS compatibillity with SDK13

run_ar — Mon, 09 Apr 2018 07:42:36 GMT

You might have other problems as well. I would recommend that you use a sniffer to check what is happening on air to see where your product is failing.

RE: iOS compatibillity with SDK13

weizhen — Wed, 28 Mar 2018 05:28:52 GMT

hi, have you try sdk14.2? I meet the same problem when I try to upgrade mine from sdk12.2 to sdk14.2. and I try what you said, but still not works.

RE: iOS compatibillity with SDK13

run_ar — Fri, 31 Mar 2017 08:47:28 GMT

@Tostikoning, Thanks for updating the case, glad to hear you figured it out. I guess the problem is that the new SD now requires that the application responds to the Data Length Update Procedure. Mentioned in the SD migration document. I'm guessing; the reason why it works with Android, is because the android device you are testing with doesn't negotiate the MTU size?

RE: iOS compatibillity with SDK13

BH — Wed, 29 Mar 2017 08:38:26 GMT

Works fine for me too. Thanks!

RE: iOS compatibillity with SDK13

Tostikoning — Tue, 28 Mar 2017 08:11:33 GMT

Okay, I found my problem.

I migrated from SDK12 to SDK13. One quite big difference which was not mentioned in the migration documentation is the change in the GATT module. This module needs to be implemented separate.

If you migrated to SDK13 following the migration documents and everything compiles, check if the Android version of NRF Connect can read your services.

If this is possible you are nearly there, just add the following code:

Add #include "nrf_ble_gatt.h" to your includes
Add nrf_ble_gatt.c to your sources
Initialize the GATT module:

void gatt_init(void)
{
    ret_code_t err_code = nrf_ble_gatt_init(&m_gatt, NULL);
    APP_ERROR_CHECK(err_code);
}

Call gatt_init() before advertise_init()
Add nrf_ble_gatt_on_ble_evt(&m_gatt, p_ble_evt); To your ble_evt_dispatch function.
Add static nrf_ble_gatt_t m_gatt; (the GATT instance) as a global variable
Compile and enjoy

This worked for me. I allow only a single connection on my peripheral, so I did not bother with the new tag cfg functionality of the new SDK.

I hope you find this useful.

RE: iOS compatibillity with SDK13

Tostikoning — Tue, 28 Mar 2017 07:20:17 GMT

I saw in the peripheral ble template app the following function being used: nrf_ble_gatt_on_ble_evt(&m_gatt, p_ble_evt); inside ble_evt_dispatch. This function wasn't used in the SDK12 template project. Maybe this is the issue. The GATT module seems to be implemented as a standalone module.

RE: iOS compatibillity with SDK13

Tostikoning — Mon, 27 Mar 2017 08:53:05 GMT

I do not have a sniffer trace, as I don't have a sniffer available.

If I use the peripheral uart example, services a shown in the iOS version of nRF Connect

If I use RTT i don't see any message or errors pop up.

RE: iOS compatibillity with SDK13

run_ar — Fri, 24 Mar 2017 10:16:34 GMT

Do you have a sniffer trace?

RE: iOS compatibillity with SDK13

BH — Fri, 24 Mar 2017 09:21:27 GMT

I observe the same when upgrading from SDK11 to SDK13. nRF Connect for iOS connect to device but do not display any services. nRF Connect with PCA10031 on windows works ok. No error messages from nRF52 when doing discovery. iOS device reset and BT on/off/on --> same result

RE: iOS compatibillity with SDK13

run_ar — Fri, 24 Mar 2017 08:35:29 GMT

Please check that the iDevice is actually doing service discovery. You can flush the cash by toggling bluetooth off/on, to force it to run service discovery.

RE: iOS compatibillity with SDK13

Wojtek — Thu, 23 Mar 2017 16:03:00 GMT

Check if any errors occur on nRF52 while doing discovery from iphone.