EATT Central

This section describes the implemented profiles and services, user interactions, and testing methods for the EATT Central application.

Implemented profiles and services

The EATT Central application implements a GATT server and the following profiles and services:

  • Generic Attribute Profile

The application behaves as a GAP central node. It searches for an EATT peripheral to connect to. After connecting, it performs service discovery, initiates an EATT connection and configures indications on the peripheral for services A and B. The Central reports the received service data and the steps taken during the setup on a terminal connected to an UART port.

Parent topic:EATT Central

Supported platforms

The EATT Central application is supported on the following platforms:

  • KW45B41Z-EVK

  • K32W148-EVK

  • FRDM-MCXW71

  • KW47-EVK

  • MCXW72-EVK

  • FRDM-MCXW72

Parent topic:EATT Central

User interface

After flashing the board, the central is in Idle mode (all LEDs flashing). To start scanning, press the SCANSW button. After connecting to the peripheral, the CONNLED turns solid. The data information together with the bearer it was received on is sent over UART. To disconnect the node, hold the SCANSW button pressed for 2-3 seconds. The node then restarts scanning.

See the table below for hardware references for EATT Central.

Platform

SCANSW

CONNLED

KW45B41Z-EVK / K32W148-EVK

SW2

LED2

FRDM-MCXW71

SW2

Blue LED

KW47-EVK / MCXW72-EVK

SW2

LED2

FRDM-MCXW72

SW4

Blue LED

Parent topic:EATT Central

Usage

The application can be tested using another board flashed with the EATT Central application as described in the EATT Peripheral.

  1. Open a serial port terminal and connect it to board, in the same manner described in Testing devices. The start screen is displayed after the board is reset.

  2. To start scanning for devices, press the SCANSW button on the EATT Central board. To make it enter discoverable mode, perform the same step on the EATT Peripheral board. The host connects with the board after it sees it advertise the service A and service B UUIDs. After connecting, the central performs service discovery, indicates its EATT support to the server by writing the Client Supported Features characteristic, enables indications for services A and B, and then initiates an EATT connection with the server. See the figure below.
    (Output console on the EATT Central connected with an EATT Peripheral)

  1. After the EATT connection is complete, the console displays the received data and the bearer on which it was sent, as shown in the figure below.
    Output console on EATT Central

Parent topic:EATT Central

Parent topic:Bluetooth LE stack and demo applications