(2005/08/23)
When a FRAM device is being used for backup, there was an occasional problem with inconsistency of the hardware internal status. A process was added to deal with this issue.
Due to the operation changes noted in Note 28-03, there was a problem that the destructor for the global object array in the overlay would not start correctly when unloading the overlay. This has been fixed.
Made numerous corrections to the following document explaining the FS library:
When the argument passed to the FX_InvSqrt
function was above a fixed value the calculation would be incorrect. This problem has been fixed.
In conjunction with the features added in Note 27-22, a MB_GetMultiBootDownloadParameter
function was added to reference the user definition expanded parameters when downloading.
Added references for the OS_InitPrintServer
and OS_PrintServer
functions, which are used for ARM 7 debug output. Also added that it is not necessary to use these functions in the application.
Added an explanation of the NitroStaticInit
function to the Function Reference, in line with the addition made in Note 27-31.
At the place where the DC_InvalidateRange
function is called from the Sound library, the specified range was larger than necessary, so corrected this to be an appropriate size. This correction reduces the load of the sound process.
During MP communications, if the communications partner disappears (e.g., the power gets cut), there is a timeout and notification is made of the disconnection. However, due to a bug in the timeout process, sometimes notification of the disconnection was not made. This bug was fixed.
In environments where communications status is extremely bad and the child repeatedly tries to connect to the parent, there was a bug that put parent into an abnormal internal state. That bug has been fixed.
As mentioned in Note 25-22, internal operation was changed to wait for the signal strength that can send the disconnection notification when disconnecting. But this has been changed to timeout after a set period of time. This corrects those cases where the process did not end when WMTestTool.srl
was used to set the Noise rate to 100%.
None.
(2005/08/08)
Added a statement to the CARD_CheckPulledOut
function reference indicating that the CARD_LockRom
function must be called and CARD-ROM bus needs to be locked before calling this function .
Added a restriction so that CARD_BACKUP_TYPE_NOT_USE
cannot be specified as the device type passed to the CARD_IdentifyBackup
function. This change was added in 2.2 PR, but it was left out of the changelog.
Corrected the path location that ISD_NITRO_DEBUGGER
indicates, which is defined in $NitroSDK/build/buildtools/commondefs.emtype.ISD
.
When there was a global object in an overlay to be unloaded that required a destructor, the destructor was called automatically. The operation has been changed so that the destructor is not called.
The following correction was made to the $NitroSDK/build/demos/gx/UnitTours/Sub_Double3D
sample demo:
The correction described in Note27-15 was not complete and the same symptoms still appeared occasionally. The problem was corrected again.
The contents of the pointer passed to the arguments of the following functions have not been rewritten; however, the const
qualifier had not been added to the arguments, so const
has been added to them.
G3_GetDLStart
function
G3_GetDLLength
function
G3_GetDLSize
function
Replaced the implementations of the MD5 functions. The code sizes are about half of what they were before, and the functions operate approximately 20% faster compared to the previous implementation. The interface has not been changed. This change was added in 2.2 PR, but it was left out of the changelog.
The following correction was made to the $NitroSDK/build/demos/mb/cloneboot
sample:
ConnectMain
function on the parent failed, a reattempt was made without ending the WH module. This bug has been fixed.
When moved from the LCD OFF state to sleep mode and then recovered a discrepancy would arise between the actual state and the internal state of the GX library. This has been fixed. (See Note22-23)
When the ignoreFatalError
argument of the WM_StartMPEx
function is set to TRUE, there should be no auto-disconnect even when a fatal error occurs with the child. However, due to a problem in this process, communications become unavailable after this point. This has been fixed.
It was confirmed that programs do not operate when the thumb build version of the ichneumon component is used. This has been corrected.
None.
NINTENDO Technical Support Center