Step-by-step guide

This guide shows the single steps to perform an evaluation of the OPTIGA™ Authenticate NBT in the static connection handover use case. 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 perform the evaluation:

• OPTIGA™ Authenticate NBT Development Kit

• Android-based mobile phone (Android 11+)

• Windows-based development PC

Setting up the software

To set up the applications for the evaluation of the static connection handover use case, the following software is required:

• ModusToolbox™

• UART terminal (eg. Tera Term)

In addition, the board needs to be programmed. To make sure everything runs smoothly, follow the provided installation guide below in order.

ModusToolbox™

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

Note

ModusToolbox™ 3.4 was used for this guide.

Open the ModusToolbox™ Setup and under Base Packages select ModusToolbox™ Tools Package and Eclipse IDE for ModusToolbox™ and under Additional Packages select ModusToolbox™ Programming tools. Click “Next” and follow the installation prompts.

Importing the example application

The OPTIGA™ Authenticate NBT SCH Application for ModusToolbox™ is directly available as a template application in ModusToolbox™. There is no need to manually clone the Git repository to your local hard drive, since this is implicitly handled by ModusToolbox™.

1. Launch the Eclipse IDE for ModusToolbox™ (e.g., via the Windows Start Menu)

2. (optional) Create a new workspace

3. Create a new project:

   • File -> New -> ModusToolbox™ Application

   • In the Project Creator:

   • Choose Board Support Package (BSP): PSOC™ 6 BSPs -> CY8CPROTO-062S2-43439

     

     Fig. 112 ModusToolbox board selection.

   • Select Application: Peripherals -> NBT Static Connection Handover

     

     Fig. 113 ModusToolbox application selection.

Flashing the application to the board

Fig. 114 The OPTIGA™ Authenticate NBT Development Kit.

1. Attach the shield to the host MCU board, as shown above (Fig. 114)

2. Connect the board to your PC using the provided USB cable through the KitProg3 USB connector

3. In the Eclipse IDE for ModusToolbox™, select the application project in the Project Explorer. Then in the Quick Panel, scroll down, and under Launches click NBT_Static_Connection_Handover Program (KitProg3_MiniProg4) and wait for it to build.

   

   Fig. 115 Flashing the application in ModusToolbox.

Note

If you are unsure about the assembly of the hardware components, please consult the ‘Quick Start Guide’ included with the OPTIGA™ Authenticate NBT Development Kit

UART terminal

A UART terminal (or terminal emulator) needs to be installed. Go to the Tera Term website and look for the latest release under Download. It will redirect you to GitHub where you can download the executable under Assets. Follow the installation wizard’s prompts to complete the installation.

Note

Tera Term 5.3 was used for this guide.

Setting up the UART terminal

• Connect the development kit’s host MCU board to the PC via USB (KitProg3 USB connector)

• Start Tera Term, set the connection type to Serial and select the KitProg3 USB-UART

• Under Setup -> Serial port change Speed to 115200 and press New setting

Fig. 116 Connecting Tera Term to the development kit.

After powering/resetting the development kit, the embedded application starts automatically and prints its logs to the UART terminal.

Evaluation of the use case

After following the above steps, the mobile phone and the development kit are ready for evaluation.

Setup

The main configuration for this use case is the bridge tag setup (for personalization and operation). The NBT needs to be connected to a host MCU via I2C. So the shield has to be plugged into the development kit’s host MCU board.

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

The mobile phone needs to have the NBT Pass-Through mobile phone app installed.

Personalization

The personalization of the OPTIGA™ Authenticate NBT is implicitly performed during the startup of the embedded application via I2C. Thus, there are no additional steps required to personalize the NBT for the evaluation of the static connection handover use case[1].

[1]

The static connection hanover option of the Personalization via NFC mobile phone app is not feasible to personalize the provided use case.

Connection handover to Bluetooth®

This section describes the operational part of the evaluation.

Bluetooth® pairing

1. Make sure the UART terminal is up and running to see the output of the embedded application

2. Power-on/reset the development kit to (re-)start the embedded application

3. Tap the phone to the development shield until a pairing request appears[2]

4. If successful, the Bluetooth® connection is established

[2]

Make sure no other device has an active Bluetooth® connection to the OPTIGA™ Authenticate NBT. If you need to reset the connection, hold the PSOC™ board’s user button (next to the KitProg3 USB connector) for more than five seconds to erase the Bluetooth® bonding information.

Sending HID Mute/Unmute commands

To send HID Mute / Unmute commands to the mobile phone, press the user button on the development kit (see Fig. 114). The phones volume bar should appear and reflect the muting/unmuting accordingly.