1**************************************************************************** 2* * 3* changelog-TwlSDK-5_1_patch6-20090526.txt * 4* * 5* Plus patch for TWL-SDK 5.1 * 6* * 7* May 26, 2009 * 8* * 9**************************************************************************** 10 11 12Revisions 13 14 Content revisions in 5_1-patch6-20090526 15 -------------------------------------------------------------------------- 16 17 - (FS) Fixed a problem where overlay in NITRO ROM could not be debugged using the IS-TWL-DEBUGGER 18 19 When you ran a NITRO ROM that included overlays and was built with TWL-SDK, using IS-TWL-DEBUGGER, the break feature in the overlays would not function. This problem has been fixed. 20 21 22 - (GX) Fixed the DEMO library 23 24 Fixed $TwlSDK/build/demos/gx/UnitTours/DEMOLib to support the new prototype of the ISTDFIOWrite function (debugger function) changed in IS-TWL-DEBUGGER version 1.06 and later. 25 26 27 Content revisions in 5_1-patch5-20090508 28 -------------------------------------------------------------------------- 29 30 - (CARD) Fixed a bug in detecting a card removal during ROM access 31 32 Fixed a bug that occurred if a card was removed while a card application running in TWL mode read data from ROM, causing the program to be forcibly stopped by an abnormal ROM hash before being notified by the card removal callback. 33 34 35 - (FS) Fixed a bug related to conflicting use of multiple archives 36 37 Fixed a bug that would sometimes cause abnormal program termination when a command was simultaneously issued to a ROM archive and a user-provided archive using the FS_LoadArchive function. 38 39 40 - (TOOL) Changed makerom.TWL 41 42 Fixed a bug that occurred when building a NAND application that uses overlays: On occasion, some ROM hash values for the overlays would not be calculated properly, causing program execution to terminate with an error when loading the overlay. 43 44 This issue has only occurred since TWL-SDK 5.1 patch 1 (090330). 45 46 47 Content revisions in 5_1-patch4-20090416 48 -------------------------------------------------------------------------- 49 50 - (CAMERA) Revised the CAMERA_SwitchOffLED and CAMERA_SetLED functions. 51 52 When the setting for the duration of blinking of the outer-camera LED was set too short, the light would never extinguish. That problem has been fixed. 53 54 Because this correction also changes the behavior of the CAMERA_SwitchOffLED and CAMERA_SetLED functions, an explanation has been added to the reference for each. 55 56 57 Content revisions in 5_1-patch3-20090415 58 -------------------------------------------------------------------------- 59 60 - (FS) Corrected unnecessary device access in the flush process 61 62 For applications that had never accessed an SD Card or NAND, the process of flushing the FAT file system involved an unnecessarily long read access. 63 64 The result was that, depending on the SD Card inserted, the sleep and reset processes could take a lot of time when the SD Card has never been accessed. 65 That problem was fixed. 66 67 68 Revised Content in 5_1-patch2-20090406 69 -------------------------------------------------------------------------- 70 71 - (DSP) Fixed a bug in the DSP_Scaling* functions 72 73 Because the corrections added with TWL-SDK 5.1 patch 1 were incomplete, noise (horizontal lines) was generated in output images when a specific argument was specified. 74 This problem has been fixed. 75 76 - (FS) Corrected a problem related to commands issued in multi-threads 77 78 There was a bug where a processing deadlock would occur in rare occasions for both threads when an FS library function is called from a high-priority thread while calling an FS library function for a low-priority thread. This has been corrected. 79 80 81 Revised Content in 5_1-patch1-20090330 82 -------------------------------------------------------------------------- 83 84 - (DSP) Fixed a bug in the DSP_Scaling* functions 85 86 Fixed a bug that prevented processing from ending or caused one or two lines to be left off of the end of the output image if the input image size and factor satisfied particular conditions when DSP_GRAPHICS_SCALING_MODE_BICUBIC was specified for the scaling mode and the specified factor scaled down along the vertical axis. 87 88 - (PM) Fixed a mutual exclusion bug in the PM library 89 A bug in the PM library caused deadlocks when PM functions were called at particular times, even though multi-thread tasks were made to be mutually exclusive. 90 This problem has been fixed. 91 92 - (TOOL) Changed makerom.exe and makerom.TWL.exe 93 94 Made the following changes to the makerom.exe and makerom.TWL.exe tools. 95 96 - Revised explanations in the Function Reference Manual, which previously stated that when Align and AlignAll competed with each other, the largest setting value would have priority even though in actuality Align always took precedence. 97 - Fixed a bug that prevented the Align and AlignAll settings from being applied to (only) the first file recorded in ROM when BannerFile was not specified. 98 - Removed a restriction that caused Align and AlignAll to be internally corrected to a minimum value of 1024 bits for Nintendo DSi enhanced programs. 99 - Revised the default value used when DigestParam is omitted to be "1024 32" so that it matches the standard RSF file. The default value used to be "2048 256". 100 - Added processing to automatically set JpegSign to TRUE when PhotoAccess includes write access specifications. 101 If you have configured JpegSign for the TCL library, remove it and configure only PhotoAccess to an appropriate value in the future. 102 103 - (WM) Improved decision-making in the WM_IsValidGameInfo and WM_IsValidGameBeacon functions 104 105 Improved both the WM_IsValidGameInfo and WM_IsValidGameBeacon functions to return FALSE for falsified beacon information because these functions had been confirmed to sometimes be unable to detect a falsified, illegal beacon during a scan. 106 107 108Known Issues 109 110 - FINALROM application jumps do not work properly on TS boards. 111 112 - If a program that was built in Hybrid mode is run in a NITRO environment, any argument data that was embedded with the buryarg tool cannot be accessed properly. 113 114 115End 116