Tile Node Application

This example requires one of the following SoftDevices: S112, S132, S140

Important: Before you run this example, make sure to program the SoftDevice.

The Tile Node Application is an example that implements the Tile Node profile using the hardware delivered in the nRF5 Development Kit.

The application includes one service:

• TOA_Service

When the application starts, the Board Support Package is initialized. Next, the tile service is started. The service takes care of the following:

• Configures the TileLib and enables the supported TileLib features.
• Enables and configures peripherals used by the TileLib.
• Configures the GATT Tile Service database.
• Configures and retrieves associated flash storage data.

Advertising

Advertising support for Tile Service is required for compatibility with Tile Network.

Support for Tile Service is advertised through the list of supported 16-bit UUIDs in the advertising packet.

The two following UUIDs are supported:

• 0xFEEC: Shipping Mode:
  This is the mode the Tile is in when in the packaging.
  In this mode, the Tile is ready to be activated and associated to a Tile customer account.
  For applications that do not support activating a Tile, there is usually no need to detect these Tiles.
  
• 0xFEED: Activated Mode:
  This is the mode the Tile is in for most of its active life.
  A Tile is in this mode after it has been activated and associated with a Tile Customer account.
  It then stays in this mode until its death.
  

At this point, the Tile Node can be activated using the Tile mobile application, providing that valid Tile Node credentials have been configured.

Tile Node credentials

You need valid Tile Node credentials [interim_tile_id, interim_tile_key] in order to access a Tile Network.

Without valid Tile Node credentials, your prototype will not interoperate with the Tile Network or the Tile mobile application.

Follow this link to get Tile Node credentials for your prototype.