| Copyright © 2005, 2006 ARM Limited. All rights reserved. | ARM DUI 0284C |
| Non-Confidential | |
 PDF version | |
| Home > RealView Debugger Commands > Alphabetical command reference > VERIFYFILE |
| |||
| Home > RealView Debugger Commands > Alphabetical command reference > VERIFYFILE | |||
The VERIFYFILE command compares the contents of a specified file with the contents of target memory.
VERIFYFILE [,{OBJ|raw|rawb|rawhw|ascii[,opts]}] filename [=address/offset]
where:
OBJThe file is an executable file in the standard target
format. RVDK can verify files in either the ELF format or an ELF
proprietary file format called ARM Toolkit Proprietary
ELF (ATPE). The proprietary file format for each version
of the RVDK is restricted to the permitted device. This is referred
to as the ATPE_Custom.
There are no opts
rawWrite the file as raw data, one word per word of memory.
There are no opts
You must specify an address with this qualifier.
rawbWrite the file as raw data, one byte per byte of memory.
There are no opts
You must specify an address with this qualifier.
rawhwWrite the file as raw data, one halfword per halfword of memory.
There are no opts
You must specify an address with this qualifier.
asciiThe
file is a stream of ASCII digits separated by whitespace. The interpretation
of the digits is specified by other qualifiers (see the opts
[start]The start address.
[start,end]The start address, a comma, and the end address.
[start,+len]The start address, a comma, and the length.
[start,end,size]The start address, a comma, the end address, a comma,
and a character indicating the size of each value, where b is
8 bits, h is 16 bits and l is
32 bits.
If the size of the items in the file is not specified, the
debugger determines the size by examining the number of white-space
separated significant digits in the first data value. For example,
if the first data value was 0x00A0, the size
is set to 16-bits.
optsOptional qualifiers available for use with the ascii qualifier:
byteThe file is a stream of 8-bit values that are written to target memory without extra interpretation.
halfThe file is a stream of 16-bit values.
longThe file is a stream of 32-bit values.
guiYou are prompted to enter the file type with a dialog.
This qualifier has no effect in the headless debugger.
filenameSpecifies the name of the file to be read.
You can include one of more environment variables in the filename.
For example, if MYPATH defines the location C:\Myimages,
you can specify:
verifyfile,raw,byte "$MYPATH\\myimage.axf" 0x8000...0x8100
address/offsetSpecifies the starting address in target memory for the comparison. If the file being read contains this information, you can adjust it by specifying an offset.
The VERIFYFILE command compares the contents of a specified file with the contents of target memory.
Data might be stored in a file in a variety of formats. You can specify the format by specifying the file type. The command then converts the data read from the file before performing the comparison.
The types of file and file formats supported depend on the target processor and any loaded DLLs. The type of memory assumed depends on the target processor. For example, ARM processors have byte addressable memory.
The following example shows how to use VERIFYFILE:
verifyfile,ascii,byte
"c:\images\rom.dat" =0x8000Verify
that the ROM image file in rom.dat matches
target memory starting at location 0x8000.
| Copyright © 2005, 2006 ARM Limited. All rights reserved. | ARM DUI 0284C |
| Non-Confidential | |
| PDF version | |
| Home > RealView Debugger Commands > Alphabetical command reference > VERIFYFILE |