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=utf-8"> 5<meta http-equiv="Content-Style-Type" content="text/css"> 6<title>KnownIssues</title> 7<style type="text/css"> 8<!-- 9body { 10/* 11 font-size : 10pt; 12*/ 13 font-weight : normal; 14 color : #000000; 15 margin : 8px; 16} 17 18div { 19 width : 98%; 20 white-space : nowrap; 21} 22 23div.title { 24 text-align : left; 25 font-weight : bold; 26/* 27 font-size : 16pt; 28*/ 29 font-size : 150%; 30 color : #202020; 31 border-style : double; 32 border-width : 8px; 33 /* タイトルを囲む枠線の色を指定 */ 34 border-color : #FF6600; 35 36 margin : 4px; 37 padding : 4px; 38} 39 40h1 { 41 font-size : 150%; 42 font-family : Arial; 43 border-bottom-width : 5px; 44 border-bottom-style : solid; 45 border-bottom-color : #FF6600; 46 padding-bottom : 1px; 47 margin-bottom : 20px; 48 letter-spacing : normal; 49 font-weight : bold; 50} 51 52 53h2 { 54 font-weight : bold; 55/* 56 font-size : 16pt; 57*/ 58 font-size : 150%; 59 border-style : none none solid double; 60 border-width : 0px 0px 2px 8px; 61 /* 見出しの線の色を指定 */ 62 border-color : #FF6600; 63 64 margin-left : 2px; 65 padding-left : 4px; 66} 67table { 68 margin-top : 2pt; 69 margin-bottom : 2pt; 70 margin-left : 0pt; 71 margin-right : 0pt; 72 padding-left : 0pt; 73 padding-right : 0pt; 74 position : relative; 75 left : 12px; 76 font-family : Arial; 77 font-size : 10pt; 78 border-style : none none none none; 79} 80td,th { 81 padding : 2pt; 82 border-width : 2pt; 83 border-style : none none none none; 84 font-style : normal; 85} 86td { 87 background : #e8f4f4; 88 font-weight : normal; 89} 90th { 91 background : #c0d8d8; 92 font-weight : bold; 93} 94 95p { 96 margin-left : 4px; 97} 98.enable { background :#ffcccc; text-align : center } 99.disable { text-align : center } 100.exsample { 101 border-style : none none none none; 102 background : #e8f4f4; 103} 104 105--> 106</style> 107 108</head> 109<body style="padding-bottom: 1600px;"> 110<h1>Symptoms Treated as Specifications</h1> 111Because a SystemUpdater update is required to fix the following current known issues, they are treated as part of specifications under CTR-SDK 2.x. 112<hr> 113<ol> 114 <li><a href="#is01">[AC] An uninitialized result may be returned when calling the <CODE>ac::Connect</CODE> function.</a></li> 115 <li><a href="#is02">[APPLET] The <CODE>IsExpectedToCloseApplication</CODE> does not send a notification even when the battery is set to 0% by the SPI debugger.</a></li> 116 <li><a href="#is03">[APPLET] Sometimes the LCD does not turn on when recovering from Sleep mode.</a></li> 117 <li><a href="#is04">[APPLET] Noise occurs when exiting some applications from the HOME Menu.</a></li> 118 <li><a href="#is05">[APPLET] The system sometimes stops on a black screen if a FATAL error occurs at the point the system is closed. </a></li> 119 <li><a href="#is06">[APPLET] Sometimes the system stops on the POWER Menu screen if the HOME Button is pressed immediately after going to the POWER Menu from an application that takes time to shut down.</a></li> 120 <li><a href="#is07">[APPLET] On rare occasions the system stops on a black screen if the system is closed/opened immediately after exiting an application.</a></li> 121 <li><a href="#is08">[APPLET] The system sometimes goes to a black screen or HOME does not work when recovered if the SD Card is removed during sleep.</a></li> 122 <li><a href="#is09">[APPLET] A card-removed error does not occur even if card emulation is turned OFF when starting an application by dragging to SPI debugger.</a></li> 123 <li><a href="#is10">[BOSS] Sometimes the system accesses the X-BOSS-Closed field of the very last task executed when it shouldn't.</a></li> 124 <li><a href="#is11">[BOSS] Sometimes information indicating immediate background execution status for a task executed immediately in the background is not flushed from NAND memory.</a></li> 125 <li><a href="#is12">[CAMERA] Sometimes the next startup fails if the system is opened and closed continuously at the same time when starting the camera.</a></li> 126 <li><a href="#is13">[CAMERA] On rare occasions the camera LED remains lit if the system is opened and closed repeatedly after calling <CODE>camera::Finalize</CODE>. </a></li> 127 <li><a href="#is14">[CEC] The maximum number of messages that can be stored in a box has changed. </a></li> 128 <li><a href="#is15">[FS] Sometimes DESCRIPTION FAT NOT FOUND is returned if <CODE>CreateExtSaveData</CODE> is executed on an SD Card in a certain state.</a></li> 129 <li><a href="#is16">[FS] Sometimes a FATAL error occurs when the SD Card is removed during ROM access.</a></li> 130 <li><a href="#is17">[SOCKET] The Send and Recv functions return ECONNRESET if connection is denied.</a></li> 131 <li><a href="#is18">[SSL] Lock cannot be released if an invalid client certificate is set. </a></li> 132</ol> 133<hr> 134<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 135<a name="is01"></a><tr><td> 136<p><span style="font-weight:blod;">Symptom</span></p> 137<p>An uninitialized Result is sometimes returned if the <CODE>ac::Connect</CODE> function is called at the exact instant when the connection with an access point is forcibly disconnected due to poor reception environment.</p> 138<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 139<p>Extremely rare.</p> 140<p><span style="font-weight:blod;">Affects</span></p> 141<p>All applications that use the <CODE>ac::Connect</CODE> function.</p> 142<p><span style="font-weight:blod;">Support Period</span></p> 143<p>CTR-SDK 3.0</p> 144</td></tr> 145</table> 146<br/> 147<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 148<a name="is02"></a><tr><td> 149<p><span style="font-weight:blod;">Symptom</span></p> 150<p>When the battery is set to 0% with an application being executed by the debugger, power goes off before shutdown notification (issued by executing the <CODE>IsExpectedToCloseApplication</CODE> function) can reach that application.</p> 151<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 152<p>Always.</p> 153<p><span style="font-weight:blod;">Affects</span></p> 154<p>Application being executed by the debugger.</p> 155<p><span style="font-weight:blod;">Support Period</span></p> 156<p>CTR-SDK 3.0</p> 157</td></tr> 158</table> 159<br/> 160<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 161<a name="is03"></a><tr><td> 162<p><span style="font-weight:blod;">Symptom</span></p> 163<p>In some extremely rare cases the screen will stay black after the system is closed and opened. Only rendering cannot be restored properly: sound output, button input, and other features run normally. Closing and opening the system again resolves this issue.</p> 164<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 165<p>Extremely rare.</p> 166<p><span style="font-weight:blod;">Affects</span></p> 167<p>All applications.</p> 168<p><span style="font-weight:blod;">Comments</span></p> 169<p>Because this same symptom can also be caused by an application's implementation, if you encounter this always check the following.<br/> 170<ul> 171<li>There may be a sequence or exact timing of events involved where rendering is not restored when awaking from Sleep Mode.<br/></li> 172</ul> 173</p> 174<p><span style="font-weight:blod;">Support Period</span></p> 175<p>TBD</p> 176</td></tr> 177</table> 178<br/> 179<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 180<a name="is04"></a><tr><td> 181<p><span style="font-weight:blod;">Symptom</span></p> 182<p>Noise occurs when exiting some applications from the HOME Menu.</p> 183<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 184<p>Depends on the application 185</p> 186<p><span style="font-weight:blod;">Affects</span></p> 187<p>All applications.</p> 188<p><span style="font-weight:blod;">Support Period</span></p> 189<p>TBD</p> 190</td></tr> 191</table> 192<br/> 193<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 194<a name="is05"></a><tr><td> 195<p><span style="font-weight:blod;">Symptom</span></p> 196<p>The system sometimes stops on a black screen if a FATAL error (including card removal error) occurs at the point the system is closed. </p> 197<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 198<p>Occurs at a high frequency if the time is right.</p> 199<p><span style="font-weight:blod;">Affects</span></p> 200<p>All applications.</p> 201<p><span style="font-weight:blod;">Support Period</span></p> 202<p>TBD</p> 203</td></tr> 204</table> 205<br/> 206<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 207<a name="is06"></a><tr><td> 208<p><span style="font-weight:blod;">Symptom</span></p> 209<p>Sometimes the system stops on the POWER Menu screen if the HOME Button is pressed immediately after transitioning to the POWER Menu from an application that takes time to shutdown.</p> 210<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 211<p>The longer an application takes to shut down, the greater the frequency.</p> 212<p><span style="font-weight:blod;">Affects</span></p> 213<p>All applications.</p> 214<p><span style="font-weight:blod;">Support Period</span></p> 215<p>CTR-SDK 3.0</p> 216</td></tr> 217</table> 218<br/> 219<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 220<a name="is07"></a><tr><td> 221<p><span style="font-weight:blod;">Symptom</span></p> 222<p>On rare occasions the system stops on a black screen if the system is closed and opened immediately after exiting an application.</p> 223<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 224<p>Extremely rare.</p> 225<p><span style="font-weight:blod;">Affects</span></p> 226<p>All applications that call the <CODE>AssignGpuRight</CODE> function when cancelling Sleep mode.</p> 227<p><span style="font-weight:blod;">Comments</span></p> 228<p>This issue does not arise unless the <CODE>AssignGpuRight</CODE> function is called when cancelling Sleep mode. </p> 229<p><span style="font-weight:blod;">Support Period</span></p> 230<p>CTR-SDK 3.0</p> 231</td></tr> 232</table> 233<br/> 234<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 235<a name="is08"></a><tr><td> 236<p><span style="font-weight:blod;">Symptom</span></p> 237<p>The system sometimes goes to a black screen or HOME does not work if the SD Card is removed during sleep.</p> 238<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 239<p>Extremely rare.</p> 240<p><span style="font-weight:blod;">Affects</span></p> 241<p>All applications.</p> 242<p><span style="font-weight:blod;">Support Period</span></p> 243<p>TBD</p> 244</td></tr> 245</table> 246<br/> 247<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 248<a name="is09"></a><tr><td> 249<p><span style="font-weight:blod;">Symptom</span></p> 250<p>A card removal error does not occur even if card emulation is turned OFF when starting an application by dragging it into SPI debugger.</p> 251<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 252<p>Always.</p> 253<p><span style="font-weight:blod;">Affects</span></p> 254<p>All applications.</p> 255<p><span style="font-weight:blod;">Support Period</span></p> 256<p>CTR-SDK 3.0</p> 257</td></tr> 258</table> 259<br/> 260<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 261<a name="is10"></a><tr><td> 262<p><span style="font-weight:blod;">Symptom</span></p> 263<p>When the immediately preceding task received a service shutdown in the the X-BOSS-Closed field, the current task will be erroneously identified as being in service shutdown status if it cannot establish a connection.</p> 264<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 265<p>Always.</p> 266<p><span style="font-weight:blod;">Affects</span></p> 267<p>All applications that use BOSS tasks.</p> 268<p><span style="font-weight:blod;">Comments</span></p> 269<p>If this occurs, there is a chance of unintended behavior by the application if the registered application gets the service shutdown using <CODE>GetProperty</CODE> and then executes a process based on the obtained value. At present, this problem does not occur in the typical user environment because we have spread the message not to use the service shutdown flag on the operations side.</p> 270<p><span style="font-weight:blod;">Support Period</span></p> 271<p>TBD</p> 272</td></tr> 273</table> 274<br/> 275<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 276<a name="is11"></a><tr><td> 277<p><span style="font-weight:blod;">Symptom</span></p> 278<p>If the power of a CTR system is turned off immediately after immediate background execution of a given task, information indicating that that task is being immediately executed in the background is not flushed from the BOSS database stored in NAND. The next time the CTR system starts, that task will be in the same status as one that executes normally in the background. </p> 279<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 280<p>Always.</p> 281<p><span style="font-weight:blod;">Affects</span></p> 282<p>All applications.</p> 283<p><span style="font-weight:blod;">Comments</span></p> 284<p>All applications that use immediate background execution of BOSS tasks.</p> 285<p><span style="font-weight:blod;">Support Period</span></p> 286<p>TBD</p> 287</td></tr> 288</table> 289<br/> 290<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 291<a name="is12"></a><tr><td> 292<p><span style="font-weight:blod;">Symptom</span></p> 293<p>If the system is opened and closed continuously at the same time the <CODE>Activate</CODE> function is executed on the camera, it will not be processed even though success is returned. Also, if Sleep mode is rejected, and the system is finally closed after repeatedly opening and closing it, the camera can be activated even though the system is closed. 294</p> 295<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 296<p>Occurs at a high frequency if the time is right. (The probability of the application rejecting Sleep mode increases depending on how many times the system is repeatedly opened and closed.)</p> 297<p><span style="font-weight:blod;">Affects</span></p> 298<p>All applications that use the camera.</p> 299<p><span style="font-weight:blod;">Comments</span></p> 300<p>Use the following workaround for this problem when using the <CODE>Activate</CODE> function to turn the camera ON/OFF. 301<ol> 302<li>Turn the camera ON/OFF using the <CODE>Activate</CODE> function.</li> 303<li>Wait (using a timeout) for the Event object returned by the <CODE>GetVsyncInterruptEvent</CODE> function to be signaled. (The timeout to use depends on the frame rate of the camera. If the frame rate is 5 fps, use a timeout of 200 ms.)</li> 304<li>When turning the camera ON: <CODE>Activate</CODE> succeeds if <CODE>Event</CODE> is signaled several times repeatedly before the timeout. When turning the camera OFF: <CODE>Activate</CODE> succeeds if there have been several timeouts. 305</ol> 306</p> 307<p><span style="font-weight:blod;">Support Period</span></p> 308<p>TBD</p> 309</td></tr> 310</table> 311<br/> 312<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 313<a name="is13"></a><tr><td> 314<p><span style="font-weight:blod;">Symptom</span></p> 315<p>On rare occasions, the camera LED remains lit if the system is opened and closed repeatedly after calling <CODE>camera::Finalize</CODE>. </p> 316<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 317<p>Rare.</p> 318<p><span style="font-weight:blod;">Affects</span></p> 319<p>All applications that use the camera.</p> 320<p><span style="font-weight:blod;">Comments</span></p> 321<p>This problem can be resolved by turning off the power or starting the camera again.</p> 322<p><span style="font-weight:blod;">Support Period</span></p> 323<p>CTR-SDK 3.0</p> 324</td></tr> 325</table> 326<br/> 327<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 328<a name="is14"></a><tr><td> 329<p><span style="font-weight:blod;">Symptom</span></p> 330<p>Values for things such as the maximum number of messages that can be received sometimes change if an application is suspended by pressing the HOME Button. </p> 331<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 332<p>Extremely rare.</p> 333<p><span style="font-weight:blod;">Affects</span></p> 334<p>All application that use StreetPass.</p> 335<p><span style="font-weight:blod;">Comments</span></p> 336<p>Note: Do not allow a malfunction as there is a possibility that more data than the amount set may be received. To restore settings, the box must be deleted and recreated. This problem does not occur if the HOME Menu is not running.</p> 337<p><span style="font-weight:blod;">Support Period</span></p> 338<p>TBD</p> 339</td></tr> 340</table> 341<br/> 342<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 343<a name="is15"></a><tr><td> 344<p><span style="font-weight:blod;">Symptom</span></p> 345<p>On rare occasions, no processing from the CTR aimed at the SD Card can be made if the SD Card is removed while creating expanded save data for the first time on that SD Card. This problem may also occur when creating expanded save data for the first time on an SD Card with very little free space.</p> 346<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 347<p>Extremely rare.</p> 348<p><span style="font-weight:blod;">Affects</span></p> 349<p>All applications that use expanded save data.</p> 350<p><span style="font-weight:blod;">Comments</span></p> 351<p>Recovery is possible by deleting the directory on the PC in which the problem SD Card is located. </p> 352<p><span style="font-weight:blod;">Support Period</span></p> 353<p>CTR-SDK 3.0</p> 354</td></tr> 355</table> 356<br/> 357<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 358<a name="is16"></a><tr><td> 359<p><span style="font-weight:blod;">Symptom</span></p> 360<p>Sometimes one of the following two FATAL errors occurs when the SD Card is removed during ROM access.<pre> 361RSL : 0xD9004588 362 <CODE>Level:</CODE> -5 363 Summary: 8 364 Module : 17 365 Desc :392 366 367RSL : 0xC8A0F001 368 <CODE>Level:</CODE> -7 369 Summary: 5 370 Module : 60 371 Desc : 1 372</pre> 373</p> 374<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 375<p>Extremely rare.</p> 376<p><span style="font-weight:blod;">Affects</span></p> 377<p>All card-based applications.</p> 378<p><span style="font-weight:blod;">Support Period</span></p> 379<p>TBD</p> 380</td></tr> 381</table> 382<br/> 383<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 384<a name="is17"></a><tr><td> 385<p><span style="font-weight:blod;">Symptom</span></p> 386<p>The <CODE>Send</CODE> and <CODE>Recv</CODE> functions return ECONNRESET if connection is denied using CONNECT.</p> 387<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 388<p>Always.</p> 389<p><span style="font-weight:blod;">Affects</span></p> 390<p>Applications directly using the socketAPI.</p> 391<p><span style="font-weight:blod;">Support Period</span></p> 392<p>CTR-SDK 3.0</p> 393</td></tr> 394</table> 395<br/> 396<table style="border:solid 1pt #000000; backgraound-color:#fffdfd;" width="900"> 397<a name="is18"></a><tr><td> 398<p><span style="font-weight:blod;">Symptom</span></p> 399<p>Lock cannot be released if an invalid client certificate is set. </p> 400<p><span style="font-weight:blod;">Frequency of Occurrence</span></p> 401<p>Always.</p> 402<p><span style="font-weight:blod;">Affects</span></p> 403<p>When using an invalid client certificate.</p> 404<p><span style="font-weight:blod;">Support Period</span></p> 405<p>CTR-SDK 3.0</p> 406</td></tr> 407</table> 408<br/><hr><p>CONFIDENTIAL</p></body> 409</html>