.) to the initial values used when specifying Reject in makerom
GX_InitEx() in gx.h
CARD_Init() with interrupts prohibited
CARD_IdentifyBackup()
PM_Init() inside OS_Init()
OS_GetConsoleType()
ntrcomp
mic2wav tool
G3*_MultTransMtx33()
GX_PowerGeometry(),
GX_Power3D()
GX_SetGraphicsMode()
FS_ReadDir did not match
make Related Files
(2007/07/10)
Made slight revisions to the transfer processing within the CARD_ReadRom function. The operational specifications have not changed.
Failures during linking used to occur if C++ constructors or static initializers were placed in the Autoload section. Consequently, the lcf template files were modified so that Autoload processing can be done for C++ constructors and static initializers.
The correct value was not being set when the OS_ARENA_MAINEX argument was provided to the OS_GetArenaLo function when performing autoloading to extended memory for debugging.
In order to correct this, a section called MAINEX was configured as a section dedicated to performing autoloads for the extended memory region, and revisions were made so that the objects to be transferred to extended memory can be enumerated in this section.
(For example,
Examples: lsf code when locating OBJS_MAINEX in extended memory:
Autoload MAINEX
{
Address 0x02400000
Object $(OBJS_MAINEX) (.text)
Object $(OBJS_MAINEX) (.data)
Object $(OBJS_MAINEX) (.bss)
}
No revisions have been made to the Overlay process as applied to extended memory.
None.
(2007/06/15)
Added a function that was originally meant to have been added in Note 46-02, but was not.
Released the MIAllocator structure and its operation functions as standard prototypes for allocating and releasing memory.
Fixed the modifications made in Note 44-09 to be even more accurate.
When specifying a variable definition list file with the -M option in makerom.exe, there was a problem with expanding the variable definitions described in that file to correct values. Specifically, a line feed code was always being added to the end of the expanded variable value.
This was fixed so that the line feed character is now removed.
A function reference has been prepared for the WFS library test release of Note 46-21, and the library officially released.
There was a bug in which TRUE would always be returned regardless of the existence of the channel that should be used. This has been fixed so that the correct value is returned.
None.
(2007/05/18)
Made revisions so that the library is forced to wait internally if CARD_UnlockBackup is called while executing an asynchronous operation on the backup device. An explanation of this has been added to the NITRO-SDK Function Reference Manual.
With respect to cache flush operations that accompany ROM access DMA transfers, it has until now been the case that a partial flush would always be performed, regardless of the transfer size; however, if the transfer size gets to be larger than a certain amount, it becomes more efficient to flush the entire cache. A function that can freely set the size threshold at which to switch between these cache flushing methods (partial and full) has therefore been added: CARD_SetCacheFlushThreshold.
A bug existed that would occasionally cause the backlight to turn off and shutdowns to occur if a card was removed during mic sampling. This problem has been fixed.
Made the Card Library compatible with the 16-megabit FLASH Backup Device and added CARD_BACKUP_TYPE_FLASH_16MBITS to the CARDBackupType enumerated type.
The NITRO-SDK Function Reference Manual and sample demos were updated accordingly.
Added a function, CTRDG_GetPhiClock, that was supposed to be added in Note 38-03, but in actuality was not.
Changed the definition of the build variable MAKELCF_FORMAT such that if an original setting value exists in another file --- for example, the application Makefile --- it is given priority.
In addition, added an explanation on the build variables MAKELCF_FORMAT and MAKELCF_FLAGS to $NITROSDK/docs/SDKRules/Rule-Defines.html.
Added a single sample code example to the FS_LoadOverlay function reference.
Added an internal restriction to GX_SetVCount to prevent it from being used in a manner similar to those listed below, since there is a danger that such forms of usage could have a detrimental effect on the LCD.
When double-screen 3D is used and separate fogs are set for each screen, there is a problem where the fog settings for the top and bottom screens become out-of-sync if a heavy processing loads exist. These fog settings and code for handling the problem has been added to $NitroSDK/build/demos/gx/UnitTours/Sub_Double3D.
Updated $NitroSDK/bin/ARM9-TS/ROM/mb_child.srl so that execution controls have become possible when starting in a debugging environment.
Added the MB_FakeSetCompareGGIDCallback function so when searching for multiple GGID's from a pseudo-multiboot child, the beacon determination method may be arbitrarily set as a callback.
Added a cautionary note to the MI_SetMainMemoryPriority function reference.
Created the MIDevice and MICache structures, and added functions to operate on them, to serve as utilities to control devices such as ROM.
A note about using buffer loops has been added to the MICAutoParam structure reference.
Made revisions so that the sample demo now operates normally using the loadrun.exe tool. This was done because the description of the sampling.bat script, which saves the execution results of the mic-2 sample demo in WAV files, was old.
Cleaned up the internal implementation of the following matrix functions, and moved the functions themselves from the GX library to the MTX library.
The function specifications have not changed.
Fixed a bug in which the stack of the thread calling OS_ResetSystem would be destroyed during a reset if the stack existed in the region where the ROM was loaded.
Because the stack of the main thread is in DTCM, this bug would not occur if calling the OS_ResetSystem function from the main thread, (even) without changing the location of its stack.
The following formatted string output functions have been added:
A bug existed where the makelcf command would output an invalid LCF if multiple parameters were specified in SearchSymbol statements in makelcf's SPECFILE. Revised the makelcf command and the standard LCF template to support multiple parameters.
Temporary support for 2Gbit ROMs described in Note 39-18 has become official.
Released a test version of the WFS library that uses MP communications to offer file systems from parent to child devices.
This library is a repackaging of the sample module that has been included under $NitroSDK/build/demos/wireless_shared/wfs.
Currently, as this is a test release, the following known issues exist:
Added descriptions regarding conditions for issuing WM_ERRCODE_OVER_MAX_ENTRY to the following files:
Since the setting values, such as ignoreFatalErrorMode, specified by WM_StartMPEx would be maintained by WM_EndMP even if leaving MP mode, the previous settings would be used the next time that WM_StartMP was called.
As a result, the ignoreFatalErrorMode value, set internally by the MP library, would become TRUE when MP communications was started by a call to WM_StartMP while using MB_EndToIdle.
In order to keep this problem from occurring, WM_StartMP has been accordingly changed to not use the various MP setting values specified by arguments to WM_StartMPEx.
Instead, use WM_SetMPParameter to explicitly change the default setting values that are used when WM_StartMP is called.
Furthermore, these MP setting values are initialized when functions such as WM_Initialize and WM_Enable are called.
WM_StartMPEx has been changed to ignore the fixFreqMode specification when mpFreq is 0, indicating continuous transmission mode.
Regardless of the signal environment, there were times when communications were cut off due to MP lifetime expiration when a Wii was the MP parent device. This has been corrected.
Added wmPadReach-child. This child device program is distributed by the mpdldemo/mpdlntr2rvl demo included in RevoEX, a development kit offering Wii network functionality.
None.
(2007/02/15)
The code style has been unified regarding indents and carriage returns in the library and demos.
The icons related to PictoChat and wireless in the $NitroSDK/data directory have been updated.
None.
(2007/01/22)
The necessary casting was not being performed in ENV_STRING(X) and ENV_BINARY(X). This has been corrected.
There had also been unnecessary debug output inside the library functions, but this has been fixed.
Added the FX_AsinIdx and FX_AcosIdx functions for finding the arcsine and arccosine.
Added a new structure GXBg23Control256x16Affine, in which the unnecessary reserved area has been deleted from the GXBg23Control256x16Pltt structure.
Following this revision, the G2*_GetBG2Control256x16Affine and G2*_SetBG2Control256x16Affine functions were added to replace G2*_GetBG2Control256x16Pltt and G2*_SetBG2Control256x16Pltt.
Added a note to the GX_SetVCount function reference, and deleted the $NitroSDK/build/demos/gx/UnitTours/VCount demo.
After initializing the library with the MB_Init function, there was a bug that caused a forced halt inside the library if the MB_End function was called without calling functions such as MB_StartParent. This problem has been fixed.
When using mb_child_simple.srl as the child program for DS Download Play, the program sometimes behaved differently from the actual system after a restart. This bug has been fixed.
When switching threads inside the IRQ handler, there was a bug where a register of a thread that newly entered the execution state would not return from the context where it had been saved. This problem has been fixed.
Added a document that deals with creating programs that support extended languages in $NitroSDK/docs/TechnicalNotes/AboutExtendedLanguage.pdf.
On rare occasions, the off period of the LCD became a value that is invalid according to the specifications (under 100 ms). This has been corrected.
Added explanations for applications developed for China and Korea to makebanner's reference manual.
The default IRQ stack size when the StackSize parameter is omitted in the makelcf tool was changed from the original 1024 bytes to 2048 bytes.
None.
(2006/11/27)
When the DS Card was removed during a DMA transfer, the image occasionally became distorted. This problem has been corrected.
All card removal detection until now has been performed through a card interrupt. This has been changed so that card removal will be detected through either a card interrupt or the card ROM-ID based on the "prohibit removal detection through card interrupt" flag.
This issue had been observed only when the "prohibit removal detection through card interrupt" flag was explicitly set.
A compilation error was observed depending on the include order when $NitroSDK/include/nitro/cp/divider.h was included without using the precompile header. This problem has been corrected.
The version of CodeWarrior used for building the NITRO-SDK package was changed to 2.0SP1.
When compiled without checking the Enums Always Int item in the IDE language setting, the enum size may become different from the size of the int type, changing the structure size. Changes have been made so that enum will always be defined to be the size of int.
An error was corrected in the Description section of the G3*_Vtx10 NITRO-SDK Function Reference Manual page.
When the cover was closed and the card was removed while running a DS download play with MB_SEGMENT_BUFFER_MIN specified as the buffer size of the MB_ReadSegment function, the MB library was forcibly stopped. This problem has been corrected.
The MB_FakeSetVerboseScanCallback function has been added, allowing notification of all received live beacons when scanning for beacons from multiboot parents, using the MB_FakeStartScan function.
This function allows simultaneous acquisition of beacons from non-multiboot parents.
Changes have been made for members' nickName and comment of the OSOwnerInfo structure so that two bytes each will be allocated for termination code.
The OS_GetOwnerInfo function has also been changed so that a termination code is inserted.
Added wait so that the V count value is always constant after running the OS_Init function.
Added the OS_VSNPrintfEx function, which is the OS_VSNPrintf function with the byte sequence output feature added, as well as the OS_TPrintfEx and the OS_TVPrintfEx functions that call it.
Korean has been added as an extended language code.
Also, $NitroSDK/build/demos/os/forKorea-1 has been added as a sample of creating a Korean application.
The revision in Note 36-13 caused a bug that prevented the system from turning off when a card was removed while performing a stream playback, even if the cover was closed. This problem has been fixed.
Previously, the SND_FlushCommand function was not thread-safe. This problem has been fixed.
The STD_CopyLString function and the STD_CopyLStringZeroFill function were not returning the correct value. This problem has been corrected.
Added character class as a supported format for the string scan function group (such as STD_TSScanf).
The linefeed code of the bash script in $NitroSDK/tools/bin has been changed from CRLF to LF to match the change in the bash specification.
Added a description of the effective range of the configuration parameter for the Reject line.
The following changes have been made to the wh sample library in $NitroSDK/build/demos/wireless_shared.
WH_Initialize function was incorrectly being called twice or more. This problem has been corrected.
wh with a callback specified in the WM_SetIndCallback function, it was uncertain which callback would be specified (from wh or WM_SetIndCallback.)WH_SetIndCallback function has been added.
$NitroSDK/build/demos/wm/wireless-all and $NitroSDK/build/demos/mb/multiboot-Model sample demos, if another download child attempted to connect to a multiboot parent right before a multiboot child started reconnecting to a parent, the second child was considered connected for a short time, even if the TGID was different. As a result, the proper child could be rejected. This bug has been fixed by allowing multiple reconnection attempts in such cases.
None.
(2006/08/28)
Added a note that CARD_GetRomHeader can obtain the correct information only with the production DS.
The antialias ON/OFF display in the sample demo $NitroSDK/build/demos/gx/UnitTours/AntiAlias was incorrectly displayed in the initial state (and only in the initial state). This problem has been fixed.
Added the OS_CheckFunctionCostBuffer and OS_CheckStatisticsBuffer functions to check whether the buffer used for the function cost calculation is full.
The backlight occasionally turned off when a DS card was removed during wireless communications. This problem has been fixed.
The following changes have been made to the individual sample library $NitroSDK/build/demo/wireless_shared.
None.
(2006/08/17)
The DS would not power down properly when a DS card was removed during wireless communications with the cover closed. This problem has been fixed.
When the status of a divider was restored using the CP_RestoreContext function inside an interrupt, the status of the divider was occasionally not completely restored at the completion of the interrupt.
To correct this issue, a wait was added in the CP_RestoreContext function.
The precautions regarding the use of CP functions inside interrupts were included only on the NITRO-SDK Function Reference Manual pages for the CP_SetDiv function, the CP_SetSqrt function, and the CP_RestoreContext function. A caution and sample code were added to the CP overview page and the NITRO-SDK Function Reference Manual pages for the other CP functions.
Furthermore, a link to this precaution was added to all the NITRO-SDK Function Reference Manual pages of functions that use a divider internally.
If a soft reset was performed with a Game Pak inserted after first powering up without one, that Game Pak would actually be recognized. This occurred due to the fact that the Game Pak recognition was performed at the time of the soft reset in addition to the usual DS startup. This problem has been fixed.
The function OS_SleepThreadDirect, capable of putting a specified thread directly into Sleep Mode, has been added.
Made changes so that the thread switching process of the OS_RescheduleThread function is executed with interrupts disabled.
Added a wait process so that the default V-count value is constant at program startup.
Some code in the PRC SuperFine algorithm was using the divider without having interrupts disabled. This problem has been fixed.
Function specifications have been changed so that the number of source characters that have actually been converted can also be retrieved in the same manner as the number of characters actually stored after conversion.
The WBT_CMD_REQ_GET_BLOCK_DONE notification was not being issued at the time of completion. This occurred when using the WBT_CMD_PREPARE_SEND_DATA notification with a NULL buffer specified for the WBT_RegisterBlock function. This problem has been fixed.
It was not possible to manage the connection status normally with the $NitroSDK/build/demos/wbt/wbt-1 sample demo when disconnection and connection was carried out repeatedly and the same mode was selected two or more times. This problem has been fixed.
The WM_SetWEPKey/Ex function would not function normally if NULL was specified for wepkey when the wepMode was WM_WEPMODE_NO. This problem has been fixed.
The wepMode would not reset in certain cases, such as when the status changed from parent to child. This problem has been fixed.
A bug was found where the wepMode of the parent attempting a connection was being set to the child side. This has been changed to reflect the value of WM_SetWEPKey/Ex function called from the child.
The following changes have been added to the wh sample library located in $NitroSDK/build/demo/wireless_shared.
WH_ChildConnectAuto, which searches for the parent with a given MAC address and automatically establishes a connection, could not be canceled normally. This problem has been fixed.
None.
(2006/07/25)
In certain instances, the console did not power down when the card was removed with the clamshell closed.
This problem has been corrected.
During the ITCM/DTCM allocated area overflow check using the lcf template file, the allocated area had been calculated as non-overlapped. This was still seen when an overlay area was configured in ITCM/DTCM and the area was actually overlapped through the use of overlays.
In certain cases, this resulted in errors when free space was still available.
Because the ITCM/DTCM size check process with added overlay is currently not implemented very well in the lcf template, the overlay area will not be part of the used area check.
For this reason, those who create applications must pay careful attention to the management of the size of the overlay region on ITCM/DTCM.
Specifically, attach a dummy variable at the end of the ITCM/DTCM region and check whether the variable address is out of bounds.
In the NITRO-SDK Function Reference Manual documentation for MATHCompareFunc, the description given under "Return Values" was the opposite of what should have been written. This problem has been fixed.
Following the changes described in Note 39-05, the MATH_QSortStackSize function was changed to not return a value less than or equal to 0.
In the $NitroSDK/build/demos/mb/multiboot-PowerSave sample, the MB_SetPowerSaveMode function was not actually being called. This problem has been fixed.
The default lifetime value used for wireless control within the MB library is now the same as that set for the WM library.
The following modifications have been made to the character code conversion functions.
The following modifications have been made to the VIB library.
The WH_SetSsid function has been added to the WH sample module in $NitroSDK/build/demo/wireless_shared/wh.
When terminating a parent using the WM_EndParent and WM_Reset functions, a new child would sometimes connect immediately after the parent disconnected as part of termination processing. The specifications have changed so that the newly connected child is now automatically disconnected in such cases.
The WM_DISCONNECT_REASON_NO_ENTRY notification will be sent to the child as the reason for that disconnection.
None.
(2006/07/07)
Automatic DS card removal detection did not work properly on the ARM7 processor side if a DS card was removed immediately after the program started. This problem has been fixed.
Added a note to the documentation of AGB backup access in the NITRO-SDK Function Reference Manual stating that IS-NITRO-DEBUGGER Version 1.66 and earlier cannot properly access the AGB backup device.
Numerous errors were corrected in the following document describing AGB cartridge backup access for the Nintendo DS.
$NitroSDK/docs/TechnicalNotes/AboutAGBBackupforDS.pdf
We ended support for the older versions of CodeWarrior, namely, version 1.0.2 and earlier, in the common definition file commondefs.cctype.CW used by the make system.
Consequently, the supported compiler is version 1.2 or later.
The function would not execute normally if the number of pieces of data to be sorted was 0 or 1. This problem has been fixed.
When compressing data using the MI_CompressLZ or MI_CompressLZFast functions, the compression failed if the data after compression was larger than the data before compression. When this occurred, a 1byte out-of-bounds access was seen in the compression target buffer.
This problem has been corrected.
8-bit versions of functions for Endian conversion have been added.
These have been created to standardize the look of the source code. They do not perform an actual conversion.
Due to an error in the conditions set by the exception handler, there was a problem such that the user-specified exception handler could not be called when a program was executed by loadrun.
This has been fixed so that the correct conditions are used.
During function cost calculation, an interrupt occasionally recorded a new cost calculation record during the _PROFILE_ENTRY and _PROFILE_EXIT function input/output record save operation. This prevented accurate cost calculations. The issue was circumvented by banning interrupts in the appropriate section of os_functioncost.c.
As a result of the changes described in "Note 36-13: (PM), Changes to the PM_ForceToPowerOffAsync function," the device would not power down when a card was removed while the LCD was turned off even if the device was closed because PM_ForceToPowerOffAsync could not be called while interrupts were disabled.
This problem has been fixed.
Parts of the description given for PM_GoSleepMode in the NITRO-SDK Function Reference Manual did not follow guidelines. This has been corrected.
There have been cases where the RTC alarm interrupt stopped working after recovering from sleep mode if the RTC alarm was not included in the recovery parameter.
This problem has been corrected.
An error in the documentation for STD_CopyLString in the Function Reference Manual has been corrected.
The STD_CopyLString function has been changed to operate in the same manner as the strlcpy function since it was implemented under a different specification from the standard strlcpy.
The function return value has been changed from a 'char' type pointer, which indicates the copy target pointer, to an 'int' type value, which returns the length of the source string.
Also, the old STD_CopyLString function, which was implemented differently from strlcpy, has been added as the function STD_CopyLStringZeroFill. The return value has been changed to a value of type int that indicates the string length of the copy source just as STD_CopyLString does.
The difference between these two functions lies in the fact that, if the copy size for STD_CopyLStringZeroFill is larger than the source string, the difference is padded with NULLs.
Functions for performing conversion between Shift_JIS and Unicode strings have been added to the STD library.
We have also added the demo, $NitroSDK/build/demos/std/unicode-1, to show how to use these functions.
Beginning with CodeWarrior 2.x, a symbol search target overlay group may be specified when linking.
The lsf file format was extended and the SearchSymbol command supported in order to support this feature.
The makelcf command and lcf template file were also modified in line with this change.
For details, see the makelcf manual.
With this change, CodeWarrior 2.0 is now officially supported.
A description of the -f option has been added to the documentation for the compstatic tool in the Function Reference Manual.
Part of the ROM format has been changed to support the new 1Gbit/2 Gbit ROMs. For a ROM image of 1Gbit or larger, a fixed size area of the top level became a system reserved area.
Beginning with NITRO-SDK 3.2 PR, the ROM format output that conforms to this new specification will be the default setting for makerom.
Add -V1 to the makerom options to output a ROM image in the old format that was used before NITRO-SDK 3.2 PR.
We have made an addition to the rsf file, which specifies the operation of the makerom tool, to check whether the given RomSize and RomSpeedType combination can actually be made into a ROM.
If the RomSpeedType is MROM, the RomSize must be 512 Mbit or less.
If RomSpeedType is 1TROM, the RomSize must be 128 Mbit or more.
Added the following modifications to the WM sample demo.
$NitroSDK/build/demos/wireless_shared/wfs. The internal status of WFS would become abnormal if the WFS_Start function was called before the initialization process of the WFS_Init function had completed.The state check inside the WM_EndDataSharing function has been deleted in line with the change described in Note 39-23.
The link level value that can be retrieved using the WM_GetLinkLevel function has been adjusted for situations where a Wii console is the MP parent.
A process for calling the WM_EndDataSharing function has been added inside both the wc and wh Reset functions. This was done because the WM_EndDataSharing function was not called by either the wh or wc sample libraries located under $NitroSDK/build/demo/wireless_shared.
When a WM library function was called from a different thread or an interrupt handler during the execution of the WM_Init function, initialization was taken to be completed even if it was not. This created the risk of unexpected or illegal operations.
A similar state management problem was seen in the WM_Finish function as well.
These problems have been fixed.
A problem with the port callback initialization in WM initialization function resulted in unnecessary warnings. This problem has been fixed.
The internal state of WM would occasionally become invalid if repeated connections and disconnections were made frequently. This problem has been fixed.
None.
(2006/05/02)
Variables adjacent to the transfer destination buffer used for DMA transfer from ROM were being affected by cache operations if the buffer cache line was not aligned on a 32-byte boundary. This has been corrected.
Added functions to the CTRDG library to access the backup device installed in the AGB cartridge.
The CTRDG_SetPhiClock and CTRDG_GetPhiClock functions have been created for setting and getting the clock value output from the PHI terminal of the cartridge.
MI_SetPhiClock and MI_GetPhiClock provided the same functionality in previous versions, but this was changed to CTRDG_ when categories were reviewed.
Even for internal operations, the CTRDG_SetPhiClock function was changed to set the clocks of both the ARM7 and the ARM9.
Previously, it changed only the setting of the ARM9. However, the clock output pattern would change when moving the cartridge access right to the ARM7.
The operation of the CTRDG_GetPhiClock function for getting the clock settings is the same as the MI-GetPhiClock function.
Processing would not complete if the callback function set using CARD_SetPulledOutCallback returned FALSE and an attempt was made to access ROM files using a function like FS_OpenFile before the CARD_TerminateForPulledOut function could be called. This problem has been corrected.
This problem did not occur when loading a file table into memory using FS_LoadTable.
Changed FX_Mul so that a message was displayed by SDK_WARNING if digits overflow.
Additions were also made to the function reference page.
Correct results could not be obtained when the value passed to this function was greater than a particular value. It was changed so that a message is displayed by the SDK_WARNING macro when the value is greater than that particular value. This problem has been fixed.
Additions were also made to the NITRO-SDK Function Reference Manual page.
Added a note to the NITRO-SDK Function Reference Manual page for the G2_SetBlendAlpha function that a backdrop cannot be specified for the first target screen.
This function is used when sorting using the MATH_QSort function. A note was added to the NITRO-SDK Function Reference Manual page for MATHCompareFunc stating that 0 must be returned if the two elements being compared are equal.
The problem where out-of-bounds access would occur during LZ compression that was revised in Note35-04 is not reflected in MI_CompressLZ, which is the low-speed version of the LZ compression function.
This problem has been corrected.
A problem was corrected where OS_GetConsoleType might return a value that differs from that described on the function reference page.
When using CodeWarrior 2.0 in the $NitroSDK/build/demos/os/exceptionDisplay-2 sample demo, the required function would be dead stripped. This problem has been corrected to explicitly prevent the dead stripping.
The stroke order for the Japanese character "GE" in the demo figure dictionary data was incorrect. This problem has been corrected.
- Provisional support for CodeWarrior 2.0. However, accompanying changes will have no effect on current applications.
We plan to officially support the extended language codes in the next release.
(2006/04/11)
Made the Card Library compatible with the 8 MB Flash Backup Device. Added CARD_BACKUP_TYPE_FLASH_8MBITS to the CARDBackupType enumerated type.
The NITRO-SDK Function Reference Manual and sample demos were updated accordingly.
Data placed in a .bss section that did not include initial values was accidentally being placed in the .data section. This occurred because a .bss section had not been specified in the .itcm/.dtcm/.wram section.
Changed $NitroSDK/build/tools/makelcf and $NitroSDK/include/nitro/section.h. Changed the .template files found under $NitroSDK/include/nitro/specfiles and $NitroSDK/build/components/ichneumon. Added a .bss section to .itcm/.dtcm/.wram.
A NITRO-SDK build error would sometimes occur depending on the version of the sed command that was run. This problem has been corrected.
Added descriptions of the MTX_Copy* functions to the FX category of the NITRO-SDK Function Reference Manual.
The following were added to the NITRO-SDK Function Reference Manual:
Added 0xFF, an undefined geometry command, as the dummy command G3OP_DUMMY_COMMAND.
It has been confirmed that the number of command cycles corresponding to each source increases when an environment map is used.
Information about this was added to the geometry command cycle list in the NITRO-SDK Function Reference Manual.
Added a group of functions for reading and writing memory with full awareness of little-endian and big-endian issues.
An error would be returned if the heap handle specification was OS_CURRENT_HEAP_HANDLE.
This problem has been fixed.
Corrected a mistake in the graphic about arena management and memory allocation in the OS arena overview in the NITRO-SDK Function Reference Manual. Also added descriptive text.
Adjusted stack processing so that the stack pointer is always aligned on an 8-byte boundary during a function call.
Corrected a problem with the specification changes given in Note 36-13.
Added the SND_SetTrackMuteEx function for selecting the processing to apply to a sound that is played while a sequence track is muted.
Changed the description for getting the authentication code on the NITRO-SDK Function Reference Manual page for the attachsign tool.
When an attempt was made to convert ppm files created with Photoshop (using a NetPBMformats plug-in), the message "Cannot convert file "xxxx.ppm" was displayed and conversion failed.
The problem was due to the fact that the processing implemented for analyzing file headers did not fully cover ppm specifications.
This problem has been fixed.
Several ppm files that could not be converted previously can now be converted.
This fix has no impact on the ppm files that could already be converted correctly.
The SVC_WaitVBlankIntr function, which was deleted from the source code for all sample demos in the NITRO-SDK (as described in Note 36-15), was being used in the pulse_vib sample demo. Consequently, this function was changed to OS-WaitVBlankIntr.
Furthermore, the specifications were changed so that the sample does not stop even if parameters that violate restrictions on the Rumble Pak library are entered.
If the number of children specified by the user (WH_CHILD_MAX) was less than WM_NUM_MAX_CHILD, the WM_GetSharedDataAddress function would be called instead of WH__CHILD_MAX. This problem has been fixed.
Added the sample demo $NitroSDK/build/demos/wm/wireless-all to show the comprehensive use of WM library functions.
Added the following modifications to the WM sample demo.
$NitroSDK/build/demos/wireless_shared/wc.
$NitroSDK/build/demos/wireless_shared/wh WH sample module can be set in wh_config.h as WH_MP_FREQUENCY.
- Added a series of functions to the CTRDG library for accessing the backup device installed in the AGB cartridge.
However, correction functioning is not guaranteed because verification of these newly added AGB backup access functions is not complete.
We plan to officially support the extended language codes in the next release.
- Provisional support for CodeWarrior 2.0. However, accompanying changes will have no effect on current applications.
We plan to officially support the extended language codes in the next release.
(2006/03/14)
In the past, it was not possible to execute pull-out detection of another device when continuously locking one of the card or cartridge buses using the OS_Lock* function over an extended period of time. This has been changed in the current release so that pull-out detection can be performed.
Specifications have been changed when the CARD_CheckPulledOut function is called multiple times so that a callback function is not called every time. The callback can now be called only once when calling the CARD_CheckPulledOut function or because of ARM7 pull-out detection.
In order to avoid sudden write access to the AGB cartridge region, processing for changing the initial settings of the protection region have been added to the CTRDG_Init function. When writing to a cartridge, cartridge information must be checked and the CTRDG_Enable function must be called.
Note: Processing will be forcibly stopped when outputting a debug string using OS_Printf or another function unless you are using IS-NITRO-DEBUGGER version 1.65, which is compatible with this function.
The function CTRDG_CheckPulledOut has been added for quick cartridge pull-out detection from the ARM9.
Changes were made so that correct settings are made by the G2_SetBG3ControlDCBmp function before the GX_LoadBG3Bmp function when using the sample demo $NitroSDK/build/demos/gx/UnitTours/2D_CharBg_Direct.
There were incorrect descriptions of the bitmap BG in the NITRO-SDK Function Reference Manual information for the G2_GetBG2ScrPtr and G2_GetGB3ScrPtr functions. This problem has been fixed.
MB_FAKESCAN_PARENT_BEACON was added to the events about which the MBFakeScanCallbackFunc callback receives notification. This notification is sent each time an MB parent beacon is received.
In line with this, processing for using the MB_GetUserVolatData function with the sample demos multiboot-Model and fake_child has been added.
The magicNumber and ver members of gameinfo, which should usually be specified inside the MB_ReadMultiBootParentBssDesc function, remained uninitialized. This problem has been fixed.
The changes described in Note 20-08: were not applied to the clone boot sample. Further, retry was impossible if even one attempt at connection to the parent failed when reconnecting to a parent after a child's boot. This problem has been fixed.
The following document about the MB library has been updated.
$NitroSDK/docs/technicalNotes/AboutMultiBoot.pdf
A note was added to the NITRO-SDK Function Reference Manual explaining a restriction that does not allow specifying extended main memory as a buffer for storing sampling results when performing microphone auto-sampling. No change has been made to library operations.
The constant PM_AMPGAIN_DEFAULT used inside the PM_GAINAMP_DEFAULT macro was not actually defined. This has been corrected and PM_AMPGAIN_DEFAULT has been added to the PMAmpGain enumerator type.
When an application attempts to turn off power to the DS unit, the DS main unit will occasionally restart if main power was turned off during the LCD OFF status.
The specifications of the PM_ForceToPowerOff and PM_ForceToPowerOffAsync functions have therefore been changed so that power is turned off after the LCDs are turned on.
When using wildcards to specify files to be stored in ROM with makerom, the order in which the files were stored depended on the order that the entries appeared in the PC file system. Consequently, the order in which files were stored would change across different PCs regardless of the fact the same application was being built.
This problem was fixed so that files are now sorted by name before being stored when using makerom.
The VIB library has been added to control the Rumble Pak option cartridge for the Nintendo DS.
We fixed the following problems with the WFS sample module compiled in $NitroSDK/build/demos/wireless_shared/wfs.
The fact that the following commands can be directly issued from one child to another was described incorrectly in the NITRO-SDK Function Reference Manual. This problem has been fixed.
The item "Overview" was added to the WBT library NITRO-SDK Function Reference Manual page.
Specifications were changed so that a Null response would not be returned from children in the middle of MP communication as described in Note 30-06. However, this would occasionally result in unstable operations depending on the environment. Consequently, the change described in Note 30-06 has been canceled and the previous specification has been restored.
In addition, instead of allowing Null responses from child devices, if a parent device receives a Null response from a child device, it assumes that the child device had a communication failure.
Since the WM_SetMPInterval function has been added, excess load problems on the child side should not result even if changes are made later on to allow Null responses to be returned.
The definition of the WMGameInfo structure has been changed. The version field was eliminated and the name was changed to magicNumber. The magicNumber field is fixed at 0x0001 when used as a DS beacon. In addition, the ver field has been established using one byte from reserved memory.
In the current version, the ver field is always 0. In the future, this will increase as the format of the WMGameInfo structure changes. To ensure backward compatibility in the future, there must be no restriction on operations based on checking the ver field. Due to these changes, it is necessary to re-write programs that accessed WMGameInfo.version.
In addition, the name of the field gameNameCount_attribute has been changed to attribute. Although this field can be accessed using the old name, be sure to use the new field name from now on.
In addition, support of the compile switch WM_GAMEINFO_TYPE_OLD, which is never used, has ended due to this change.
WM_IsValidGameBeacon and WM_IsValidGameInfo functions were added to determine whether or not the scan result beacon is that of a DS wireless play parent. Internally, a determination is made whether WMGameInfo.magicNumber is correct. In addition, each WM demo has been changed to use this function.
Communications would be discontinued after a set time interval and the MP lifetime would run out when the MP communications option minPollBmpMode was enabled. This problem has been fixed.
Only titles that perform special communications using minPollBmpMode are affected by this problem.
This document about the WM library has been updated:
$NitroSDK/docs/technicalNotes/AboutWirelessManager.pdf
Corrected the descriptions of macros where () were not attached to arguments.
This change has no effect as long as the arguments being used do not change functionality based on the presence or absence of parentheses.
The following macros have been changed:
None.
(2006/01/16)
Added overviews to the NITRO-SDK Function Reference Manual pages in the CARD library.
Added a page for the packnlf tool to the NITRO-SDK Function Reference Manual.
The code style has been unified regarding indents and carriage returns in the library and demos.
There was a possibility when using the MI_CompressLZFast function for LZ compression that there would be out-of-bound memory accesses.
The same problem was found in ntrcomp.exe after NITRO-SDK 3.0 RC2. There was also the possibility of unusual termination or a slight increase in the size of compressed data.
These problems have been fixed.
An infinite loop inside the library would result if the cartridge bus was locked when the OS_ResetSystem function was called because this function internally accesses cartridges. This problem has been fixed.
This problem appears only in NITRO-SDK 3.0 RC3.
Changes described in Note 32-23 resulted in the display of garbage characters on the startup screen. This problem has been fixed.
The stroke order of the Japanese character "KE" in the figure dictionary data for the demo was wrong, so "KE" in the figure dictionary demo was corrected.
Changed the debug output of the wh, wfs, and wc sample libraries in $NitroSDK/build/demo/wireless_shared to display "0x" before hexadecimal numbers.
MP communications could fail easily depending on the environment. Improvements were consequently made by making changes to the communications internal parameters.
None.
(2005/12/26)
The following inline function groups which perform bit operations were added:
When a small buffer size was designated with the MB_ReadSegment function and the distribution data was dynamically loaded from the archive, block transfer became unable to proceed. This problem has been fixed.
Transfer rates were adversely affected where WM_ERRCODE_SEND_FAILED was issued frequently on the parent device in bad communication environments during block transfers in the MB library. This problem has been fixed.
The ARM946E-S, a CPU on the Nintendo DS, does nothing when the pld instruction is executed. This information has been added to the NITRO-SDK Function Reference Manual page for the DC_TouchRange function, which executes that instruction.
Depending upon the initial value of the thread structure initialized with OS_CreateThread, an access exception error would be raised when the thread was executed. This problem has been fixed.
A compilation error prevented a correct build when the macro switch NOT_USE_ALLOC in the sample source of the $NitroSDK/build/demos/wbt/wbt-1 sample demo was enabled. This problem has been fixed.
The value of the result member of the arguments to the user callbacks that indicates command completion was not being set. This problem has been fixed.
The configuration of each of the MP communication parameters added in 3.0 RC2 was not functioning properly. This problem has been fixed.
Previously, all of the SDK demos that used WH referenced $NitroSDK/build/demos/wireless_shared/wh/wh_config.h directly and had shared configurations. Now, each demo has its own individual configuration.
Because of this change, the location of wh_config.h has been changed to $NitroSDK/build/demos/wireless_shared/wh/default/.
Internal operations are sometimes affected immediately after a disconnect. The WM library was modified to address this.
None.
(2005/12/05)
CARD_RESULT_TIMEOUT can be returned even if the backup write succeeds if the backup write is small and it executes during wireless communication. This problem has been fixed.
Added the following group of functions for controlling access permissions to AGB cartridges.
Added the SDK_VERSION_NUMBER macro for converting the SDK version to a numeric value.
Also added the constant SDK_CURRENT_VERSION_NUMBER to represent the current SDK version.
Added SDK_INLINE and SDK_DCL_INLINE as macros for specifying inline functions.
This allows the format of inline specifications to be changed all at once.
The entire NITRO-SDK must be rebuilt if these macros are changed.
Code size can be reduced by changing these macros from static inline to inline. This applies only when using the environment with the compiler version in which the inline function problem was fixed and only when using functions that changed from inline to static inline.
Since changing these macros could produce uncertain results, base the decision to use them on the needs of the application.
Strings could not be included in a banner file if the start of the game title or descriptive text happened to match a specified parameter described in the bsf file used by the makebanner tool. This problem has been fixed.
$NitroSDK/tools/bin/ntexconv.exe has been updated to the version of netconv.exe inside the latest release of the TXLib package.
Although the functioning of the SDK does not change because ntexconv.exe is used only during the creation of icon images, the version of ntexconv.exe in the SDK can now be used even when creating textures.
The paknlf tool has been added. This tool collects all file specifications referenced by a .nlf file as absolute paths and outputs them as a ZIP file.
Although this tool was included it NITRO-SDK 3.0 RC, it was not mentioned in the changelog.
The following correction was made to the MBP sample module included in $NitroSDK/build/demos/wireless_shared/mbp:
MBP_StartRebootAll and the last child still connected cancelled its connection just as the other children were attempting to reboot. This problem has been fixed.
The buffer size required to call the MB_FakeInit function has been defined as MB_FAKE_WORK_SIZE. This value is defined as the size of the data retrieved by the conventional MB-FakeGetWorkSize function.
Applications could fail to detect that they were sharing the same GGID when using wireless play and download play. This could happen because the WM_ATTR_FLAG_MB flag remained disabled while only the WM_ATTR_FLAG_ENTRY flag was enabled for the first beacon that was sent by an MB parent device.
The function M_CompressLZFast, which requires a work buffer of about 9 kB, has been added to perform LZ compression at rates several times faster than MI_CompressLZ, the function that has been available for LZ compression.
NITRO_ENABLE_ARM7_PRINT has been added as a build switch for setting the debugger to automatically call the OS_InitPrintServer and OS_PrintServer functions from inside the OS library.
Standard specifications are used if this switch is not specified.
This build switch is enabled only for the OS library. The OS library must be rebuilt if the setting is changed.
SVC_WaitVBlankIntr does not release resources to low-priority threads. Since this would cause problems depending on how the function was used, a call to SVC_WaitVBlankIntr is now automatically replaced by a call to OS_WaitVBlankIntr. Note, however, that this replacement is made using defines inside a header file. The desired result is achieved only after the first rebuild.
The result of this change is actually a slight increase in overhead until V-blank interrupt wait operations are executed. Although there is almost no effect on application behavior, if you must use conventional system calls for some reason, you can disable this change by defining the environment variable NITRO_SVC_WAITVBLANK_COMPATIBLE. Be sure to verify your code thoroughly since the problem with threads remains unresolved if you do this.
or Note 32-18: Although it was reported in Note 32-18: that the SVC_WaitVBlankIntr function could be overwritten by another definition using weak symbols, the original functionality has been restored because the need for weak symbols has now been eliminated.
Deleted OS_InitPrintServer and OS_PrintServer from all NITRO-SDK sample demo source code.
Deleted PXI_Init from all NITRO-SDK sample demo source code.
Demo operations are not affected by this change.
The parts of all NITRO-SDK sample demo source code that used to call SVC_WwaitVBlankIntr have been changed to call OS_WaitVBlankIntr.
Demo operations are not affected by this change.
0x240000 is used for the lcf template definition even though the start address of the extended main memory arena given on the OS arena overview page is 0x23e0000. (If there is an overlay, an even higher address results.)
The definition 0x23e0000 is used so as to match the information on the OS overview page.
We fixed the following problems with the WFS sample module compiled in $NitroSDK/build/demos/wireless_shared/wfs.
Processing inside the sample demo below, which uses the WFS sample module, has been changed so that parent disconnections during a read by a child calling FS_ReadFile can be detected.
Corrected a problem in the $NitroSDK/build/demos/gx/UnitTours/{2D_CharBg_3,Sub_CharBg_3} sample demo where execution would stop due to an ASSERT if the object was shrunk too much.
Previously, the V alarm count was fixed at 260 for the parent and at 240 for children during frame synchronous communication mode when beginning to prepare the first MP communication of each frame. The WM_SetMPTiming function has been added to affect this setting. Due to restrictions on the implementation, these values must be set either in the range 220 to 260 or the range 0 to 190.
The ARM7 operates actively during communication processing and frequently blocks the ARM9 from accessing main memory. The average operational performance of the ARM9 can sometimes be improved by adjusting communication timing to help alleviate the situation. The conventional setting values are used as defaults unless other settings are explicitly made.
Until now, the size of transmissions sent using MP communication have been fixed at values given by the parentMaxSize and childMaxSize fields of the WMParentParam structure that the parent sets with the WM_SetParentParameter function before communication starts. The parent send size and child send size can be set using the functions WM_SetMPParentSize and WM_SetMPChildSize, respectively.
The send size of the parent and child are initialized to the values set for parentMaxSize and childMaxSize in the WMParentParam structure when the parent executes the WM_StartParent function. Smaller values than these can be set using the WM_SetMPParentSize and WM_SetMPChildSize functions. However, the default initial values cannot be exceeded. Setting the parent send size on the child side is meaningless. However, the setting for the child send size is used to overwrite the child send size setting on the parent side every time MP communications are carried out.
There is not much advantage in changing the setting for parent transmissions since the smaller the amount of data, the shorter the radio signal output. Still, the child side always sends out a radio signal with the number of bytes designated in childMaxSize. Thus, by reconfiguring the necessary size, the transmission time can be reduced and communications can be stabilized. Given the current implementation, if an amount of data larger than the send size (as modified using these functions) has already been configured by the WM_SetMPDataToPort function, that data will not be sent. Instead, it will just continue to collect in the send queue.
The function WM-SetMPInterval has been added to allow setting the time interval between one MP communication and the next. This occurs during MP communications in continuous communication mode and beginning from the second transmission in frame synchronous mode. This can be specified independently for the parent and children in units of microseconds.
The default values are 1000 microseconds for the parent and 0 microseconds (no interval) for the children. Throughput can be increased by adjusting this value. However, throughput may also be worsened due to dropped data if the MP communication interval for the parent is shorter than the time it takes the children to process the received data. Generating unnecessary resends will also adversely affect the bandwidth efficiency.
A feature for displaying information about the parent to be connected to has been added to the parent list window in the sample demo $NitroSDK/build/demos/wm/dataShare-Model.
The text output screen displayed at the startup of the sample demo $NitroSDK/build/demos/wm/dataShare-Model would sometimes break. This problem has been fixed.
Although the maximum number of MP communications per frame (including resends) used to be fixed at six, this can now be set to other values. Set WMMMPParam.maxFrequency using WM_SetMPParameter. The processing of the fixFreqMode argument by WM_StartMPEx has been changed so that maxFrequency is also set to the value of mpFreq.
If a send fails, a correction is applied to the receive signal strength level that can be retrieved by WM_GetLinkLevel. However, this correction is performed differently for the parent than for the children. The receive signal strength level for the parent and for the children can differ greatly even under the same conditions.
To solve this problem, the standard to detect failed transmission of a parent was relaxed. In this way, the reception strength level of the parent became closer to that of the child.
A special option has been added to ignore various validity checks (pre-check of the send/receive size setting value, send/receive buffer size, and communication time limit of 5600 microseconds) that were done in the WM_StartMP function. Set WMMPParam.ignoreSizePrecheckMode to TRUE using the WM_SetMPParameter function before calling WM_StartMP.
Combining this feature with the WM_SetMPParentSize and WM_SetMPChildSize functions allows the send size to be adjusted according to changing conditions, such as the number of children that are connected. In the application, do not to exceed the communication time limits or the send/receive buffer size. If the send buffer size is insufficient and an attempt is made by the parent to start MP communications, this will be detected at execution time. If the condition continues, communication will be cut off because of the timeout on MP lifetime.
Unexpected behavior was reported where several event counters were cleared when accessing buffers located in a particular address space in wireless hardware.
Consequently, the event counters may have a value that is less than the actual event counts.
Some event counters retrieved by WM_GetWirelessCounter may not have the correct values.
Information has been added to the NITRO-SDK Function Reference Manual about this.
None.
(2005/11/07)
When an EEPROM device was being used for backup, there was an occasional problem with abnormalities in the initial values of the hardware internal status at startup. A process was added to deal with this issue.
Added detection of whether the card had been removed after every read performed by the CARD_ReadRom function or the CARD_ReadRomAsync function.
As a result, the application will no longer refer to invalid data before it receives a notification of the remove-detection callback.
Modified the Card Library to support the 4 MB Flash Backup Device. Added CARD_BACKUP_TYPE_FLASH_2MBITS to the CARDBackupType enumerated type.
The NITRO-SDK Function Reference Manual and sample demos were updated accordingly.
The #pragma define_section parameters were incorrectly written as being delimited by commas, namely: “#pragma define_section DTCM ".dtcm",".dtcm",abs32,RWX.”
They were changed to be delimited by a space, namely: “#pragma define_section DTCM ".dtcm" abs32 RWX.”
Correct any other erroneous descriptions like the one above in the same way.
Added the xml2env tool to convert resource data for the ENV library written in XML format to the C source file format. Also added the init2env tool for converting resource data for the ENV library written in INIT format to the C source file format.
In the NITRO SDK 3.0 PR - 3.0 PR4 packages, there was a flaw in the script used when creating packages that resulted in the THUMB version ichneumon components not operating correctly.
This problem has been fixed.
(DevEnv) Changed the version of CodeWarrior used for the SDK package build to 1.2SP1.
Also made it so that the build numbers of the CodeWarrior compiler and linker used to build to $NitroSDK/include/nitro/version.h are recorded.
Added an explanation of the compilation target to the function information in the NITRO-SDK Function Reference Manual.
Added a reference to the ENV library
Changed the ENV_Init function. Added the function ENV_AppendResourceSet. Previously, ENVResource was passed as an argument to the ENV_Init function. Now, several ENVResources can be registered.
The condition parameters of the ASSERT used by G3BS_LoadMtx43 were wrong. This problem has been fixed.
The following correction was made to the $NitroSDK/build/demos/gx/UnitTours/Sub_Double3D sample demo:
The correction described in Note 29-02 was not complete and the same symptoms still appeared occasionally. The problem was corrected again and explanations were added as comments to the SwapBuffers command and the geometry engine.
There was a bug in the MATH_QSort function. It was possible that some values would not be sorted properly in either ascending or descending order after being sorted.
This problem has been corrected.
If the IRQ stack size on the ARM7 side was set to 0 or was negative, the domain was determined by the first position in WRAM. The cause was a mistake in the HI address calculations of the ARM7-specific WRAM arena.
It should have been based on the end of a program domain which occupies the first position of WRAM.
After the fix, the calculations were correct.
However, since the stack area specification was defined with a positive value in the previous mongoose and ichneumon, there functioning is the same whether before or after the correction.
Since the mongoose and ichneumon SDK attachments are used in typical game applications, they are not influenced by this change.
Added the OS_GetTotalOccupiedSize function, which gets the memory size used in the heap.
The existing OS_GetTotalAllocSize function totaled the size of the data area of the memory block being used. The OS_GetTotalOccupiedSize function, on the other hand, also adds in the size of the header portion of the memory block.
When the FINALROM is built, the OS_PutString function was replaced with unreachable code, but the dead code stripping of the argument was not executed.
This problem has been corrected. Now, none of this function is executed and the dead code stripping of the argument is performed.
Conditions are inspected when compiling. The SDK_COMPILER_ASSERT macro was added to generate a compilation error if those conditions are not met.
When waiting for a V-Blank interrupt using the SVC_WaitVBlankIntr system call, the thread called for this function does not stop. There is thus a problem that resources are not obtained by lower priority threads while waiting for the interrupt.
The cause is in the system call. The OS_WaitVBlankIntr function was created as an alternative that stops the thread while waiting for a V-Blank interrupt.
Also, the SVC_WaitVBlankIntr function which calls the system call was made into a weak symbol. It was also modified so that it could be overwritten by another definition.
In functions that take as an argument a pointer to a cache operation function that starts with DC or IC, use const for internal operations that do not change the content.
The functions that were changed are:
In the check stack overflow functions OS_SstIrqStackWarningOffset and OS_SetThreadStackWarningOffest that set the check code in the middle of the stack, the overflow check code set at the bottom of the stack was being overwritten.
For this reason, the stack check was not operating correctly. This problem has been fixed.
In the ROM image, you can get argument data embedded with the tool command buryarg from the program using functions such as OS_GetArgv function and OS_GetOpt. This argument data buffer can now be changed at run time.
See the OS_SetArgumentBuffer function and the OS_GetArgumentBuffer function.
Also, we have made available the OS_ConvertToArguments function for converting a string to an argument data buffer.
The macro that changes both actual time and tick values in functions such as OS_SecondsToTicks and OS_TicksToSeconds was corrected.
Calculations were being done with 32-bit accuracy. When too large argument was given, overflow occurred and the correct value was not returned.
The correction is as follows:
-Internal operations in existing macros have been changed to use 64 bits.
-If you explicitly want to use 32-bit internal operations, the following functions are available:
The Chinese version startup screen, which is displayed with OS_InitChina, has been updated.
When a certain thread registered with the thread queue was terminated by functions such as OS_DestroyThread or OS_KillThread, the information about the thread was removed from the thread queue.
This information includes when that thread terminates another thread while waiting for that thread to end in the OS_JoinThread function.
Until now, deleted thread information remained in the thread queue. As a result, when the OS_WakeupThread function was executed to make all threads in the queue executable, the deleted threads were included also. This caused a bug in the thread list status.
This problem has been fixed.
The pdic2c.pl sample tool used with the PRC demo was in an old format. This has been corrected.
Also, an option has been added to output header files and source files to separate files.
When data including the day of the week is read from the RTC, the day of the week calculated from the date is now returned.
Previously, the value stored in the RTC was returned as is. However, after passing the last date that can be displayed by the RTC -- 12/31/2099 23:59 -- the day of the week information was wrong until the RTC was reset.
With the function SND_CalcDecibel (or SND_CalcDecibelSquare), -723 was returned when the argument was set at 0. This was corrected to return -32768.
Up until this correction, when using the volume modulation, sound could still be heard even if the player volume had been set to 0.
This problem has been fixed.
Created an STD library to handle the string operation related to the API group.
The following functions are included in the STD library:
STD_StrCpy is an alternate name for STD_CopyString.
The system callback notification WBT_CMD_REQ_GET_BLOCK_DONE, which should be generated only when a partner's WBT_GetBlock function finishes, was also being generated by WBT_GetBlockInfo. This problem has been fixed.
Applications that do not use this notification are unaffected.
We fixed the following problems with the WFS sample module compiled in $NitroSDK/build/demos/wireless_shared/wfs.
WFS_Init was called multiple times, the function would still be in the interrupts-prohibited state when it returned. This problem has been fixed.
WFS_Init function is called.
WM_PORT_BT, which is reserved by the SDK as a port number, was being used in the various sample demonstrations using WFS.
Made the channel information on the same parent device change when WMTestToll.srl scans.
There was a mistake in the description on the WM_SetLifeTime page in the NITRO-SDK Function Reference Manual. This problem has been fixed.
The description said that the frame lifetime default value was "no lifetime". However, the correct description is "beacon interval x 5."
When mongoose is used as an ARM7 component, access to the ARM9 main memory during the asymmetric operation of transitioning the state of the WM library is largely inhibited. This problem has been solved by improving the mongoose component.
Note that this problem was not necessarily solved, merely improved.
Added the connectedAidBitmap field to WMPortRecvCallback. The AID bitmap during the current connection is stored there.
WM_STATECODE_PORT_INIT was added to WMStateCode. It was changed so that the port receive callback in this state code is called when WM_SetPortCallback is called. This assumes that the initialization operation is run using the connectedAidBitmap field or the myAid field of WMPortRecvCallback.
In order to maintain connection notification consistency, keep in mind that the callback call by WM_STATECODE_PORT_INIT also happens during an interrupt prohibited state.
Due to this change, there is a possibility that a similar incompatibility with Note 32-38 might occur.
The test API in the WM library has been expanded. This API is used for testing and is otherwise not normally used.
Despite this new API, WM library operations have not been altered when this library is used normally.
However, the WMApiid listing type has been extended by the addition of this API. Bear in mind that programs which depend on the row order of the listing may be affected.
When the parent device maintained an MP connection, the wireless communication feature was stopped after a child device called the WM_EndMP function at a specific time. This problem has been fixed.
This bug appears in the SDK after version 3.0.
When wireless communication has finished, the termination callback for asymmetric functions related to wireless communications will no longer be called.
We know the bug occurs when several child devices are connected using fake_child.
Further, when communication is terminated by an operation from the parent device, this bug is not an issue.
Previously, when WM functions (such as WM_DisconnectChildren) were called and communication was disconnected, a disconnection notification was not generated. WM_STATECODE_DISCONNECTED_FROM_MYSELF has now been added to WMStateCode in the parent to provide a disconnection notification.
Because of this change, there is a chance that an incompatibility may arise.
The state codes that can go into the state field of WMStartParentCallback, WMStartConnectCallback, and WMPortRecvCallback are increasing. Therefore, use caution when stopping the execution of programs when a state code other than one of the known WM_STATECOD_* state codes has been received.
Also, even if DataSharing explicitly disconnects the child from the parent using this notification, DataSharing will not stop.
The following functions were added as a result of this change:
The fixes described in Note 31-24 and Note 30-07 did not fully address the problems. As a result, these problems have been fixed again.
$NitroSDK/tools/bin/ntexconv.exe) is an older version than the ntexconv in the TXLib package of the current release.ntexconv only to create icon images, using an older version does not pose a problem. However, there would be a problem if ntexconv were used to create textures. You are encouraged to use the ntexconv that is in the latest TXLib package.
(2005/09/08)
Added the CARD_CancelBackupAsync function for aborting the asynchronous process on the backup device.
As a result, added CARD_RESULT_CANCELED to the CARDResult enumerated values for processes that were aborted with this function.
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.
Added CARD_RESULT_NO_RESPONSE to the CARDResult enumerated values as a result value for backup manipulation functions.
This is an error value that was split off from CARD_RESULT_TIMEOUT. It is returned when contact with the card appears to be poor.
Added support for overlay groups.
The linker assumes that overlays belonging to the same group are located in the same memory region.
By specifying mutually exclusive overlay modules as belonging to the same group, it is possible to use function calls between overlays to detect errors during linking.
To maintain compatibility, the group with the same name as the current section name is set if the overlay group specification is omitted.
In some cases, if the section description in an lsf file had sections named "<existing section name>" + "_bss," such as "main"and "main_bss," problems would occur.
In addition to "_bss," the same problem occurred with some text strings, such as "_DATA," "_BSS."
This is a lcf.template file problem.
We fixed the *.lcf.template files under $NitroSDK/include/nitro/specfiles.
As a result, you can no longer directly reference symbol information about overlays that existed in previous versions.
Because there may be problems with applications that directly reference symbols, the *.lcf.template files for the older version are for now included in $NitroSDK/include/nitro/specfiles/2.x.
Overwrite the files in $NitroSDK/include/nitro/specfiles as needed.
(When building with make, specify the LCFILE_TEMPLATE variable.)
The official way to obtain information about overlays is to reference the overlay table using the overlay ID as an index.
When an overlay was placed in DTCM, a bug occurred with the arena configuration of the main memory area. This problem has been fixed.
We also fixed the ITCM arena configuration for use with a ITCM overlay.
We added support for overlays of the extended main memory region, which was not possible previously.
The loadrun command that downloads and runs binary data to the IS-NITRO-EMULATOR.
It can be terminated with a timeout or a call to the OS_Exit function.
The nitrorun script calls the buryarg command, which embeds argument data in the binary and the loadrun command at the same time.
This allows execution of the binary in a manner that is similar to passing arguments from the command line.
Added the ENV library, which retrieves a value corresponding to a resource from its resource name.
This is used to provide the program with operating environment parameters. Although the library must be recompiled, it is convenient for rewriting parameters and configuring an environment common to several programs.
Due to the operation changes noted in Note 28-03, the destructor for the global object array in the overlay would not start correctly when unloading the overlay. This problem has been fixed.
Made numerous corrections to the following document explaining the FS library:
There was a bug in the FX_FX64C_TO_F32 macro, which converted from fx64c to f32 types. It did not return a precise value.
This problem has been fixed.
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, the MB_GetMultiBootDownloadParameter function was added to reference the user-defined expanded parameters when downloading.
When reading data from NVRAM, the read failed when the target read buffer address was greater than 0x02400000.
This problem has been corrected.
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.
There was a problem where the upper address of the DTCM arena is determined.
This was caused when a negative value was specified for the stack size in the rsf file.
This problem has been fixed.
Added an explanation of the NitroStaticInit function to the NITRO-SDK Function Reference Manual, in line with the addition made in Note 27-31.
In functions related to OSThread, we determined and changed some "OSThread*" type arguments to be defined as "const OSThread*."
These are the functions that were changed:
Added the OS_GetOpt function, which makes it convenient to obtain strings that start with '-' as program execution options from argument data in binary files (for example, srl files that were embedded using the buryarg tool command).
Parameters should come after the options.
Added code that uses the OS_GetOpt function in the $NitroSDK/build/demos/os/argument-1 sample demo.
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 problem has been corrected.
Added WM_SCANTYPE_ACTIVE_CUSTOM and WM_SCANTYPE_PASSIVE_CUSTOM to WMScanExParam.scanType. These support special usage that limits SSID matching confirmations performed with the WM_StartScanEx function to certain lengths.
When these scanTypes are used, SSID match confirmations will be made only up to the length specified with WMScanExParam.ssidMatchLength.
As a result, we changed the WMScanExParam structure.
In infrastructure mode, by specifying SSIDs using WM_StartScanEx during scans, matching confirmation was performed for only the first eight bytes.
We modified it so that matching confirmation is performed for the length specified by WMScanExParam.ssidLength.
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.
We added a feature that notifies the status code of the communication partner. This partner uses a callback function to help analyze the cause of failure when a connection fails that is attempting to use WM_StartConnect[Ex].
Specifically, we added the wlStatus member to the WMStartConnectCallback structure.
Under normal circumstances there is no need to reference this from the application.
(2005/08/10)
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 3.0 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.
Added the OS_SetThreadDestructorStack function, which specifies the stack used when a thread destructor is executed. If another is not specified, the stack pointer does not change when its own thread is destroyed. When the thread is destroyed by other threads, the pointer changes to the stack's top address.
When a thread that was paused with the OS_Sleep function is destroyed by another thread, the alarm set for the OS_Sleep function is canceled. Previously, because the alarm was not canceled, the alarm handler was sometimes called needlessly or the alarm list was overwritten.
We changed the processing during overload on the child because of internal processing conditions. This is related to Note 29-08. Previously, when the child side ARM was overloaded and the transmit data settings were not on time, a null response was generated. This was changed to no response. As a side effect, when a child machine is overloaded, the receive processing is skipped. This impairs communication efficiency slightly but reduces the load.
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/04)
Corrected the path location that ISD_NITRO_DEBUGGER indicates, which is defined in $NitroSDK/build/buildtools/commondefs.emtype.ISD.
The following correction was made to the $NitroSDK/build/demos/gx/UnitTours/Sub_Double3D sample demo:
The correction described in Note 27-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 modifier has been added to them.
G3_GetDLStart functionG3_GetDLLength functionG3_GetDLSize functionWe added the OS_GetLowEntropyData function, which generates and returns different data each time it is executed based on the system status.
We also added $NitroSDK/build/demos/os/entropy-1 as a demo.
After the transition from the LCD Off state to sleep mode and then back, a discrepancy arose between the actual state and the internal state of the GX library. This has been fixed. (Reference: Note 22-23:(PM) Changed the Recovery Process after Transitioning From LCD OFF State to Sleep Mode)
Added WM_STATECODE_INFORMATION for notification of the callback of WM_SetIndCallback. This provides a notification containing information about the events occurring internally.
The contents of the notification are found in the WMIndCallback.reason callback argument. WM_INFOCODE_FATAL_ERROR is defined as a reason value. This value is used when ignoreFatalError in the WM_StartMPEx function is set to TRUE and a fatal error occurred.
Added the WM_SetPowerSaveMode function, which switches to power save mode during infrastructure communication.
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 problem has been fixed.
Previously, when a child received an MP frame not addressed to it, the WM_StartMP function would receive a notification that the "state" was WM_STATECODE_MP_IND and the errcode was WM_ERRCODE_INVALID_POLLBITMAP. This was changed so that no notification is sent at all.
The MP ACK frame's WM_STATECODE_MPACK_IND notification was changed in a similar way.
This change does not affect sending and receiving using ports.
It was confirmed that programs do not operate when the thumb build version of the ichneumon component is used. This has been corrected.
None.
(2005/07/22)
Added a sample demo that uses the Pictocatch process to $NitroSDK/build/demos/cht/catch-min.
This sample implements only the bare minimum functionality so that it has less code than the previous PictoCatch sample demos.
We added support for precompiled headers for $NitroSDK/include/nitro.h.
The build system precompiles $NitroSDK/include/nitro.h before the build and reads the result while building the file.
This should result in a faster build.
If you want to stop the compilation temporarily, set a value for NITRO_NO_STD_PCHDR.
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.
In the $NitroSDK/build/demos/gx/UnitTours/2D_Oam_256_16 sample demo, a bug made the +Control Pad unusable in the FINALROM build.
This problem was fixed.
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.
Added a mechanism to check for stack overflow in the IRQ mode stack, similar to that in the thread stack.
A check code is written at the top and bottom of the stack (or between, if necessary). By checking if these sections are rewritten, it helps to determine if the stack is filled up to those points.
Below are the functions that were added for this purpose:
Added a mechanism that allows you to pass argument data to the ROM file and then obtain this data in the program.
You can use the $(NitroSDK)/tools/bin/buryarg tool to embed argument data. You can then use the data in a program by calling the OS_GetArgc and OS_GetArgv functions. By using this feature, you can change the program's execution conditions without recompiling.
We added a demo that uses this feature called $NitroSDK/build/demos/os/argument-1.
This feature is provided for debugging purposes and is invalid in FINALROM builds.
We added the OS_KillThread and OS_KillThreadWithPriority functions. These functions terminate other threads. You select which function to use based on whether you want to set the thread priority when terminating the thread.
The difference between OS_KillThread and OS_DestroyThread is whether the thread destructor of the terminated thread is called.
We added a demo that compares these two functions. It is called $NitroSDK/build/demos/os/thread-9.
We implemented thread destructors that call preset functions when a thread is terminated.
The destructors are set using the OS_SetThreadDestructor function.
Thread destructors are called under the following circumstances:
OS_ExitThread function.
OS_KillThread* function.
OS_KillThread* function.
OS_DestroyThread function.
OS_DestroyThread function.
$NitroSDK/build/demos/os/thread-7.
We added a user parameter member to the OSThread thread structure.
The system does not reference or change this area.
This may be used for any purpose in each application.
The following functions are for setting and getting thread parameters:
Previously, the maximum number of threads that could be used by the OS at the same time was 16. (Normally the maximum was 16. However, by rewriting the header definitions, it was possible to vary the maximum from 8 to 32.) This limit has been removed.
The thread-related APIs have not changed.
Reflecting this change, we have added two sample demos that create large numbers of threads: $NitroSDK/build/demos/os/thread-8 and $NitroSDK/build/demos/os/thread-10.
None.
(2005/07/15)
Added the CARD_CheckPulledOut function, which determines status directly from ARM9. In other words, it does not wait for the notification of the result of the card removal detection process that the ARM7 performs periodically.
This function is not needed for normal scenes where the Card is not being accessed. However, in scenes where you need to know without delay that the Card has been removed, you can use this function instead of CARD_IsPulledOut.
Added CARD_BACKUP_TYPE_EEPROM_512KBITS and CARD_BACKUP_TYPE_FRAM_256KBITS to the enumerated type CARDBackupType so the CARD library can support 512 kB EEPROM and 256 kB FRAM as backup devices.
Corrected the cache operations involved in the reading of the cartridge information region during the execution of the CTRDG_Init function.
Up until now, when the cartridge information such as the maker and game code was obtained, incorrect values were sometimes returned. This problem has been fixed.
Added the bin2obj tool for converting binary files into object files.
This tool operates the same way as the BinToElf tool in the CodeWarrior for NINTENDO DS package. You can use either one.
When a build was performed from the CYGWIN command line, the build would fail if the cygdrive prefix was not /cygdrive, the default setting.
Builds are now possible even if the cygdrive prefix has been changed to another value.
In programs that used the LCF template in $NitroSDK/include/nitro/specfiles/ARM9-TS-cloneboot-C.lcf.template, the .sinit sections were not linked and the features of the static initializer could not be used. This problem has been fixed.
With StackSize specified in rsf (linker spec file), subtracting the absolute value from the maximum possible specified size when a negative number was provided as the first parameter was not valid.
This problem has been fixed.
Changed the default value of the SDK_TS_VERSION constant that indicates the PMIC version. The value was 100; it has been changed to 200.
SDK_TS_VERSION = 200 appears in versions E and later for the IS-NITRO-EMULATOR hardware. It corresponds to the PMIC version embedded in the Nintendo DS retail product.
This change does not alter the internal operations of the NITRO-SDK features. However, this could affect applications that use this constant as a build switch for changing behavior (such as sample demos that use the microphone) .
When NITRO_TS_VERSION is specified as the environment variable, SDK_TS_VERSION takes the specified value, not the default value.
NITRO-SDK has an OS and an SPI library prepared for every TS_VERSION.
This is relevant when the development environment uses the TS breadboard and so on, with the owner information in an old save format. However, when the save format is the same as that used for the retail DS system, the library is exactly the same.
When the make system is used, the library for linking is selected automatically based on the environment variable. But in a development environment using an IDE, you need to manually select which library to link.
Nonetheless, except in cases where the development environment used the TS breadboard, and so on, there is really no meaning to selecting a library. Consequently, it is all right to use the library that is linked by default.
Changed the #include search path when building with Makefile to include the directory of the file that called #include.
If the previous search path is required, enter a directive such as MACRO_FLAGS += -cwd proj
inside Makefile.
Added the FS_CreateFileFromMemory function and FS_CreateFileFromRom function to treat a specific memory region or Card as a temporary file to open it.
Also added the sample demo $NitroSDK/build/demos/fs/file-3 that demonstrates the operation of these functions.
Added the FS_End function to return the state to what it was before the FS library was initialized.
When the FS_WaitAsync function was called for a file handle and an asynchronous command was not yet processing in the archive, the archive processing would stop. This problem has been fixed.
When the FS_UnloadOverlay or FS_EndOverlay function unloaded an overlay, the destructor was not called correctly. This problem has been fixed.
This applies to objects when both of the following are true:
*.data section.
The arctangent functions below returned incorrect values when the (x,y) slope was extremely close to 1. This problem has been fixed.
The following correction was made to the $NitroSDK/build/demos/gx/UnitTours/Sub_Double3D sample demo:
When double screen 3D and a heavy load process were put together, the image on the upper screen would occasionally instantly wrap around to the bottom screen (or vice versa). This problem has been fixed.
When the G3C_UpdateGXDLInfo and G3B_UpdateGXDLInfo functions were called from inside functions that manipulate display lists, ASSERT would be applied when a display list was being created that was the same size as the buffer.
This problem has been corrected.
When sorting with the MATH_QSort function, the function would sometimes access the target array out of bounds.
This problem has been corrected.
Replaced the implementation of the SHA-1 functions.
The code size has hardly changed, but it runs approximately twice as fast as before.
The interface has not been changed.
Added functions that perform fast Fourier transforms.
Also added the demos $NitroSDK/build/demos/math/fft-1 and fft-2 to confirm the operation of these functions.
Added $NitroSDK/build/demos/mb/multiboot-wfs as a sample of a child in Single-Card Play using the file system over wireless communication.
For a child booted with the MB protocol, there was a restriction that prevented the use of expanded memory and forcibly set main memory to 4 MB. This restriction has been removed, thus enabling the use of expanded memory by IS-NITRO-EMULATOR and other hardware that has 8 MB of main memory.
Added the userParam member to the MBGameRegistry structure.
Store as much as 32 bytes of any kind of data in this buffer. Use the MB_RegisterFile function to allow a Single-Card Play child to reference this data after startup.
The MI_CompressHuffman function and ntrcomp.exe had a bug that sometimes caused abnormal compression of data that was filled with a single value.
This problem has been corrected.
If the OS_WakeupThreadDirect function was called for a thread that was in the wait state after a call to the OS_Sleep function, there would be problems with the alarms. This problem has been fixed.
There were errors in the list operations on the mutex stored in the OS when the mutex was locked by the OS_TryLockMutex function.
As a result, sometimes the OS_UnlockMutex function would cause exceptions. Problems would also arise when a thread ended while the mutex was still locked. This has been fixed. Note that the OS_LockMutex function (which is different from the OS_TryLockMutex function just mentioned) works correctly and has no problems.
Added the OS_YieldThread function. This function performs thread rescheduling. It also gives executable threads with the same priority level as the current thread an opportunity to execute.
Corrected the internal processes that confirm that the cache has been cleaned/invalidated at program startup for autoload and at the initialization of each segment.
The startup screen display process for Chinese language applications can be modified with SDK_WEAK_SYMBOL and made public with the OS_ShowAttentionChina function. Its implementation can be changed with external definitions.
In conjunction with this, added the sample $NitroSDK/build/demos/os/forChina-fs to show how to load the data for images that are used only at startup from the file system without a static link.
The cause of the bugs mentioned in Note 24-10 and Note 25-16 has been clarified. Along with this, the internal implementation of the functions DC_FlushRange and DC_FlushAll have been changed so that the CPU flush command works properly.
Specifically, a command to wait for the write buffer to be empty had been inserted immediately before the flush command and when returning from the interrupt handler. This was done in order to avoid the symptoms of the problem, which was that a clean cache line would be invalidated when the flush command was executed if the write buffer was full.
The function specifications have not changed.
There was a problem with the list processing of mutexes stored in OSMutex.
Specifically, a problem arose when a thread used the OS_LockMutex or OS_TryLockMutex function to lock more than one OSMutex at the same time.
This has been fixed.
The problem does not occur if a thread locks only one OSMutex at a time.
Added explanations about the main items and the special features of the NITRO-SDK header files in the OS category of the NITRO-SDK Function Reference Manual.
Explanations were added about the following files:
nitro.h
nitro_win32.h
nitro/sinit.h
nitro/code32.h, nitro/code16.h, nitro/codereset.h
nitro/dtcm_begin.h, nitro/dtcm_end.h
nitro/itcm_begin.h, nitro/itcm_end.h
nitro/parent_begin.h, nitro/parent_end.h
nitro/version_begin.h, nitro/version_end.h
nitro/wram_begin.h, nitro/wram_end.h
nitro/version.h
Added functions to the RTC category that convert between type RTCDate and RTCTime date/time data and the total number of seconds that have elapsed since January 1, 2000. Also added functions that convert between type RTCDate data and the total number of days that have elapsed.
The demo that can be used to confirm these operations is $NitroSDK/build/demos/rtc/convert-1.
Functions have been created for debugging purposes that can change the RTC's date and time. To avoid incorrect use of these APIs in non-debugging applications, a restriction has been introduced that causes any request to write to the RTC to fail if NITRO_FINALROM has been specified.
Following are the functions whose operations have been changed:
The following correction was made to the sample demo $NitroSDK/build/demos/wbt/wbt-fs:
Table memory processed with the FS_LoadTable function would not be released with every connection and disconnection, thus causing memory leaks. This problem has been fixed.
The following changes were made to the $NitroSDK/build/demos/wireless_shared/wc sample module and the $NitroSDK/build/demos/wbt/wbt-1 demo:
During continuous MP communications, the wireless parent would unconditionally overwrite the Send buffer when a new child was connected. Depending on the timing, data would be sent to wireless hardware while data was being loaded to the Send buffer. This would result in WBT packet mismatches. This problem has been fixed.
To fix the problem, a process was added to $NitroSDK/build/demos/wbt/wbt-1/src/main.c that defines one of three actions for the WBT parent to take based on the information it has on the current child connection situation:
1) If it is the first child, begin MP communications.
2) If it is the second or later child, do nothing. (It is all right to do nothing, since continuous MP communications are taking place.)
3) If there is no child, terminate continuous MP communications.
Since the above process requires information about the disconnection of child units, $NitroSDK/build/demos/wireless_shared/wc/wc.c has been changed so that a callback is called on the sample side when a child is disconnected.
In order to reduce the amount of memory used by WM, the specifications have been changed for these three functions that are almost never used: WM_StartKeySharing, WM_EndKeySharing and WM_GetKeySet. Along with this change, a fixed buffer for Key Sharing is now obtained when WM is initialized.
In addition, since the Key Sharing features are scheduled to be deleted at a later date, a section was added to the document asking that programmers instead use the functions WM_StartDataSharing, WM_EndDataSharing, and WM_StepDataSharing.
It has been determined that when an SSID filter is specified by the WM_StartScanEx function, the SSID inside the discovered parent information sometimes has invalid data that differs from the specified SSID.
To deal with this problem, a process has been added inside the WM library that, when necessary, overwrites the filter-specified SSID with the SSID inside the discovered parent information.
Note that this happens only when the parent is using infrastructure mode communications and is hiding its SSID.
Updated the tool that is used for testing wireless communications: NitroSDK/bin/ARM9-TS/Rom/WMTestTool.srl.
Previously, when an access point was discovered during scanning, the message "WLAN AP" was displayed. This has been changed so that now the SSID is displayed.
This was implemented for both Scan Test mode and ScanEx Test mode.
Previously, when the wireless communications parent called the WM_StartMP function, it would send an MP frame even if no child was connected. This has been changed so the parent does not do this.
The basic behavior of the port's send/receive callbacks has not changed.
During MP communications, when the child responded with nothing but NULL and the communication timed out, the notification WM_STATECODE_DISCONNECTED would be posted multiple times to the parent's callback WMStartParentCallback. This problem has been fixed.
This problem occurred mainly when a child was started by IS-NITRO-DEBUGGER and was paused for a long time during MP communications.
Previously, during continuous communications mode and after communications failed repeatedly, transmissions would continue. However, in a situation where only empty data is being sent and received, the number of MP communication transmissions grows rapidly and the child's data-receiving process cannot keep up. This can trigger problems.
To mitigate this problem, a restriction has been set that limits the number of MP communication transmissions that the parent can send in a single frame to 6 (including resends).
This restriction is not placed on normal communications.
None.
(2005/05/09)
We added DMA channel validity testing to the MI library in Note 21-33, but in the CARD and FS libraries, the code that specifies channels is separated from the code that uses channels and the restrictions were not readily apparent. Accordingly, we added validity testing to the top of functions that request DMA channels in these libraries. We added a warning about this to the function reference.
We added a build switch that defines the floating point library (CW_LIBFP) and the ability to redefine it in the makefile. Also, the default library was changed from FP_fullI_v5t_LE.a to FP_fastI_v5t_LE.a.
The FINALROM version overlay function called unnecessary debugging functions and expanded the code size during link. This was fixed.
We added a sample demo called multiboot-PowerSave that uses the MB_SetPowerSaveMode function to toggle the power save mode in the Single-Card Play parent.
We implemented a mechanism to add new language codes and added Chinese as an extended language code. We are currently drafting guidelines for the creation of applications that support Chinese.
A feature was added so that the instrument will ignore the specified note length and continue to play to the end of the waveform data if SND_BANK_DISABLE_RELEASE (=255) is specified for the release field of the SNDInstData structure.
The following revisions were made to the $NitroSDK/build/demos/wireless_shared/wfs sample module and the $NitroSDK/build/demos/wbt/wbt-fs sample demo:
WFS_End function was called from an interrupt handle. This was fixed. We added a note in the header file of the WFS sample module indicating that it cannot be called from an interrupt handler.
WFS_End function was called after the WM library has ended, the port callback failed to release internally and execution stopped with an error, as made in the specifications. However, we changed the specification to simply ignore this section.
SDK_NO_THREAD is defined during the build.
With the samples that did not call the WcFinish function even though the WcInit function of the WC sample module could be called more than once, the correction was made so that these two functions are called properly. We revised the following demos so that the two functions are properly paired:
There were none.
(2005/04/21)
The reference for the CARD_Init function did not mention the threads for asynchronous processing that are generated internally. We added a description.
We added the functions CTRDG_IsAgbCartridgePulledOut and CTRDG_IsOptionCartridgePulledOut, which are used to detect the removal of the cartridge device. In Note 18-20 for changes in NITRO-SDK 2.0 RC, descriptions were added to the reference but there were no implementations of the functions corresponding to the additions.
Clearly stated in each function reference that CTRDG_IsExisting function must be called periodically because the ARM7 will not automatically detect removal while the cartridge bus is locked.
The additional text in the reference for Note 23-01, which was released in NITRO-SDK 2.0 official release, was incorrect in saying that the manufacturer's code and game code are only obtained during initialization. The text was corrected.
We revised the memory map and expanded the MainRAM area that is allocated to ARM9 by default. Previously the area allocated to DTCM started at 0x27C0000, but it now starts at 0x27E0000. Also, the MainRAM area allocated to ARM9 was expanded from 0x2000000–0x23BFFFF to 0x2000000–0x23DFFFF. (This increases its size by 128 KB.) The MainRAM area allocated to ARM7 is now 0x27E0000–0x27FEFFF. When the main memory size was 4 MB, under the default protection region setting, the ARM7 program area from 0x23E0000–0x23FFFFF was enabled for reading and writing from the ARM9. We changed the position of protection unit 2 and the area is now protected. When the main memory size is 8 MB, the start address of the extended arena in main memory is now 0x23E0000 rather than 0x2400000. The size was expanded to 128 KB.
We added validity testing code to the FS library functions that cannot be called from inside interrupt handlers.
In the function G3_FrustumW, the value of element _23 of the matrix that stores the result was wrong. This problem was fixed.
A non-recursive quicksort function was added under the MATH category as MATH_QSort.
We added functions that perform data checksum and CRC calculations. We also added references and demos for these functions.
We made the following changes to the demos/os/favorite-color demo.
demos/spi/mic-2. This problem was corrected.
Added an option to automatically generate TGID passed as an argument to the MB_Init function by specifying the newly defined constant MB_TGID_AUTO. As a result, the tgid argument was expanded from a u16 to a u32, but all other specifications are unchanged.
The following functions were added to allow the explicit external setting of parameters in the WM library that are used internally in the MB library.
We made the following correction to the source code of the samples in the $NitroSDK/build/demos/wireless_shared/mbp directory:
MBP_GetChildMacAddress and MBP_GetChildInfo were called for the AID of an unconnected child, a NULL was not returned. This problem was fixed.
The insertion position of the stack underflow detection code for launch threads initialized with OS_InitThread was 64 bytes lower than the bottom of the stack memory. This problem was fixed.
In the internal implementation of OS_Sleep function, the period from the setting of the alarm until thread-wait was not thread-safe. This problem was fixed.
As a result of internal implementation changes we made, which are described in Note 24-10, the operation of the DC_FlushAll function was no longer thread-safe. We corrected this. We also explained in the reference that the processing time of cache operation functions that use an area argument is proportional to the size of the area.
In some of the sample demos in the OS library, interrupts were disabled while the tick system was used. This was fixed so that the OS_EnableIrq function is called properly.
The references for the following format string functions erroneously said that they do not perform output operations with the final ROM library:
We added provisional support for extended language codes. We changed some of the tools, but there was no impact on the current applications. We plan to officially support the extended language codes in the next release.
Previously, NITRO-SDK contained only the sound library files while NITRO-System contained the sound library files, documentation, and demos. Starting with this release, everything will be included in NITRO-SDK. We have released the source files for the sound library in the $NitroSDK/build/libraries/snd directory and added sound library sample demos to the $NitroSDK/build/demos/snd directory. We also added function references for the sound library.
If sequence parameters are changed immediately after calling SND_StartSeq function, there was a possibility that starting the sequence and updating parameters may not be processed in the same frame. To fix this, we added the functions SND_PrepareSeq and SND_StartPreparedSeq. Parameter changes made between SND_PrepareSeq and SND_StartPreparedSeq are guaranteed to be processed at the time the sequence starts.
We improved the process to disconnect used by the wireless library when a parent detects a problem with a child. Also, we changed the library's internal operation so that if a parent fails to disconnect from a child by using WM_Disconnect function, it will attempt to disconnect a prescribed number of times.
We added the function WM_GetNextTgid, which automatically generates TGIDs based on the RTC time settings.
(2005/04/07)
Added the CARDRomHeader structure that represents the information in the ROM registration data to the CARD library.
We added process that test-reads 1 byte in CARD_IdentifyBackup function. The result value of this test-read can be obtained by using CARD_GetResultCode function. In tandem with this change, the return value type was changed to BOOL. When calling the function, the access bus must be locked using CARD_LockBackup function.
In tandem with support for the one-time ROM build option (explained in Note 24-04), we have added demos that specify mask ROM and one-time ROM. They are card/card-mrom and card/card-1trom.
In addition to mask ROM, one-time ROM is now supported as a build option for program ROM. RomSpeedType was added to the section parameters in the makerom.exe tool so that MROM, 1TROM or UNDEFINED can be specified. Also, we added a NITRO_ROMSPEED build switch to the NITRO-SDK make environment so that RomSpeedType can be specified during building. If you don't specify anything, it is set to UNDEFINED. For details, see the demo in Note 24-03.
Deleted the definition of the SDK_VERSION_PATCH constant that was always 0 for the SDK version information defined in version.h header file. In tandem with this change, the 4-byte version information value format contained in the program's resident code was changed. Deleted 4 bits in the SDK_VERSION_PATCH field, and expanded the SDK_VERSION_MINOR field to 8 bits. It has been expanded in the lower bit direction. The showversion tool was changed to reflect these changes. Please note the changes if you develop tools or other applications that read the SDK version information.
The G3_GetDLSize function sometimes returned a value that was 4 bytes larger than the actual display list size. This problem was fixed.
We added to the MATH category a message digest value calculation function that uses the standard message digest algorithms MD5 and SHA-1. Also, we added calculation functions that use the HMAC-MD5 and HMAC-SHA-1 keyed-hashing algorithms.
We added the MB_GetGameEntryBitmap function, which gets the AID bitmap of the entered children in the game information being distributed.
When a thread that locked the card bus and a lower priority thread called OS_ResetSystem function were running, reset internal process became deadlocked. This problem was corrected.
We confirmed that when the cache line management state is valid and dirty, in rare instances, the CPU flush instruction failed to operate. The internal implementation of DC_FlushRange and DC_FlushAll functions, which provide this functionality in the SDK was changed so that it is achieved by a combination of the CPU's store and invalidating instructions. The function specifications have not changed.
Made the following changes to the demos/os/favorite-color sample.
The functions RTC_SetDate and RTC_SetDateAsync, which change only the date, did not work correctly and did not change the date. This problem was fixed.
We added functions that obtain sound driver data. The functions are shown below.
SND_COMMAND_IMMEDIATE can be specified as an additional argument flag of the SND_FlushCommand function. When SND_COMMAND_IMMEDIATE is specified, issued commands will be processed without waiting for the next sound frame.
SND_INST_NULL was added as a value that can be taken for the type member of the SNDInstData structure that is used by the SND_ReadInstData function. Instrument data set to SND_INST_NULL will not make any sound.
Added the description about CLASS1, which is an internal state for "Description of wireless communication library" (AboutWirelessManager.pdf).
As a result of revisions in NITRO-SDK 2.0 RC5, if a child connected and disconnected before WM_StartMP function was called, the parent's ARM7 performs an invalid process. Although this problem was fixed in NITRO-SDK 2.0, it was not completely fixed. This is now completely fixed.
There was a problem where the APIID in the argument passed to the callback function specified by WM_StartScanEx function could not be differentiated from APIID of the WM_StartScan function because these two were the same. (As a result, the two APIs could not be used properly.) This problem is fixed.
Some bugs were found in NITRO-SDK 2.0 official release. If the machine being disconnected was unable to communicate, the disconnection would fail and the internal state of the wireless library would become inconsistent. Related to this, when a break was executed from the debugger during communications, other communicating parties did not receive a message indicating normal disconnection due to a timeout. We fixed these bugs.
With DS wireless play, WEP Key encryption can be used only when communicating over a connection. Added a demo that does this: wm/wep-1.
There were none.
(2005/03/11)
Clearly stated in the function references that the return value of CTRDG_GetAgbMakerCode and CTRDG_GetAgbGameCode functions is the value obtained when CTRDG_Init function is called. Also added that when using a Game Pak in development hardware, the Game Pak slot power must be set to ON before calling CTRDG_Init function.
The code style has been unified regarding indents and carriage returns in the library and demos.
References for the DS programs included in $NitroSDK/bin are added to $NitroSDK/man_en_US/romfiles under the category [Built DS programs].
Where necessary, the function reference now has descriptions of ranges of values that can be passed as arguments.
The macro SDK_WEAK_SYMBOL is defined as a modifier for the declaration of weak symbols. In CodeWarrior, it is defined as: #define SDK_WEAK_SYMBOL __declspec(weak)
Due to the correction made in RC5, there was a problem where the process did not complete properly because of the internal determination error when the function that loads overlays was called in an application built by specifying NITRO_COMPRESS. This has been fixed.
Added the option -A4 that adjusts the ending with 0s to make the output file size to be multiples of 4 when compressing data with ntrcomp.
In the function PRC_GetRecognizedEntriesEx_Superfine, the conditions to determine validity for SDK_ASSERT were too strict. These were modified to be appropriate.
The return values of the following function groups were changed from void to BOOL, so that they indicate whether it succeeded or failed .
PRC_InitPrototypeDB*
PRC_InitInputPattern*
PRC_ResampleStrokes_*
Due to the correction made in RC5, there was a problem where the parent's ARM7 performed invalid process if a child connected or disconnected before WM_StartMP function was called. This problem is fixed. This problem does not usually occur in applications that call WM_StartMP function immediately after WM_StartParent function succeeds.
Due to changes made in RC5, there was a problem where send was not performed properly if minPollBmpMode in the WM_StartMPEx function was set to TRUE. This problem was fixed.
Under certain signal conditions, although this occurred rarely, communication content was erased. This problem was fixed.
Previously, the send queue for port communications had 64 levels. This was changed to 32 levels in order to reduce memory usage by the wireless communications library. For one pair of Data Sharing, the send queue is at most two levels.
The structure passed to the callback for WM_SetMPData* functions has been changed. Previously, destBitmap was specified, but for AID of the disconnected DS system, the bit value that corresponded to the restBitmap field was indeterminate. This has been changed so that it is always 0. In addition, a sentBitmap field that stores an AID bitmap of a partner capable of sending was newly added. To determine if any DS systems did not receive the transmission because they were not connected or disconnected, compare the destBitmap field with the sentBitmap field.
The status check for the ARM7 wireless communications drivers have been improved. As a result, the callback for the following functions can return the WM_ERRCODE_ILLEGAL_STATE error.
wepkeyid in WM_SetWEPKeyEx function.
Previously, WM_EndKeySharing function always returned an error. This was fixed.
We made the following revisions to the sample source code in $NitroSDK/build/demos/wireless_shared/wh:
WH_SetUserGameInfo, which sets user game info for the parent's beacon.
There were none.
(2005/02/25)
A new component, ichneumon, arranges the execution codes for wireless functionality in VRAM. For details, see AboutComponents.pdf, which was also added. The idle and ferret components, which were provided with NITRO-SDK through 2.0 RC4, are no longer supported.
In the demo that demonstrates the use of the PictoChat functionality, there was a spelling error in the name of the function that enables/disables the PictoChat functionality in WC, which is the common wireless control module.
We revised the source code in the library and demos so that some pedantic warning options are supported. We improved the section that converted integer types that are the same size, but do not both have a symbol.
Added a new sample demo overlay-staticinit, which demonstrates the explicit addition of a static initializer in the C/C++ source.
Previously, when an archive was unloaded and then loaded, the internal state would partially change to suspended, and asynchronous commands that were issued repeatedly and held would not be executed. This bug was fixed.
If the file that corresponds to the specified overlay was opened successfully during the internal process of the FS_LoadOverlayImage and FS_LoadOverlayImageAsync function, TRUE was always returned without reflecting the result of the next FS_ReadFile function. This has been changed to reflect the result.
The return value of GX_GetOBJVRamModeBmp function was changed from a GXOBJVRamModeChar type to a GXOBJVRamModeBmp type.
The GXBg23ControlAffine structure contained the invalid member colorMode. Affine BG is fixed to 256 colors so this member is invalid. The colorMode definition was deleted from the GXBg23ControlAffine structure.
When G2_GetBG3Control* and G2S_GetBG3Control* functions were called, access to incorrect addresses occurred. This problem was fixed.
The newly added WVR library (for details, see Note 22-40) and the ichneumon component (for details, see Note 22-01) allow you to use the ARM7 wireless library in VRAM. While the wireless library is being used, the VRAM bank cannot be used for anything else. The previously available GX_SetBankFor* function group was changed so that if a VRAM bank that has been locked by the WVR library is reallocated, OS_Panic is called and the operation stops. Also, the GX_TrySetBankFor* function group, which tries to allocate VRAM banks separately was newly added. Note that with these new additions, OS_Init function needs be called before calling GX_Init function.
The MATH_CountLeadingZeros function is replaced by an inline function using the ARM's clz instruction when outputting ARM code and a function equivalent to the clz instruction when outputting Thumb code. However, when the default code was set to Thumb code using NITRO_CODEGEN=THUMB and output code was switched using #include <nitro/code32.h>, the MATH_CountLeadingZeros function was not switched to an inline function. This bug was fixed.
The following functions were added as interfaces that allow the user application to place data in the beacon transmitted by the DS download play parent. A fake multiboot child machine using MB_FakeInit can use this interface to receive specific accompanying information about the user from the parent before a connection is made. The presence or absence of this data will not affect the operation of a DS download child at IPL.
The following new functions can compress data in a DS application at runtime:
The MI_SetAgbCartridgeFastestRomCycle function was added. This function sets the ROM access cycle for AGB Game Paks. It sets 8-4 access in the DS and is equivalent to 3-1 weight in the AGB.
"Note 21-33: (MI) Dealt with multiple DMA bug," after using DMA0, a dummy empty DMA transfer is performed, but new processing performs a dummy empty DMA transfer also at OS_Init to handle the first DMA transfer that uses DMA0.
The ARM7 processing of the microphone's automatic sampling engine is now optimized for the ARM7. This change fixed the problem with freezing that occurred when a sampling rate of 32 KHz was used in the mic-1 demo.
A link to the Interrupt Overview page was added to the OS Overview page. The Interrupt Overview page was added in NITRO-SDK2.0 RC4, but there was no link to it.
Functions that pause and restart thread rescheduling were added to the OS library. They are OS_DisableScheduler and OS_EnableScheduler.
The functions DC_LockdownRange and IC_LockdownRange, which locked the cache to prevent its destruction, left some regions unlocked. This problem was fixed.
The following functions were added. They release locked blocks in the cache and make it possible to update the cache again.
Process was added so that the OS_ResetSystem function internally calls DC_WaitWriteBufferEmpty after calling DC_FlushAll. This is because the cache content remaining before reset could overwrite the program data loaded by OS_ResetSystem.
Added the function OS_GetITCMAddress, which obtains the base address of instruction TCM. The return value of this function is always the constant 0x01FF8000.
If sleep mode was entered from LCD Off mode, an error occurred with the graphics mode state, and the screen was not displayed in some cases, after the Nintendo DS was restored from Sleep mode. Now, the DS will return to LCD Off mode. This will have no effect on the restore process if the DS entered Sleep mode from Active mode.
The sound library distributed with NITRO-SDK is now the 2005/02/22 version.
During sequential MP communications using ports 8 though 15, packets would be duplicated under certain conditions. This problem was fixed.
When all of the above conditions were met, an identical packet was received in the next transmission as a new packet. This bug would appear as freezing and synchronization problems during DataSharing. If multiple packets are not packed into one payload, this problem will not occur. Accordingly, the problem will not occur if double mode is not used or if the max transmission size set with WM_SetParentParam only allows one DataSharing packet to be sent at a time.
Added description of restrictions to reference for WM_StartMPEx function. If sequential communication is used when the minPollBmpMode argument is set to TRUE with this function, you should periodically send "keep alive" data to all the children over all the ports used for sequential communication so that children not receiving over 60 frames of data will still be considered alive.
When WM_SetMPDataToPort* transmits unsuccessfully, the WM_ERRCODE_SEND_FAILED acknowledgement callback is passed a restBitmap that contains invalid members. This problem was fixed.
If WM_Reset were called during wireless communication when the parent was connected to a child, in some cases, processing would not be completed for a long period (normally 4 seconds, but it can be changed using WM_SetLifeTime) depending on conditions. This problem was fixed.
WM_IsBssidEqual and WM_CopyBssid implicitly required arguments with addresses that were aligned to 16-bit boundaries, and thus they did not operate correctly with odd-numbered addresses. This bug was fixed. We also added the new functions WM_IsBssidEqual16 and WM_CopyBssid16, which have the same functionality as the old versions.
With WM_StartParent and WM_StartConnect, the event acknowledgement following a successful connection is sometimes called before the callback indicating successful completion of asynchronous processing. A warning to this effect was added to the reference manual.
When a resend occurred while data was being sent in a specific pattern, the data that was supposed to be sent would vanish and the callback indicating completion of transmission was not sent. This problem was fixed. This problem can occur when using broadcast communication and communication to certain children at the same time.
We made the following revisions to the sample source code in $NitroSDK/build/demos/wireless_shared/wh:
WH_SetReceiver now uses WM_ERRCODE_SUCCESS to compare the return value when calling WM_SetPortCallback.
We fixed the following problem with the demo source code in $NitroSDK/build/demos/wireless_shared/wfs.
WFS_InitParent and WFS_InitChild would update the internal state before initialization processing was completed and this caused problems during MP communications callbacks. This problem was fixed. This problem does not occur when initializing WFS after the WM state is READY and before it is PARENT/CHILD.
The following APIs were added to provide processing under more precise settings.
WM_StartConnectEx, we in-lined the existing WM_StartConnect function. When building with previous versions of NITRO-SDK, object files and library files that internally call WM_StartConnect will generate a "function undefined" error during linkage with the program. You must rebuild these files.
When starting MP communications with WM_StartMP(Ex), in some cases, the midstream acknowledgement of MP communication was called before the callback of the function was called. This was fixed. We changed the internal operation so that MP-related midstream acknowledgements will not occur before the callback of WM_StartMP(Ex). This change caused the operation of the ARM7 to stop in some rare instances if a child connected and disconnected repeatedly. This problem was fixed. Also, we found that if a child disconnected from the parent when WM_StartMP(Ex) was called but before the callback was called, the library would malfunction in some cases. This problem was fixed.
In rare instances, a parent Nintendo DS using wireless communication would fail to send a beacon even after it successfully became a parent. This was fixed.
Previously, the proper WM_SetMPData* function was not sent a callback regarding the transmit data left in the transmit queue at the end of communication. Now a callback is always returned. As a result of this change, all asynchronous APIs for WM now return at least one callback.
We confirmed that problems with library operation could occur after a wireless parent nearing its connection capacity connected with additional children, causing it to exceed its connection capacity. This problem was fixed.
The description document for the wireless communication library was officially released as docs/TechnicalNotes/AboutWirelessManager.pdf.
With the addition of the ichneumon component (details are in Note 22-01), we also added the WVR library, which deploys the wireless executable code in VRAM, starts/stops it and removes it, when this component is in use.
There were none.
(2005/01/14)
Created a CHT library to handle the PictoChat-related API group. The following functions are included in the CHT library:
As of January 13, 2005, there is no description of how to use the PictoChat-related library in the DS Program Guidelines. If you are considering using this library, first contact NOA support.
MATH was created as a category for mathematical functions. MATH_ILog2 is included, in addition to functions min and max. MATH_ILog2 calculates log2(x) in integer range at high speed on the ARM9.
The following functions have been added as random number libraries with the linear congruential method.
Also, $NitroSDK/build/demos/math/rand_lc was added as a demo.
In the pseudo Single-Card Play child device library MB_FakeChild, there was a bug that cut communication with a FATAL error when an MP communication error, which can be retried, occurred. This bug was fixed.
When set to use internal thread with MB_ReadSegment function call, the state management of internal threads did not occur correctly when ending library with the MB_End function, and operation after reinitialization was abnormal. This bug was fixed.
When terminating the MB library with the MB_End function or the MB_EndToIdle function, incorrect operation occurred after MB library termination due to its timing and to MB internal events that occur during the termination process. This bug was fixed.
Added MBP_USING_PREVIOUS_DOWNLOAD switch in the following source used by the multiboot demo.
When this switch is ON, starts download of as-needed preceding data for entered child device. Using the sequence with this switch ON, it may be possible to keep to a minimum the download wait time, depending on the timing of child connection.
Added the function WM_IsExistAllowedChannel for confirming the presence or absence of a usable channel for wireless communication. This function does not depend on the internal state of the WM library, and only determines the existence of a permitted channel.
For the WM asynchronous function group, operation is not guaranteed for calls of other functions during asynchronous processing. However, for the WM_SetMPData( ToPort(Ex) ) function only, it is possible to reserve send data by consecutive calls. In this case, the actual data to send may break if you consecutively call over ten times. For this reason, we fixed it so that it performs stricter exclusion processing. As a result of the fix, the method was changed so that WM_ERRCODE_FIFO_ERROR is explicitly returned by WM_SetMPData( ToPort(Ex) ) when performing a send requests where data is likely to break.
In MP communication, the power save time of the child device was, on rare occasions, longer than normal. This bug was fixed.
In the sample demo with FS using wireless, the internally-set receive callback function was not cleared when WFS_End is called, and the internal callback function was called unintentionally. This bug was fixed.
The demo was fixed so that it decides the channel using a random number when there are multiple channels using the same wave. This is in order to better distribute channels to use when the parent device decides the channel in the wireless demo. This process is reflected in the following demos:
Fully updated the content of the document AboutFileSystem.rtf, which describes the file system library, and added it as AboutFileSystem.pdf.
Added Get functions that read drawing register. The functions are shown below.
In the sub 2D engine, there was a bug where VRAM extension flag of a non-existent bitmap OBJ was defined as the define value. The following definitions were eliminated.
Also, the GXS_SetOBJVRamModeBmp function was fixed so that it checks, using ASSERT, arguments that use this flag.
Fixed so that, during data transfer with GX, data is copied by the CPU without using DMA when the data size is small. Transfer by synchronous process is normally processed on the CPU for transfers under 28 bytes for 16-bit copies, and under 48 bytes for 32-bit copies.
When performing VRAM bank settings using the GX_SetBankForBGEx function, the warning by ASSERT did not appear even when loading data in an incorrect address during the DEBUG build. This bug was fixed.
The capture enable flag set with the GX_SetCapture function is usually automatically reset after completion of capture. However, the GX_ResetCapture function was also added as a separate cancellation function that can reset. However, be aware that you cannot abort a capture that is already in progress.
In the force stop process performed when hot swap of DS Game Card or Game Pak is detected, the wave send sometimes didn't stop completely during wireless communication. Also, it was sometimes unclear whether the LED was illuminated. These bugs have been fixed.
The CARD_ReadRomID function has been eliminated because there is no purpose in using it from a user application.
Added a function for getting and setting the access permission state in order to prevent child device programs started with wireless download from carelessly accessing the NITRO-CARD. When applications not started from the NITRO-CARD access the NITRO-CARD, you must call the CARD_Enable function after deciding according to the rules in the Programming Guidelines.
In the TP_GetLatestRawPointInAuto function, all values sampled in the interval of the previous one frame were treated as touch OFF when they were touch ON and INVALID. It was fixed so that in this situation also the validity value is set and returned as touch ON.
When performing touch panel sampling at a specific timing, there was a combination, depending on the hardware, where a lot of noise from the LCD was picked up. For this reason, we improved the countermeasures against noise during sampling.
Added the following APIs that dynamically change the sampling rate without stopping sampling while auto-sampling is running.
Also, fixed part of the sample demo mic-1, and made the sample also use this API.
The interrupt check flags OS_IE_USER_FLAG0 and OS_IE_USER_FLAG1 were only available on the ARM7. These flags were added in "Note 6-35: (OS) Added interrupt check flags for applications" (NITRO-SDK Version 1.2 PR1). These are now also available on the ARM9.
Added OS_DestroyThread(), which specifies and terminates a thread. (This function was originally prepared as an internal function.)
Be careful when using this function, as it is a little risky to terminate another thread without notice.
"Note 13-18: (PAD) Eliminated PAD_SetIrq() and PAD_ClearIrq()" (NITRO SDK 2.0 PR4 release), use of key interrupts was prohibited. Therefore, interrupt-key-1 (key interrupt demo) in the OS demo has been eliminated. Furthermore, WaitIrq-2, which used key interrupts, was changed so that it uses timer interrupts.
Up to now, in order to use extended main memory arena, it was necessary to make OS library with NITRO_MEMSIZE=8M specified. However, it is now possible to declare whether or not to use extended main memory arena by specifying OS_EnableMainExArena() and OS_DisableMainExArena() before OS_Init() (OS_InitArena() when not using OS_Init()).
However, extended main memory arena can never be used when operating in an environment (including actual equipment) with only 4 MB of main memory installed.
There were mistakes in the OS_DisableWriteBufferForProtectionRegion() function, and it behaved the same as the OS_EnableWriteBufferForProtectionRegion() function. This has been fixed.
Added the following functions related to heaps.
Also, changed the type of OS_CheckHeap() from long to s32.
Supported streaming expansion of compressed data. By using this function, it is possible to perform expansion with a smaller buffer while reading LZ-compressed data, Run Length compressed data, or Huffman-compressed data from a Game Card. The following demo has been added as a sample that actually performs streaming expansion of data:
For MI_SendGXCommandAsyncFast() and MI_SendGXCommandAsync(), the volatile specification was not appropriate and caused the termination wait to work improperly when the specified DMA was already in use. This has been fixed.
Created restrictions on source address when using DMA0 to deal with the hardware bug when there are multiple DMAs. Specifically, made it impossible to specify 0xmmnnnnnn (mm = 0x04 and 08-ff, nnnnnn is arbitrary) in source address of DMA0. These restrictions also apply for source address when transfer ends.
Also, dummy empty DMA transfer is performed after using DMA0.
There are no restrictions on DMA1 through DMA3.
Changed order of PXI control register clear and PXI interrupt setting from "interrupt setting -> register clear" to "register clear -> interrupt setting".
This was done because with the previous order, data remained in the PXI FIFO register when setting an interrupt, and an interrupt occurred at that point.
In applications using the clone boot function, added functionality to makerom that determines at time of ROM image creation whether or not the region for adding authenticator with the attachsign tool can be allocated in/on the ROM image.
This function is enabled by adding -A as the start option of makerom. When using a makefile, it is best to set option -A for MAKEROM_FLAGS as follows:
MAKEROM_FLAGS = -A
Until now, the documents under $NitroSDK/docs/TecnicalNotes were in various formats such as doc and rtf. These have been converted and standardized to pdf format.
Provided demo in $NitroSDK/build/demos/tips/MyBuildMessages that changes link message and compile during/when make -s.
The emuchild.exe that prearranges signature to binary when using clone boot normally output full-sized files. However, to reduce the size of output files, it was changed so as to exclude data after the static region of the ARM9 and 7. Use the added -f option to output full-sized binary.
The sound library distributed with NITRO-SDK is now the 2004/12/27 version.
There were none.
(2004/11/29)
The function was added to allow a pseudo Single-Card Play child device to be entered into the Single-Card Play parent device in the application that is running from a DS card. By using this feature, it is possible to have both the Single-Card Play child device and the Multi-Card Play child device in the wireless play.
Also, as a demo program, the fake_child demo that makes an entry to the Multiboot-Model parent device was added to the following folder.
$NitroSDK/build/demos/mb/fake_child
In NITRO-SDK 2.0 RC2, there was a problem that the buffer size that was returned by the MB_GetParentSystemBufSize() function was smaller than the actual value by WM_SYSTEM_BUF_SIZE bytes. This problem was solved. However, MB_SYSTEM_BUF_SIZE that is defined in nitro/mb.h for the same buffer size is not affected by this problem.
Expanded the feature so that it is possible to specify a buffer length value that is smaller than the return value of the MB_GetSegmentLength() function which would be passed as an argument to the MB_ReadSegment() function. The smallest size is defined as MB_SEGMENT_BUFFER_MIN. For details on the instance where this extended function is used, see the reference for the MB_ReadSegment() function.
To integrate with other categories, the current MB_StartParentEx() and MB_EndEx() functions were changed to MB_StartParentFromIdle() and MB_EndToIdle(). The old names have been eliminated.
There was a problem that caused inconsistency in the internal state of the MB library when a child was disconnected from a parent by using the WM_Disconnect() function while distributing Single-Card Play data. MB_DisconnectChild() function which allows for the safe disconnection of a child even during MP communication.
The following problems were found when the receive buffer size setting was changed with the Single-Card Play parent.
MBUserInfo cannot be received.
For this reason, the specification was changed so that the receive buffer size of the MB parent cannot be changed. Because of this, the argument that sets the receive buffer size in the following functions was eliminated.
Added a sample clone boot that illustrates the creation procedure of the clone boot program.
There was a problem that caused the retry to fail if the connection to the parent failed even once when reconnecting to a parent after a child booted in the multiboot-Model demo.
This problem was solved as shown below:
wireless-shared/wh/wh.c, a correction was made to change to the WH_SYSSTATE_CONNECT_FAIL state properly when the connection to a parent failed.
WM_Reset() before retrying the connection if the connection failed.
Check the points above if you create an application by using this demo as an example.
Added a document regarding the Single-Card Play procedure, reconnection with the Single-Card Play parent, and performing a clone boot in $NitroSDK/docs/TecnicalNotes/AboutMultiBoot.doc.
In the release and debug versions of the mongoose component, the work area that is required for operating the driver cannot be allocated in some cases. Also, there was a problem with the process of reusing the mongoose work area in all versions. When the APIs were called in a specific order and the connection and disconnection were repeated, the work area may run out and the connection process may not work properly. These bugs have been fixed.
When the ARM7 on a child device freezes because of a change to the halt state while performing communication, the child device's wireless hardware automatically continues to return Null and the generated error cannot be detected by the application on the parent device. To deal with this issue, the internal process was changed to cut off the connection if a child device continues to return a Null value for a certain period of time.
When the ARM7 on a parent device freezes because of a change to the halt state, the parent device's wireless hardware automatically continues to keep sending a beacon and the generated error cannot be detected by the application on the child device. A change was made to automatically disconnect if the no MP frames are received from the parent device for a certain period of time. The default value is set to 4 seconds on both the parent and child devices.
In addition to this change, the mpLifeTime argument was added to WM_SetLifeTime().
Normally, the Null response or MP frame send skip occurs when the load on the ARM7 is temporarily increased. They do not occur continuously.
Published the "Wireless Communication Tutorial" – a tutorial for creating the wireless communication program based on the wireless communication program sample dataShare-Model that uses the WM library.
Added the FS_LoadOverlayImageAsync() function that loads overlays asynchronously.
The feature of the FS_RegisterOverlayToDebugger() function that registers overlays that were loaded asynchronously to the debugger was integrated into FS_StartOverlay(). Because of this, it is not necessary to call the FS_RegisterOverlayToDebugger() function explicitly. To maintain compatibility, this API was left as an empty function.
The GX_GetVCountEqVal() API is provided to obtain the current setting of the VCOUNT match interrupt. Also, the name of the related APIs GX_SetVCounterEqVal() and GX_IsVCounterEq() were changed to GX_SetVCountEqVal() and GX_IsVCountEq(). The old API names can be used by defining a different name in the macro.
The GX_SetBankForBGEx() function was added as a function to use the combination that cannot allocate consecutive addresses such as VRAM-A and VRAM-B for the VRAM bank setting for the BG. By using this function, VRAM-EFG is allocated to 0x6000000-0x6017FFF and the biggest one of the VRAM-ABCD is allocated to 0x6020000-0x607FFFF.
demo/gx/UnitTours/2D_CharBg_BankEx was added as a demo that uses this function.
Changed the process that prevents the CARD_TerminateForPulledOut() function (that is called by default after a card removal is detected) from stopping by using the OS_Terminate() function to stopping normally if the cover is open and to forcibly turn the power OFF if the cover is closed.
Added the following functions that restore the data that was filtered with ntrcomp by using runtime.
MI_COMPRESSION_DIFF was added to the data type that is obtained with the MI_GetCompressionType() function.
The function which CPU clears memory was defined in crt0.c, and other libraries (OS and MI) were using this function. When a Nintendo DS multiboot child device cancels out of the data receive process, there were instances in which this region was destroyed. The memory clear function that is used in crt0 and the memory clear function that is used by other libraries were separated.
If multiple alarms were set to VAlarm, there were some instances in which the order of the alarm was not controlled properly depending on the V count that was set, the number of lines allowed for the delay, or the timing in which the interrupt is generated. Because of this problem, the automatic sampling of the touch panel during the wireless communication was not performed properly in some cases. This bug was fixed.
The following OS functions for debugging were made to be the weak symbols. If the user defined the function with the same name, that function will have priority.
The entities of OS_Panic(), OS_Warning(), OS_TPanic(), and OS_TWarning(), which are OSi_Panic(), OSi_Warning(), OSi_TPanic(), and OSi_TWarning() respectively, were also made to be weak symbols.
There was a problem in which the SND_InvalidateWaveData() function stopped the generation of other sounds that are not related. Because of this problem, if the sound data in the memory was deleted while in the surround mode, the sound was not generated until the surround mode was stopped. This bug was fixed.
The following are problems in the MIC_GetLastSamplingAddress() function.
MIC_StartAutoSampling() function.
These problems were corrected, and there was a specification change for the MIC_GetLastSamplingAddress() function to return the memory location that stores the last sampled data, or return a value of NULL if the data was not sampled even once.
Of the pattern recognition APIs, the identifier names that contained the word "regularize" were changed to "normalize."
Member variables of the structures PRCInputPatternParam
PRCPrototypeDBParam
PRCPrototypeList were changed.
The structure member variables of each of these have changes. Also, the constant value in the C program which is output by $NitroSDK/tools/bin/pdic2c.pl was changed to PDIC_NORMALIZE_SIZE.
To prevent allocating the same buffer to the sendBuf argument of WM_StartMP*() and the sendData argument of WM_SetMPDataToPort*(), changes were made to generate an error if these two buffers are the same.
This note pertains to the GX_SetBankForBGEx() function that is described in "Note 20-15: (GX)." The GX_GetVCountEqVal() function was added and the other VCOUNT match interrupt related API was changed with this version. The region check will not be performed for the DEBUG build. When the invalid address was written, it will not be stopped by ASSERT. These problems will be fixed in the next or later versions to be released.
(2004/11/04)
In WM_GetAllowedChannel(), when an error occurs (WM_Init() was not called in advance), the return value, which was previously 0, is now 0x8000.
This allows you to distinguish between this error and the error that occurs when there is no available channel (return value of 0x0000).
The WM_End() function used to perform the library force quit process and memory release after the user callback was called. But we changed the method so that all end processes are completed before the callback is called.
This change is in response to requests from people who want to call the next WM_Initialize() function in the callback for the WM_End() function.
We added a new structure that is passed to the callback for WM_Disconnect() and WM_DisconnectChildren(). This structure is similar to the WMCallback structure, but has additional members, which contain an AID bitmap of the devices that requested the disconnect and an AID bitmap of the devices that were disconnected.
The member variables at the beginning of the newly created WMDisconnectCallback structure match those of previous WMCallback structure and the new structure can be treated as a WMCallback structure.
When WM_Reset() was called after MP communication was established, the automatic processing for MP communication would not be reset.
We corrected this bug and now the automatic processing is always reset. This may reduce the processing burden.
If MP communication occurred between WM_EndDataSharing() and WM_EndMP(), erroneous processing occurred in some cases. This bug was corrected.
Please note that if WM_EndDataSharing() is called immediately before calling WM_StartDataSharing(), a problem may occur.
When using data sharing with libraries before RC1, the maximum shared data size multiplied by the number of shared machines was 252 bytes. We expanded this value to 508 bytes. As a result, the size of the WMDataSharingInfo structure has increased by 1K byte. To return to the previous state, change WM_DS_DATA_SIZE_508 in wm.h to #undef.
When setting MBUserInfo, which is an argument of MB_Init(), the termination of the user name was indicated by a NULL, and even when the nameLength variable was changed, the change was not reflected on the child screen.
This bug was fixed.
We added MB_StartParentEx(), which can be called even when the wireless library is in the idle state, and MB_EndEx(), which sets the wireless library to the idle state and then stops. They correspond to the standard MB_StartParent() and MB_End(). In other respects, they can be used in the same way as the standard functions.
If a multiboot parent running the MB library calls MB_RegisterFile() and MB_UnregisterFile() alternately to dynamically change a saved program, if the GGID of the program before the change matches the GGID of the program after the change, the change is not detected on the IPL side.
We have added a warning about this to the reference for MB_UnregisterFile().
We added a demo that surveys signal usage during MB preprocessing for multiboot. It is in $NitroSDK/build/demos/mb/mbm. Because MBM_MeasureChannel() will get the optimal channel and then turn off power to the wireless system, after obtaining the callback, you should begin multiboot processing from MB_Init() as usual.
In the multiboot sample demo's parent operations, we changed the tgid setting value, which is used to manage wireless connection sessions, so that when possible, it changes each time the power is turned ON. The minute and second values from the current time obtained with RTC are used as tgid values.
In the MB_End() function, library end processing such as memory release was performed after the user callback was called. Revised it so that all end processing is completed before the callback is called.
This revision is the same as Note 19-05, and is to deal with the situation where MB re-initialization is performed in the MB_End() user callback. This corrected a problem where the documentation and actual operation did not match.
When connection with parent failed during child's file access in the wbt-fs sample demo, file operations invoked thereafter would fail to complete. This problem was fixed.
During caching of received data in the wbt-fs sample demo, some areas that should have been flushed were invalidated.
This problem was fixed.
Two problems with the WBTlibrary were corrected.
WBT_GetBlockInfo() was called when a block was not stored on the other machine, the WBTBlockInfo structure that was returned by the callback would have unpredictable values. The structure now returns with all members cleared to zero.
WBT_GetBlockInfo() function had higher priority than WBT_GetBlock() and this would sometimes cause a deadlock. This was fixed by reducing the priority of WBT_GetBlockInfo().
We added the function FS_RegisterOverlayToDebugger() to the FS library. This function is used to notify the debugger of an overlay load when you use a series of low-level functions (such as file read) to load an overlay module rather than using high-level functions, such as FS_LoadOverlay().
If you use FS_GetOverlayFileID(), FS_ReadFile() and FS_StartOverlay() in combination to load an overlay, call this function before calling FS_StartOverlay(), so that you will be able to trace the operation in the debugger.
We added a demo, $NitroSDK/build/demos/fs/overlay, which contains an example of the function's usage.
We changed the routine for alarms resulting from the V-count (VAlarm). Previously, the "first VAlarm in the loop resulting from an interrupt" only calls a handler when the V-count was the precisely the specified value. This resulted in processing delays in the wireless library and other libraries that relied on this feature.
The "first VAlarm in the loop resulting from an interrupt," is, as its name suggests, a VAlarm handler called by a V-count interrupt. After this handler is called, the call count of other registered alarms is checked and handlers are called if necessary.
This processing was changed so that the VAlarm handler called by the interrupt is called even when the V-count exceeds the specified value. The amount that the V-count can exceed this value (the delay) can be set by the programmer. (If the call is not in time, it will be performed in the next frame.)
One argument (delay) was added to the VAlarm configuration function, OS_SetVAlarm(), for this purpose.
Previously, the function call was:
OS_SetVAlarm( alarm, vcount, handler, arg );
Now it is:
OS_SetVAlarm( alarm, vcount, delay, handler, arg );
For details see the reference for OS_SetVAlarm().
There has always been a way to specify a delay with a periodic VAlarm, but with an interrupt-triggered VAlarm, the delay did not work. Now you can specify the precise delay for the alarm.
OS_SetVAlarm() now has one more argument, but if you want to use the previous function call and not specify a delay, use the same arguments and call OS_SetOneTimeVAlarm() instead of OS_SetVAlarm(). This function will set the delay to 10. (Internally, the delay has always been treated as being 10.)
The maximum value for the delay is OS_VALARM_DELAY_MAX. If this value is specified, the specified VAlarm handler will be called no matter how much time elapses.
We added the following color information definitions and functions. We also added a reference.
OS_FAVORITE_COLOR_ enumerated constants
OS_FAVORITE_COLOR_VALUE_ color value constants
An error occurred when cost calculations were performed with the function cost profiler OS_CalcThreadStatistics() and a thread other than the current thread was targeted. The cost buffer is cleared after the cost calculation results are stored in the statistics buffer. However, the current thread's buffer was cleared rather than the targeted thread's buffer. This has been fixed.
There was a problem with the tick value setting function (OS_SetTick()). The other interrupt request flags were disabled. This has been fixed.
This function could affect the operation of alarm systems in use. Please be careful when using OS_SetTick() in an application.
The reset function, OS_ResetSystem(), does not initialize the hardware, so you must explicitly stop the hardware functions or confirm that they are stopped before calling this function. For safety reasons, we have added code to the function that stops several hardware functions.
This problem was also fixed.
There was a problem when an autoload was performed using a data section created in DTCM. This has been fixed.
The function CARD_GetRomHeader was added. This function allows the program initiated by wireless download to obtain ROM header information stored in the DS CARD that is currently inserted.
The card library and upper-level library functions did not check for possible conflicts with other automatically initiated DMA during DS CARD access. Code that checks for this was added.
When ferret was used as an ARM7 component there was no way to detect whether the Game Card or Game Pak was removed. We added this feature to ferret.
This detection feature is valid only the TS edition of the library.
Correction of NITRO-SDK 2.0 RC1 "Note 18-16: (PM) Eliminating ghost images during sleep mode" caused the following problem. As a result of the fix of the ghost image problem, when the machine was woken up after being transitioned into sleep mode by PM_GoSleepMode(), the GX library's status changed from its pre-sleep status, and this caused the LCD to restore incorrectly in some cases. This was fixed and now the LCD will restore correctly after being in sleep mode.
The debug MI library uses an ASSERT to check whether the transfer address for DMA is included in ITCM and DTCM. The ITCM start address was 0x00000000. This was changed to the regular value of 0x01FF8000.
The function MI_DmaFill*(), which uses DMA to fill memory with a uniform value, would sometimes transfer values incorrectly when an interrupt was generated during execution. This problem was corrected and MI_DmaFill*() is now an interrupt-safe function.
Two function names were changed. They are functions relating to the underflow (lines over) flag of the rendering engine's line buffer.
G3X_IsLineBufferOverflow()andG3X_ResetLineBufferOverflow()
were changed to
G3X_IsLineBufferUnderflow()andG3X_ResetLineBufferUnderflow()
The following constants in $NitroSDK/include/nitro/hw/ARM9 were declared incorrectly.
They were corrected.
When the table in G3X_initTable was cleared to zero, the last 16 bytes in the toon table were not cleared.
This bug was fixed.
The sound library distributed with NITRO-SDK is now the NITRO-SYSTEM 2004/10/12 version. The update was also added to patches after 2.0RC1plus3.
Added reference information for CTRDG_IsNumberID() and CTRDG_IsBitID(), which check if specified peripheral devices are installed in the Game Pak.
Included mock-production version IPL mb_child program under $NitroSDK/bin/ARM9-TS/Rom. The name of the previous one was changed to mb_child_simple.srl.
Also, included in the same directory WMTestTool.srl, which is a tool for testing wireless. You can use the following test modes. We are currently preparing detailed manuals.
There were none.
(2004/10/07)
Note: Due to the changes with WM library in version 2.0 RC1, programs with 2.0 FC or older versions cannot be compiled as is. Following are some major updates.
Deleted the test mode operation functions WM_StartTestMode() and WM_StopTestMode().
The specification of WM_GetAllowedChannel() was that even though it was a synchronous function, it did not return a valid value unless it was in IDLE state after executing WM_PowerOn(). However, this specification had a potential for confusing the library users, so the changes were made to return a valid value any time after it was initialized with the WM_Init() function.
Noise was added when using the sound library to play high pitched sounds during the wireless communication. This issue was improved significantly.
The specification was changed to disconnect the device when an unrecoverable and fatal error occurred with the wireless communication protocol due to the influence by other wireless communication devices other than Nintendo DS. The application receives the same notification as normal disconnection, so there is no need to write corresponding codes.
An unique setting value that is required for each Nintendo DS system during the wireless communication is kept internally in Nintendo DS. If this setting value is destroyed for some reason, the communication cannot be executed properly. Therefore, the program stops automatically if the wireless setting value is destroyed when there was an attempt for the wireless communication.
6) For game group ID, both u16[2] type definitions and u32 type definitions are used. It caused confusion, so they were standardized as u32 types. Interface changes in APIs were executed for the following.
WMParentParam structure
WM_SetGameInfo() function
MB_Init() function
Due to this change, sample demos that perform the wireless communication were updated.
The argument ignoreFatalError was added to WM_StartMPEx(). Normally, FALSE should be given.
The maximum value of the maximum numbers of bytes that can be sent by parent or child that is specified with WMParentParam increased from 508 bytes to 512 bytes. However, the 5600-microsecond limitation required for MP communication has not been changed, so the number of bytes must be set within the limits. The value of MB_COMM_PARENT_SEND_MAX in MB library is not changed.
As the distance between the parent and child increases while minPollBmpMode of WM_StartMPEx is set to TRUE, the communication was disconnected with the return value of WM_GetLinkLevel set to the maximum level of 3. This problem was solved. At the same time, the behavior of the radio receive strength that is taken by WM_GetLinkLevel was changed. The frequency of the value change became slow.
Both the u16[3] type definitions and u8[6] type definitions were used for MAC addresses, and it was causing confusions. This was standardized as u8[6] types. Interface changes in APIs were executed for the following.
WM_SetDCFData function
WMStartParentCallback structure
WMStartScanCallback structure
WMPortRecvCallback structure
WMScanParam structure
Due to this change, sample demos that perform the wireless communication were updated.
For all of the wireless sample demos that use the setting value that exceeds the required time for MP communication as it is defined in the programming guidelines, made changes to use the value within the proper range.
With mb_child.srl, when the user name of the parent was 10 characters, it did not work properly. This problem was corrected.
Previously, according to the display sequence confirmation, when IPL was downloaded, this demo waited until the parent completed the boot preparation after the data transfer. It was changed to wait for all children before the data transfer.
The program mb_child.srl, which is used by children for multiboot, used Japanese characters for display, but it was changed to display in English.
Added the WBT_CancelCurrentCommand function that is used for canceling the file receiving operation that is being processed with the WBT_GetBlock function.
The warning "Failed sound alarm OS_SendMessage" was output in the ball demo, but it was changed not to be output.
This warning indicates that the sound process on ARM7 is being executed properly. When playing 44kHz sounds on all of the 16 channels at 3 octaves higher, this warning may be output because the heavy load on CPU processes. Do not play the sound that can cause the heavy load on the CPU processes.
Changes were made so that the user name used by the parent for the mb/multiboot demo process is obtained from the owner information in the Nintendo DS system.
However, the fixed value is used, as it was done previously in the old environment which the OS_GetOwnerInfo() function cannot use, such as TS and TEG of TS_VERSION < 200 and NVRAM_FORMAT < 100.
Included the tool showversion that displays the NITRO-SDK version that is embedded in ROM file. Valid only with NITRO-SDK 2.0 FC or later versions. For details on restrictions, see the reference manual.
Included the final version of the banner display tool. Compared to the last version, fonts that can be used are changed.
When the application-specific lsf file is being used, the segment name in the resident module and srl/nef target name are set differently, an error was generated during the module compression process when NITRO_COMPRESS is enabled.
By correcting the lcf template file to output the intermediate file component.files from the description of lsf file, and to use compstatic to reference that file, the description of the resident area name in lsf file and the module compression process are linked.
Previously, the size of the protection region for main memory was always set to 4 MB at startup, and the protection region setting was set to 8 MB only if SDK 8M was defined when OS_InitArenaEx() was called (called in OS_Init()) and 8 MB memory was mounted.
However, if there was an attempt to use autoload to transfer the module to the extended memory region, that transfer occurred before OS_InitArenaEx(), and it was not possible to proceed because of exception that was generated.
Because of that, the rules regarding the protection region size for main memory have been changed.
OS_InitArenaEx() is called, if SDK 4M is defined or the amount of mounted memory is 4 MB, the region size changes to 4 MB.
This change allowed the transfer to the extended memory region.
Changes were made to stop the sound playback with ARM7 when OS_ResetSystem() is called.
These were added to the thread initialization executed by OS_CreateThread().
OS_ExitThread(), OS_JoinThread(), and OS_DestroyThread().
There was an error with the buffer underflow check that is performed by one of the profile features, PROFILE_EXIT, which is a function trace. This has been fixed. Also, the register for detecting underflow was not displayed properly, and it was corrected.
When using PM_SetLCDPower() to switch the LCD status, LED was forcibly turned ON. However, it was changed so that the LED status does not change.
When entering sleep, the image displayed before entering sleep sometimes stayed displayed. Changes were made to wait for one frame after the screen output was turned off to avoid residual images.
There was an error with the IRQ mask return process on ARM7 after the sleep process. Depending on the cause for awakening from sleep, the cause was left as valid even when awakening from sleep after the necessary IRQ causes were enabled. To be more precise, the card removal check after sleep was not detected by card interrupts. This problem was solved.
Added APIs for calling callbacks for sleep. They can be registered for before changing into sleep mode and after awakening from sleep mode. In addition, multiple callbacks can be registered.
When CARD_Init() was called twice, the FIFO Callback overridden warning was given. (It calls FS_Init() and CARD_Init(), so it is the same when calling CARD_Init() and FS_Init().) It was corrected so that the warning is not given.
The following cartridge functions are now the official release, and references were added.
Previously, there was a problem that RTC alarm interrupt was not generated properly because of the conflict between the interrupt for generating RTC alarm and IS-NITRO-EMULATOR hardware. To deal with this problem, the temporary measure was taken to make ARM7 execute polling to monitor the RTC alarm status at fixed intervals. Since the hardware conflict issue was solved with IS-NITRO-DEBUGGER software version 1.11, the polling method was abolished and changed to the method that handles interrupts.
There was a possibility of causing inconsistency between the date structure that can be obtained with functions such as RTC_GetDate(), and the day of the week in the calendar. This problem was fixed.
To use only the clear depth image without allocating VRAM to the clear color image slot, the following settings were added.
When using these settings, all of the clear images are cleared with 0x0000, and the alpha value is also set to 0. With this setting, the texture image slot 2 is disabled, so make sure that VRAM is not allocated to this slot.
A demo that uses these settings is added to demos/gx/ClearDepthOnly.
There were none.
(2004/09/30)
The test release version of the wireless block transfer library (WBT) became the official release. There are references and samples wbt-1 and wbt-fs.
There was a problem that stopped the auto-sampling process of the touch panel when starting the wireless process. This has been fixed.
Corrected the problem that the exclusive control of the data sharing function was not executed.
There was a problem that stopped auto-sampling when starting the wireless communication with the auto-sampling of the touch panel enabled. This has been fixed.
When calling wireless asynchronous APIs at different threads at the same time, the result of the process became invalid. This problem was solved.
There was a problem with the exclusive control of send/receive for data sharing, and in rare cases data sharing was stopped. This has been fixed.
The specification was changed so that when a recoverable error occurs during send/receive of the data sharing, WM_StepDataSharing keeps returning WM_ERRCODE_FAILED.
6) There was a possibility that the child was not recognizing the parent properly when WM_StartScan was executed. This was solved. To be more precise, when the beacon without the Gameinfo information is obtained, the GameInfo obtained by the precedingWM_StartScan is carried over, and by referencing GameInfo directly without evaluating gameInfoLength, the wrong parent information is obtained. To deal with this problem, changes were made so that when a parent was found with WM_StartScan and it was the beacon without GameInfo, GameInfo is zero-cleared. In additional, the sample demo was changed to actually check the evaluation.
With the multiboot-Model demo, when a child reconnects to the parent, the channel of the parent changed unexpectedly and the connection could not be established.
When using a cable to connect IS-NITRO-EMULATOR hardware, all channels can be used for connections, and this problem occurs when using the actual wireless feature.
This bug was fixed.
In the makebanner tool that was added in 2.0 PR 6 to generate banner files, there was a problem that caused the first line of the description in the banner spec file to be ignored. This problem occurred when the first line in the banner spec file was not a comment line. This has been fixed.
When the character code in the banner spec file was not correct, the empty file was output without generating errors. This problem was solved and changed the description regarding the character code of the reference to "UTF-16LE with BOM."
Even though libsyscall.a that is embedded in the final ROM was specified with the make variable LIBSYSCALL, due to the link order of linkers and libsyscall.a was linked as in the default setting.
To avoid relying on the link order specification when specifying LIBSYSCALL, the storage location of the default libsyscall.a was separated from other SDK libraries. By doing so, libsyscall.a files that are specified with LIBSYSCALL is linked preferentially, not according to the link order specification.
The default libsyscall.a is now stored in the following location. libsyscall.a is common for Debug/Release/ROM versions.
$NitroSDK/lib/ARM9-TS/etc/libsyscall.a
The CodeWarrior IDE users must change the storage location of libsyscall.a in the project file as needed.
When using the compstatic tool to perform the overlay compression process, a problem occurred and in some cases the proper compressed data was not generated. This bug was fixed.
The font set used in banner file was replaced with an updated version. Note that some characters were deleted.
For details regarding banner files, see the guidelines documents regarding the IPL banners.
If the beginning of the banner file stored in ROM was not 512-byte aligned, it does not operate properly. If the value that is smaller than 512 bytes was specified with the AlignAll command in the spec file, a problem may occur.
To avoid this problem, changes were made so that the operation of Segment All is 512-byte aligned without using the value set with AlignAll.
Note that when the AlignAll command is not being used, it is necessary to insert Align 512 before the BannerFile command.
There were some errors in the definition values regarding the hardware register map. These values are not used in SDK, and they will not affect the operation of SDK directly.
REG_GX_VRAMCNT_C_MST_SIZE REG_GX_VRAMCNT_C_MST_MASK REG_GX_VRAMCNT_D_MST_SIZE REG_GX_VRAMCNT_D_MST_MASK REG_GX_VRAMCNT_E_MST_SIZE REG_GX_VRAMCNT_E_MST_MASK
This bug was fixed.
Changes were made so that a separate MI_SendGXCommandAsyncFast() can be started from the DMA callback that was started by MI_SendGXCommandAsyncFast().
MI_SendGXCommand() was using the automatic DMA, and there was a possibility of conflicting with another automatic DMA. Because of this, MI_SendGXCommand() was made to loop with immediate DMA and the automatic startup was eliminated. The former MI_SendGXCommand() was changed to MI_SendGXCommandFast(), but this includes automatic DMA and should be used with caution.
When the FS_GetPathName() function is called, there is a possibility of stopping by SDK_ASSERT because of the errors in the internal process.
This problem was fixed.
A change was made on the ARM9 side to call CARD_Init() from OS_Init().
Corrected the card removal detection process. Previously, some parts such as the card removal during sleep were not working properly.
Previously, to detect card removal, the CARD_IREQ interrupt was checked by ARM9, but the new method uses polling with ARM7. Normally it checks whether the CARD_IREQ interrupt is generated, but when the ROM header information is referenced and then that card uses the CARD_IREQ interrupt, it is done by loading the card ID. When the removal is detected, ARM7 notifies ARM9.
As a countermeasure for the coordinate jumping which occurs when the pen is released, the conditions that becomes INVALID were changed, and the determination is based on the stricter rules. There may be a possibility of increasing the number of cases where the INVALID flags become on.
NITRO_COMPRESS is specified for make, an error is generated when the base names (the part without the file extension) for the .nef file and the .sbin file, which is the binary for the resident module.
mb_child.srl is 10 characters, it does not work properly.
To recover from sleep by the IREQ interrupts of the Game Pak, it may recover, not only by the removal of the Game Pak, but also by the interrupt from the Game Pak device whose IREQ interrupt is being used for other things.
Consequently, to make the system wake up from sleep by the removal of the Game Pak, proceed only when the Game Pak inserted in the slot is the one expected in the application. Otherwise, do not specify PM_TRIGGER_CARTRIDGE for the trigger for waking from sleep.
(2004/09/21)
WM_Initialize function was left in cache in dirty state, it affected the operation of the WM library. This problem was solved.
minPollBmpMode in WM_StartMPEx was set to TRUE with a parent and the parent communicated with only a certain child for a fixed period of time, other children were disconnected because of the timeout. Especially if the sequential communication was being used at ports with number 8 or higher and some children were forcibly disconnected, the above mentioned problem occurred easily. To solve this problem, change was made so that during the MP communication both the parent and children transmit Keep Alive frame with the number of sendable bytes set to 0, only if minPollBmpMode is set to TRUE.
WM_GetMPReceiveBufferSize and WM_MP_SIZE_PARENT_RECEIVE_BUFFER.
WM_STATECODE_CONNECTED, DISCONNECTED, changes were made so that aid is always the AID of the connection targets. Its own AID is assigned to myAid.
docs/TechnicalNotes/WirelessManager.doc. A draft was released.
When loading an overlay with the program that was built by specifying NITRO_COMPRESS, the entire BSS region was not cleared and the variable of the initial value 0 was not initialized properly. This problem was solved.
A system that calls the callback when the Game Pak was pulled out while playing the game. It becomes valid if the Game Pak library was initialized with CARD_Init(). With the default setting, it does not do anything.
A system that calls the callback when the Card was pulled out while playing the game. With the default setting, both processors become the halt state and stop.
When creating a display list that was packed with G3C, indeterminate data was written because of the processes that deal with the geometry FIFO hardware problems. This problem was solved.
Previously, the RTC interrupt process was emulated by polling at ARM7 because of the conflict problem with IS-NITRO-DEBUGGER. The change was made only with the FinalRom library, and now the RTC interrupt of the NITRO hardware is used.
With the Debug version and Release version, the RTC interrupt is emulated by polling, as it was done with previous versions.
The MIC_StartAutoSampling and MIC_StartAutoSamplingAsync functions used I/F that specifies the structure directly at the parameter. To cut down on the stack usage, it was changed to the I/F that specifies a pointer to the structure.
The sound library included with NITRO-SDK became the 2004/09/16 version.
Included an addbanner tool for creating the test viewer of the banner file. This tool creates the ROM file that displays the banner information on NITRO screens.
Added the demo that creates the final ROM. This demo shows an example of the process that incorporates files that are necessary to be included in the final ROM.
The information in this demo is as of the time of the SDK release. The rules regarding the submission of final ROM may change after the release, so check the latest information on the company's support web site.
Reference for the attachsign tool is not complete.
(2004/09/13)
Added functions that obtain the owner information that is saved in the Nintendo DS system. It allows to obtain the owner information that the end user edited by using the IPL program in the system.
Also, the function that obtains the MAC address of the wireless hardware in the system was added. The MAC address is set to a different value for each hardware system, and it can be used with an application that does not use the wireless feature.
These are the three functions that were newly added.
OS_GetOwnerInfo()
OS_GetOwnerRtcOffset()
OS_GetMacAddress()
Implemented soft reset, and the program can be restarted from the entry point. It is possible to assign any u32 value at the reset time and pass it to the rerun module. This function does not initialize the hardware. Because of this, the processes such as automatic DMA must be terminated before calling this function.
However, the first 16 KB of the ROM data that was loaded at the startup is not reloaded at reset time, and the execution cannot be done if this part is destroyed. The library does not determine it, so it is necessary to make sure that it is not destroyed by the software.
When the system has been started as a child by multiboot, the system cannot be restarted with OS_ResetSystem(). To proceed safely, call OS_Panic() inside OS_ResetSystem() to stop. (after outputting a message, it becomes an infinite loop, except the FINALROM version). If there are any problems with the operation, determine if it is the multiboot child by using MB_IsMultiBootChild() and switch cases.
Added the OS_ClearAlloc() function that destroys the memory allocation system after it was build in arena with OS_InitAlloc(). After calling OS_ClearAlloc(), a new memory allocation system can be built in the same arena.
When there is an attempt to set a new alarm by using the alarm structure that is being used with alarm and V-count alarm, it stops with OS_Panic() regardless of the build method. Previously it stopped only the DEBUG build and others entered infinite loop.
Added the bit definition of the DMA registers in $NitroSDK/include/nitro/mi/dma.h. Previously it was defined in the header file in the library construction tree, but the location has been changed to make it accessible from an application.
Added functions are shown below.
| When Initializing | |
|---|---|
WM_Init |
Synchronous function that initializes the work buffer required for the library. |
WM_Enable |
Changes the wireless hardware to be the usage permitted state. It also starts the LED to blink. |
WM_PowerOn |
Starts up the wireless hardware and executes initialization that is necessary. |
| When Stopping | |
|---|---|
WM_PowerOff |
Shuts down the wireless library. |
WM_Disable |
Changes the wireless hardware to be the usage prohibited state. It also stops the blinking of the LED. |
WM_Finish |
Synchronous function that stops the library and releases the work buffer. |
To reduce the battery power consumption, try not to start up the wireless hardware until immediately before the startup of the actual wireless communication (WM_PowerOn). Also, when the wireless communication is not needed (WM_PowerOff), shut down the wireless hardware.
WM_SetMPDataToPort() to return a success value even if the transmission was not complete due to the weak radio wave signals. This change solved the rare problem that stopped the data sharing.
pollBitmap (Poll map) was not being sent to itself, and it was causing a problem when the target child for the communication was switched by pollBitmap. This problem was solved.
WM_INVALID_PARAMETER error is returned when a specified value is larger than the size of the data that can be transmitted with one MP communication. Added a feature to debug output the warning when the transfer data size is larger than the recommended value, as it is explained in the programming guide line.
WM_StartMP(), was set to WM_STATECODE_MP_IND, it only passed WM_ERRCODE_SUCCESS as errcode. With NITRO-SDK 2.0 PR6 and later versions, WM_ERRCODE_INVALID_POLLBITMAP is returned when itself was not included in pollBitmap of MP.
This situation occurs frequently when there are more than two children in the MP communication, and it should not be treated as unrecoverable error.
WM_ERRCODE_SUCCESS, WM_ERRCODE_TIMEOUT, and WM_ERRCODE_FAILED were passed as errcode when the state value, which is the argument for the callback to WM_StartMP(), was set to WM_STATECODE_MP_IND. It was corrected as shown below.
WM_ERRCODE_INVALID_POLLBITMAP when itself is not included in pollBitmap at the corresponding MP frame. This occurs frequently when more than 2 children are used for the MP communication, and it should not be treated as unrecoverable error.
WM_ERRCODE_FAILED was returned when itself was included in pollBitmap with MPACK (in other words, when the parent could not receive the reply). This was changed to return WM_ERRCODE_SEND_FAILED.
WM_ERRCODE_SUCCESS, WM_ERRCODE_TIMEOUT, and WM_ERRCODE_FAILED were used as the errcode that was passed to the callback of WM_SetMPData() and WM_SetMPDataToPort(). However, WM_ERRCODE_TIMEOUT and WM_ERRCODE_FAILED were combined into WM_ERRCODE_SEND_FAILED. In doing so, WMPortSendCallback.destBitmap now includes the bitmap of aid for the child that needs to retry after the communication failure. (the child that was disconnected during the communication is not included in destBitmap.)
WM_StartMP() was set to WM_STATECODE_MPEND_IND.
Previously, the order of callbacks was:
WM_SetMPDataToPort())
WM_STATECODE_MPEND_IND (callback of WM_StartMP())
WM_SetPortCallback())
However, the order was changed to:
WM_SetPortCallback())
WM_SetMPDataToPort())
WM_STATECODE_MPEND_IND (callback of WM_StartMP())
This change was made so that data that reflects the latest receive data is transmitted immediately when the standard structure such as executing the next WM_SetMPDataToPort() by the callback of WM_SetMPDataToPort() is used for the program.
WM_SetMPDataToPortEx() function. User defined data can be added to the argument of the transmission complete callback.
WMParentParam was set to the size that was 2 bytes smaller than the specified value. This problem was solved. parentMaxSize and childMaxSize were the parameters that specify the maximum size of user data to be transmitted. There is no need to count the size of the control data in the wireless library.
WMParentParam.KS_Flag.
ksFlag was added to each of the function macros of WM_SIZE_MP_PARENT_SEND_BUFFER, WM_SIZE_MP_PARENT_RECEIVE_BUFFER, WM_SIZE_MP_CHILD_SEND_BUFFER, and WM_SIZE_MP_CHILD_RECEIVE_BUFFER.
To calculate the buffer size for key sharing, specify TRUE, if not FALSE, to ksFlag.
WM_Reset was called.
WM_SetMPFrequency that changes the frequency of MP communication dynamically.
Included the icon in the following location to indicate the strength of wireless communication. For more rules and regulations, see the guidelines for the wireless communication.
$NitroSDK/data/wl_icons
Test released WBT, the library that enables the block transfer protocol between a parent and a child by using the MP communication of the wireless library (WM).
The following problems have been found in this test release.
The sound library that is distributed with NITRO-SDK became the 2004/09/02 version.
Added feature for compressing the resident module that is loaded with IPL. Because of this, ROM capacity and the initial load size for the startup can be reduced.
In the make system of SDK, this feature is automatically enabled if a value is set to the macro variable NITRO_COMPRESS. Consider the tradeoffs in the extraction time before using this feature. When the compression is enabled in SDK, the following processes are executed.
crt0.c after it was executed.
It is possible to compress the overlay module in the same way as the resident module. Extraction of the overlay module is integrated into the related APIs, so there is no need to be conscious about the processing when you access the module via API.
In order to implement this process, the following tool files have been changed from NITRO-SDK 2.0 PR5. When using an unique rsf file and lcf.template file, these files need to be changed.
$NitroSDK/include/nitro/specfiles/ROM-TS.rsf
$NitroSDK/include/nitro/specfiles/ARM9-TS.lcf.template
This compression and extraction processes can be applied to the execution module in the ROM file that is passed to the multiboot child.
Changes were made to startup nitload of the sample program that is included in the IS-NITRO-DEBUGGER package by specifying run for the make command target.
Included ferret (ARM7 component without the wireless features) that supports each TS versions of the hardware such as IS-NITRO-EMULATOR. Normally, there should not be any problems with using mongoose (ARM7 component with the wireless feature), so there is no need to use ferret in the TS environment unless you need to compile the source for the TEG environment without any changes.
Previously, it was made to get out of the function with interrupts prohibited when the heap check was executed in OS_CheckHeap() and the check failed. This problem was corrected.
There was a problem with the runlength compression routine at tools/bin/ntrcomp, and the 129 to 130 bytes at the end of file were not extracted properly if the uncompressed data block size at the end of file was 129 to 130 bytes. This problem has been changed.
With the process that checks to make sure that multiple automatic DMAs are not started, the ones that are started and the ones that are not started were treated the opposite way. This was corrected so that the check is executed properly.
With NITRO-SDK 2.0 PR5, there was a problem that the wireless feature did not work properly when the wireless and sound features were used at the same time. This problem was solved.
However, because of the DMA hardware specification, there is a possibility of interrupting the sound when the playback causes a large burden on the data transfer, such as playing the waveform data with the sampling rate of 44kHz at the pitch that is 3 octaves higher.
A problem was found and the return value of the MB_GetSegmentLength function was smaller that the size that was actually required. This problem was solved.
There was a problem with the Debug version of the MB demo Multiboot sample in NITRO-SDK 2.0 PR5, and the startup was stopped with GX error. Also with the Debug version, there was a problem that caused the improper operation in the interrupt hander during the downloading process due to the lack of stack area.
When the backup access function of CARD was called, the function failed only at the first time it was called. This problem was solved.
CharacterRecognition-1 demo in NITRO-SDK 2.0 PR5 was not working properly due to the stack overflow. This problem was solved.
Added console output functions such as OS_TPrintf that reduces the stack consumption size by using OS_VSNPrintf. With OS_TPrintf, the code usage and stack usage are reduced by removing floating points from the usable format.
Usable formats depend on OS_VSNPrintf. For details, see the OS_VSNPrintf manual.
Reference for compstatic and attachsign tools is not complete.
(2004/08/30)
WM_StartConnect() function and the interface of the WMStartParentCallback structure were changed.WM_StartMPEx() function to allow detailed settings.WM_SetGameInfo() function has changed.WM_DisconnectChildrenWM_GetMPSendBufferSizeWM_GetMPReceiveBufferSizeWM_GetAllowedChannelWM_SetEntryWM_GetLinkLevelWM_ConvGgid*WM_Disconnect() functionAdded processes to deal with hardware restrictions or generate warnings for the automatic DMAs that do not process immediately, listed below:
V-blank startup
H-blank startup
Display synchronization
Work RAM display
Memory Card data
Game Pak DMA
Geometry Command FIFO
The automatic DMAs cannot be used together. When an attempt was made to start multiple DMAs, it was stopped with OS_Panic(). However, H-blank startup DMA and V-blank startup DMA can be used together.
Also, the following corrections were made to the Geometry Command FIFO DMA.
MI_SendGXCommand() was moved to ITCM.MI_SendGXCommandAsync() was changed so it does not use the automatic DMA of the Geometry Command to make it possible to use it with other automatic DMAs. The asynchronous transfer became possible by controlling the immediate DMA using software interrupts.MI_SendGXCommandAsync(), which uses the automatic DMA, was changed to MI_SendGXCommandAsyncFast().Included the mongoose component and libspi., a library that support each version of TS hardware. To switch the component and library in the make system of SDK, set the TS board version number for the environment variable NITRO_TS_VERSION. If the NITRO_TS_VERSION is not set, then NITRO_TS_VERSION=100 (IS-NITRO-EMULATOR hardware version D) is selected.
To create an application that supports IS-NITRO-EMULATOR hardware version E, it needs to be set as NITRO_TS_VERSION=200.
The supported components and libraries are shown below.
| TS version number | mongoose/libspi.a file names that correspond (e.g. for ARM and Release versions) |
| 0 |
$NitroSDK/component/mongoose/ARM7-TS/Release/mongoose_sub_TS0.*$NitroSDK/lib/ARM9-TS/Release/libspi_TS0.a
|
| 100 |
$NitroSDK/component/mongoose/ARM7-TS/Release/mongoose_sub_TS100.*$NitroSDK/lib/ARM9-TS/Release/libspi_TS100.a
|
| 200- |
$NitroSDK/component/mongoose/ARM7-TS/Release/mongoose_sub_TS200.*$NitroSDK/lib/ARM9-TS/Release/libspi_TS200.a
|
Due to the increasing size of the source code, it is increasingly difficult to support the wireless component of mongoose in the TEG environment. Because of this, support for this feature has been terminated.
makeromCorrected makerom, and added file names and file directory names that start with a dot ".?*" to the initial values used for Reject (or with wildcard it is ".?*") By doing so, files in the .svn directory, which is the control directory of the version management system Subversion, are not added to the ROM file.
As in the previous version of makerom, in order to add the files that start with ".?*" to the ROM file system, Reject must be reset at the beginning of the RomSpec section in the rsf file.
Reject CVS vssver.scc
If you were already using the file name that begins with ".", pay special attention.
NITRO SDK PR5 uses version 0.6.1 of CodeWarrior for building the SDK binary file. CodeWarrior 0.6.1 is included in the SDK.
In the ARM9-TS.lcf.template file, the way the .itcm/.dtcm sections were placed was different from what was expected in makelcf, and the codes defined in the .itcm/.dtcm sections were not placed in the autoload section of ITCM/DTCM.
Makelcf was corrected, and in case an Object/Library description did not limit the section, the section placed by this description is now limited to the basic section used by the compiler (such as text, .rodata, .data, and .sdata). It does not include sections such as .itcm/.dtcm that were newly defined in theNITRO-SDK.
When setting the mosaic size, there were problems with G2*_SetBGMosaicSize(), which clears the OBJ mosaic, and G2*_SetOBJMosaicSize(), which clears the BG mosaic.
These problems are fixed.
GX_InitEx() in gx.hIn $NitroSDK/include/nitro/gx.h, GX_InitEx() and GX_GetDefaultDMA() were not declared as inline functions. This problem was corrected.
The CARD module now supports FLASH device as well as EEPROM device. With sub board and flash card, this can be used on the retail product and the debugger.
CARD_Init() with interrupts prohibitedThere was a problem when calling CARD_Init() with interrupts prohibited, the control was not returned from the function.
This problem is fixed.
CARD_IdentifyBackup()After calling CARD_IdentifyBackup() and its process has completed, the callback function that was specified with the last executed CARD asynchronous function was called again.
This problem is fixed.
When executing a DMA transfer using either the Main memory display startup DMA mode or the H-Blank DMA mode, the access right priority must be "ARM9." Otherwise, the display may not appear properly due to a delay in the DMA automatic startup when ARM7 tries to access the main memory. The access right priority is specified with MI_SetMainMemoryPriority().
Changes were made so that switching access rights is done with gx/UnitTours/2D_BmpBg_MainRam and gx/UnitTours/Window_HDMA, which use these DMAs. Also, the same information was added to the related reference manuals.
If the Tick value was obtained while the compiler optimization level was at or above a certain level, an correct value could not be obtained when the timer interrupt used with the Tick value was issued at a specfic time.
This problem is fixed.
In NITRO-SDK 2.0 PR4, the interrupt check flag (IrqCheckFlag) was automatically set to ON during V-Blank. This change was cancelled in the ARM9 library, and it was returned to the previous setting.
Regarding the operation to turn IrqCheckFlag ON internally in the OS, IrqCheckFlag can be called multiple times without causing any problems, so there are no problems with IrqCheckFlag being turned on every time V-Blank is called in the application. However, it was the cause of the malfunction for the application that turns on IrqCheckFlag once every two frames during the V-Blank process in order to update the status at the timing of 30 frames per second.
This is equivalent of the IrqCheckFlag patch in version 2.0 PR4.
As announced in Note: 10-02, the DTCM addresses have changed, but there was one part that was not changed.
This part was fixed. As a result of this change, DTCM is always 0x27c0000, regardless of the environment.
PM_Init() inside OS_Init()PM_Init() is now called from inside OS_Init() of ARM9.
OS_GetConsoleType()When using IS-NITRO-DEBUGGER, if the Game Pak slot power was on, the result of the operating environment obtained by OS_GetConsoleType() was returned as IS-NITRO-EMULATOR, which was a wrong result.
This problem is fixed, so the function returns IS-NITRO-DEBUGGER, a correct result
A hardware problem was found in determining whether the touch panel is being touched. If the coordinate value was measured when it was halfway between being touched and not being touched, sometimes it became a correct value.
Now the RTC alarm can serve as a trigger to awaken from sleep.
In previous versions, 12- or 24-hour time notation can be selected for the notation display format. Since the 24-hour notation is used in the boot menu, the time format has been fixed to 24-hour format to avoid problems.
The time display selection API can no longer be used, and the information indicating morning or afternoon has been deleted from the API. Also, the time notation display in the sample demo rtc-1 is fixed to 24-hour notation.
Because of the operation in the NITRO boot menu, the A button is more likely to be pressed when starting up of a game application. It requires some caution if the application causes some actions by pressing A button.
For determining some of the demo button triggers (buttons that were newly pressed in that frame), the initial value was set to 0 (not being pressed). However, this was changed so that the initial value is set with the current status of the button.
ntrcompAdded reference manuals for the ntrcomp tool and ppmconv* tools (ppmconv/ppmconv8/ppmconvbg ).
None.
(2004/8/11)
$NitroSDK/build/demos/wm/dataShare-1
WM_SetLifeTime()
WM_MeasureChannel()
WM_InitWirelessCounter()
WM_GetWirelessCounter()The DS Download Play library was added to NITRO-SDK. This is the API that provides the DS Download Play function, which sends the game program to the NITRO that has no card. Internally, this library uses the wireless manager (WM) library.
The program for executing multiboot, mb_child.srl (changed from mb_child.bin in SDK 2.0 PR5), was included in the directory shown below. This program operates the same way as the retail version of a child that has no card. Use this for the operation tests until the multiboot feature is added to IPL.
$NitroSDK/build/demos/mb/multiboot
Demo sample for the multiboot function that was added at the same time is included in the directory shown below.
$NitroSDK/bin/ARM9-TS/Release/mb_child.srl
This is the API for controlling the power management IC. By using this library, it is now possible to manage the LCD and backlight power supply and to check the power remaining in the battery.
Changes were made so that the one time touch panel sampling can be processed during the microphone auto sampling. When the touch panel request was received during the microphone auto sampling, the touch panel data read process is executed the next time the microphone sampling ends.
If the touch panel sampling was not completed before the next microphone sampling time, it is assumed to that the microphone's data has dropped and the microphone sampling value will be interpolated by using the immediately preceding value.
A demo for this feature is included in the directory shown below:
$NitroSDK/build/demos/spi/spiMonkey2
IS-NITRO-DEBUGGERWith the hardware with the mass produced version of the power management IC (PMIC), the preprocessing is now required to operate the amp in the PMIC to obtain the correct microphone output value. For this, processes that operate parameters such as the PMIC amp gain value were added to the mic-1, mic-2, and spiMonkey demos.
Also with this preprocessing, a macro value SDK_TS_VERSION was introduced to be able to work with different versions of PMIC. The environment variable NITRO_TS_VERSION was added to change the macro value dynamically. The NITRO_TS_VERSION value defined when it was built is passed to SDK_TS_VERSION, which takes the values shown below.
| SDK_TS_VERSION | Description of the device |
| 0 | From TS breadboard to IS-NITRO-EMULATOR Version C. |
| 100 | IS-NITRO-EMULATOR Version D. |
| 200 | The device equipped with the next version of PMIC. |
With the PMIC of the IS-NITRO-EMULATOR Hardware Version D, a significant amount of noise is added to the microphone device if the backlight of the LCD is lit. This hardware problem will be solved but, until then, turn off the LCD when you use the mic-1 demo microphone.
The mic2wav opened the output file as a text file, and data was not converted properly. This problem is fixed.
The LCD power management function was changed to PM_SetLCDPower. Along with this change, the following functions and the definitions of the enumerator types were deleted.
GX_PowerLCD(), GX_PowerLCDTop(), GX_PowerLCDBot()
GX_POWER_LCD, GX_POWER_LCDTOP, GX_POWER_LCDBOT
G3*_MultTransMtx33To shorten the geometry engine execution time, added the G3*_MultTransMtx33 function, which multiplies by packing G3*_MultMtx33 and G3*_Translate as one matrix.
Added GX_InitEx(), GX_SetDefaultDMA(), and GX_GetDefaultDMA() to use as a function to set and obtain the DMA number used by GX. By specifying GX_DMA_NOT_USE for the DMA number, it can be set not to use the DMA.
GX_PowerGeometry() and GX_Power3D()With GX_PowerGeometry(), GX_Power3D(), the power for the geometry engine was not turned off. This problem was solved.
Made changes so that the BG mode and BG0 2D/3D selection flag were reflected to the register even when it is not in display mode. This value is referenced for using display capturing when it is set other than graphics display mode.
Released the function groups for accessing the devices that are on the NITRO-CARD. It can be used on the retail product by using the sub board and flash card.
FS_ReadDir did not matchWhen using the FS_ReadDir function to enumerate a directory entry, if a directory entry already exists in these files, the obtained file ID did not match the actual ID. This problem is fixed.
Note 13-14: (DevEnd) Corrected the problem when expanding the
makelcf / makerom variables; added support for the variable definition files
With makelcf / makerom, in some cases when setting a string that exceeds 1000 characters for the variable that can be specified with the –D option, and then expanding it in the template file, an error occurred and stopped the process. This problem is fixed.
Also, the process of passing variables by using command lines will be restricted by the maximum length of the command line set with each command line process. To prevent this problem, the variable definition can be specified from the external file. Because of this, by giving the file with the description of [variable name = value] to makelcf / makerom with the –M option, the variable definition can be done without having to worry about the restriction on the command length of the command lines.
The correction was made so that the additional information used by the debugger for tracking the autoloaded codes is output to the overlay name file. To be more precise, the change was made in the definition part of the overlay name file for the *.lcf.template file in
$NitroSDK/include/nitro/specfiles
By using this additional information, debugging of the autoload module is possible. For more information on the plans for this feature to be added to each debugger system, refer to the release note for each debugger or the support site.
Renaming process of the C++ library to CXX failed in the mingw environment. This problem is fixed.
Set up the V blank counter and added the function OS_GetVBlankCount() to obtain the value.
PAD_SetIrq() and PAD_ClearIrq()Eliminated PAD_SetIrq() and PAD_ClearIrq() because the key interrupt could not be used due to the hardware restriction. However, the key interrupt can be used for returning from the sleep mode. In that case, specify the condition with PM_GoSleepMode().
For synchronous DMA, the process was added after DMA to make it wait while the DMA is busy.
When these synchronous DMA APIs are placed on the TCM, ARM9 did not wait for the completion and is returned from API even with starting up the DMA. This was corrected so that it always waits for the completion with the synchronous DMA, regardless of the transfer location. If it is not necessary to explicitly execute the process to wait for the DMA completion, use the asynchronous DMA API.
The following instructions have been changed:
MI_DmaCopy16/32
MI_DmaFill16/32
MI_DmaSend16/32
MI_DmaClear16/32
MI_VBlankDmaCopy16/32
Changed the sound libraries distributed with NITRO-SDK to the 2004/08/10 version.
3D_BoxTestWith the GX demo 3D_BoxTest, because the box text was executed without setting 1 for the PolygonAttr FAR clip flag and the 1-dot polygon display flag, the proper result may not have been obtained due to the hardware settings. This was corrected by setting a flag immediately before the Boxtest.
LinesOverWith the demo LinesOver, G3X_GetPolygonListRamCount() and G3X_GetVtxListRamCount() were called while the geometry engine was busy, and the value that was being rendered was obtained. The process was added immediately before it to wait for the process of the geometry engine to complete.
Also, before the rendering was complete, G3X_GetRenderedLineCount() and G3X_IsLineBufferOverflow() were called. They were moved to after the V-Blank.
spiMonkeyCorrected the output screen of the SPI demo spiMonkey to be on the touch panel screen.
In the past, the char types switched between signed and unsigned (unsigned for jp) by the value for the NITROSDK LANG, but it was standardized as signed. This change was introduced with NITRO-SDK 2.0 PR1.
(To be corrected in the next or a later release)
PM_GoSleepMode(), RTC alarm, game pak, and card interrupts are not yet supported.IS-NITRO-DEBUGGER, OS_GetConsoleType() returns a wrong result (IS-CGB-EMULATOR).(2004/07/29)
Added and revised the section regarding the WM Library in the Reference Manual.
There is no change in the library itself and the library header file between SDK 2.0 PR3plus and SDK 2.0 PR3.
(2004/07/27)
In the memory map definitions, defined macro in the system shared region did not match the definition of the system region structure. This error was made during the revision of the NITRO-SDK 2.0 PR2.
This problem is fixed.
In the NITRO-SDK library header file, the padding warning switch for the structure was turned off, and was not turned back on. Because of this problem, the padding warning switch was left OFF. This was not intentional.
This problem is fixed. Until now the padding warning did not appear when you compiled the program. However, this change may bring up padding warnings that were not generated before. The following methods can prevent this problem.
make CCFLAGS_WARNING='–w all,nopadding'
// suppress the padding warning
#pragma warn_padding off
struct padded
{
u16 leng;
// double-byte padding inserted here
s32 data[4];
};
// restore the padding warning
#pragma warn_padding reset
To suppress padding warnings in the entire source file, add #pragma warn_padding off at the beginning of the source.
This is an urgent release, so the remaining problems that existed in SDK 2.0 PR2 still exist in this version.
(2004/07/26)
Released the WM (Wireless Manager) as the lower bit library to drive the wireless device.
$NitroSDK/build/demos/wm
This directory contains a sample function. At this point, it operates when the target is set to TS. Success is not guaranteed when the target is set to TEG or when using it with ensata.
The communication functions that are not yet supported in this version, such as wireless DS Download Play (multiboot) and block transfer, and the enhanced version of the upper level library, are under development.
(This item applies only to the TS environment. With the TEG environment, there is no change in the memory map.)
Reviewed the memory map and expanded the MainRAM region that can be allocated to ARM9 by default.
More specifically, DTCM was placed in the region that starts at 0x2380000, but now starts at 0x27C0000. Along with this change, the MainRAM region that is allocated to ARM9 was changed from 0x2000000—0x237FFFF to 0x2000000—0x23BFFFF (increased by 256KB). The region that can be allocated to ARM7 was changed to 0x37C0000—0x37FEFFF.
As described in Note 10-02, the DTCM address was changed for the TS environment only. The makelcf's start-up parameter ADDRESS_DTCM was added to notify the lsf file of the different DTCM addresses used by TEG and TS. When NITRO_PLATFORM is set to TEG, it is 0x02380000. When NITRO_PLATFORM is set to TS, it is 0x027c0000 (in order to handle 8MB main memory, 0x400000 was added). Use this variable so that TEG and TS can share the lsf file.
For example:
Autoload DTCM
{
Address $(ADDRESS_DTCM)
Object * (.dtcm)
}
A link error occurred because the label for the exception table was not defined when the code was created with C++ exceptions. This problem is fixed.
The system call SVS library was updated, and the functions shown below were added. Also updated the reference manual to include the new functions.
Newly added functions:
SVC_Div()
SVC_DivRem()
SVC_GetCrc16()
SVC_Halt()
SVC_IsMmemExpanded()
SVC_Sleep()
SVC_Sqrt()
SVC_UncompressHuffman.html()
SVC_UncompressLZ.html()
SVC_UncompressRL.html()
SVC_UnpackBits.html()
There were places where the Lock ID (u16) of the lock functions in the OS was declared as u16 and u32 in the argument. It was standardized to be u16. However, the return value for the function that returns the lock ID or error message was not changed and is still u32.
The lockID type of the argument changed from u32 to u16.
OS_LockByWord() OS_LockCartridge() OS_LockCard()
OS_UnlockByWord() OS_UnlockCartridge() OS_UnlockCard()
OS_TryLockByWord() OS_TryLockCartridge() OS_TryeUnLockCard()
The return value changed from s32 to u16.
OS_ReadOwnerOfLockWord()
In the manual, added a caution that the return value is s32.
OS_GetLockID()
Changed the notation of the following function names from UnLock to Unlock.
OS_UnlockByWord()
OS_UnlockCartridge()
OS_UnlockCard()
(As mentioned in Note 9-23, this change was intended for version 2.0 PR1. However, the change was made in this version by mistake.)
The names of the MI_GetCartridgeRomCycle* function was revised and standardized as 1st and 2nd. Along with this change, the enumeration types MICartridgeRomCycle1 and MICartridgeRomCycle2 were changed to MICartridgeRomCycle1st and MICartridgeRomCycle2nd.
(To be corrected in the next or a later release)
(2004/07/20)
Note: The bold paragraphs in Note 9-01 were added on 2004/07/26.
To support the IS-NITRO-DEBUGGER and Nintendo DS software developer's board NITRO-TS, the default target changed from TEG to TS. (From now on, IS-NITRO-DEBUGGER and NITRO-TS refer to the same thing, unless otherwise noted.)
The TS module is created by not defining NITRO_PLATFORM for the environment variable or the macro variable of the make command, or by setting the value to "TS". Here is an example.
% make NITRO_PLATFORM=TS
Normally, the directory ARM9-TS or ARM9-TS.thumb is created in the subdirectories bin, lib or obj within the directory that executed make. Each module is generated in this directory.
Also, in order to compile with the existing TEG target version, you must explicitly specify
% make NITRO_PLATFORM=TEG
Support for the TEG target version will continue until at least the end of 2004).
Corrected makerom so it matches the specification of the manufactured ROM image. To be consistent with the inspection process during production, the ROM binary file name extension was changed from .bin to .srl.
However, in the makefile description, the target variable name of the ROM image is left as TARGET_BIN.
The link methods for overlays were changed.
An asterisk (*) is no longer used to specify a file with the LCF file.
In the LCF file, all libraries are enumerated, but the positive sign (+) cannot be used for the library name. Because of this restriction, the name of Metrowerks C++ Runtime Library is changed from MSL_C++_NITRO_Ai_LE_strb.a to MSL_CXX_NITRO_Ai_LE_strb.a to make a copy, and the copy is referenced.
In the sample demo in the following directory, the source files are compiled in multiple subdirectories, and are linked by the parent directory.
$NitroSDK/build/demos/tips/MultiLink
Made it possible to add dependent files to the nef and bin files by specifying LDEPENDS_NEF and LDEPENDS_BIN.
NITRO_CODEGEN_ALLAdded the compile switch NITRO_CODEGEN_ALL. Use this switch to create libraries for both ARM and THUMB versions.
% make NITRO_CODEGEN=ARM
% make NITRO_CODEGEN=THUMB
The switch results in the compilation executing twice. (The compilation is executed in the order specified with NITRO_CODEGEN.)
The sound library distributed with the NITRO-SDK became the 2004/06/22 version.
FS_RegisterArchiveName()Due to the internal processing of the FS_RegisterArchiveName() function, an inconsistency problem occurred when the registered archive was released. This problem is fixed.
Sometimes the wrong string was displayed when an interrupt occurred during debugging of the thread with the async demo. This problem is fixed.
FS_WaitAsync is still runningIf the OS_WakeupThreadDirect() function is called while a thread is set to wait for an FS asynchronous function (using the FS_WaitAsync function), control is returned even though the process is not complete. This problem is fixed.
GX_SetBankForTex(), GX_LoadTexEx(), and GX_LoadTex()The three functions that process the noncontiguous VRAM banks had problems with the data transfer, but they were fixed.
In the DEMOLib of the GX demo, the default value of the clear color alpha value was changed from 0 to 31.
FX_AtanIdx() and FX_Atan2Idx()Added the FX_AtanIdx() and FX_Atan2Idx() functions, which return the arctangent within the range of the u16 type. Until now, only FX_Atan() and FX_Atan2(), which return the arctangent in units of radian, were available.
Added the following functions as the API that performs only the calculation without setting the data to the geometry engine.
MTX_FrustumW()
MTX_PerspectiveW()
MTX_OrthoW()
MTX_LookAt()
With these functions, you can obtain the same matrix using G3_FrustumW(), G3_PerspectiveW(), G3_OrthoW(), G3_LookAt().
NITRO_MEMSIZE is set to 8MWhen a file that was compiled with NITRO_MEMSIZE set to 8M during make is executed on a development device with 8MB of main memory, the extended main memory arena is now set properly. Previously, the protection region was not set correctly and had to be set by the application.
Improved thread safety by prohibiting interrupts in a critical section using memory allocation functions, such as OS_Alloc*() and OS_Free*().
OS_JoinThread() and OS_IsThreadTerminated()Added OS_JoinThread(), which combines threads and waits for the specified thread to be terminated, and OS_IsThreadTerminated(), which checks whether the thread has terminated.
The debug build uses ASSERT to check if it overlaps the TCM address, but there was an error with the boundary condition. This problem was fixed.
OS_SetProtectionRegion()OS_SetProtectionRegion() was changed to set and enable the protection region. Before, it was not enabled.
Changed the clock information in the profiler from u16 to u32 to enable the measurement of functions that require more time. Also fixed an error in the calculation of the required compilation time.
Created functions to obtain the compression type and the size of the expanded data in memory. MI_GetCompressionType() obtains the compression type, and MI_GetUncompressedSize() obtains the size of the expanded data.
MI_GetCartridgeRomCycle* functionsStandardized the names of the MI_GetCartridgeRomCycle* functions as 1st and 2nd. In addition, the names of the enumeration types MICartridgeRomCycle1 and MICartridgeRomCycle2 were changed to MICartridgeRomCycle1st and MICartridgeRomCycle2nd.
MI_CpuCopyFast()At debug time, build with MI_CpuCopyFast(), ASSERT was required to be a multiple of 32 bytes. It was changed to a multiple of 4 bytes.
Prohibited interrupts with the DMA parameter setting process (internal function MIi_DmaParams*()) and stop process (MI_StopDma()).
When a 32-bit divisor is set in the Divider, zeros are entered into the upper 32 bits of the Divider's divisor register. By doing so, even if using a division mode with a 32-bit divisor, the Divide-by-0 error flag is enabled only if all 64 bits of the divisor register are zeros.
With the functions that perform sampling via microphones, the available sampling types were expanded, and you can now specify the output in signed data format.
Test released the PRC library, which permits pattern recognition of data drawn on the touch panel.
$NitroSDK/build/demos/prc
Here is the demo.
For more information, see:
$NitroSDK/docs/TechnicalNotes/PatternRecognition.doc
The precision of the data obtained from the touch panel was changed from 12 bit to 9 bit. The lower 3 bits are masked on the ARM7. This change anticipates a compatibility issue that may occur in the future.
(To be corrected in the next or a later release)
(2004/06/16)
When threads were switched in the IRQ handler, the context of the Divider and Square Root Unit were not saved. This has been revised, and the context is appropriately switched.
Corrected the faulty rounding process for negative numbers when using FX_F32_TO_FX32() and made FX32_CONST() an alias for FX_F32_TO_FX32(). Also added the FX16_CONST(), FX64_CONST(), and FX64C_CONST() macros.
Cleaned up the test code that was mixed in with the loop portion of
OSi_IdleThreadProc(), the idle thread execution function located in
$NitroSDK/build/libraries/os/common/src/os_thread.c
spiMonkey demonstrationWhen the spiMonkey demo was built with the Debug version, the demo ran but the screen update rate was extremely slow. This problem is fixed.
makerom/makelcf< variable valuesA bug in handling variable values in makerom/makelcf could prevent normal operations. This bug is fixed.
(To be corrected in the next release)
(2004/6/10)
The defined values for GX_DISP_SELECT_***, the power control register's "LCD output switching flag," were swapped to conform to the final production product (0 and 1 were reversed).
The same revision was performed on ensata. When executing applications created with SDK versions 1.2 or 1.2 RC1 or later on ensata, verify that the version of ensata being used supports this revision.
Added an API to operate a microphone device and demos that use the API. Also added the spiMonkey demo that uses the MIC, Touch Panel, and Sound libraries simultaneously.
Changed the maximum sampling rate that can be specified with auto sampling to 4 times/frame. It is expected that higher sampling rates cannot be guaranteed with the anticipated cost reduction in hardware.
When an interrupt was generated directly after transmitting a touch panel control command to ARM7, a bug prevented returning from waiting for a reply from ARM7. This problem is fixed.
Added an argument in RequestAutoSamplingStart() to specify the buffer size. In doing so, a buffer size larger than the sampling rate can be specified and overwriting with new data can be supported.
TP_SetCallback() argument formatBecause TP_SetCallback() arguments were pointers to function pointers, it was changed so that function pointers could be passed directly as arguments.
async demoThe total size (when loading all threads in the async demo) is displayed as total **** byte. However, an error in the size calculation resulted in an incorrect number. This problem is fixed.
Corrected the problem that prevented the data cache update process from being carried out for each of the functions that operate the overlay module.
FS_SetDefaultDMA() functionA problem caused a file to be loaded incorrectly if DMA settings were changed with FS_SetDefaultDMA() when
executing in an environment that used a NITRO-CARD. This problem is fixed.
When the logical product of IE and IF was 0 at the beginning of an IRQ handler, it would exit without doing anything. This was caused by an infinite loop when an interrupt was generated during IE configuration. This problem is fixed.
Changed the maximum thread count that can be created with the thread system from 8 to 16.
OS_GetNumberOfThread()Added the OS_GetNumberOfThread() function to get the number of threads currently created.
A fixed value had been used when configuring the arena range for ARM7. However, this has been changed to configure an arena for the ARM7 shared WRAM and an arena for the ARM7-dedicated WRAM to take into account the size of the free region after storing the ARM7 program in Shared WRAM and ARM7-dedicated WRAM.
In addition, the two arenas are configured with ARM7 and the
remaining arenas are configured with ARM9 due to reception of defined values from the lcf file when configuring arenas with OS_InitArena().
In a previous version, OS_SetProtectionRegion()
was renamed OS_SetProtectionReginParam(),
and a new function that more directly configured the address and size was named OS_SetProtectionRegion().
OS_GetProtectionRegion() was divided by function into OS_GetProtectionRegionParam(), OS_GetProtectionRegionAddress(), and OS_GetProtectionRegionSize().
The Profile features were separated from the OS library and made into an independent library. In doing so, it is unnecessary to recompile the OS library when Profile features are used.
The necessary libraries can be linked by specifying
NITRO_PROFILE_TYPE=CALLTRACE
when enabling the call trace function and by specifying
NITRO_PROFILE_TYPE=FUNCTIONCOST
when enabling the cost measuring function.
Corrected the problem in the display of indents beyond four levels in the call trace function.
OS_GetConsoleType()Added the OS_GetConsoleType() function to obtain the current operating environment. The value that can be obtained also includes information on the ROM data read device and main memory
size.
OS_Printf(), are handled in the FINALROM buildChanged the way display functions such as OS_Printf() are handled in the FINALROM build. Previously, OS_Printf() was called and became the return function without doing anything, but it is no longer called. In addition, OS_Panic() stops without displaying anything.
The following TCM function names have been changed to match the name specifications for other functions. The left is the function name before the change; the right is the new function name.
OS_SetParamITCM() → OS_SetITCMParam()
OS_SetParamDTCM() → OS_SetDTCMParam()
OS_GetParamITCM() → OS_GetITCMParam()
OS_GetParamDTCM() → OS_GetDTCMParam()
In addition to eliminating the need to recompile the OS library by dividing the profile related features into a separate library, compilation of callTrace-1, callTrace-2, exceptionDisplay-3, functionCost-1, functionCost-2, and functionCost-3 that had not been previously included in the OS demo Makefile are now included.
In the AntiAlias demo, antialiasing was not applied because ClearColor
was not set and blending did not occur with the background color. This problem is fixed.
In the 2D_Oam_5 and Sub_Oam_5 demos, problems in operation with the FINALROM build occurred because the data cache was not flushed. This problem is fixed.
Ensata upgradeDue to an Ensata upgrade, the operating limitations on AntiAlias, PosVecTest, and CurrentMtx, which could only be used while Ensata was operating, were lifted.
Extended palette VRAM configuration names defined with
GXVRamBGExtPltt
GXVRamOBJExtPltt
GXVRamSubBGExtPltt
GXVRamSubOBJExtPltt
have been standardized to notation that includes the slot number. The previous names remain as aliases, although this is not mentioned in the manual.
GX_InitWhen GX_Init() was called multiple times, it would stop because the V-Alarm structure held in static internally would initialize each time. This has been changed so that the V-Alarm structure is initialized only once even if GX_Init is called multiple times.
GX_GetObjThe following in-line functions have been prepared.
G2_GetOBJCharName()
G2_GetOBJColorMode()
G2_GetOBJEffect()
G2_GetOBJColorParam()
G2_GetOBJMode()
G2_GetOBJPosition()
G2_GetOBJPriority()
G2_GetOBJShape()
FX32_CONST() macroAdded the FX_CONST() macro to define fx32 format constants.
MI_UncompressRL8()There was a bug in the MI_UncompressRL8()
function that extracted run-length compressed data in 8-bit units. The bug is fixed.
makerom and makelcfAdded a Tool item to the reference manual that includes an explanation of makerom and makelcf.
A simple tool was included to rewrite information configured with the Boot menu. Use it as a calibration configuration tool for the touch panel. The execution file is:
$NitroSDK/bin/ARM9-TEG/Release/BootMenu.bin
Executing this on TEG causes the basic menu to start up. Because configuration items other than the touch panel may differ from the final product, think of them as reference material at this time.
Changed so that the "–g" option can be used to compile and link when building the FINALROM version in the build environment created with the SDK-supplied CodeWarrior make.
The "–g" option in CodeWarrior adds only debug information to the NEF file; the ROM image binary is the same.
In addition, the NITRO_NO_OPT_G switch is available to compile and link without the "–g" option.
Use the following to remove the "–g" option to build.
make NITRO_NO_OPT_G=1
makeromA bug caused the error message, Wrong format list file to be displayed even when no error had occurred and also stopped the execution of makerom when makerom was
executed in certain environments. This bug is fixed.
(To be corrected in the next or a future release)
spiMonkey, does not operate correctly.(2004/05/24)
Added support for CodeWarrior NITRO V0.5. Added support for the change in library file names and the change in LCF files.
elftobin to makeromChanged the ROM binary creation tool from elftobin
to makerom. This allows the file system and overlay to be supported.
ALIGN(32)The lcf-related files were correct sot that 32-byte alignment might be maintained for the beginning and end of the overlay segments to prevent problems related to the cache line for the overlay.
Added $(LDEPENDS_NEF) and $(LDEPENDS_BIN) to the files dependent on .nef and .bin generation rules, respectively. The specifics are shown below.
$NitroSDK/build/buildtools/modulerule.cctype.CW:
$(BINDIR)/%.nef: $(OBJS) $(LCFILE) $(MAKEFILE) $(LDEPENDS_NEF)
$NitroSDK/build/buildtools/modulerule:
$(BINDIR)/%.bin: $(BINDIR)/%.nef $(MAKEROM_ARM7) $(ROM_SPEC) $(LDEPENDS_BIN)
There are cases when you want to include the NitroSDK header files when C-compiling with a program other than CodeWarrior when creating NITRO-related tools on Windows. But, the processing system for Visual C++ generated an error when nitro.h was included because variable argument macros are not supported.
$NitroSDK/include/nitro_win32.h is available to cope with this situation.
By defining the two define values shown below in nitro_win32.h, it is possible to include header files such as gx.h, memorymap.h, and type.h.
#define SDK_FROM_TOOL
#define SDK_HAS_NO_LONG_LONG_INT_
However, the #define of SDK_HAS_NO_LONG_LONG_INT_ is specified as "to replace 64-bit integers from being long long int to _int64," so this definition is unnecessary in environments where the long long int definition, such as gcc, is enabled.
It was decided that the distribution of the IDE demo sample program for using CodeWarrior would be terminated. Since a NITRO stationary file is already available in CodeWarrior for NITRO, it was decided that the IDE sample was no longer necessary.
Added the ferret integrated component to process various devices. If not specified otherwise, this component connects by default.
The component path is located under
NitroSDK/components/ferret/ARM7-TEG/(Target)
(For the Thumb component, the ARM7-TEG portion becomes ARM7-TEG.thumb.)
Added a library to use the ROM file system in applications created with makerom. Directory list/search, synchronous/asynchronous file read, overlays, etc. are possible.
The FS library supports processes that read access the NITRO-CARD, the NITRO standard software supply medium. The FS library internally switches between using the Game Pak image or NITRO-CARD image as the file system according to the TEG board device connection.
In connection with this, SVC_ReadCard() was deleted.
The touch panel control related APIs are supported.
Be aware that the TP library and API that were distributed in a separate package have changed in connection with the process assignment change for ARM7 and ARM9. In addition, perform the touch panel calibration process again because of the change in the touch panel calibration parameters that occurred in connection with these changes.
The new touch panel calibration binary is
NitroSDK/bin/ARM9-TEG/Release/BootMenu.bin. After starting the binary, select TOUCH PANEL from the screen menu and perform the calibration.
To safely use the Divider and Square Root Unit interrupt processes in callbacks, APIs (CP_SaveContext and CP_RestoreContext) were prepared to store and return the current status of the Divider and Square Root Unit.
In addition, the Divider and Square Root Unit now support multi-threads.
APIs for operating the 2x2 matrix MtxFx22-type variable 2x2 are available.
MTX_Identity22()
MTX_Concat22()
MTX_Inverse22()
MTX_Transpose22()
MTX_Rot22()
MTX_Scale22()
Due to a hardware bug in the command FIFO overflow processing on the TEG board, GX_LoadMtx44 and other functions did not process correctly. This was fixed in the library. This hardware bug will be corrected in the production model.
GX_VRAM_ARM7_128_C to GX_SetBankForARM7()GX_VRAM_ARM7_128_C was added as an argument supported by GX_SetBankForARM7().
GX_VRAM_BGEXTPLTT_01_F to the BG extended paletteCorrected the problem that caused configuration to be incorrect when GX_VRAM_BGEXTPLTT_01_F was set in the API GX_SetBankForBGExtPltt.
Swapbuffer process on the geometry engineAdded the demo below as a method using a polygon counter to determine whether the 3D engine calculation experienced process drop-out.
$NitroSDK/build/demos/tips/SwapCrossOver
When a discrepancy exists with the 2D screen due to a process drop-out on the 3D screen calculation, consider using this method for synchronization that uses a polygon counter.
scaleWCreated the following transparent conversion APIs to set scaleW to a desired value.
G3_FrustumW()
G3_PerspectiveW()
G3_OrthoW()
In addition, MTX_Frustum(), MTX_Perspective(), and MTX_Ortho() are also separately available to create matrices without transmitting to the geometry engine.
GX_Init functionThe implementation of the command FIFO reset process was changed. G3_End() is issued after 128 NOP units are sent as an internal process.
A bug in G3X_SetFog prevented fogMode from returning to 0 from 1. This is fixed.
In consideration of the controlling the various systems that may be
connected in the future, the initialization of the thread system was changed to occur by default. OS_InitThread() is called with OS_Init().
If creating a library that does not use the thread system, compile after defining NITRO_NO_THREAD.
OS_SPrintf()With a smaller code load than the standard springf() function, the OS_SPrintf() format string function and its system were added by partially eliminating output support, such as for floating point decimal values. This function is primarily used on ARM7 for string processing.
MI_ReadByte() and MI_WriteByte() were
prepared for memory byte access in consideration of the convenience of program creation on the TEG version. These will be converted to simple byte access instructions on the production version library.
OS_WaitIrq(), OS_WaitAnyIrq(), and OS_WaitInterrupt()Added the OS_WaitIrq() function that waits for a specified IRQ and the OS_WaitAnyIrq() and OS_WaitInterrupt() functions. OS_WaitIrq() and OS_WaitAnyIrq() give processing over to other threads while waiting for an IRQ.
OS_WaitInterrupt() uses OS_Halt() to wait, so thread movement does not occur. This has been prepared to operate the same as SVC_WaitIntr().
ATTRIBUTE_ALIGN()Added the ATTRIBUTE_ALIGN() macro to specify arrangement alignment when defining variables. The macro name
follows the NINTENDO GAMECUBE SDK definitions.
The size of the low priority idle thread stack created when the Thread system is started is set to 128 bytes on ARM9 and 64 bytes on ARM7 for SVC.
OS_GetLockID() and OS_ReleaseLockID()Added OS_GetLockID() and OS_ReleaseLockID() as a structure to manage lock IDs used by OS.
OS_SetSwitchThreadCallback()Added a callback feature when switching threads. The callback is registered with OS_SetSwitchThreadCallback().
Mutex
with OS_ExitThread()When a thread is ended with OS_ExitThread(),
the Mutex locked by that thread is released.
The main loop process for the ARM7 component is OS_Halt().
OS_SetProtectionRegion7() and
OS_SetProtectionRegion7Corrected so that OS_SetProtectionRegion7()
and OS_SetProtectionRegion7 operate on Region 7 rather than Region 6.
Defined the CPU clock values HW_CPU_CLOCK_ARM7 and HW_CPU_CLOCK_ARM9 for each processor and the CPU
clock value HW_CPU_CLOCK for the current compiler target processor.
OS_Panic() termination operationChanged the OS_Panic() terminate
operation from OS_Halt
to OS_Terminate().
Changed the OS demo structure. waitIrq-1 and waitIrq-2 were added due to this change.
In addition, callTrace-1, callTrace-2, exceptionDisplay-3, functionCost-1, functionCost-2, and functionCost-3 were prepared as demos that do not go in Makefile. These are not included in Makefile because they require that the OS library be compiled using a special option.
Due to hardware specifications, a timing problem with enabling/disabling interrupts and IRQ generation caused IME=0 when an IRQ was generated. When this occurs, it exits without doing anything.
Added a call trace the uses the profile feature of CodeWarrior and a mechanism to measure function costs.
See the following file for an explanation of support for the profile feature by NITRO-SDK.
$NitroSDK/docs/TechnicalNotes/MechanismOfProfiler.doc
Prepared the OS_IE_USER_FLAG0 and OS_IE_USER_FLAG1 check flags, which can be freely used with applications similar to the SDK interrupt causes.
The sound library distributed with the NITRO-SDK is version 2004.4.12.
(To be corrected in the next or a future release)
makerom/makelcf.ensata.(2004/04/05)
We now support
CodeWarrior NITRO V0.4. Therefore, the compiler start time options -avoid_strb and
-avoid_byte have been replaced.
Compiler version
information is stored in verinfo.cw.cc and
verinfo.cw.ld, under $NitroSDK/build/buildtools.
These files will be automatically updated when you upgrade from CodeWarrior
0.3 to 0.4. However, if you downgrade from 0.4 to 0.3, they will not be
updated, which will cause problems. When you downgrade CodeWarrior you must
either manually delete the $NitroSDK/build/buildtools/verinfo.cw.*
files, or input make clean-verinfo from the command line.
GX_HBlankOBJProc() /
GXS_HBlankOBJProc()In
GX_HBlankOBJProc() / GXS_HBlankOBJProc(), actual
behavior was the opposite of the values in the proc parameter.
This has been fixed.
G2_SetOBJAttr() / G2S_SetOBJAttr()In G2_SetOBJAttr() and
G2S_SetOBJAttr(), when you were operating in GX_OAM_MODE_BITMAPOBJ mode and
using GX_OAM_EFFECT_AFFINE, the rsParam parameter
specifications were not reflected in OAM.
This has been fixed.
GX_DisableBankFor*()In GX_DisableBankFor*(),
internal behavior was incorrect, which caused it to behave improperly.
This has been fixed.
NitroPostLinker.batThe NitroPostLinker.bat
file referenced the environment variable CWFOLDER_IRIS.
We changed it to
reference the environment variable CWFOLDER_NITRO.
Due to a link procedure
bug in the fs/file-1 demo, even if you added NitroStartUp(),
NitroStartUp() would not be linked.
This has been fixed.
makerom
(beta version)In the makerom tool, which is currently included as a tool evaluation version, if the ARM9's resident module size was too small, an error was generated.
This has been fixed.
makelcf (beta version)In the lcf template file for the makelcf tool, which is currently included as a tool evaluation version, part of the module size calculation was incorrect.
This has been fixed.
(2004/03/30)
G3_Frustum()
bugThere was a flaw in
$NitroSDK/build/library/gx/src/g3_util.c and the G3_Frustum() matrix could not
be properly set up.
This bug was fixed.
An error occurred and
the program stopped when Slot 0 for the texture image in VRAM_A was set aside
and the image was transferred with GX_LoadTex(). This bug was fixed.
The program stopped with
ASSERT if a process such as a texture load was done when VRAM_B was allocated
to the OBJ.
This bug was fixed.
The return value from
G3X_GetCommandFifoStatus() was not accurate.
This bug was fixed.
A change was made so the
DTCM position could be changed. This is made possible by
changing the HW_DTCM value in $NitroSDK/include/nitro/hw/common/mmap_global.h.
However, a full make must be carried out for the library after the change.
There was a flaw in
$NitroSDK/include/nitro/codereset.h. It always switched to thumb.
This bug was fixed.
When the debugger was
using the exception vector, the hook process for the vector was incorrect due
to the coexistence of settings in the NITRO-SDK. Accurate operation was not
possible.
This bug was fixed.
Until now, a self-cancel of an alarm in the periodic alarm handle was not possible. This is now possible.
A function
OS_IsThreadAvailable() was added to initialize the
thread system and check if it can be used.
Stopped use of ldconst
and lda to specify the assembler for
substituting constants and addresses. It was standardized to ldr only.
(Before Change) (After Change)
ldconst r0, #CONSTANT -> ldr r0, =CONSTANT lda r0,Address -> ldr r0, =Address
There was a mistake in
the assert determination for $Nitro_SDK/include/nitro/gx/gx_bgcnt.h.
This bug was fixed.
A fixed point definition
to show 0.5 was added to $NitroSDK/include/nitro/fx/fx_const.h.
The fixed points of fx16, fx32, and fx64
are defined as FX16_HALF, FX32_HALF, and
FX64_HALF.
Standardized the
rounding up process for FX_MUL32x64C and FX_Mul32x64c.
The ROM file system function and overlay problems were carried over.
(2004/03/17)
Added a PXI Library for carrying out communication between ARM9 and ARM7.
The following graphics samples were added.
|
|
Affine extension/256 colors x 16 extension palette character BG display |
|
|
Affine extension/256 color bitmap BG display |
|
|
Affine extension/direct color bitmap BG display |
|
|
Affine extension/256 colors x 16 extension palette OBJ display |
|
|
|
|
|
One-dimensional mapping/character OBJ display |
|
|
Two-dimensional mapping/bitmap OBJ display |
|
|
OBJ window display |
|
|
Translucent OBJ display |
|
|
Carries out box test |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Displays shadow using shadow polygon |
|
|
Views anti-aliasing |
|
|
Motion Blur effect using capture |
|
|
Sets up clear color |
|
|
Sets up clear image |
|
|
Outputs current clip coordinate matrix and direction vector coordinate matrix |
|
|
Changes texture flip/repeat |
|
|
Polygon line over display |
|
|
Master brightness adjustment |
|
|
Outputs |
|
|
Overflows polygon list RAM/vertex RAM. |
|
|
Obtaining and changing V-counter |
|
|
View port setup change |
|
|
Window transformation with operation during H-Blank period. |
|
|
Window transformation with H-Blank DMA. |
|
|
Common processing |
Added data compression
tool ntrcomp. It is located in $NitroSDK/build/tools/ntrcomp/.
Added document about
installing and using both NITRO-SDK and AGBSDK at same time to
$NitroSDK/docs/HowToJoinAGBDevEnv.txt.
Added the entries 80_EF
and 80_EG to the VRAM bank combination setup. Changed so VRAM can be
aligned to BG or OBJ using EF and EG combination.
In addition, to handle
requests for aligning VRAM with combinations not supported with the SDK, a
document was compiled describing how to add entries by revising the SDK source.
The document is located in $NitroSDK\docs\SDKHowTo/HowToMakeMyVRamBankType.txt.
If the original
PROTECTION matrix stack level was 0 during initialization of the matrix stack,
a stack underflow was caused.
This bug was fixed.
A link was added to go from 3D geometry (G3*) in the left window of the manual to the geometry command cycle list.
Added the function OS_Sleep()
to stop a thread for a specified time.
When the thread was
switched in the IRQ handle, the location referenced in the thread list was
incorrect and a thread was not run unintentionally.
This bug was fixed.
The function
OS_ReadMessage() was created to reference the
first message in the message queue and copy it only. OS_ReadMessage()
is different from OS_ReceiveMessage(). It does not try to send a
message and recover blocked threads. Also, it does not change the content of
the message queue.
With the timer interrupt
during the setting of the IRQ interrupt check flag, an incorrect bit was
accessed and set.
This bug was fixed.
When multiple periodic
functions with similar startup times were input for the V-count alarm, a bug
occurred in which only the first function was executed. This bug was fixed.
Along with this fix, a
change was made so a delay allowed count could be specified for the run time of
the periodic function for the V-count alarm.
A bug was found in the
tick system. The system would only count up to a certain number of digits.
This bug was fixed so that 64-bit
values could be handled.
Conversion macros were
added for time specified in seconds, milliseconds and microseconds; and the
tick count value based on the system clock used in OS_Sleep()
and OS_SetAlarm(). These macros are listed below.
OS_MicroSecondsToTicks( usec )
OS_MilliSecondsToTicks( msec )
OS_SecondsToTicks( sec )
OS_TicksToMicroSeconds( tick )
OS_TicksToMilliSeconds( tick )
OS_TicksToSeconds( tick )
A timer interrupt
callback was setup with OS_SetIrqFunction(), the timer interrupt was started, and the callback
was called. Even if a timer interrupt was setup again at this point, the
interrupt was cleared when it returned from the callback.
This bug was fixed.
OS_DisableInterrupts()Both IRQ and FIQ were
stopped with OS_DisableInterrupts(), but a change was made so only
IRQ was stopped due to conditions related to the debugger.
The lock/unlock and context
switch of the AD Bus stops both IRQ and FIQ.
The specifications were changed so if a debugger exception handler is present it is called before calling the user exception handler.
The categories for the
registers reg_DISP_DISPSTAT and reg_DISP_VCOUNT
were transferred to GX and the names were changed to reg_GX_VCOUNT
and reg_GX_DISPSTAT.
The reg_OS_POWCNT
categories were transferred to SND. The name was changed to reg_SND_POWCNT.
Minor fixes were done to
the ARM9 and ARM7 register tables, $NitroSDK/build/buildsetup/ioreg/io_reg_list*,
$NitroSDK/build/buildsetup/ioreg_sp/io_reg_list*. Almost all of the current
specifications were compiled together. The areas added that were not present
before are mainly in the EXI and PXI categories.
Corrections were done to
some errors in the reference manual. One of these was to change MI_SetWRAMBank()
to MI_SetWramBank(). Also please note that in conjunction with
this change, the html file for the MI_SetWramBank() manual was
changed from MI_SetWRAMBank.html to MI_SetWramBank.html.
This problem was in the
OS. There was a mistake in the IRQ handler table. The interrupt elements
allocated to the bits in the IE register were not all in order and there were
some not being used. This was not considered when the table was made so when
interrupts after unused items referenced the table, they accessed the wrong
areas. This problem was fixed.
Unused items were also
allocated to elements in the table. There were two extra alignment elements in
ARM9 and three extra in ARM7. There was a marginal increase in the memory used.
The ROM file system function and overlay problems will be carried over.
(2004/02/27)
The irisSDK now supports NITRO hardware. At
the same we changed the SDK name to NITRO-SDK.
Notice that following this
name change, in the NITRO-SDK the following changes have been made from irisSDK.
iris.h to nitro.h.include/iris to include/nitro.IrisMain to NitroMain.IRISSDK_ROOT to NITROSDK_ROOT.IRIS_DEBUG
to NITRO_DEBUG.$NitroSDK/tools/elftobin/NitroPostLinker.bat
as a Postlinker for NITRO in IDE.We grouped some of the library source files and header files according to the processor, and stored them respectively in the ARM9/ARM7/common sub directories.
Anyone who until now has
been directly specifying #include <iris/os/alloc.h> instead of
iris.h, os.h when including header files for the OS, etc., must
now specify #include <nitro/os/common/alloc.h>.
We prepared an API (GXS
function group) to support the Sub LCD. We also added demo programs that use
the API. Refer to directories that begin with Sub, under
$NitroSDK/build/demos/gx/UnitTours.
We changed the ELF file
extension to .nef. We also plan to support .nef
with NITRO development-related tools.
We changed the directory
that contains sample code from $NitroSDK/build/tests to
$NitroSDK/build/demos.
We embedded code for
auto test control in some files, for SDK library test processing. In
particular, this code is enclosed in #ifdef SDK_AUTOTEST - #endif.
This code is for our internal use. If you are going to copy sample code and use
it, we do not mind if you remove the auto test code.
It is now possible to
generate a thumb code version library. To switch, you can use the make
command start time variables or the environment variable NITRO_CODEGEN.
Sample command
|
Generate THUMB version code |
|
|
|
Generate ARM version code |
|
|
Currently, if you omit
NITRO_CODEGEN, it will generate an ARM code version library.
We prepared include files that allow each function to switch ARM code / Thumb code generation, and to return to initial settings.
|
Instruct ARM code generation |
|
|
|
Instruct Thumb code generation |
|
|
|
Return to initial settings |
|
|
(Example)
If you want the function void A(void) to generate using Thumb code:
#include <nitro/code16.h>void A(void){ ....}#include <nitro/code32.h>
In CodeWarrior, pragma can directly change the output code. However, our policy is to use these files to absorb, as much as possible, the differences in compilers. We recommend that you use them.
We have made the following additions and revisions to support code creation with C++.
NitroStartUp() function and a
static constructor before calling NitroMain().$Nitro/build/demos/os/cplusplus-1).If the NitroStartUp()
function has been prepared on the application side, the SDK
will call the NitroStartUp()
function before the static constructor process. If you initialize the memory
management mechanism in NitroStartUp(), it will be possible to
use the new() function in the static constructor process.
We now support X, Y
button read in the PAD_Read()
function.
Notice that due to
hardware specifications, interrupts generated by X, Y button input
(see PAD_SetIrq()) are not supported.
We revised make-related
files (commondefs, modulerules, etc., in
$NitroSDK/build/buildtools).
This implemented / revised the following.
make -f option. Fixed.We eliminated compound
statements (multiple statements within {}) with macros definitions.
Because it caused problems with ARM/Thumb code output switching, we moved the inline assembler functions (from static inline asm) from the header files to C source.
Changed the name of the
macro variable CODEGEN_PROC to NITRO_PROC. This macro
variable is in Makefile, and is used to switch output
code for ARM9/ARM7.
We remade the executable
files for ARM7 that are linked to the ARM9 executable files by default when you
make binary files. They contain X, Y button read processes. The files are
located under $NitroSDK/build/components/idle/ARM7.
If you link executable
files for ARM7 from a previous SDK and ARM9 executable files created by this
version of the SDK, the PAD_Read() function will not work properly.
Take notice of this if you are explicitly specifying the ARM7 executable files
with Makefile.
We described IRQ stack size in the LCF file. This makes it possible to set it.
We added a mechanism to display the context at the time that an exception is generated (excluding IRQ exceptions, FIQ exceptions, and SWI exceptions). You can also call a user callback routine.
When a NULL callback was specified, it proceeded without setting the callback. In the case that there is no stall due to bus access contention, after transmitting DMA commands, it returns from the function without waiting.
The DEBUG library will issue a warning when a region that includes ITCM or DTCM is specified as either a DMA transfer destination or source.
We made it so that
crt0.c will clear DTCM. This will clear the stack region. We also made it so
that the BG/OBJ palettes, and OAM will be cleared.
32-byte border rounding
for the lower order of start addresses had not been implemented in DC_StoreRange(),
DC_FlushRange(), DC_TouchRange(),
IC_InvalidateRange(). We implemented it.
Concerning the thread mechanism, we added the following:
OS_CreateThread().
You can now pass an argument to the execute startup function.OS_InitThread()
is called will now have a priority of 16. OS_SetThreadPriority(),
OS_GetThreadPriority()) to acquire and change thread priorities.We prepared the
OS_CheckStack() function to check for thread
related stack leaks.
We used 2 16-bit timers to implement a 64-bit clock counter. We also implemented an alarm mechanism that calls callback functions at specified times. Because this multiplexes timer interrupts, it can register more callback functions than the number of hardware timers. These functions are options. You can choose whether or not to use them.
We multiplexed V count interrupts, so that you can register multiple callback functions. For details see the reference manual for OS V-count related functions.
We added
MI_DmaSend*, MI_CpuSend* API.
In the DEBUG version
library, an assert was generated if you set OS_TIMER32_23 as the ID in
OS_StartTimer32(), or if you set OS_TIMER48_123 as the
ID in OS_StartTimer48().
We fixed this.
In the memory interface
we prepared memory manipulation functions such as MI_CpuClear()
that use the CPU instead of DMA. We abolished the UTL library.
The TEG board has a hardware bug. If a certain pattern of data is output to the main processor bus at the beginning of the V-Blank period, polygon display will be corrupted. Countermeasures for this are performed in the library.
The actual code is
embedded in GX_Init(). For details see the region
enclosed by #ifdef SDK_TEG_WA_VBLANK - #endif in
$NitroSDK/build/libraries/gx/src/gx.c.
This code uses V-count alarms. Therefore, if you want to use this process, do not turn off V-count alarms.
In the demos that perform light processing, the total of the parameters such as light color was very large—not an appropriate value. Therefore when polygons even slightly faced light, the light value became MAX. We adjusted this.
We also revised
parameter table definitions related to specular light in DEMOLib
so that they approach cosinen. You can see the change caused
by the difference in parameter tables in the gx/UnitTours/3D_Shininess
demo.
We added a DL buffer
overflow check to the dynamic DL creation function group G3*. This is only
enabled when the DEBUG version library is linked.
Fixed a G3_Ortho()
implementation bug.
G3_EndMakeDL() did not
return the proper size. We fixed this bug.
We added an argument to
G2_SetBG*Control256x16Pltt() that specifies the character base block.
There was a problem in
the display list that was generated by G3CS_LoadTexMtxEnv(),
G3CS_LoadTexMtxTexCoord(). We fixed this.
An API now supports A3I5 textures. Confirm emulator specification to see whether this texture can actually be displayed.
We support the 3D vector
type VecFx16, which uses Fx16 elements. We prepared the VEC_Fx16* series to
handle it.
We added the C linkage
specification extern "C"
to the $NitroSDK/build/demos/gx/UnitTours/DEMOLib header files.
The main purpose of this
DEMO library is to simplify the implementation of UnitTours.
Therefore, there may be times when we will not be able to respond to change
requests concerning this specification. Please take this into consideration
when using this DEMOLib in an application.
Decided to postpone ROM file system function and implementation of overlay.
(2004/02/04)
In the main loop
SVC_WaitVBlankIntr();
G3_SwapBuffers(GX_SORTMODE_AUTO, GX_BUFFERMODE_W);
The above, APIs appear in reversed order and an unnecessary V-blank wait is generated. Exchanging them fixes the problem.
The 3D graphics test code that caused the problem is fixed.
VEC_Mag overflow measures.When a large vector is placed in VEC_Mag, internal calculation
generates overflow, and the result is strange.
This bug has been fixed.
In fx_mtx43.c, the X axis transform element in matrix b is
ignored.
This bug has been fixed.
There were mistakes in G2_SetBG3Priority definitions.
This bug has been fixed.
Although built library files are bundled in the package, if you used libos.a
in the library as-is, OS_Printf did not output to IS-IRIS-EMULATOR.
When the library was rebuilt in an environment in which IS-IRIS-EMULATOR
had been completely installed, the problem disappeared.
We bundled the corrected library files in a patch.
libstubsisd.aWhen linking the ARM7 side processors, if the environment variable "IS_IRIS_DIR"
is not included, it attempts to link libstubsisd.a. However,
because this file did not exist an error occurred.
Added ARM7 version libstubsisd.a and its source file.
The system reserved region size changed (32bytes->64bytes) with the new BOOT ROM. This was not supported.
This bug is now fixed. In accord with this, the size of the system mode stack region has become smaller by 32 bytes.
(Plan to fix in the next release)
G2_SetBG*Control256x16Pltt().OS_TIMER32_23, as the ID in OS_StartTimer32, or if you set
OS_TIMER48_123 as the ID in OS_StartTimer48().NINTENDO Technical Support Center