Name
VolInfo – Displays the contents of a firmware volume
Synopsis
VolInfo [-x <XrefFile>] [--offset <Offset>] <InputFile>
Description
VolInfo displays the contents of a firmware volume residing in a file for informational purposes.
Options
If no options are specified, tool prints usage.
-x xref, --xref xref
xref is the path to a file-guid cross reference file.  This file is used to provide human readable names to the GUIDs found in the firmware volume.
--offset offset
offset is the offset within the file to start processing the firmware volume. This is used if the specified disk file is a firmware device image which generally contains multiple firmware volumes. The offset can be specified as a decimal number or a hexadecimal number  (for example, 0x1ffe).  If a 'k' suffix is attached to the number, then the number will be multiplied by 1024 (0x400) to turn the number into kilobytes.
Status codes returned
STATUS_SUCCESS 	0	The action was completed as requested.	
STATUS_ERROR 		2	The action failed.	

Examples
Assume that $(WORKSPACE) is /home/joeuser/src/edk2 and the firmware volumes have been built into Build/EdkUnix/DEBUG_UNIXGCC/FV:
~/src/edk2$ VolInfo  Build/EdkUnix/DEBUG_UNIXGCC/FV/FVMAIN.fv
Assuming that a firmware device image had been built and that the firmware volume of interest resided at byte offset 65536 of that file, then the following command would show that firmware volume:
~/src/edk2$ VolInfo  --offset 65536 path/to/FV/EDKUNIX.fd
Or, equivalently,
~/src/edk2$ VolInfo  --offset 64k path/to/FV/EDKUNIX.fd
Or, equivalently,
~/src/edk2$ VolInfo  --offset 0x10000 path/to/FV/EDKUNIX.fd
GuidedSectionTools.txt 
This (optional) file is built as part of the edk2 build process. It is generated in the FV directory alongside the firmware volume file. The VolInfo utility looks for this file alongside the input firmware volume file, and if found it will read its contents to define tools used for extracting GUID defined firmware volume sections.
Each line contains three tokens separated by whitespace. The three tokens are (in order): 1) the GUID associated with the tool, 2) a name for the tool, and 3) the path to the tool executable. An example of a possible line from the file:
a31280ad-481e-41b6-95e8-127f4c984779 TIANO /path/to/TianoCompress
Files 
GuidedSectionTools.txt
Bugs 
No known issues
Report bugs to edk2-buildtools-devel@lists.sourceforge.net
Files 
GuidedSectionTools.txt
License
Copyright (c) 1999 - 2011, Intel Corporation. All rights reserved.

This program and the accompanying materials are licensed and made available under the terms andconditions of the BSD License which accompanies this distribution.  The full text of the license may befound at: http://opensource.org/licenses/bsd-license.php

THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.