1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2<HTML> 3<HEAD> 4<META http-equiv="Content-Type" content="text/html; charset=windows-1252"> 5<META http-equiv="Content-Style-Type" content="text/css"> 6<META name="GENERATOR" content="IBM WebSphere Studio Homepage Builder Version 6.5.0.0 for Windows"> 7<LINK rel="stylesheet" href="../CSS/revolution.css"> 8<TITLE>makemaster</TITLE> 9</HEAD> 10<BODY> 11<H1 align="left">makemaster</H1> 12 13<H2>Description</H2> 14<P> 15The <CODE>makemaster</CODE> tool creates Revolution master data (RVM) for the RVT-R Reader from a disc layout file (DLF). 16</P> 17 18<H2>System Requirements</H2> 19<ul> 20<li>NDEV software (2006/08/21 or later version) 21<li>Cygwin OpenSSL package (0.9.8b-1) 22</ul> 23<P> 24To run <CODE>makemaster</CODE>, you need to install version 2006/08/21 or later of the NDEV software. You also must install the Cygwin OpenSSL package. 25</P> 26<P><EM><STRONG>Note: OpenSSL 0.9.8b-1, which is the version of OpenSSL for which operation has been confirmed, is not currently distributed as a Cygwin package. Download OpenSSL 0.9.8b-1 from WarioWorld, the Nintendo support site.</STRONG></EM></P> 27 28<H2>Preparation</H2> 29<P> 30Before creating master data with <CODE>makemaster</CODE>, you must confirm the program operating environment and the DDF file description. 31</P> 32 33<ul> 34<li>You cannot create RVM files with a MEM2 memory size set to 128 MB. If the memory size is set to 128 MB, use the <CODE>setsmem2size</CODE> command to set it to 64 MB. 35<li>If the country code has not been specified, use <CODE>setcountrycode</CODE> to set the region for the program you are creating. 36<li>Confirm the contents of the <CODE>.ddf</CODE> file (by default, this is at <CODE>$(NDEV)/bin/NdevRun.ddf</CODE>). In particular, check that the values for <CODE>FSTuserEnd</CODE> in the <CODE>[BB2]</CODE> section are set to the following: 37<ul> 38<li>For single-layer discs: <CODE>FSTuserEnd=0x100000000</CODE> 39<li>For double-layer discs: <CODE>FSTuserEnd=0x1DC000000</CODE> 40</ul> 41Also confirm that the contents of the <CODE>[DiskID]</CODE> section have been set appropriately. 42</ul> 43<P> 44After doing this, execute the <CODE>ndrun</CODE> NDEV software. Doing so creates DLF, DSF, and RCF files that reflect the above information. 45</P> 46<P><B>Note:</B> In order to create master data, you need the DLF, DSF, and RCF files and the data used by the application (stored in the <CODE>DvdRoot</CODE> directory). Inconsistencies in these files could arise if you create the master data on some computer other than the one that was used for development.</P> 47 48<H2>Using the Library</H2> 49<P> 50There are four versions of the <CODE>makemaster</CODE> command: <CODE>makemaster</CODE>, <CODE>makemasterX</CODE>, <CODE>makemasterNF</CODE>, and <CODE>makemasterNFX</CODE>. They all take the same arguments. 51</P> 52 53<H3>Creating a Master Image</H3> 54<dl><dd><pre class="construction"> 55% makemaster[NF][X] dlf rvm [-p password] 56</pre></dd></dl> 57 58<P> 59When <CODE>makemaster </CODE> executes, it calls <CODE>ndstop</CODE> internally. Note that this ends any programs that are running. Use <CODE>makemasterX</CODE> when creating master data in an environment in which the NDEV is not connected. This version is functionally the same as <CODE>makemaster</CODE>, but has been revised so that it does not call <CODE>ndstop</CODE>. 60</P> 61 62<P> 63If you have specified <CODE>password</CODE>, a password-protected <CODE>.rvm</CODE> file will be created. Writing to a password-protected RVM file requires entry of the password specified in <CODE>makemaster</CODE>. 64</P> 65 66<P> 67When <CODE>makemaster[X]</CODE> is used to create an RVM file from a DLF file that was generated with SDK version 3.1 or later, all firmware that has been officially released up to that point will be added to the RVM file for use as update data. The firmware is installed automatically when this RVM file is run on the development hardware. 68</P> 69 70<P><B>Note:</B> Use <CODE>makemasterNF[X]</CODE> if you do not want to include the update firmware. The existence or absence of update firmware will not affect the operation of your application.</P> 71 72<P><EM><STRONG>Note: Use this master data for submission regardless of the existence or absence of update firmware.</STRONG></EM></P> 73 74<H3>Deleting Temporary Files</H3> 75<dl><dd><pre class="construction"> 76% makemaster[NF][X] dlf clean 77</pre></dd></dl> 78 79<P> 80Temporary files remain behind if <CODE>makemaster[NF][X]</CODE> is aborted in mid-operation, but these files can be deleted by using the <CODE>clean</CODE> option. 81</P> 82 83<H2>Caution</H2> 84 85<ul> 86<li> 87Temporary files are generated when <CODE>makemaster</CODE> executes. For a single-layer disc, these files are larger than 10 GB, and for a dual-layer disc, they are larger than 20 GB. Before running <CODE>makemaster</CODE>, make sure that the hard drive has around 20 GB of free space for a single-layer disc or roughly 40 GB for a dual-layer disc. 88<li> 89Before running a program on RVT-R READER, you must install the necessary firmware for that application on RVT-R READER. To install firmware on an RVT-R READER without using an RVM file that includes update firmware, you must write the firmware installer included with the SDK (<CODE>RVL/bin/swupdateXX_X_X_XX.gcm</CODE>) to an RVT-R disc and then execute. For more information on the writing method, see <CODE>makeUpdateDisc/readme.txt</CODE>. 90</ul> 91 92<P><B>Note:</B> The firmware includes encryption features. Master data that has firmware embedded as update data is therefore a service that falls under row 8 (i) (ii) of the appended table of the Foreign Exchange Order. However, because the conditions in the Ministerial Ordinance on Invisible Transactions, Article 9, paragraph 1, item 10(b) are satisfied, an Application for Permission for Service Transactions is not necessary. Import, export, and use in countries outside of Japan must comply with the laws and regulations of those countries. If there are any problems, use master data created without firmware, using <CODE>makemasterNF[X]</CODE>.</P> 93 94<H2>Location</H2> 95<P> 96<CODE>$REVOLUTION_SDK_ROOT/X86/bin/makemaster</CODE><BR> <CODE>$REVOLUTION_SDK_ROOT/X86/bin/makemasterNF</CODE><BR> <CODE>$REVOLUTION_SDK_ROOT/X86/bin/makemasterX</CODE><BR> <CODE>$REVOLUTION_SDK_ROOT/X86/bin/makemasterNFX</CODE><BR> 97</P> 98 99<H2>Revision History</H2> 100<P> 1012009/01/16 Added a description of how update firmware is handled as regards master data for submission.<br>2009/01/05 Revised terminology.<br>2008/06/11 Integrated into Revolution SDK.<br>2007/09/07 Fixed a bug with <CODE>makemasterX</CODE> that prevented update data from being included on the disc.<br>2007/09/03 Updated the document structure.<br>2007/08/07 Added an explanation in <STRONG>Cautions</STRONG> about the firmware encryption features.<br>2007/07/20 Changed <CODE>makemaster</CODE> so that firmware used by an application is now included in the disc as update data. Added <CODE>makemasterNF</CODE> and <CODE>makemasterNFX</CODE>.<br>2007/06/25 Changed the specifications for <CODE>makedevpart</CODE>. The <CODE>dev.dlf</CODE> file is now output to the current directory. Deleted <CODE>makeRVTR</CODE>. Added support for dual-layer discs.<br>2007/06/15 Added <CODE>makedevpart</CODE>.<br>2007/01/15 <CODE>makemaster</CODE> now checks the simulated memory size of MEM2. Added support for password-protected master data. Added <CODE>makemasterX</CODE>.<br>2006/10/30 Added support for Revolution SDK version 2.3 and later versions.<br>2006/09/21 Added support for Revolution SDK version 2.2 patch.<br>2006/09/08 Added support for Revolution SDK version 2.2. Not backward-compatible. Corrected the value of <CODE>FSTUserEnd</CODE> that should be be specified by the <CODE>ddf</CODE> file. (The program will not run if this value is wrong.)<br> 2006/08/30 Added support for Revolution SDK version 2.1 patch.<br> 2006/08/17 Added support for Revolution SDK version 2.1.<br> 2006/08/14 Released. 102</p> 103 104<hr><p>CONFIDENTIAL</p></body> 105</HTML>