⚠️ Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Please check the ble_app_security example of the SDK. The DA14585/586 supports the OOB mechanism, only when legacy pairing is used. By default, it is enables – the CFG_ENABLE_SMP_SECURE in da1458x_config_advanced.h is enabled. neither Android nor iOS support the OOB mechanism for Bluetooth pairing. The app_on_tk_exch( ) will be called if a temporary key needs to be used for the pairing procedure (OOB, PassKey Entry, Numeric Comparison). In the example project, user_app_on_tk_exch(), depending on the pairing method. In case of OOB, local device will assign to OOB data the value defined in APP_SECURITY_OOB_TK_VAL
Hi MADHUSF,
Please check the ble_app_security example of the SDK. The DA14585/586 supports the OOB mechanism, only when legacy pairing is used. By default, it is enables – the CFG_ENABLE_SMP_SECURE in da1458x_config_advanced.h is enabled. neither Android nor iOS support the OOB mechanism for Bluetooth pairing. The app_on_tk_exch( ) will be called if a temporary key needs to be used for the pairing procedure (OOB, PassKey Entry, Numeric Comparison). In the example project, user_app_on_tk_exch(), depending on the pairing method. In case of OOB, local device will assign to OOB data the value defined in APP_SECURITY_OOB_TK_VAL
Thanks, PM_Dialog