Vault 7: Projects
This publication series is about specific projects related to the Vault 7 main publication.
Demo Operation
This demo uses the selected hardware platform as an drive on the computer using the internal flash of the device as the
drive storage media. Connect the hardware platform to a computer through a USB cable.
The device should appear as a new drive on the computer named “Drive Name”. The volume label or file information can be
changed in the Files.c file located in the project directory.
1.6.11.1 Troubleshooting
Issue 1
: The device appears correctly in the device manager, but no new drive letters appear on a Windows® operating
system based machine.
Solution
: See Microsoft knowledge base article 297694: http://support.microsoft.com/kb/297694
If there is a drive letter conflict (ex: because a network drive has been mapped to a letter low in the alphabet), on some
operating systems the newly attached USB drive may not appear. If this occurs, either obtain the hotfix from Microsoft, or
remap the conflicting mapped network drive to a letter at the end of the alphabet (ex: Z:).
Issue 2
: The device enumerates correctly and I can access the new drive. Even though the drive is not full yet, when I try to
write to the drive, I get an error message something like, “Cannot copy (some name): The directory or file cannot be created.”
Solution
: In order to copy new files onto the drive volume, both the file contents themselves must be copied to the drive, and
the FAT table must also be updated in order to accommodate the new file name and path. Even if the drive has plenty of free
space available, the FAT table may have reached its limit. In order to keep the default demos small, the FAT table is
configured to be only 512 bytes long. This is not very large, and can easily be exceeded, especially if the files on the drive
have long file names. In order to use the remaining space available on the drive, it is recommended to keep the individual file
names as short as possible to minimize their size in the FAT table. Alternatively, the firmware can be modified so that the
FAT table is larger, and therefore able to accommodate more file name and path characters.
Issue 3
: When I try to format the drive, I get an error message and the drive does not get formatted properly.
Solution
: By default, common Windows based operating systems will try to place a large FAT table on the newly formatted
disk (larger than the default 512 bytes of the demo firmware). If the FAT table is larger than the total drive space, the drive
cannot be formatted. In order to successfully format the drive, an alternative method of formatting will be needed that places
a smaller FAT table on the drive. For example, the drive can be effectively reformatted by reprogramming the microcontroller
with the original HEX file. Alternatively, if the firmware is modified to increase the total drive space, the Windows operating
system managed FAT table may be able to fit. Unfortunately, this will shrink the effective drive size, making less of it
available for actual file data.
Issue 4
: When I format the drive, the drive size shrinks.
Solution
: See the solution to issue #3 above.
1.6.12 Device - Mass Storage - SD Card Reader
This demo shows how to implement a simple SD card reader
Description
Supported Demo Boards
The matrix of which demos are supported on a specific board can be found in the Release Notes demo board support
section. Verify that the board you wish to use will work with this demo. This table also describes some of the limitations that
1.6 Demos MLA - USB Library Help Device - Mass Storage - SD Card Reader
279
Protego_Release_01_05-Related-OEM-Documentation-MLA_v2013_12_20-help_mla_usb.pdf