Cannot bind outside of IoT Toolbox app

[cnew01]

I am using the KW45B41Z-EVK and the associated examples. I am trying to adapt the examples so that I can use them with a custom app. I have been working with the examples provided in SDK 24.12.0 and I cannot bind to the board outside of the IoT toolbox app with the default wireless UART example. I've been trying to use a 3rd party app to connect and debug (nRF Connect). Is this expected behavior? Is there a setting that locks binding to the IoT Toolbox app?
I have tried changing the following settings in app_preinclude.h and still encounter the same issue. 

/*! Enable/disable use of bonding capability */

#define gAppUseBonding_d                1

/*! Enable/disable use of pairing procedure */

#define gAppUsePairing_d                1

/*! Enable/disable use of privacy */

#define gAppUsePrivacy_d                0

#define gPasskeyValue_c                 999999

#define gWuart_AutoStart_c              0

gAppUsePrivacy_d being set to 1 keeps the same issues, and I can't even connect in the 3rd party app when gAppUseBonding_d and gAppUsePairing_d are set to 0.

[cnew01]

I do not understand. The issue is I am not able to bind and be connected through a Bluetooth Low Energy Scanning App, which shouldn't care about the BLE profile.

[sofiaurueta · Accepted solution]

Hello,

The Wireless UART example is implementing a custom profile, it implements a custom writable ASCII Char characteristic.

The example is looking for the same service in the central device, please look at the function BleApp_StateMachineHandler, case mAppExchangeMtu_c:,

                /* Start Service Discovery*/

                (void)BleServDisc_FindService(peerDeviceId,

                        gBleUuidType128_c,

                        temp.pUuidObj);

The example is looking for the same UUID, and that could be the reason of the disconnection. The NXP APP (IoT toolbox) has registered this UUID.

You could try to add the same UUID in your application or comment the Gap_Disconnect API.

Regards,

Ana Sofia.

[sofiaurueta]

Hello,

Hope you are doing well.

The Wireless UART example application implements both the GATT client and server for the custom Wireless UART profile and services. As it is a custom profile, your application has to implement it.

In this case, your application does not know the profile, and the disconnection occurs. (in code, the Wireless UART example disconnects if the Service Discovery was not found).

When working with application, both sides need to have the complete support of their profile, so if the mobile does not interact as expected, the board will not respond properly.

For more information about Wireless UART, please refer to section 5.12 "Wireless UART" of the Bluetooth Low Energy Demo Applications User's Guide

Best Regards,

Ana Sofia.