Building the DUB Tools
The DUB tools are Mergebin.exe, Slicebin.exe, Makekey.exe, MKSigs.exe, and Addsigs.exe. The tools are in %_WINCEROOT%\Public\DUB\Oak\Tools. Before building any of the DUB tools, start the DUB shell and then type the following parameters on the build computer:
SET CVINC=D:\Program Files\DevStudio\VC\Include
SET CVLIBS=D:\Program Files\DevStudio\VC\Lib
A project file and the source code for Mergebin.exe are in %_WINCEROOT%\Public\DUB\Oak\Tools\Mergebin. Mergebin.exe is created in %_WINCEROOT%\Public\DUB\Oak\Tools\Mergebin\Release. The compiled binary version for Mergebin.exe is in %_WINCEROOT%\Public\DUB\Oak\Tools\Bin.
The following table shows the Mergebin.exe command-line options.
Option | Description |
---|---|
-v | Specifies verbose output. |
-b Dubboot.bin | Specifies the boot file. |
-i Dub.bin | Specifies the DUB OS image. |
-o Merge.bin | Specifies the output .bin file. Mergebin.exe creates this file, if necessary. |
-l StartAddress | Specifies the Merge.bin compressed DUB OS address in flash memory and ROM. For example:
-l 0x80020000 See Oeminfo.c. |
A project file and the source code for Slicebin.exe are in %_WINCEROOT%\Public\DUB\Oak\Tools\Slicebin. Slicebin.exe is created in %_WINCEROOT%\Public\DUB\Oak\Tools\Slicebin\Release. The compiled binary file for Slicebin.exe is in %_WINCEROOT%\Public\DUB\Oak\Tools\Bin.
The following table shows the Slicebin.exe command-line options.
Option | Description |
---|---|
-p OutputPath | Specifies the directory for the output slice files. Slicebin.exe creates the directory, if necessary. |
-f FileSize | Specifies the maximum size, in kilobytes, for the slice files. |
-u UserFile | Specifies the name of a file to download optional user data. |
-v | Specifies verbose output. |
-x DUBPrefix | Specifies the prefix to use for slice files; the default is FILE_. |
A project file and the source code for Makekey.exe are in %_WINCEROOT%\Public\DUB\Oak\Tools\Makekey. The Makekey.exe file is created in %_WINCEROOT%\Public\DUB\Oak\Tools\Makekey\Release. The compiled binary file for Makekey.exe is in %_WINCEROOT%\Public\DUB\Oak\Tools\Bin.
A project file and the source code for MKSigs.exe are in %_WINCEROOT%\Public\DUB\Oak\Tools\MKSigs. MKSigs.exe is created in %_WINCEROOT%\Public\DUB\Oak\Tools\MKSigs\Release. The compiled binary file for MKSigs.exe is in %_WINCEROOT%\Public\DUB\Oak\Tools\Bin.
The following table shows the MKSigs.exe command-line options.
Option | Description |
---|---|
FileSpec | Provides the file specification of the files to sign. |
DescriptorString | Provides a descriptive string that is used by the encoder and decoder to validate data. If spaces are defined in the string, the string must be surrounded by double quotation marks. The following code examples show how to enter a descriptive string.
|
A project file and the source code for Addsigs.exe code are in %_WINCEROOT%\Public\DUB\Oak\Tools\AddSigs. Addsigs.exe is created in %_WINCEROOT%\Public\DUB\Oak\Tools\Addsigs\Release. The compiled binary file for Addsigs.exe is in %_WINCEROOT%\Public\DUB\Oak\Tools\Bin.
The following table shows the Addsigs.exe command-line options.
Option | Description |
---|---|
-i InputPath | Specifies the directories for the input manifest and signature data files. |
-o OutputPath | Specifies the directory for the output manifest file; Addsigs.exe creates this directory, if necessary. The default is the current directory. |
-x SignaturePrefix | Specifies a signature file prefix, which can be up to four characters. The default is Sigs. |
-e SignatureExtension | Specifies a signature file extension, which can be up to three characters. The default is .sig. |