?? dfusign.html
字號:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- Copyright 2001, 2002 Cambridge Silicon Radio Limited -->
<html>
<head>
<title>CSR DFU Tools - dfusign</title>
</head>
<body bgcolor="white">
<h1 align=center>CSR DFU Tools - dfusign</h1>
The <code>dfusign</code> tool is used to sign <a href="#ss" title="Signing Stack Software">stack software</a>, <a href="#as" title="Signing Application Software">application software</a>, <a href="#sps" title="Signing Protected Stack Persistent Store">protected stack persistent store</a>, <a href="#aps" title="Signing Protected Application Persistent Store">protected application persistent store</a> or <a href="#fs" title="Signing File System">file system</a>. See the individual descriptions below for details.
<h2><a name="ss">Signing Stack Software</a></h2>
<dl>
<dt>Usage</dt>
<dd>
<code><b>dfusign</b> [-v] [-o <i>OUTPUTBASENAME</i>] -s <i>STACKPROGFILE</i> [-d <i>STACKDATAFILE</i>] [-ks <i>STACKKEYFILE</i>]</code>
</dd>
<dt>Parameters</dt>
<dd>
<dl>
<dt><code>-v</code></dt>
<dd>Run in verbose mode, displaying detailed information about the actions performed.</dd>
<dt><code>-o <i>OUTPUTBASENAME</i></code></dt>
<dd>Base name for the output files, to which <code>.xpv</code> and <code>.xdv</code> extensions will be added. If this parameter is omitted then the output files overwrite the source files; use this option with care.</dd>
<dt><code>-s <i>STACKPROGFILE</i></code></dt>
<dd>Name of the <code>.xpv</code> file containing the stack software's program code.</dd>
<dt><code>-d <i>STACKDATAFILE</i></code></dt>
<dd>Name of the <code>.xdv</code> file containing the stack software's constants. If not specified then the name is constructed by replacing the <code>.xpv</code> extension of the <code><i>STACKPROGFILE</i></code> with <code>.xdv</code>.</dd>
<dt><code>-ks <i>STACKKEYFILE</i></code></dt>
<dd>Name of the file containing the private key to use for signing the stack software.</dd>
</dl>
</dd>
<dt>Remarks</dt>
<dd>
Sign a pair of stack software <code>.xpv</code> and <code>.xdv</code> files using the private stack key. The resulting files are suitable for downloading to devices whose boot loader either contains the corresponding public key, or which does not contain any key.
<p>
If the <code>-ks</code> parameter is omitted (no key file specified) then no signing is performed; the only action is to update the firmware header, checksum and CRC. This usage is intended for internal CSR use only.
</dd>
<dt>Example</dt>
<dd>
<code>dfusign -v -o stack_signed -s stack_unsigned.xpv -ks my_stack_key.private.key</code>
</dd>
</dl>
<h2><a name="as">Signing Application Software</a></h2>
<dl>
<dt>Usage</dt>
<dd>
<code><b>dfusign</b> [-v] [-o <i>OUTPUTBASENAME</i>] -a <i>APPFILE</i> -ka <i>APPKEYFILE</i></code><br>
</dd>
<dt>Parameters</dt>
<dd>
<dl>
<dt><code>-v</code></dt>
<dd>Run in verbose mode, displaying detailed information about the actions performed.</dd>
<dt><code>-o <i>OUTPUTBASENAME</i></code></dt>
<dd>Base name for the output file, to which a <code>.app</code> extensions will be added. If this parameter is omitted then the output file overwrites the source file; use this option with care.</dd>
<dt><code>-a <i>APPFILE</i></code></dt>
<dd>Name of the <code>.app</code> file containing the application software.</dd>
<dt><code>-ka <i>APPKEYFILE</i></code></dt>
<dd>Name of the file containing the private key to use for signing the application software.</dd>
</dl>
</dd>
<dt>Remarks</dt>
<dd>
Sign an application <code>.app</code> file using the private application key. The resulting file is suitable for downloading to devices whose persistent store either contains the corresponding public key, or which do not contain any key.
<p>
This should normally be performed on a file that has not been signed already. If a previously signed file is used then the old signature is left and a new one appended, resulting in a larger file. This could easily result in a file that is too large to download.
</dd>
<dt>Example</dt>
<dd>
<code>dfusign -v -o app_signed -a app_unsigned.app -ka my_app_key.private.key</code>
</dd>
</dl>
<h2><a name="sps">Signing Protected Stack Persistent Store</a></h2>
<dl>
<dt>Usage</dt>
<dd>
<code><b>dfusign</b> [-v] [-o <i>OUTPUTBASENAME</i>] -ps <i>STACKPSFILE</i> -ks <i>STACKKEYFILE</i></code><br>
</dd>
<dt>Parameters</dt>
<dd>
<dl>
<dt><code>-v</code></dt>
<dd>Run in verbose mode, displaying detailed information about the actions performed.</dd>
<dt><code>-o <i>OUTPUTBASENAME</i></code></dt>
<dd>Base name for the output file, to which a <code>.stack.psr</code> extension will be added. If this parameter is omitted then the output file overwrites the source file; use this option with care.</dd>
<dt><code>-ps <i>STACKPSFILE</i></code></dt>
<dd>Name of the <code>.psr</code> file containing the stack software's persistent store data.</dd>
<dt><code>-ks <i>STACKKEYFILE</i></code></dt>
<dd>Name of the file containing the private key to use for signing the protected stack persistent store.</dd>
</dl>
</dd>
<dt>Remarks</dt>
<dd>
Sign a stack persistent store <code>.psr</code> file using the private stack key. The resulting file is suitable for downloading to devices whose boot loader either contains the corresponding public key, or which does not contain any key.
<p>
This can be performed on files that have been signed previously; the existing signature is replaced.
<p>
If the file is to contain the public application key, then that should be added using <a href="dfukeyinsert.html" title="dfukeyinsert"><code>dfukeyinsert</code></a> prior to being signed.
</dd>
<dt>Example</dt>
<dd>
<code>dfusign -v -o stack_ps_signed -ps stack_ps_unsigned.psr -ks my_stack_key.private.key</code>
</dd>
</dl>
<h2><a name="aps">Signing Protected Application Persistent Store</a></h2>
<dl>
<dt>Usage</dt>
<dd>
<code><b>dfusign</b> [-v] [-o <i>OUTPUTBASENAME</i>] -pa <i>APPPSFILE</i> -ka <i>APPKEYFILE</i></code>
</dd>
<dt>Parameters</dt>
<dd>
<dl>
<dt><code>-v</code></dt>
<dd>Run in verbose mode, displaying detailed information about the actions performed.</dd>
<dt><code>-o <i>OUTPUTBASENAME</i></code></dt>
<dd>Base name for the output file, to which a <code>.app.psr</code> extension will be added. If this parameter is omitted then the output file overwrites the source file; use this option with care.</dd>
<dt><code>-pa <i>APPPSFILE</i></code></dt>
<dd>Name of the <code>.psr</code> file containing the application software's persistent store data.</dd>
<dt><code>-ka <i>APPKEYFILE</i></code></dt>
<dd>Name of the file containing the private key to use for signing the protected application persistent store.</dd>
</dl>
</dd>
<dt>Remarks</dt>
<dd>
Sign an application persistent store <code>.psr</code> file using the private application key. The resulting file is suitable for downloading to devices whose persistent store either contains the corresponding public key, or which do not contain any key.
<p>
This can be performed on files that have been signed previously; the existing signature is replaced.
</dd>
<dt>Example</dt>
<dd>
<code>dfusign -v -o app_ps_signed -pa app_ps_unsigned.psr -ka my_app_key.private.key</code>
</dd>
</dl>
<h2><a name="fs">Signing File System</a></h2>
<dl>
<dt>Usage</dt>
<dd>
<code><b>dfusign</b> [-v] [-o <i>OUTPUTBASENAME</i>] -h <i>FILESYSTEM</i> -ka <i>APPKEYFILE</i></code>
</dd>
<dt>Parameters</dt>
<dd>
<dl>
<dt><code>-v</code></dt>
<dd>Run in verbose mode, displaying detailed information about the actions performed.</dd>
<dt><code>-o <i>OUTPUTBASENAME</i></code></dt>
<dd>Base name for the output file, to which a <code>.fs</code> extension will be added. If this parameter is omitted then the output file overwrites the source file; use this option with care.</dd>
<dt><code>-h <i>FILESYSTEM</i></code></dt>
<dd>Name of the <code>.fs</code> file containing the file system.</dd>
<dt><code>-ka <i>APPKEYFILE</i></code></dt>
<dd>Name of the file containing the private key to use for signing the file system.</dd>
</dl>
</dd>
<dt>Remarks</dt>
<dd>
Sign a file system <code>.fs</code> file using the private application key. The resulting file is suitable for downloading to devices whose persistent store either contains the corresponding public key, or which do not contain any key.
<p>
This can be performed on files that have been signed previously; the existing signature is replaced.
</dd>
<dt>Example</dt>
<dd>
<code>dfusign -v -o file_sys_signed -h file_sys_unsigned.fs -ka my_app_key.private.key</code>
</dd>
</dl>
<p align=right><font size="-1">© 2001, 2002, 2003 <a href="http://www.csr.com" title="CSR" target="_blank">CSR</a></font></p>
</body>
</html>
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -