1<html> 2<head> 3<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 4<meta http-equiv="Content-Style-Type" content="text/css"> 5<title>ctr_makerom</title> 6<style type="text/css"> 7<!-- 8body { 9/* 10 font-size : 10pt; 11*/ 12 font-weight : normal; 13 color : #000000; 14 margin : 8px; 15} 16 17div { 18 width : 98%; 19 white-space : nowrap; 20} 21 22div.title { 23 text-align : left; 24 font-weight : bold; 25/* 26 font-size : 16pt; 27*/ 28 font-size : 150%; 29 color : #202020; 30 border-style : double; 31 border-width : 8px; 32 /* タイトルを囲む枠線の色を指定 */ 33 border-color : #FF6600; 34 35 /* RVLプラットフォーム系列 */ 36/* 37 border-color : #34beed; 38*/ 39 40 /* TWLプラットフォーム系列 */ 41/* 42 border-color : #ff458f; 43*/ 44 45 margin : 4px; 46 padding : 4px; 47} 48H1 { 49 font-size : 150%; 50 font-family : Arial; 51 border-bottom-width : 5px; 52 border-bottom-style : solid; 53 border-bottom-color : #FF6600; 54 padding-bottom : 1px; 55 margin-bottom : 20px; 56 letter-spacing : normal; 57 font-weight : bold; 58} 59 60h2 { 61 font-weight : bold; 62/* 63 font-size : 16pt; 64*/ 65 font-size : 150%; 66 border-style : none none solid double; 67 border-width : 0px 0px 2px 8px; 68 /* 見出しの線の色を指定 */ 69 border-color : #FF6600; 70 71 /* RVLプラットフォーム系列 */ 72/* 73 border-color : #34beed; 74*/ 75 76 /* TWLプラットフォーム系列 */ 77/* 78 border-color : #ff458f; 79*/ 80 81 margin-left : 2px; 82 padding-left : 4px; 83} 84CODE { 85 font-family : "Courier New", monospace; 86 position : normal; 87 left : 12px; 88 font-size : 10pt; 89} 90table { 91 margin-top : 2pt; 92 margin-bottom : 2pt; 93 margin-left : 0pt; 94 margin-right : 0pt; 95 padding-left : 0pt; 96 padding-right : 0pt; 97 position : relative; 98 left : 12px; 99 font-family : Arial; 100 font-size : 10pt; 101 border-style : none none none none; 102} 103td,th { 104 padding : 2pt; 105 border-width : 2pt; 106 border-style : none none none none; 107 font-style : normal; 108 text-align : left; 109} 110td { 111 background : #e8f4f4; 112 font-weight : normal; 113} 114th { 115 background : #c0d8d8; 116 font-weight : bold; 117} 118 119p { 120 margin-left : 4px; 121} 122p.code { 123 font-family : "Courier New", monospace; 124 position : normal; 125 left : 12px; 126 font-size : 10pt; 127 background : #e8f4f4; 128} 129 130--> 131</style> 132 133</head> 134<body> 135<a name="top"></a> <!-- ※注意事項 --> <!-- ・（任意）となっているものは、記載が無くても問題ありません。 --> <!-- ・各項目についてる（必須）や（任意）は、作成後に削除してください。 --> <!-- ・各項目内の書き方は、パッケージごとに自由で問題ありませんが、同じパッケージ内で違いがでないようにしてください。 --> <!-- ・タグはすべて小文字、終了タグを持たないものは「/>」で閉じてください。--> <!-- ・HTMLコードのインデントは、各種社内コード規約と同様にスペース4文字か4文字幅のタブになるようにしてください--> 136 137<h1>ctr_makerom</h1> 138 139<h1>Table of Contents</h1> 140<ol> 141<li><a href="#intro">Introduction</a></li> 142<li><a href="#usage">How to Use</a></li> 143<li><a href="#rsf">RSF File</a></li> 144<li><a href="#desc">DESC File</a></li> 145<li><a href="#titleid">Game Software Prototype Code</a></li> 146<li><a href="#omake">Variables Defined Within OMakefiles</a></li> 147<li><a href="#history">Revision History</a></li> 148</ol> 149 150 151 152<h2><a name="intro">Introduction</a></h2> 153<P>This <CODE>ctr_makerom</CODE> tool is for creating CCI (CTR Card Image) files. CCI files are created based on the content in RSF files.</P> 154 155<P>If a NAND application is specified as the output format, a CXI (CTR eXecutable Image) file is generated as the output. The requirements for CXI file generation are the same as for CCI files.</P> 156 157<h2><a name="usage">How to Use</a></h2> 158<h3>What's Required</h3> 159<p>You will need the following to create a CCI file:</p> 160<ul> 161<li> ELF file that was created using "RVCT for Nintendo" 162<li> RSF File 163<li> DESC File 164</ul> 165 166<p> 167RSF files contain the information required to create a CCI file. They must be created individually for each application. By default, the SDK's default RSF file is used. Be sure to always use the DESC file included in the SDK. 168</p> 169 170<h3>Commands</h3> 171 172 173<p class="code"> 174% ctr_makerom32 ELF_FILE -rsf RSF_FILE -desc DESC_FILE [-o OUTPUT_FILE] [-Dname=value...] [-f FORMAT] [-info INFO_FILE] [-banner BANNER_FILE] [-icon ICON_FILE] [-content CONTENTS_PATH:INDEX] [-j NUM] 175</p> 176 177<p class="first_ja">You must specify the ELF, RSF, and DESC files. All other options are optional.</p> 178 179<h4 >Options</h4> 180 181 182<div class="table"> 183<table border="1"> 184<thead> 185<tr> 186<th align="center">Options</th> 187<th align="center">Description</th> 188</tr> 189</thead> 190<tbody> 191<tr> 192<td align="center"><CODE>-rsf</CODE></td> 193<td align="center">Specifies the RSF file.</td> 194</tr> 195<tr> 196<td align="center"><CODE>-desc</CODE></td> 197<td align="center">Specifies the DESC file.</td> 198</tr> 199<tr> 200<td align="center"><CODE>-banner</CODE></td> 201<td align="center">Specifies the banner file.</td> 202</tr> 203<tr> 204<td align="center"><CODE>-icon</CODE></td> 205<td align="center"> 206Specifies the icon file.<br/>Unless you specify an icon file with this option, you cannot get the EULA version from the application. 207</td> 208</tr> 209<tr> 210<td align="center">-content CONTENTS_PATH:INDEX</td> 211<td align="center"> 212Specifies content (.cfa) included in the CCI.<BR>Specify the contents file path in <CODE>CONTENTS_PATH</CODE>.<BR>Specify the partition number including the content in <CODE>INDEX</CODE>.<BR>The values specifiable for <CODE>INDEX</CODE> vary depending on the following conditions. 213<table border="1"> 214<tr> 215<td>When an <CODE>ELF_FILE</CODE> is specified</td> 216<td>The value 1 through 7 can be specified for <CODE>INDEX</CODE>.</td> 217</tr> 218<tr> 219<td>When an <CODE>ELF_FILE</CODE> is not specified</td> 220<td>The value 0 through 7 can be specified for <CODE>INDEX</CODE>.</td> 221</tr> 222</table> 223 224</td> 225</tr> 226<tr> 227<td align="center"><CODE>-o</CODE></td> 228<td align="center">Specifies the output filename. If omitted, the output file will have the same basename as the ELF file used as input, and instead of the .elf extension, the output file extension will be .cci for card applications and .cxi for NAND applications.</td> 229</tr> 230<tr> 231<td align="center"><CODE>-Dname=value</CODE></td> 232<td align="center">Specifies the variable name (<CODE>name</CODE>) and value (<CODE>value</CODE>) to reference in the RSF file. Locations where <CODE>$(name)</CODE> is written in the RSF file are replaced with the <CODE>value</CODE> command line argument and then evaluated.</td> 233</tr> 234<tr> 235<td align="center"><CODE>-f FORMAT</CODE></td> 236<td align="center">Specifies the format of the image to output. The following values can be specified for <CODE>FORMAT</CODE>. 237<table border="1"> 238<tr> 239<td><CODE>card</CODE></td> 240<td>Outputs in .cci format. Specify this option when creating a standard card application.</td> 241</tr> 242<tr> 243<td><CODE>nand</CODE></td> 244<td>Outputs in .cxi format. Specify this option when building a NAND application.<br/>You must use the .cxi file generated as input to <CODE>ctr_makecia</CODE> to create a .cia file in order to create images that can actually be imported to NAND.</td> 245</tr> 246<tr> 247<td><CODE>data</CODE></td> 248<td>Output is made in .cfa format. The generated .cfa file can be made to include a separate CCI by using the <CODE>-content</CODE> option.</td> 249</tr> 250</table> 251If nothing is specified, the default value of <CODE>nand</CODE> is used. 252</td> 253</td> 254</tr> 255<tr> 256<td align="center"><CODE>-info</CODE></td> 257<td align="center">Specifies the output file to which to output information about the output image. If unspecified, the output filename will have the <CODE>.xml</CODE> filename extension. This file contains information about the application title and ROMFS. 258</td> 259</td> 260</tr> 261<tr> 262<td align="center"><CODE>-j NUM</CODE></td> 263<td align="center">Specifies the number of makerom parallel processes. However, only some processes can be performed in parallel.<br/>When it is not specified, the CPU core count for the execution environment is acquired and used. 264</td> 265</td> 266</tr> 267</tbody> 268</table> 269</div> 270 271<h2><a name="rsf">RSF File</a></h2> 272 273<p>This is a file that contains the settings for the CCI file.</p> 274 275<h3>Format</h3> 276 277<p>The RSF file format is shown below.</p> 278 279<p class="code"> 280BasicInfo:<br/> Title: # Application title<br/> CompanyCode: # Company code<br/> ProductCode: # Product code<br/> MediaSize: # Media size<br/> Logo: # Logo data specification<br/> BackupMemoryType: # Backup memory type<br/> 281 282</br> TitleInfo: <br/> Category: # Title category<br/> UniqueId: # Unique ID for title code<br/> ChildIndex: # DLP child index<br/> <br/> Rom:<br/> HostRoot: # Root path of the ROM file system<br/> Reject: # File and directory names to exclude from the ROM file system<br/> <br/> AccessControlInfo:<br/> Priority: # Main thread priority.<br/> UseExtSaveData: # Whether to use expanded save data.<br/> ExtSaveDataNumber: # Expanded save data number.<br/> FileSystemAccess: # File system access permissions.<br/> <br/> SystemControlInfo:<br/>StackSize: # Stack size of main thread.<br/> RemasterVersion: # The remaster version<br/> <br/> Option:<br/> EnableCompress: # Enables/disables compression of static memory<br/> 283 284</p> 285 286<p> 287Configure the values of the items under the six main sections (<CODE>BasicInfo</CODE>, <CODE>TitleInfo</CODE>, <CODE>Rom</CODE>, <CODE>AccessControlInfo</CODE>, <CODE>SystemControlInfo</CODE>, and <CODE>Option</CODE>).<br/>Set the values using the following format: 288 289<h3>Specifying Single Values</h3> 290<p class="code"> 291Key Name: Value 292</p> 293 294<h3><a name="sequence_element" />Specifying Multiple Values</h3> 295<p class="code"> 296Key Name:<br/> - Value 1<br/> - Value 2<br/> ...<br/> 297</p> 298 299</p> 300 301<h4>Notes</h4> 302<ul> 303<li>Tabs cannot be used in place of half-width spaces.</li> 304<li>You must use at least one half-width space after the colons and hyphens that separate the key names from the values.</li> 305<li>Indentation (using half-width spaces) is required at the beginning of the line for each sub-item.</li> 306<li>Main sections must not be indented.</li> 307<li>Each sub-item within a given main section must be indented by the same number of spaces.</li> 308</ul> 309 310Descriptions of the settings for each of these items are shown below. 311 312<h4><CODE>BasicInfo</CODE></h4> 313<div class="table"> 314<table border="1"> 315<thead> 316<tr> 317<th align="center">Item</th> 318<th align="center">Description</th> 319<th align="center">Comments</th> 320</tr> 321</thead> 322<tbody> 323<tr> 324<td align="center"><CODE>Title</CODE></td> 325<td align="center">The title of the application. Specifies the application title in eight or fewer ASCII characters.</td> 326<td align="center"></td> 327</tr> 328<tr> 329<td align="center"><CODE>CompanyCode</CODE></td> 330<td align="center">The company code. Company code that was assigned when the licensing agreement was signed with Nintendo. Two ASCII characters.</td> 331<td align="center"></td> 332</tr> 333<tr> 334<td align="center"><CODE>ProductCode</CODE></td> 335<td align="center">Product code. Specifies the product code issued by Nintendo.</td> 336<td align="center"></td> 337</tr> 338<tr> 339<td align="center"><CODE>MediaSize</CODE></td> 340<td align="center">Specifies the media size. Specify a value of 125 MB, 256 MB, 512 MB, 1 GB, or 2 GB.</td> 341<td align="center"></td> 342</tr> 343<tr> 344<td align="center"><CODE>Logo</CODE></td> 345<td align="center">Specifies the type of logo data.</td> 346<td align="center">Specify "<CODE>Nintendo</CODE>" for Nintendo titles, "<CODE>Distributed</CODE>" for titles for which Nintendo purchased the publishing license from the software manufacturer or titles for which Nintendo acquired the publishing license from a publisher, and "<CODE>Licensed</CODE>" for all other titles. If omitted, "<CODE>Nintendo</CODE>" is used as the default value.<br/><br/>The value "<CODE>Published</CODE>" was valid in previous versions, but it has been replaced by "<CODE>Distributed</CODE>". If you specify "<CODE>Published</CODE>", it is handled as "<CODE>Distributed</CODE>". In future releases it will not be possible to specify "<CODE>Published</CODE>". 347</td> 348</tr> 349<tr> 350<td align="center"><CODE>BackupMemoryType</CODE></td> 351<td align="center"> 352Specify the backup memory type. This is ignored for download applications.<br/>Specify None, 128 KB, or 512 KB. 353</td> 354<td align="center"> 355</tr> 356</tbody> 357</table> 358</div> 359 360<h4><CODE>TitleInfo</CODE></h4> 361<div class="table"> 362<table border="1"> 363<thead> 364<tr> 365<th align="center">Item</th> 366<th align="center">Description</th> 367<th align="center">Comments</th> 368</tr> 369</thead> 370<tbody> 371<tr> 372<td align="center"><CODE>Category</CODE></td> 373<td align="center">Specifies the application type.<br/> 374<table border="1"> 375<tr> 376<td><CODE>Application</CODE></td> 377<td>Specify this when building a typical application.</td> 378</tr> 379<tr> 380<td><CODE>DlpChild</CODE></td> 381<td>Specify this when building a download play child.<br/>This must be specified along with <CODE>ChildIndex</CODE> (described later).</td> 382</tr> 383</table> 384</td> 385<td align="center">When unspecified, a value corresponding to <CODE>DESC</CODE> is automatically selected.</td> 386</tr> 387<tr> 388<td align="center"><CODE>UniqueId</CODE></td> 389<td align="center">The application's unique ID. Specifies the ID issued by Nintendo.<br />Specifies the same ID as the parent device for Download Play child devices.</td> 390<td align="center">Valid values are from 0x00300 to 0xf7fff.</td> 391</tr> 392<tr> 393<td align="center"><CODE>ChildIndex</CODE></td> 394<td align="center">Specifies the download play child index.</td> 395<td align="center">You can specify values from 0 through 255.</td> 396<td></td> 397</tr> 398</tbody> 399</table> 400</div> 401 402 403 404<h4><CODE>Rom</CODE></h4> 405<div class="table"> 406<table border="1"> 407<thead> 408<tr> 409<th align="center">Item</th> 410<th align="center">Description</th> 411<th align="center">Comments</th> 412</tr> 413</thead> 414<tbody> 415<tr> 416<td align="center"><CODE>HostRoot</CODE></td> 417<td align="center">The root path of the ROM file system.<br/>Specify either an absolute path or a relative path from the directory that is the current directory when executing <CODE>ctr_makerom</CODE>. All files and directories under the directory specified here will be stored in the ROM file system. However, any files or directories that start with a period ("<CODE>.</CODE>") will not be stored in the ROM file system, nor will any files or directories specified under the <CODE>Reject</CODE> item.</td> 418<td align="center"></td> 419</tr> 420<tr> 421<td align="center"><CODE>Reject</CODE></td> 422<td align="center">Specify the names of files and directories to exclude from the ROM file system.<br/>Any files or directories that match the names specified will not be stored in the ROM file system. You can set multiple values. Names can use the "<CODE>*</CODE>" and "<CODE>?</CODE>" wildcards ("<CODE>*</CODE>" matches 0 or more characters, and "<CODE>?</CODE>" matches a single character).</td> 423<td align="center">Use the syntax described in the <a href="#sequence_element">Specifying Multiple Values</a> section.</td> 424</tr> 425</tbody> 426</table> 427</div> 428 429<h4><CODE>SystemControlInfo</CODE></h4> 430<div class="table"> 431<table border="1"> 432<thead> 433<tr> 434<th align="center">Item</th> 435<th align="center">Description</th> 436<th align="center">Comments</th> 437</tr> 438</thead> 439<tbody> 440<tr> 441<td align="center"><CODE>StackSize</CODE></td> 442<td align="center">Specify the stack size of the main thread (in bytes).</td> 443<td align="center">Must be a multiple of 4096.</td> 444</tr> 445<tr> 446<td align="center">RemasterVersion</td> 447<td align="center">Specifies the remaster version. If unspecified, the version is treated as if 0 had been specified.</td> 448<td align="center"></td> 449</tr> 450</tbody> 451</table> 452</div> 453 454<h4><CODE>AccessControlInfo</CODE></h4> 455<div class="table"> 456<table border="1"> 457<thead> 458<tr> 459<th align="center">Item</th> 460<th align="center">Description</th> 461<th align="center">Comments</th> 462</tr> 463</thead> 464<tbody> 465<tr> 466<td align="center"><CODE>Priority</CODE></td> 467<td align="center">Specifies the priority of the main thread.</td> 468<td align="center">You can specify values between 0 and 31 (inclusive).</td> 469</tr> 470</tbody> 471<tbody> 472<tr> 473<td align="center"><CODE>UseExtSaveData</CODE></td> 474<td align="center">Specify <CODE>true</CODE> when using expanded save data.</td> 475<td align="center">The default value is <CODE>false</CODE>.</td> 476</tr> 477</tbody> 478<tbody> 479<tr> 480<td align="center"><CODE>ExtSaveDataNumber</CODE></td> 481<td align="center">Specify the expanded save data number using 20 bits.</td> 482<td align="center">The default is the <CODE>UniqueId</CODE>.</td> 483</tr> 484</tbody> 485<tbody> 486<tr> 487<td align="center"><CODE>FileSystemAccess</CODE></td> 488<td align="center"> 489Specifies the file system access permission attributes.<br />Specify from the following values: 490 <ul> 491<li><CODE>DirectSdmc</CODE>: Allows direct access to the SD Card. Specify this when using the library that directly accesses SD Cards.</li> 492<li><CODE>Debug</CODE>: Enables debug features, such as direct access to SD Cards. This value cannot be specified for retail versions.</li> 493 </ul> 494</td> 495<td align="center">Use the syntax described in the <a href="#sequence_element">Specifying Multiple Values</a> section.</td> 496</tr> 497</tbody> 498</table> 499</div> 500 501<h4>Option</h4> 502<div class="table"> 503<table border="1"> 504<thead> 505<tr> 506<th align="center">Item</th> 507<th align="center">Description</th> 508<th align="center">Comments</th> 509</tr> 510</thead> 511<tbody> 512<tr> 513<td align="center"><CODE>EnableCompress</CODE></td> 514<td align="center">Specify <CODE>true</CODE> to enable static memory compression or <CODE>false</CODE> to disable it. Memory is not compressed if doing so does not decrease the size. The compression rate is output to the file specified in the <SPAN class="argument">-info</SPAN> argument.</td> 515<td align="center">If this argument is not specified, the default value of <CODE>true</CODE> is used.</td> 516</tr> 517</tbody> 518</table> 519</div> 520 521<h3>Variables</h3> 522 523<p> 524Using the <CODE>-Dname=value</CODE> option allows you to pass variable names and their corresponding values to the <CODE>ctr_makerom</CODE> tool. The <CODE>ctr_makerom</CODE> tool replaces any occurrences of <CODE>$(name)</CODE> within the RSF file with the specified <CODE>value</CODE>, then evaluates the results. An example is shown below. 525</p> 526 527<p class="code"> 528$ ctr_makerom32 test.axf -o test.cci -rsf test.rsf -DTITLE=Test -DROMFS_ROOT=files<br/> <br/> --- test.rsf<br/> BasicInfo:<br/> Title: $(TITLE)<br/> <br/> Rom:<br/> HostRoot: "$(ROMFS_ROOT)"<br/> <br/> --- Value at final evaluation<br/> BasicInfo:<br/> Title: Test<br/> <br/> Rom:<br/> HostRoot: "files"<br/> 529</p> 530 531<h2><a name="desc">DESC File</a></h2> 532<p> 533DESC files are placed in the <CODE>CTR_SDK/resources/specfiles</CODE> folder. Use the appropriate DESC file depending on the type of application you are creating.<br/> <br/> 534<table border="1"> 535<thead> 536<tr> 537<th align="center">Application Type</th> 538<th align="center">DESC File</th> 539<th align="center">Comments</th> 540</tr> 541</thead> 542<tbody> 543<tr> 544<td align="center">General applications</td> 545<td align="center"><CODE>Application.desc</CODE></td> 546<td align="center"></td> 547</tr> 548<tr> 549<td align="center">Download Play child</td> 550<td align="center"><CODE>DlpChild.desc</CODE></td> 551<td align="center"></td> 552</tr> 553</tbody> 554</table> 555<br/> 556 557Edits to the DESC file are prohibited. Editing this file may prevent your application from operating properly. 558</p> 559<p> 560When you use the build system, the option <CODE>-desc CTR_SDK/resources/specfiles/Application.desc</CODE> is specified automatically when you run <CODE>ctr_makerom</CODE>.<br/>You can also specify within the OMakefile what DESC file to use. For details, see the <a href="../SDKRules/BuildRules.html">Build Rules</a>. 561</p> 562 563<h2><a name="titleid">Game Software Prototype Code</a></h2> 564<p> 565The following code has been assigned for software testing and prototyping purposes. Use this as an ID for internal testing. Be careful to avoid duplicate IDs within your company and development department. 566 567Note that running <CODE>ctr_makerom</CODE> displays a warning if you are using <CODE>UniqueId</CODE> for the prototype code. 568 569<p class="code"> 570BasicInfo:<br/> CompanyCode:"00"</br> ProductCode: "CTR-*-****"</br> <br/> TitleInfo:<br/> UniqueId : 0xFF000 ～ 0xFF3FF</br> <br/> * ... A-Z, 0-9<br/> 571</p> 572 573<B>Note:</B> In CTR-SDK 0.14.1 and prior versions, <CODE>ProductCode</CODE> used the format below, but this format is no longer usable in subsequent versions.<br/>The value that is used in the 0.14.1 environment is the value with the "<CODE>(###)</CODE>" portion removed. 574 575<p class="code"> 576 ProductCode: "CTR-*-**** (###)"</br> 577</p> 578 579</p> 580 581 582<h2><a name="omake">Variables Defined Within OMakefiles</a></h2> 583<p> 584Refer to <A href="../SDKRules/BuildRules.html#makeromvariable">Build Rules (<CODE>ctr_makerom</CODE>)</A> for more information about variables defined within the <CODE>OMakefile</CODE>. 585</p> 586 587</tbody> 588</table> 589</div> 590<h2><a name="history">Revision History</a></h2> 591 <dl class="history"> 592 <dt>2010/12/27</dt> 593<dd>Added a method for specifying the remaster version.<br /> 594 </dd> 595 <dt>2010/12/10</dt> 596<dd>Added remarks about ChildIndex.<br /> 597<dd>Added information about Download Play child devices to UniqueId.<br /> 598 </dd> 599 <dt>2010/12/07</dt> 600<dd>Added description of when no logo is specified.<br /> 601 </dd> 602 <dt>2010/11/18</dt> 603<dd>Added description of DESC file types.<br /> 604<dd>Added description of the change in logo specification.<br /> 605<dd>Added description of the <CODE>-icon</CODE> option.<br /> 606 </dd> 607 <dt>2010/11/11</dt> 608<dd>Added description of file system access permission attributes.<br /> 609 </dd> 610 <dt>2010/11/10</dt> 611<dd>Added description of product code format change.<br /> 612 </dd> 613 <dt>2010/10/29</dt> 614<dd>Added description of expanded save data and backup memory specifications.<br /> 615 </dd> 616 <dt>2010/10/26</dt> 617<dd>Added description of logo data.<br /> 618 </dd> 619<dd>Changed specifiable range for <CODE>UniqueId</CODE> to <CODE>0x300</CODE>.<br /> 620 </dd> 621 <dt>2010/10/07</dt> 622<dd>Added the <CODE>-j</CODE> option.<br /> 623 </dd> 624 <dt>2010/09/24</dt> 625<dd>Changed the <CODE>-cxi</CODE> option to <CODE>-content</CODE> and included a description.<BR> 626<dd>Included a description of the <CODE>-banner</CODE> and <CODE>-icon</CODE> options.<BR> 627<dd>Included a description of <CODE>Category</CODE> and <CODE>ChildIndex</CODE> specifications for <CODE>TitleInfo</CODE> and the logo specification for <CODE>BasicInfo</CODE>.<BR> 628 </dd> 629 <dt>2010/08/17</dt> 630<dd>Added the "Game Software Prototype Code" section. 631 </dd> 632 <dt>2010/08/03</dt> 633<dd>Added descriptions of the <CODE>EnableCompress</CODE> and <CODE>MediaSize</CODE> options. 634 </dd> 635<dd>Deleted the <CODE>InitialCode</CODE> option. 636 </dd> 637 <dt>2010/07/19</dt> 638<dd>Added a description of the <CODE>-info</CODE> option, <CODE>CompanyCode</CODE>, <CODE>ProductCode</CODE>, and <CODE>UniqueId</CODE>. 639 </dd> 640 <dt>2010/07/14</dt> 641<dd>Added a description of CXI files. 642 </dd> 643 <dt>2009/12/22</dt> 644<dd>Initial version.<br /> 645 </dd> 646 </dl> 647<hr><p>CONFIDENTIAL</p></body> 648</html>