# Vault 7: Projects

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

### Cherry Blossom

# SRI-SLO-FF-2012-177-CherryBlossom_UsersManual_CDRL-12_SLO-FF-2012-171

- 1
- 2
…
- 29
- 30
- 31
- 32
- 33
…
- 174
- 175

SECRET//20350112
6.5 (U) Firmware Types
(S) CB produces the following different firmware “products”:
• Production Test Firmware – firmware suitable for offsite testing (FAT) and
installation in sponsor internal test site. Firmware is typically configured for short
initial beacon and includes a shell/telnet daemon.
• Production Release Firmware – firmware suitable for fielding/operation.
Firmware typically configured for longer initial beacon, no debug info, and no
shell/telnet daemon.
• Wireless Upgrade Test Package – Wireless Upgrade Package with firmware
suitable for offsite testing (FAT) and installation in sponsor internal test site.
Firmware typically configured for short initial beacon and shell/telnet daemon.
• Wireless Upgrade Release Package – Wireless Upgrade Package with firmware
suitable for fielding. Firmware typically configured for longer initial beacon, no
debug info, and no shell/telnet daemon.
6.6 (U) Requesting a Production Release Firmware/Wireless Upgrade
Package
(S) The typical process for getting a production release firmware (i.e., for use in an actual
operation), is to specify the make, model, hardware version, and firmware version of a
device that has undergone FAT (see 6.2, or for new device support, see 6.1). The next
step is to specify a number of parameters that must be built into the firmware. These
parameters are enumerated in section 15.5.2. The CB team then configures these
parameters into the Image Formation tool (see 15.5) and builds a production release
firmware (or Wireless Upgrade Package) for the device of interest. The Image Formation
tool is completely automated, and so a firmware build takes about a minute depending on
hardware. Once the firmware/upgrade package is built, it is tested for successful wireless
upgrade (using a device that is not connected to the internet), and if the initial beacon is
not excessively long, tested for initial beacon at the proper time and to the proper beacon
address. The production release firmware is then delivered to the sponsor on a CD with
the following:
• Production Release Firmware/Wireless Upgrade Release Package
• Configuration file used to build the firmware (“flytrap.config”)
• Firmware Upgrade Procedures document
• md5sum’s
31
SECRET//20350112

- 1
- 2
…
- 29
- 30
- 31
- 32
- 33
…
- 174
- 175