MSP BSL Encryptor GUI


Welcome to the BSL Encryptor GUI!

This document will outline a brief overview of the BSL Encryptor GUI.



What is the MSP BSL Encryptor?

The Encryptor tool will generate a securely encrypted output file from an input application in MSP .TXT format or from a key update. 
This tool is meant to be used with MSP BSLs supporting authenticated encryption, such as Crypto-Bootloader.
For more information, please visit:
SLAA682: "Secure In-Field Firmware Updates for MSP MCUs"
SLAU657: "Crypto-Bootloader (Crypto-BSL) for MSP430FR59xx/69xx Family"

 BSL GUI Overview



How to encrypt an application?

The steps required to encrypt an application are shown in the following image:  

 Open File

Steps required to encrypt an application.
1) Select the "Encrypt File" tab
2) Enable the "Generate Encrypted File" checkbox
3) Select the application file
4) Select the application version number
5) Select the encryption key and nonce by either loading them from an existing file, or specifying the values in the corresponding fields
6) Optionally, enable "Save Key to File" checkbox to save the key and nonce to a file (which can be subsequently loaded by the application)
7) Click on "Generate Output File". Pop-up windows will appear to specify the file name and folder of the key file - only if the checkbox from previous step was selected-, and the encrypted output image
8) The results and any errors will be shown by the GUI
 



How to updates the encryption keys?

The steps required to generate a secure file with updated keys are shown in the following image:  

 Open File

Steps required to generate new keys.
1) Select the "Update Keys" tab
2) Enable the "Update Key" checkbox
3) Select the new key by either loading it from an existing file, or specifying it in the corresponding fields
3.a) Select the key version. Crypto-Bootloader checks the key version and prevents older keys from being loaded to the device. The version can be loaded automatically when using an existing file
3.b) Select the key type. The key can either be: Data (used to decrypt the application image) or KEK (used to decrypt new keys). The key type is loaded automatically when using an existing file
4) Optionally, enable "Save New Key to file" checkbox to save the new key, version and type to a file (which can be subsequently loaded by the application)
5) Select the KEK (key used to encrypt keys) and its nonce by either loading it from an existing file, or specifying it in the corresponding fields
6) Optionally, enable "Save KEK to file" checkbox to save the KEK and nonce to a file (which can be subsequently loaded by the application)
7) Click on "Generate Output File". Pop-up windows will appear to specify the file name and folder of the new key and/or KEK file - only if the corresponding checkboxes are enabled- , and the output file with the new encryption keys
8) The results and any errors will be shown by the GUI.  



When to use the GUI?

The GUI should be used to generate an encrypted data file as well as to update a key file when using the MSP Crypto-Bootloader.



The GUI's Generated Output

The GUI will output a file with the encrypted application and/or updated keys file, in TXT format. This will be used in conjunction with the Crypto-Bootloader solution.


For More Information

SLAA682: "Secure In-Field Firmware Updates for MSP MCUs"
SLAU657: "Crypto-Bootloader (Crypto-BSL) for MSP430FR59xx/69xx Family"  



Trouble Opening the GUI?

The GUI requires Java Runtime Engine v1.6+ to run properly.  As a result, you may need to download the most recent version of the JRE.  The GUI is designed to automatically sense the JRE version on your machine upon being opened, and guide you to http://www.java.com if necessary.

Due to Java limitations, the GUI may give an error upon being opened if there is a semicolon or space in the pathname, or if the pathname is very long.  If the GUI fails to open, with an unclear error, please move the entire directory for the GUI into a different path that addresses these two problems.