Trust Platform Design Suite

This page provides a brief overview of the Trust Platform Design Suite for CryptoAuthentication, including installation and use.

The Trust Platform Design Suite is a combination of unique secure flows that enables you to easily prototype various security use cases. It's built around the CryptoAuthentication devices ATECC608A sub-families: Trust&GO, TrustFLEX and TrustCUSTOM, and an optimized secure provisioning flow.

To learn more, visit Microchip's web page "Trust Platform for the CryptoAuthentication™ Family".

Trust Platform Design Suite Overview

The Trust Platform Design Suite consists of a hardware prototyping kit, provisioning tools, an example use case C-based projects, and a secret exchange package generator.

  • CryptoAuth Trust Platform hardware prototyping kit comes pre-programmed with firmware that allows the provisioning of the ATECC608 device.
  • The software tools are Python-based computer programs allowing you to provision the ATECC608A device (on the CryptoAuth Trust Platform) for your specific use case.
  • The example security C-based projects allow you to use the provisioned ATECC608A devices in a working application.
  • The secret exchange package generator enables Microchip to provision your ATECC608A devices for production.

Trust Platform Design Suite Software Installation

The Trust Platform Design Suite software package requires Microsoft Windows® 10 64-bit or macOS® Mojave 10.14.6 or newer.


Choose your operating system from the tabs below:

Google Chrome is the preferred web browser. The installer provides a simple solution that installs all the requirements to run the Trust Platform Design Suite.

  • Download the installer.
  • Run the Trust Platform executable file.
  • Review and accept the end-user license agreement terms.
  • Install for "Just Me" (not all users).
  • You may need to change the install location folder. Verify the destination folder is:
    • C:\Users\<user_name>\Trust _Platform
  • Leave the checkboxes unchecked.

Once installed, there will be menu shortcuts created in two separate sections. Click on Start (Windows Laptop) and type “Trust Platform”. This will navigate to the Notebook section.

  • Anaconda3 Section: This section will consist of the following:
    • Anaconda Navigator
    • Jupyter Notebook: This will point to the default Jupyter notebook from Anaconda
    • Anaconda Prompt
  • Trust Platform Section:
    • Notebook: This points to the notebook that directly shows the installed files
    • Start_Here.html: This directly opens the design suite step by step HTML guide. It requires Google Chrome to open the same.
trust_platform1.png

Getting Started with Jupyter Notebook:

Jupyter Notebook is an application packaged along with other packages in the Anaconda Distribution. Jupyter Notebook is an open-source web application that allows the user to create documents that contain code and narrative text that can be executed in place. It provides Graphical User Interface (GUI) elements, the ability to add images, and gives it the interactive look that is absent in normal code files.

The cells of the Notebook can be used to write code or text using markdown. The code cells contain executable code and the text cells contain the explanation of the code's functionality.

Jupyter Notebook Folder Structure:

  • The Jupyter Notebook emulates the folder structure of the host computer.
  • On Windows, opening notebook from the Trust Platform section, the Notebook link will directly start Jupyter Notebook in the DesignTools folder.
  • The image below explains the folder structure of the design suite.
trust_platform5.png

On macOS, Jupyter Notebook will default to your HOME directory. You will need to navigate to trust_platform/DesignTools to reach the folder structure shown above.

  • The main folders of the Design Suite are as follows:
    • TFLXTLS Resource Generation has content related to the TrustFLEX part. It consists of the Crypto_Resource_Generator notebook that will assist you in generating the required resources to execute any use case.
    • TFLXTLS Use Cases is sub-divided into two folders called c and notebooks.
      • c consists of the C-project of each use case that can be executed using either the MPLAB® X or Atmel Studio 7 IDEs.
    • TNGTLS Manifest Generation consists of the "TNGTLS Manifest File Generation” notebook that will help you to generate a manifest file for the Trust&GO device.
    • TNGTLS Use Cases consists of the notebooks folder that contains the AWS-IoT with ECC608A TNGTLS Jupyter notebook.

Start Here HTML Page:

  • On Windows: in the Start Menu type Start Here. It will open a Google Chrome page as follows:
  • On macOS, navigate to $HOME/trust_platform/DesignTools and open Start_Here.html with either Google Chrome or Apple Safari web browsers.
trust_platform6.png
  • This collection of pages will walk you through three steps:
    1. Selection of the right trust platform device for your use case
    2. Prototype the use case
    3. Set up custom secure provisioning for TrustFLEX or TrustCUSTOM. Trust&GO devices are pre-provisioned and do not require this step.
© 2019 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.