Step-by-step guide

This guide shows the single steps to install the NBT Personalization mobile phone app which is utilizeded by other use cases. The scope is the evaluation of the OPTIGA™ Authenticate NBT Development Kit with an Android-based mobile phone.

Prerequisites

The following components have to be available to install and use the app:

• OPTIGA™ Authenticate NBT Development Kit

• Android-based mobile phone (Android 11+)

• Windows-based development PC

Setting up the mobile phone app

Download and install Android Studio from the official website. Follow the installation wizard’s prompts to complete the installation.

Note

Android Studio Narwhal 3 Feature Drop | 2025.1.3 was used for this guide.

Importing the example app

1. Launch Android Studio (e.g., via the Windows Start Menu)

2. Select Clone Repository [1] in the top right corner. In the new window, include the following information:

   • Version control: Git

   • URL: https://github.com/Infineon/optiga-nbt-example-perso-android.git

   • Directory: local target directory [*]

   

   Fig. 127 Android Studio cloning the repository.

3. Clone the repository and select Trust project

[1]

Older versions use Get from VCS (Get from Version Control). If you have a later version than the one used for this guide, please be aware that the label might have changed.

[*]

You can keep the standard directory path it generates

Building and installing the app

1. Connect your Android mobile phone to your PC via USB [2]

   • Once your phone is connected, it should prompt you to allow USB debugging (Developer options enabled). This has to be enabled!

     

     Fig. 128 Pop-up on the phone to allow USB debugging.

2. In Android Studio at the top you should see your mobile phone. Next to it, select Run 'app' to build the app. It is now installed on the physical device and you can run it.

   

   Fig. 129 Android Studio running the application.

[2]

Note that any type of USB port can be used (eg. USB-A, USB-B, or USB-C)

Note

Alternatively, the .APK of the app can also be manually build, transferred to the mobile phone and installed there. In Android Studio the .APK can be built via Build -> Build App Bundle(s) / APK(s) -> Build APK(s).

Evaluation of the use case

After following the above steps, the mobile phone app can be used to personalize the OPTIGA™ Authenticate NBT for multiple predefined use cases.

Setup

The main configuration for this use case is the NFC-only tag setup (for personalization and operation). Even though the NBT can be connected to a host MCU via I2C, this is not required for the operation of this use case. So the shield can be used standalone (not plugged into the host MCU board).

Fig. 130 Hardware setup for evaluation of this use case.

The mobile phone needs the NBT Personalization mobile phone app installed.

Personalization

This section describes the operational part of the evaluation.

Reset to pseudo default state

The NBT Personalization mobile phone app can be used to reset the device to pseudo default state before performing the use-case-specific personalization.

During this step, the NDEF file’s content is cleared and the file access policies are set to the default values. The content of the proprietary files is not touched.

Personalize certain use case

To perform personalization of the OPTIGA™ Authenticate NBT via NFC make sure that NFC is enabled on the Android device and follow the steps below:

• Launch the NBT Personalization mobile phone app

• Tap the mobile phone to the OPTIGA™ Authenticate NBT

• Select the OPTIGA™ Authenticate NBT use case to be personalized (see Fig. 131)

• Tap the mobile phone again to the OPTIGA™ Authenticate NBT to run the personalization.

  

  Fig. 131 Personalization options for the OPTIGA™ Authenticate NBT.

The mobile app can be used to personalize the device with example configurations for the following use cases:

• Asynchronous data transfer

• Brand protection

• Pass-through

• Static connection handover

For the provided use cases including embedded applications, the personalization is implicitly performed via I2C during the startup of the application. In that case, dedicated personalization via the NBT Personalization mobile phone app is not required.