| nRF5 SDK v12.0.0 |

Choose documentation: | nRF5 SDK | S130 SoftDevice API | S132 SoftDevice API | S212 SoftDevice API | S332 SoftDevice API

All Data Structures Functions Variables Typedefs Enumerations Enumerator Groups Pages
Pairing Device with Dynamic Pairing
The Gazell protocol is considered experimental for the nRF52 Series.

# Device pairing

This project requires a host running the Host pairing example as counterpart.

The application sends packets continuously. If a packet transmission fails (either times out or encryption failed), the Device will attempt pairing to a Host by sending a pairing request, consisting of an "address request" and a "Host ID" request.

If the Device is paired to a Host, pairing data will be stored in non volatile memory.

Before adding a packet to the TX queue, the contents of the GPIO Port BUTTONS is copied to the first payload byte (byte 0).

The application alternates between sending the packets encrypted through the pairing library or directly as plaintext using pipe UNENCRYPTED_DATA_PIPE.

You can find the source code and the project file of the example in the following folder: `<InstallFolder>\examples\proprietary_rf\gzll\gzp_dynamic_pairing`

# Host pairing

This project requires a device running the Device pairing example as counterpart.

The application listens for packets continuously, monitoring for pairing requests as well as normal user data.

The Gazell pairing library uses pipe 0 and pipe 1 for encrypted communication. The application will grant any request for a Host ID, thus granting pairing. Unencrypted packets can be received on pipe 2.

When DATA is received, the contents of the first payload byte of the are output on GPIO Port LEDS.

You can find the source code and the project file of the example in the following folder: `<InstallFolder>\examples\proprietary_rf\gzll\gzp_dynamic_pairing`