Is there any peripheral sample for OOB legacy pairing?

Hi

Is there a specific reason you want to use "just" legacy OOB pairing? I don't think there are any examples doing exactly this by default, but if you want to make one I would suggest checking out the peer manager usage chapter here.

As for pairing with a temporary key, you might be interested in the ble_app_gls which generates a passkey used for pairing.

Best regards,

Simon

Hi
Thank you for your prompt reply.
The reason for using legacy OOB is that the central device does not support LESC.
I read the part you indecated but I still can't find out about LP_CONFIRM_R and STK generation.
Does nRF52 support ”legacy OOB” in the first place?

Best regards,
wang

Hi Wang

Yes, the nRF52 series all support legacy OOB pairing. The authentication key is generated like this in the NFC examples that uses legacy OOB for example. 

{
                // Generate Authentication OOB Key and update NDEF message content.
                uint8_t length = random_vector_generate(m_oob_auth_key.tk, BLE_GAP_SEC_KEY_LEN);
                random_vector_log(length);
                err_code = nfc_tk_group_modifier_update(&m_oob_auth_key);
                APP_ERROR_CHECK(err_code);
            }

I'm not sure what you refer to with LP_CONFIRM_R as that's not mentioned in the entire SDK as far as I can see?

Best regards,

Simon

Hi Simon,
Thank you for your courteous reply.
I recognize that the attached code only generates TK and writes the information in the NFC tag and is not used in the pairing process. Is it correct?
I wanted to know how to realize the part of the red frame.

Best regards,
wang

Hi again

The temporary key is used in the OOB legacy pairing, and the pairing itself is done by the ble_evt_handler() of both central and peripheral side of the application. in the nRF5 SDK the pairing is taken care of by the peer manager and SoftDevice.

Best regards,

Simon