# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Protego

# Protego Release 01.05 -- Build Procedure

- 1
- 2
- 3
- 4
- 5
- 6

SECRET//NOFORN
An example of build images for a complete system with key number 3002 would be:
• 3002_P1.X.production.hex (MP Master uC image)
• 3002_P2.X.production.hex (TSS uC image)
• 3002_P3.X.production.hex (MSS uC image)
Since the Deployment Box does not contain any keys, the images for the
Deployment Box would be:
• P4.X.production.hex (Deployment Box Master uC image)
• P5.X.production.hex (Deployment Slave uC image)
For reprogramming the MP master processor, the P1_S.X (P1 Slave) and
maintenance image P2_Maintenace are created using an engineering maintenance
key located within the images. They would be:
• P1_S.X. production.hex (MP Slave uC image)
• P2_ Maintenace.production.hex (TSS reprogramming P2 uC image)
These two images are used on any Protego system, regardless of key, to
reprogram the MP master processor
Step 1: Building the Initial Protego Images (No Keys)
Open the C:\RMS_Programs directory in the command line prompt and execute the
build_protego.bat script. This will build files for each image which consist of .hex,
.elf, and .map files. These files will be located in a new time stamped _build
directory within the RMS_Programs directory.
Only P1, P2, and P3 images need keys added to their images.
File descriptions:
.hex file - Build image in Intel hex format that conveys binary information in the
ASCII text form. This file is used when loading the image on the processor.
.elf file - Executable and Linkable Format is a common standard file format for
description of executables, object code, and shared libraries.
.map file - The map file shows information relating to where objects were positioned
in memory. It
is useful for confirming if user-defined linker options were correctly processed, and
for
SECRET//NOFORN

- 1
- 2
- 3
- 4
- 5
- 6