CTR-SDK Change Log

Documentation regarding the applet::AssignGpuRight and ReleaseGpuRight functions have been removed from the function reference because there is no need to call them from an application.
At present, plans call for leaving behind disclosed header files, but completely hiding these functions in future versions of CTR-SDK.

Note 155-02: (BOSS) Extended the specifications of the `TaskError::GetProperty` function.

TASK_ERROR_CODE was added, in addition to the conventional TASK_COMM_ERROR_CODE, as an identifier for getting error information.
TASK_ERROR_CODE will become the standard identifier, so use it from now on.

Note 155-03: (CAMERA) Revised argument names for the `GetStereoCameraCalibrationMatrix*` functions [SDK]

The third argument of the GetStereoCameraCalibrationMatrix function and fifth argument of the GetStereoCameraCalibrationMatrixEx function were named in a way that might lead to confusion, so they have been changed from translationByPixel to translationUnit.
Along with this change, a description of these arguments has also been added to the function reference.

Note 155-04: (CEC) Added mutex exclusion for functions that access the box

There was a bug where the value set for the maximum number of receivable messages in the message box, and other such parameters, were being unintentionally changed if the OpenMessageBox or CloseMessageBox function was called during execution of the DeleteAllMessages function.
Mutex exclusion was added so that these functions cannot execute simultaneously.

Note, however, that there is still a chance that this problem may also occur when interrupting an application by pressing the HOME Button.
As such, pay careful attention so that no malfunctions arise at this time as the system may receive more data than it is set to handle.

Note 155-05: (CFG) Now display a warning if an API function is called without having called `Initialize`

Specifications have been made so a warning message is output to the debug log if an API function is called without having first called Initialize.

Note 155-06: (CX) Added a function for expanding files compressed with LZ format backward compression.

The UncompressBLZ and SecureUncompressBLZ functions have been added for expanding files compressed with LZ backward compression.

Note 155-07: (DLP) Added a function to the server for getting client download progress [SDK | SampleDemos]

The nn::dlp::ServerGetClientState function was added to get client download progress.

Note 155-08: (DSP) Hid the API unnecessary for application development from view [SDK]

The following API functions in the nn::dsp namespace have been hidden from public view.

RegisterInterruptEvents
RecvData
SendData
RecvDataIsReady
SendDataIsEmpty
ReadPipeIfPossible
WriteProcessPipe
CheckSemaphoreRequest
ClearSemaphore
MaskSemaphore
GetSemaphore
SetSemaphore
Sleep
WakeUp
GetHeadphoneStatus
(The nn::snd class includes an API function of the same name. Use that.)

Note 155-09: (DevEnv) Deleted `NN_USE_MAKECCI` [SDK]

An unnecessary macro definition (-DNN_USE_MAKECCI) was specified as a compiler option in the CTR-SDK build system.

Note 155-10: (DevEnv) Added battery status icons [SDK]

Battery status icons and associated documentation have been placed in the $CTR_SDK/resources/icon/BatteryLevelIcon directory.

Note 155-11: (DevEnv) Added communication icons [SDK]

Communication icons and associated documentation have been placed in the $CTR_SDK/resources/icon/CommunicationIcon directory.

Note 155-12: (DevEnv) Added a document explaining the differences between development systems and production hardware

The documentation related to the differences between development systems and production hardware has been placed in the following directory.
$CTR_SDK/documents/TechnicalNotes/AboutHardwareDifference/AboutHardwareDifference.pdf

Note 155-13: (FND) Added `UnitHeap::GetAlignment` [SDK]

An interface has been added for getting the alignment unit that can be allocated from the unit heap.

Note 155-14: (FONT) Added a document on internal bitmap fonts [SDK]

The following documentation about internal bitmap fonts has been added.
$CTR_SDK/documents/resources/BuiltInFont/BuiltInFont.html

Note 155-15: (FS) Fixed a bug where `4MbitVerificationFailed.bin` was not returning the expected result [SDK]

4MbitVerificationFailed.bin is a binary used to issue fs::ResultVerificationFailed when mounting save data. It has been revised and replaced because it has been returning fs::ResultBadFormat since CTR-SDK 2.1.

Note 155-16: (FS) Added characters that must not be used in archive names [SDK]

The fact that "$" must not be used at the start of an archive name was added to the function reference.

Note 155-17: (GR) Revised to check the maximum number of four-dimensional vectors that can be set using `MakeUniformCommandVS` and MakeUniformCommand.

Specifications have changed so that an assert is generated if an attempt is made to set a number of four-dimensional vectors inside MakeUniformCommandVS or MakeUniformCommandVS (used to set four-dimensional vector arrays as uniform) that exceeds the maximum number (24) allowed.

Note 155-18: (GR) Fixed a bug with commands related to `zBias` when using the `RenderState::ShadowMap::MakeTextureCommand` function [SDK]

A bug was fixed related to issuing commands to 0x8b [23:1], equivalent to the dmp_Texture[0].shadowZBias uniform, when using the RenderState::ShadowMap::MakeTextureCommand function.

Note 155-19: (GR) Delete `RenderState::ShadowMap::zScale` [SDK]

Settings of the reserved uniform shadowZScale were discovered to be disabled in hardware. Code was changed so that commands are not issued using this variable.

Note 155-20: (GR) Revised commands issued when kicking off rendering with `Vertex::MakeDrawCommand` [SDK]

Among commands generated when kicking off rendering with Vertex::MakeDrawCommand, there were locations in code where the byte enable [31:8] was not set to zero when writing to register 0x245.

Note 155-21: (GR) Deleted `gr::Shadow` [SDK]

gr::Shadow was deleted. Its planned removal has been mentioned before in the function reference.
Use the RenderState::ShadowMap class from now on for generating render state-related commands.

Note 155-22: (GX) Added a function reference for the `SetInternalDriverPrioMode` function [SDK]

A function reference was added for nn::gx::CTR::SetInternalDriverPrioMode (and the corresponding C function nngxSetInternalDriverPrioMode).

Note 155-23: (GX) Fixed a bug with the `gd::ShaderStage::SetFloatConstantBuffer` function regarding registers specified as "Unmanaged" [SDK]

Incorrect operations would result even if the ShaderStage::CreateShaderPipeline function was called by the ShaderStage::SetFloatConstantBuffer function on a register specified as "Unmanaged" when using the geometry shader.
This bug has been fixed.

Note 155-24: (GX) Changed the gd texture cache flush timing [SDK]

The texture cache was being flushed every time a texture was set in the texture unit. Specifications have changed so that the texture cache is now flushed only when necessary for each rendering pass.
In addition, a cache flush operation on the texture unit has been added. It is used by both the CopyTextureSubResource and CopyTexture2DResourceLinearToBlock functions.

Note 155-25: (GX) Fixed a bug where data was not being set correctly in constant_uniform registers of the gd library beginning from c64 and up. [SDK]

A bug has been fixed where c64 through C95 in the floating point constant register c# are not reflecting changes made by commands issuing changes.

Note 155-26: (GX) Changed the name of various API functions in the gd library [SDK]

The name of gd library API functions have been changed according to the convention below.
Note, however, that conventional names have been left behind for compatibility purposes.
Plans call for the removal of old names in a future CTR-SDK update.
Please use the new names from now on.
Conventional -> Revised

Classes

VertexShader -> Shader

enum

OutputStage::StencilFailOperation → OutputStage::StencilOperation
RasterizerStage::CullingType → RasterizerStage::Culling
Resource::NativeResourceFormat → Resource::NativeFormat
Resource::ResourceFormat → Resource::Format
Resource::CompressedResourceFormat → Resource::CompressedFormat
ProceduralTextureStage::ProceduralTextureRgbMap → ProceduralTextureStage::UvMap
ProceduralTextureStage::ProceduralTextureClamp → ProceduralTextureStage::Clamp
ProceduralTextureStage::ProceduralTextureShift → ProceduralTextureStage::Shift
ProceduralTextureStage::ProceduralTextureMinFilter → ProceduralTextureStage::MinFilter

Functions

ShaderStage::SetShaderPipelineConstantF → ShaderStage::SetShaderPipelineConstantFloat
ShaderStage::SetShaderPipelineConstantB → ShaderStage::SetShaderPipelineConstantBoolean
ShaderStage::SetShaderPipelineConstantI → ShaderStage::SetShaderPipelineConstantInteger

Note 155-27: (GX) Fixed a bug with the `gd::Finalize` function [SDK]

There was a problem with finalization when using the gd:Finalize function.
Initialization was not being performed correctly even if the gd::Initialize function was called after calling the gd::Finalize function. This bug was fixed.

Note 155-28: (GX) Support for operations on numbers of vertex elements even less than given by settings of the `gd::InputLayout` shader [SDK]

Behavior has been changed so that operations will proceed even if InputLayout is defined as having fewer vertex elements (numElements) than the number of shader bind_symbols.

Note 155-29: (GX) Added an error check when creating `gd::InputLayout` [SDK]

A process used while creating InputLayout was added for checking that the slot numbers (m_StreamSlot) in InputElementDescription have been defined in order beginning from 0.
If they are not defined in order, the error ResultInputLayoutInvalidStreamSlots is returned.

Note 155-30: (GX) Fixed a bug with the `UnmapVertexBufferResource`, `UnmapTexture2DResource` function in the `gd::Resource` class [SDK]

Sometimes modified data was not being correctly applied due to a bug with the Resource::UnmapVertexBufferResource and UnmapTexture2DResource functions.
This bug has been fixed.

Note 155-31: (GX) Added an argument for specifying whether to copy initialized data to `gd::Resource::Create*` functions [SDK]

The argument copyInitialData has been added to the Resource::CreateTexture2DResource, Resource::CreateVertexBufferResource functions.
The default is true.
Now, if false is set, data is directly accessed without copying even if main memory (FCRAM) is specified.

Note 155-32: (GX) Added the `gd::Resource::Helper::GenerateMipMapsCPU` function [SDK]

The Resource::Helper::GenerateMipMapsCPU function was added to support the automatic generation of mipmap data by the CPU.

Note 155-33: (GX) Added support for `gd::TextureStage projection` textures [SDK]

The TextureStage::SetTexture2DProjectionForUnit0 function has been newly added to support projection textures.

Note 155-34: (GX) Revised the default value of `ptMinFilter` when using the `gd::TextureStage::SetDefault` function [SDK]

Contrary to specifications, MIN_FILTER_NEAREST was being used as the default value for the ptMinFilter argument of the gd::TextureStage::SetDefault function. The default value has been changed to MIN_FILTER_LINEAR to match stated specifications.

Note 155-35: (GX) Removed the `GetRegisterCount` and `GetManagedLocation` functions in the `gd::UniformLocation` class [SDK]

The GetRegisterCount and GetManagedLocation functions of the gd::UniformLocation class have been removed because they are not needed for development.

Note 155-36: (GX) Updated the shader tool [SDK]

The following changes were made to the shader tool.

Revised conditions that result in an assembler error when it comes to undefined operations due to executing commands in a particular order.
(Made changes so that a dependency relationship is determined if the register is the same for condition 5, 6, and 7, even if a component is not overlapped.)
Changed conditions on generating a stall by the performance check feature.
Made changes so that a stall due to dependency relationship between registers is determined even if a component is not overlapped.)

Note 155-37: (GX) Updated the documentation [SDK]

The following changes were made to the GX documentation.

DMPGL20_specification.pdf

Added the fact that the output value of each texture combiner stage is clamped in the range [0,1].
Revised an erroneous description of the byte order of compressed textures that include an alpha.
Added a supplement regarding the addressing of compressed textures.
Deleted dmp_Texture[0].shadowZScale from specifications (because it was clearly invalid due to hardware specifications).

DMPGL20_programming_guide.pdf

Added the description for "Configuring Textures" under the section "Performance-Enhancement Techniques."
Deleted dmp_Texture[0].shadowZScale from specifications (because it was clearly invalid due to hardware specifications).
Added supplementary information to "Implementing Vertex Shaders" in the section "Performance-Enhancement Techniques."
Added a description of a phenomenon to "Lines Are Unxpectedly Rendered Onscreen."

DMPGL20_system_API_specification.pdf

Deleted parallel execution mode and synchronous execution mode from specifications.
Added supplementary information regarding nngxFilterBlockImage transfer addresses.
Deleted dmp_Texture[0].shadowZScale from specifications (because it was clearly invalid due to hardware specifications).
Added a specification that specifying 0 in register 0x228 is an illegal operation.
Revised descriptions given in 5.8.20.13 Shadow Texture Settings and 5.8.20.14 Gas Texture Settings.
Added supplementary information about the post-vertex cache to 3.4 NN_GX_CMDLIST_HW_STATE.
Revised the description given in 5.8.14.1 Base Address.
Added supplementary information to "Registering Interrupt Handlers for Command Completion."
Added a section titled "Execution Cost of PICA Register Write Commands."

VertexShaderReferenceManual.pdf

Added a description of rcp, rsq, exp, and log instructions to "Results of Exceptional Operations."
Added additional information to their references as well.
Added a description of how to distinquish ∞, -∞, and NaN when using the cmp command.
Revised the description given in "Output Order of Calculation Results."
Changed the conditions for stalling given in "Stalls Due to Instruction Dependencies."
Revised invalid operations conditions in the "Invalid Operation Due to a Specific Order of Instruction."
Added supplemental information to "Stalls Due to Conflicts Among Arithmetic Units."
Added an item titled "Unconditional Stalls."
Revised the sample code titled "Packing Multiple Attributes into a Single Output Register" using output_map(data_name, mapped_register).

Note 155-38: (HIO) Added `HostFile::Exists` [SDK]

Added HostFile::Exists to function the same as HostFile::IsExist.
Do not use HostFile::IsExist as it will be deleted in a future release.

Note 155-39: (HIO) Fixed a bug with the `SerialChannel::GetWritableSize` function [SDK]

A bug was fixed where the value returned by hio::SerialChannel::GetWritableSize was smaller than the original value.

Note 155-40: (HIO) Deleted documentation related to the host interface [SDK]

Because the documentation supplied with PARTNER-CTR HIO Daemon is the latest available regarding the HostIO host interface, information on that topic was removed from CTR-SDK documentation.

Note 155-41: (HTTP) Deleted the `SetSocketBufferSize` function [SDK]

The nn::http::Connection::SetSocketBufferSize function was deleted.

Note 155-42: (INIT) Adopted the default implementation of `calloc/realloc` [SDK]

If nninitStartUp is not replaced, malloc and free could be used by default, but not calloc and realloc.
Specifications were changed so that calloc and realloc can also be used by default.
These functions may be replaced with original implementations just as malloc/free.

Note 155-43: (NSTD) Added the `ntsd` library [SDK]

The nstd library was added as a separate implementation of the standard library.
This library includes MemCpy and MemMove for optimized copying of memory according to the given alignment. It also includes TSPrintf, TSNPrintf, and TVSNPrintf for forming strings using a small stack.

Note 155-44: (OS) Added the `Alarm::TryInitialize` function [SDK]

The TryInitialize function was added to the Alarm class. The function receives whether initialization succeeded or failed as a return value.

Note 155-45: (OS) Added the `StackMemory::TryInitialize` function [SDK]

The TryInitialize function was added to the StackMemory class. The function receives whether initialization succeeded or failed as a return value.

Note 155-46: (OS) Updated the System Programming Guide [SDK]

The System Programming Guide ($CTR_SDK/documents/TechnicalNotes/SystemProgramingGuide/SystemProgramingGuide.pdf) included deprecated content that was deleted.

Note 155-47: (OS) Improved error handling inside the library [SDK]

Code was revised to fix a problem with the error handling inside some functions in the OS library.
No changes were made to the behavior of these functions during normal use.

Note 155-48: (OS) Changed behavior when an internal error occurs [SDK]

Up until this release the display would switch to a fatal error screen if an internal error occurred in the OS library. Since this would cause the display of a fatal error screen due to the simplest programming mistake, specifications have been changed for the development environment so that program execution merely stops rather than displaying a fatal error screen.

Note 155-49: (SND) Changed specifications for `DecodeAdpcmData` [SDK]

const was added to the pInput and param arguments.
Code was also revised so that context information when decode ends is stored in the context argument.

Note 155-50: (SND) Fixed a bug causing noise during HOME Button transition [SDK]

There has been a bug since CTR-SDK 2.0 where a small amount of audio noise is introduced when changing screens using the HOME Button, when going to sleep, and when recovering from sleep. This bug has been fixed.
This was actually fixed in CTR-SDK 2.3.4 but was accidentally omitted from the change log.

Note 155-51: (SND) Added the `Voice::DeleteWaveBuffer` function [SDK]

The Voice::DeleteWavebuffer function has been added for deleting buffer information added using the Voice::AppendWaveBuffer function.

Note 155-52: (SND) Added the `Voice::UpdateWaveBuffer` function [SDK]

The Voice::UpdateWavebuffer function has been added for updating the sampleLength and loopFlag parameters included in buffer information added using the Voice::AppendWaveBuffer function.

Note 155-53: (DSP) Hid several Voice API functions from view [SDK]

The following functions have been hidden from view:
Use them for referencing arguments from now on.

void SetMonoFilterCoefficients(const MonoFilterCoefficients* pCoeff)
void SetBiquadFilterCoefficients(const BiquadFilterCoefficients* pCoeff)
void GetMonoFilterCoefficients(MonoFilterCoefficients* pCoeff)
void GetBiquadFilterCoefficients(BiquadFilterCoefficients* pCoeff)

Note 155-54: (SND) Found a workaround for a problem where `AllocVoice` data abort would occur if an invalid call to `FreeVoice` was made [SDK]

Specifications were changed to fix a problem where there was a chance of data abort inside the AllocVoice funtion if an invalid voice, such as a dual FreeVoice, was processed.

Note 155-55: (TOOL) Changed where CTR tool references are placed [SDK]

The CTR tool references located in $CTR_SDK/tools/TargetTools had been included with function references until now, but have been moved to index.html.
With this move, the items "CTR Tools" and "Windows Tools" have been added to index.html.

Note 155-56: (TOOL) Revised specifications so that save data is maintained during overwrite import on the DevMenu [SDK]

Up until this release, save data would be deleted if a CIA File was overwrite imported on the DevMenu. Save data is no longer deleted.
To delete save data, first delete the program using the X Button.
Further revision has been made so that imports are cancelled if there has been no change to the program when an overwrite import is performed.

Note 155-57: (TOOL) Revised specifications so that a write-protected SD Card cannot be used on the DevMenu [SDK]

Specifications have changed so that file operations are unavailable if a write-protected SD Card is inserted in using DevMenu.
To use an SD Card, switch to a writable one.

Note 155-58: (TOOL) Added a feature for exporting BOSS data using SaveDataFiler [SDK]

Specifications have changed so that BOSS memory is also exported when exporting expanded save data using SaveDataFiler.

Note 155-59: (TOOL) Fixed a bug where icons would be corrupted when importing expanded save data using SaveDataFiler [SDK]

A bug was fixed where icons used for expanded save data were being corrupted when expanded save data was imported using SaveDataFiler.

Note 155-60: (TOOL) Revised the file destruction feature of `SaveDataFiler` [SDK]

A bug was fixed where an error dialog box was being displayed even though file destruction succeeded when destroying files using SaveDataFiler.
The message displayed when file destruction fails was also made easier to understand.
For details, see the function reference.

Note 155-61: (TOOL) Changed the behavior when `UniqueId` is not set [SDK]

In past releases, if UniqueId in the RSF was unspecified, processing would continue as if 0xf7fff had been specified for UniqueId. This has been changed so that an error now results.
Furthermore, 0xff3ff is specified at the end fo sample code as UniqueId in Application.rsf, which serves as the default RSF.

Note 155-62: (TOOL) Fixed a bug related to option specifications when using `ctr_WaveConverter` [SDK]

A bug has been fixed with ctr_WaveConverter32.exe where it would execute even if an option not listed in the help was specified.

Note 155-63: (TOOL) Added support for LZ formatted backward compression when using `ctr_compress` [SDK].

The following options were added to ctr_compress: -lb for compressing in LZ back compressed format and -xlb for decompressing such compressed data.

Note 155-64: (TOOL) Revised `makebanner` [SDK]

Made the following modifications to makebanner.

Changed specifications so that a warning message is issued if the rating information PEGI_GEN is set, but PEGI_BBFC is not set.
Changed specifications in the American and European regions so that the English title name is automatically used for languages whose title name is blank.
Changed specifications so that the width of titles is checked.
An error message is displayed if a title exceeds a specified string width.
Although the file that makebanner outputs to used to be calculated in terms of a relative path from the directory in which th bsf file was located, specifications have changed so that output is made in terms of a relative path from the current directory.

Note 155-65: (TOOL) Removed a warning when `UniqueId` is used in trial code [SDK]

A warning used to be issued when code for testing was specified in UniqueId when using ctr_makerom. This has been eliminated.

Note 155-66: (UBL) Revised the Function Reference Manual [SDK]

A description of the CTR system ID was added to the function reference for GetUserId. Information about the maximum number of people that can be registered on the blocked-user list was added to the function reference for Entry.

Note 155-67: (UDS) Revised behavior so that SubId 0xFF is prohibited when using the `CreateNetwork` function [SDK]

Specifications were changed so that the error nn::uds::REsultOutOfRange is returned if SubId 0xFF is specified with the CreateNetwork function.
This is due to the fact that SubId 0xFF is used when the Scan function queries all modes.

Note 155-68: (UDS) Made deletions from the function reference for the `SetPowerSaveMode` function [SDK]

The SetPowerSaveMode function was deleted from the function reference because although it was listed in the function reference, it could not be used.
There is no plan for continued support of the SetPowerSaveMode function.

Note 155-69: (ULCD) Made public the `GetCoefficientForParallax` function [SDK]

The GetCoefficientForParallax function was disclosed to the public.
This function can be used to speed up calculation of the parallax required when making stereoscopic display of an orthogonal projection.
For details, see AboutULCDLibrary.pdf.

Note 155-70: (Y2R) Added mention that the `IsBusyConversion` function no longer returns `true` when Y2R conversion hangs up [SDK]

Although past documentation mentioned that events obtained by the GetTransferEven function were no longer signaled if conversion stopped due to problems with Y2R transfer, it did not include the fact that the IsBusyConverion function no longer returns true. This has been added.

Note 155-71: (Miscellaneous) Removed `ResultSuccess` from the function reference [SDK]

Specifications have been changed so that Result::IsSuccess is used instead of ResultSuccess given in the function reference.

Note 155-72: (Error EULA) Added a feature for specifying the display language [SDK | SystemUpdater]

A function has been added for specifying the language to use for messages displayed in an applet.
Specify the type of *_LANGUAGE using errorType of the Config parameter. By specifying the language you want displayed using useLanguage, messages inside applets will be displayed in the specified language regardless of the language set under System Settings.

Known Issues with SDK 2.4.0 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.

CTR-SDK Version 2.4.0 SystemUpdater 0.15.20

(2011/06/28)

Note 154-01: (AC) Fixed a bug where `nn::ac::Connect` would be unintentionally canceled [SystemUpdater]

A bug was fixed where nn::ac::Connect would be unintentionally canceled in an environment where some APs cannot be used, such as when the system cannot access the Internet during connection processing.
This was actually fixed in CTR-SDK 2.3 but was accidentally omitted from the change log.

Note 154-02: (DevEnv) Updated the development menu (TestMenu) [System Updater]

The following changes were made to the developer menu (TestMenu).

Changed specifications so a message is displayed when an error occurs.
Added support for hotswapping of SD cards.
Added upper screen display items.

Debug Mode enabled/disabled
EULA agreement version and EULA version are required for CTR-SDK
Battery level (however, the only thing that has changed is during TestMenu re-rendering)
SD Card information
User name

Note 154-03: (HOME Menu) Added a feature for deleting the icon database and icon cache [SystemUpdater]

Limited to the HOME Menu of developers only, a debugging function for deleting the icon database and icon cache has been added when starting the HOME Menu while holding down X and Y.

The icon database is a database located in system NAND memory that saves the icon of the application started. The icon stored here is displayed in the Activity Log.
Note, however, that once an icon is stored, the icon in the database will not be updated unless the unique ID and version of the application change, even if the application is started with a subsequent change made to the icon.
The icon cache stored the icon data of applications saved on an SD Card for increasing the speed of loading of icon data on the HOME Menu.

Because the icon cache is not overwritten even if a change is made to the icon just as with the icon database, specifications were changed so that the icon can be deleted in order to verify any changes.

Note 154-04: (HOME Menu) Fixed a bug where BOSS would sometimes run while an application was running [SystemUpdater]

A bug was fixed where, even though the application had turned BOSS operations off, BOSS would begin to operate whenever a system applet would start or stop such as when interrupting an application to view the friend list.

Note 154-05: (HOME Menu) Added a feature so that unsupported banner models are not displayed [SystemUpdater]

Specifications were changed so that banner models not output by NW4C_ForBanner in the NW4C environment especially for creating banners are not displayed on the HOME Menu for developers.
However, there is no bug where banner models are not being displayed; therefore, if this symptom occurs, review the banner model in question.

Note 154-06: (OS) Added support for loading cia files whose save data has not been initialized by debugger [SystemUpdater]

Specifications have changed so that cia files can be loaded and/or imported without having the debugger initialize save data.
PARTNER-CTR Debugger 2011/05/11 release or later is required to use this feature.

Note 154-07: (TOOL) Fixed a bug where the menu would stop running after applying SystemUpdater [SystemUpdater]

If the system mode is set to anything other than Prod on development hardware to which SystemUpdater 0.14.23 has been applied, a bug will occur if SystemUpdater 0.15.8 or later is executed using "Keep current setting" where subsequent menus will not start. This bug has been fixed.

Note 154-08: (TOOL) Revised shared expanded save data created when starting TestMenu [SystemUpdater]

A bug has been fixed where the specifications of shared expanded save data created when starting TestMenu differed from those of shared expanded save data created when starting the HOME Menu.
This bug fix has basically no effect on application development.

Note 154-09: (Error EULA) Added support for button input during the error display [SystemUpdater]

During the display of error messages, specifications have changed so that all sequences can be advanced with only A and B Button input.
However, button input remains the same (will not work) as always during the EULA display.
This was actually changed in CTR-SDK 2.2 (SystemUpdater 0.15.3) but was accidentally omitted from the changelog.

Note 154-10: (Error EULA) Added a feature for specifying the display language [SDK | SystemUpdater]

Note 154-11: (Software Keyboard) Added a non-Japanese keyboard to supported keyboard types [SystemUpdater]

A keyboard completely incapable of Japanese input (including Japanese kana letter input and predictive text) has been added to the keyboard types.

Known Issues with SDK 2.4.0 System Updater 0.15.20

See the Symptoms Treated as Specifications file in the CTR-SDK for details on known issues with System Updater.

CTR-SDK Version 2.4.0 Sample Demos

(2011/06/28)

Note 153-01: (CAMERA) Revised Stereo demo comments [Sample Demos]

Comments in the stereo camera demo were revised because they might lead to misunderstanding.

Note 153-02: (CX) Added the UncompressBlz sample demo [Sample Demos]

A sample demo was added to demonstrate the UncompressBLZ and SecureUncompressBLS functions.

Note 153-03: (DLP) Added a function to the server for getting client download progress [SDK | SampleDemos]

The nn::dlp::ServerGetClientState function was added to get client download progress.
With this change, specifications have changed so this function is used with the SimplerServer demo.

Note 153-04: (GX) Improved the speed at which ProcTexEditor images are written [Sample Demos]

This was changed because the source code for writing images has become old.
Some text during writing was also deleted.

Note 153-05: (GX) Added `gd` sample demos [Sample Demos]

The following demos have been added as gd library sample demos.

CombinationSample
FogAndLight
FogSample
LightingAniso
LightingSample2
MipMapSample
PartsysGas
PartsysSimple
ProctexClamp
ProctexFFunction
ProctexRandom
ProjectionTexture
ShadowKnotCube
ShadowSimple
SilhouetteSimple
SubdivisionLoopSimple
SubdivisionSimple
TextureCombinerSample

Note 153-06: (GX) Deleted the uniform `shadowZScale` [Sample Demos]

The reserved uniform shadowZScale has been deleted from source code because it was found to be invalid due to hardware specifications.
There is no problem with setting it as usual.

Note 153-07: (SND) Added the WaveBufferOperator sample demo [Sample Demos]

The sample demo titled WaveBufferOperator has been added. This demo shows how to use the Voice::DeleteWaveBuffer and Voice::UpdateWaveBuffer functions.

Known Issues with SDK 2.4.0 SampleDemos

　 None.

■ CTR-SDK Version 2.3.4 System Updater 0.15.19

(2011/06/09)

Note 152-01: (MCU) Fixed a bug that prevented the recharge LED from turning off [System Updater]

Fixed a bug that prevented a system's recharge LED from turning off until the system was turned on, even after it was fully charged, if you had started to charge the system while it was turned off with less than 60% battery life remaining.

Known Issues with SDK 2.3.4 System Updater 0.15.19

In some extremely rare cases the screen will stay black after the system is closed and opened. Audio output, button input, and other features still function normally when this happens; the only feature that has not recovered is rendering. Close and open the system once more to resolve the symptoms.
This same issue, however, can also be caused by applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have any possible sequence or timing in which rendering might not recover after awakening from sleep.

■ CTR-SDK Version 2.3.4 System Updater 0.15.18

(2011/06/08)

Note 151-01: (FS) Reverted ROM access speeds for card-based software [System Updater]

Reverted the adjustments made by Note 149-04 to ROM access speeds for card-based software.

Known Issues with SDK 2.3.4 System Updater 0.15.18

In some extremely rare cases the screen will stay black after the system is closed and opened. Audio output, button input, and other features still function normally when this happens; the only feature that has not recovered is rendering. Close and open the system once more to resolve the symptoms.
This same issue, however, can also be caused by applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have any possible sequence or timing in which rendering might not recover after awakening from sleep.

■ CTR-SDK Version 2.3.4 System Updater 0.15.17

(2011/06/01)

Note 150-01: (HTTP) Disabled SetSocketBufferSize [System Updater]

Disabled the http::Connection::SetSocketBufferSize function, which had few uses.
Now the buffer size remains unchanged even after this function is called, and it always returns nn::ResultSuccess.

Known Issues with SDK 2.3.4 System Updater 0.15.17

In some extremely rare cases the screen will stay black after the system is closed and opened. Audio output, button input, and other features still function normally when this happens; the only feature that has not recovered is rendering. Close and open the system once more to resolve the symptoms.
This same issue, however, can also be caused by applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have any possible sequence or timing in which rendering might not recover after awakening from sleep.

■ CTR-SDK Version 2.3.4 System Updater 0.15.16

(2011/05/27)

Note 149-01: (AC) Fixed a bug where connection would not complete with certain APs when sending the wrong WEP key [System Updater]

Fixed a bug where attempting to connect to certain access points using WEP encryption and sending the wrong key would cause an internal infinite loop, with the connection never being completed.
Even if this bug occurred, you could break out of the loop by moving outside of the AP's range or pushing the wireless switch off to disable wireless communication.

Note 149-02: (FS) Improved ROM access response when ROM access and access to save data or other data occur at the same time [System Updater]

Improved ROM access response when accessing save data, expanded save data, or other data during ROM access.

Note 149-03: (FS) Sped up formatting of save data for card-based applications [System Updater]

Shortened the time required when calling the nn::fs::MountSaveData function from a card-based application.

Note 149-04: (FS) Improved ROM access speed for card-based software [System Updater]

Adjusted the ROM access speeds of card-based applications to mostly eliminate the differences when accessing production cards versus development cards and emulation memory.

Note 149-05: (HTTP) Fixed a bug where keep-alive would not work properly via a proxy [System Updater]

Fixed a bug where using a keep-alive via a proxy would result in attempting to access a server at a different URL.
(This fix is provisional, and simply disables the use of keep-alives via a proxy.
A different fix will be released at a later date to allow the proper use of keep-alives via a proxy.)

Note 149-06: (OS) Fixed a bug where resources would not be released on application shutdown [System Updater]

Fixed a very rare bug where system resources would not be properly released after an application shutdown.

Note 149-07: (SSL) Fixed a bug where communication would fail when communicating using many certificates in parallel [System Updater]

Fixed a bug where using many certificates in parallel for communication (which can easily happen when using keep-alives with HTTPS) would cause the SSL heap to run out and communication to fail.

Known Issues with SDK 2.3.4 System Updater 0.15.16

In some extremely rare cases the screen will stay black after the system is closed and opened. Audio output, button input, and other features still function normally when this happens; the only feature that has not recovered is rendering. Close and open the system once more to resolve the symptoms.
This same issue, however, can also be caused by applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have any possible sequence or timing in which rendering might not recover after awakening from sleep.

CTR-SDK Version 2.3.4 System Updater 0.15.9

(2011/05/24)

Note 148-01: (BOSS) Fixed a bug that prevented BOSS functions from returning [System Updater]

Fixed a bug that that prevented BOSS functions called by the application from returning after the application had repeatedly called boss::Initialize and boss::Finalize.

Note 148-02: (SOCKET) Fixed a DNS bug [System Updater]

Fixed a bug that prevented GetHostByName and GetAddrInfo from properly processing host names that started with a number.

Known Issues with SDK 2.3.4 System Updater 0.15.9

In some extremely rare cases the screen will stay black after the system is closed and opened. Audio output, button input, and other features still function normally when this happens; the only feature that has not recovered is rendering. Close and open the system once more to resolve the symptoms.
This same issue, however, can also be caused by applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have any possible sequence or timing in which rendering might not recover after awakening from sleep.

CTR-SDK Version 2.3.4 Release

(2011/05/18)

Note 147-01: (APPLET) Relaxed conditions on calling `PrepareToCloseApplication` [SDK]

Revised PrepareToCloseApplication so that it will run properly even if Sleep Mode is not prohibited when it is called.

Note 147-02: (SND) Stereo sound was played when Mono was selected in System Settings. This bug was fixed. [SDK]

Fixed a bug in the CTR-SDK that, since version 2.1, caused stereo sound to be output even when Mono was selected for Sound in System Settings.

Known Issues with the SDK 2.3.4 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.
FontConverter is sometimes not able to convert Windows fonts correctly if the following settings have been made.

Vector fonts (marked with "(V)" in the font list) are used
A large font size is set (it is possible that what size is problematic is dependent on the font)
Two levels of gradation are set for the number of gradations under the advanced settings (this applies to both the A4 and LA4 settings)

CTR-SDK Version 2.3.4 System Updater 0.15.8

(2011/05/18)

Note 146-01: (AC) Fixed a bug that returned unknown error codes [System Updater]

Fixed a bug in CTR-SDK 2.x that caused unknown error codes to be returned when a system was forcibly disconnected from an access point during a connection test.

Note 146-02: (AC) Reduced the time required to process a failed connection [System Updater]

Fixed a bug that caused unnecessary active scans when connecting to a USB access point.
This fix causes connections to fail more quickly wherever there are a lot of stealth SSIDs.

Note 146-03: (APPLET) Fixed a bug that prevented the `Awake` callback from being invoked when the system entered Sleep Mode immediately after a library applet was launched [System Updater]

Fixed a bug that prevented the Awake callback from being invoked upon recovery from Sleep Mode if the system entered Sleep Mode immediately after a library applet was launched.

Note 146-04: (FRIENDS) Fixed a bug that prevented the system from returning from Sleep Mode if it had not yet obtained any friend codes or set a Personal Mii [System Updater]

Since version 2.2 of the CTR-SDK, the system would often fail to recover from Sleep Mode when opened, if the system entered Sleep Mode near an access point it could connect to, without having obtained a friend code and while setting a Personal Mii in Mii Maker. This bug was fixed.

Note 146-05: (TOOL) Made `SystemMode dev1` usable, with some restrictions, on test units [System Updater]

Made SystemMode dev1 usable, with some restrictions, on test units.
These restrictions are as follows.

This mode cannot be switched to from the Config tool. You must select it when you apply the System Updater.
If you select SystemMode dev1 using the System Updater, the HOME Menu is not imported and will thus not launch even if you change Menu to home menu with the Config tool. To launch the HOME Menu, you must re-apply the System Updater.

Note 146-06: (UDS) Firmware compatibility with CTR-SDK 2.3.2 and subsequent versions [System Updater]

CTR-SDK 2.3.2 includes changes that affect UDS compatibility.
Note: Starting with the firmware for CTR-SDK 2.3.2 (System Updater 0.15.7), applications built with CTR-SDK 2.0 – 2.3.1 will no longer be able to run UDS communication properly when running on systems that use this firmware.

Note 146-07: (UDS) Fixed a bug that caused the `SendTo` function to return non-UDS errors [System Updater]

Fixed a bug in the SendTo function that caused it to return non-UDS errors that were not documented in the Function Reference Manual, depending on when the system was disconnected from the network.

Note 146-08: (UDS) Fixed a bug that resulted in invalid node information if you destroyed or disconnected from a network [System Updater]

Fixed a bug that caused the GetConnectionStatus and GetNodeInformation functions to return invalid node information right before or after the DestroyNetwork or DisconnectNetwork functions were called.

Known Issues with SDK 2.3.4 System Updater 0.15.8

In some extremely rare cases the screen will stay black after the system is closed and opened. When this happens, audio output, button input, and other features function normally. Only the rendering functionality fails to recover from Sleep Mode. These symptoms are resolved by closing and reopening the system.
Similar symptoms, however, can also be caused by application implementations. If these symptoms occur, you must make sure that your application's implementation does not have any possible sequences or situations that could cause rendering to fail on a recovery from Sleep Mode.

CTR-SDK Version 2.3.3 Release

(2011/05/11)

Note 145-01: (CRYPTO) Fixed a bug that occurred when a large amount of data was assigned as an HMAC key [SDK]

Fixed a bug where a bad HMAC value would be calculated when more than 64 bytes of data were assigned to the CalculateHmacSha1 or CalculateHmacSha256 function as an HMAC key.
This bug was introduced in CTR-SDK 2.1, and was not present in earlier versions.

Note 145-02: (GX) Fixed a bug in the `gd::ForceDirty` function [SDK]

Fixed a bug where calling the gd::ForceDirty function would not reissue a command for the primitive to be rendered (e.g., TRIANGLE).

Note 145-03: (GX) Fixed a bug where the uniform setting was not correctly reflected in `gd::ShaderStage` [SDK]

Fixed a bug where the shader uniform was not correctly configured when all of the following conditions were met:

The SetShaderPipelineConstantF function is used
The same ShaderPipeline is used consecutively to render two objects
The two objects have both a uniform with the same value and uniforms with different values

Note 145-04: (MIC) Fixed a bug in the `GetForbiddenArea` function [SDK]

Fixed a bug where the GetForbiddenArea function did not return the correct result when gain was 68 or greater.

Note 145-05: (SND) Fixed a bug where specifying a high pitch would hang the system [SDK]

Fixed a bug where the DSP core would enter an infinite loop if an extremely high pitch (e.g., 100 or more) was specified in Voice::SetPitch.
However, this fix does not guarantee that the high pitch will be reproduced as intended, because increasing the pitch also increases the processing load on the DSP (nearly linearly).

Note 145-06: (TOOL) Replaced `1MbitVerificationFailed.bin` [SDK]

Replaced the binary for returning fs::ResultVerificationFailed when mounting a backup device, because the old one did not return the expected result. The new binary correctly returns fs::ResultVerificationFailed.
This was actually fixed in CTR-SDK 2.0 but was accidentally omitted from the change log.

Known Issues with SDK 2.3.3 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.

CTR-SDK Version 2.3.3 System Updater 0.15.7

(2011/05/11)

Note 144-01: (BOSS) Fixed a bug where timeouts of the update task had no effect [System Updater]

Fixed a bug where timeouts of HTTP communication by update tasks had no effect.

Note 144-02: (BOSS) Fixed a bug where it took a long time for BOSS tasks to start executing on a stealth AP [System Updater]

Fixed a bug where it took a long time for a BOSS task to start while sleeping (the task was not executed when it should have been) in an environment using a stealth AP.

Note 144-03: (BOSS) Fixed a bug where BOSS termination was delayed in an environment where friend login was unavailable [System Updater]

Fixed a bug where BOSS termination took a long time in an environment where friend login was unavailable, because the cancellation of friend login by BOSS had no effect.

Note 144-04: (BOSS) Fixed a bug where `G_ALTASK` `STOPPED` could not be specified in a policy list [System Updater]

Fixed a bug where G_ALTASK STOPPED could not be specified in a policy list (it would be deemed to be an invalid policy list).

Note 144-05: (BOSS) Fixed a bug that prevented cancellation of a policy list acquisition [System Updater]

Fixed a bug where if a BOSS process was canceled (e.g., due to a Suspend operation after the system was closed), the cancellation had no effect if BOSS was in the middle of getting a policy list.

Note 144-06: (DLP) Fixed a bug where the client could not find the server [System Updater]

Fixed a bug in CTR-SDK 2.3.2 where the client could not find the server even after scanning.

Note 144-07: (FS) Changed format of save data [System Updater]

Changed the format of save data for CTR card applications created with the CTR-SDK 2.X series.
This format is not compatible with save data created using previous versions, so a reformat is necessary.
There are no changes to usage or performance.
This change will have no impact on the save data for CTR card applications or download applications created with the CTR-SDK 1.X series.

Note 144-08: (HOME Menu) Fixed a bug in the display of application icon banners [System Updater]

Fixed the following bugs in the display of application icon banners:

Application order would change suddenly
When an application was added in DevMenu, it would appear on the edge even if there was empty space
Wrapped applications would open without any user action
The banner in the upper screen was scrambled

Note 144-09: (HOME Menu) Changed save locations of application layout information and icon images [System Updater]

Changed the save location of the application layout information and icon images (icon cache) from the ROOT directory of the SD card to the expanded save data.
Consequently, the notes for checking icon images on the HOME Menu have also changed.
See the Readme of the applet package for details.

Note 144-10: (UDS) Fixed a bug where repeated connections and disconnections by a client caused inconsistency between number of nodes and node ID list [System Updater]

Fixed a bug where repeated connections and disconnections by a client over a short period of time caused a mismatch between the value of the nowEntry member and the number of valid nodes in the nodeIdList member of the ConnectionStatus structure obtained from nn::uds::GetConnectionStatus.

Note 144-11: (UDS) Fixed a bug where an invalid value was returned when the friend's local friend code was decoded [System Updater]

Fixed a bug where an invalid value was returned if an encoded local friend code obtained via UDS communication was decoded, even if the peer was a friend.

Note 144-12: (Notifications) Fixed a bug where Notifications sometimes stopped working when a DS card was inserted [System Updater]

Fixed a bug where opening the Notifications details screen with a DS card inserted sometimes caused Notifications to stop working.

Note 144-13: (Notifications) Fixed a bug with starting and stopping software from Notifications [System Updater]

When Start Application was pressed on the Notifications - Details screen, the behavior of the HOME menu was unstable after the application was exited. This problem has been fixed.

Note 144-14: (Notifications) Fixed a bug with EULA check when starting software from Notifications [System Updater]

If Start Software was selected from the Notifications - Details screen, the application would start up ignoring any EULA even if the application required acceptance of a EULA upon startup. This problem has been fixed.

Note 144-15: (Notifications) Fixed a bug preventing software from being started from a local notification [System Updater]

Fixed a bug where the Start Software button was not displayed on the details screen of a local notification.

Note 144-16: (Software keyboard) Fixed a bug with the cell phone-style keyboard for North American and European regions [System Updater]

On the cell phone-style keyboard for the North American and European regions, the character code for the "@" symbol should have been 0400, but it was FF20. This problem has been fixed.

Note 144-17: (Friend List) Fixed a bug with friend lists [System Updater]

Fixed a bug where the screen would flicker, scrolling would be jerky, or the friend list would terminate under some conditions.

Note 144-18: (System Settings) Fixed problem of blank in Other Settings: Region name [System Updater]

In the US/EU versions of the System Settings, the region name in the user information was saved as empty when the following procedure was carried out. That problem has been fixed.

Parental Controls were configured in the System Settings.
In the System Settings, a country that has no individual region settings was selected in Profile > Region Settings
(For example, Anguilla for the US region, or Iceland for the EU region.)

When this was done, the region name in the language that was set in the system settings was cleared.
Normally, the country name is used for the region name that is set here.
In other words, when nn::cfg::CTR::GetSimpleAddress(pSimpleAddress) was called to obtain region information, pSimpleAddress->regionName[nn::cfg::CTR::GetLanguage()] was an empty string.

Note 144-19: (System Settings) Added CTR software management and DSiWare management screens to the Data Management Screen [System Updater]

In the Data Management screen, the CTR software management screen now supports the deleting of downloadable applications, and the DSiWare management screen now supports the deleting and copying of DSiWare.

Known Issues with SDK 2.3.3 System Updater 0.15.7

In some extremely rare cases the screen will stay black after the system is closed and opened. The symptoms are improved by closing and reopening the system at a point where only rendering cannot be restored properly (i.e., sound output, button input, and other features run normally).
This same issue, however, can also occur with applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have a sequence or time when rendering does not recover after awakening from sleep.

CTR-SDK Version 2.3.3 Sample Demos

(2011/05/11)

Note 143-01: (UDS) Fixed a bug where scanning an unnamed master with `com_demo1` gave it another master name [Sample Demos]

Fixed a bug where scanning an unnamed master with com_demo1 gave it the display name of another master that was scanned at the same time.

Known Issues with SDK 2.3.3 Sample Demos

　 None.

CTR-SDK Version 2.3.2 Release

(2011/04/27)

Note 142-01: Note 142-01:(APPLET) Fixed problem with HOME Button transition from library applet [SDK | System Updater]

Sleep was permitted momentarily while returning from a library applet by a press of the HOME Button.
If, while in this sleep state, the nn::applet::CTR::ProcessHomeButton function was called and at the same time the system was closed, the processing would get hung up on an ASSERT check. That problem was fixed by making the transition to the HOME Menu remain locked.

Note 142-02: (GX) Updated DMPGL 2.0 System API Specifications [SDK]

Made the following changes to DMPGL20_system_API_specification.pdf:

Added a section about the load array settings and performance.
Added a description about load array padding elements.
5.9.18 talked about about conversion from float32 to signed int8 for [0,1]. However, the range of conversion values is [-1,1], not [0,1], so that was corrected.
Added nngxMoveCommandbufferPointer, which had been inadvertently omitted.
Revised the bit-width for SIZE in the command buffer header.
Added a description of the command buffer execution registers.

Note 142-03: (HIO) Fixed a bug with `HostFile::Read` [SDK]

When a byte size of larger than 0x200200 was passed to HostFile::Read memory would be destroyed. That problem was fixed.

Note 142-04: (HIO) Revised the Function Reference Manual [SDK]

Revised the reference to mention that nn::hio::GetEnvironmentVariable will return ResultSuccess even when there is no environment variable.

Note 142-05: (TOOL) Changed the version notation of the `Config` tool [SDK]

The version notation for Config now shows the micro version.

Note 142-06: (TOOL) Revised `SaveDataFiler` [SDK]

When a damaged file was exported, the written size was different from the actual size. That problem was fixed.

Note 142-07: (TOOL) Fixed `makecia` failure to create CIA [SDK]

When the size of the file input to makecia was a multiple of 4MB, it would fail to create the CIA file. That problem was fixed.

Known Issues with SDK 2.3.2 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.

CTR-SDK Version 2.3.2 System Updater 0.15.6

(2011/04/27)

Note 141-01: (AC) Accelerated finalization when resources not released [System Updater]

When an application ended without releasing resources provided to the AC, such as Event, the finalization process took a long time. That process has now been accelerated.

Note 141-02: (APPLET) Fixed problem of deadlocking when sleep permitted and the `CancelLibraryApplet` function was called [System Updater]

A deadlock occurred if sleep was permitted and the CancelLibraryApplet function was called. The problem was fixed.

Note 141-03: Note 142-01:(APPLET) Fixed problem with HOME Button transition from library applet [SDK | System Updater]

Note 141-04: (BOSS) Fixed problem with retry of tasks executing immediately in background [System Updater]

When a task was executing immediately in the background and it entered the Retry state because of a disconnection or for some other reason, that task would not later resume execution from where it left off. That problem was fixed.

Note 141-05: (BOSS) Fixed problem of normal tasks sometimes being executed right after Start, ahead of their execution time [System Updater]

Sometimes, registered and started tasks would execute immediately after Start (i.e., before their execution time). That problem was fixed.

Note 141-06: (BOSS) Fixed problem of invalid X-BOSS-Digest value for play history upload tasks [System Updater]

In tasks to upload the play history, an invalid X-BOSS-Digest value (an empty string) was given to the HTTP request. That problem was fixed.

Note 141-07: (FRIENDS) Fixed problem of being online even though asynchronous login process failed because system went to sleep [System Updater]

If the system went to sleep during the the asynchronous process to log in, the asynchronous process would return failure but the login request would remain, with the result that the system would be online after it woke from sleep. That problem was fixed.

Note 141-08: (FRIENDS) Workaround for possibility of blocking of as long as roughly 1 second when API is called while login process is executing [System Updater]

When the login process is running in the background and a Friends library function is called, blocking can occur for as long as around 1 second. This problem has been dealt with.

Note 141-09: (FS) Fixed problem with verification error range when loading files [System Updater]

When loading a region in which nn::fs::ResultVerificationFailed was generated, the Result returned an error for a region where the error did not occur. That problem was fixed.

Note 141-10: (UDS) Fixed problem of CONNECTION_LOST always being given as reason for client disconnection when DestroyNetwork performed [System Updater]

Normally, when the master performs DestroyNetwork a disconnect-request packet is sent to all clients and they are immediately disconnected from the network.
At this time, GetConnectionStatus gets DISCARDED_FROM_NETWORK as the reason for disconnection (DisconnectReason).
However, sometimes the disconnect-request packet is not received, and when this is the case the client is disconnected around 1 second after DestroyNetwork is performed.
In this case, the reason for disconnection is CONNECTION_LOST.

However, because of a bug, the reason for disconnection was always returned as CONNECTION_LOST because the master actually was not sending a disconnect-request packet.
This problem was fixed in the following ways, depending on which version of the CTR-SDK to which the application is linked:

CTR-SDK 1.x versions
As was the case previously, the master does not send a disconnect-request packet.
CTR-SDK 2.3.2 and later versions
The master sends a disconnect-request packet.

The firmware for CTR-SDK 2.2 and CTR-SDK 2.3 is such that the master sends a disconnect-request packet regardless of the CTR-SDK version to which the application is linked, so there is a possibility of connection compatibility problems.

Known Issues with SDK 2.3.2 System Updater 0.15.6

In some extremely rare cases the screen will stay black after the system is closed and opened. The symptoms are improved by closing and reopening the system at a point where only rendering cannot be restored properly (i.e., sound output, button input, and other features run normally).
This same issue, however, can also occur with applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have a sequence or time when rendering does not recover after awakening from sleep.
If you reset the settings using the Config tool, start an application without going through the startup sequence on the HOME Menu, and then open and close the system, the system will stop and the top and bottom screens will turn black.

CTR-SDK Version 2.3.1 Release

(2011/04/21)

Note 140-01: (TOOL) Revised display of `DevMenu` firmware version [SDK]

The firmware version displayed in DevMenu showed the wrong micro version. That was corrected.

Note 140-02: (TOOL) Modified `SaveDataFiler` [SDK]

Made the following changes to the SaveDataFiler tool.

The menu now updates when an SD Card is inserted or removed.
When file destruction fails, a dialog now displays.
You can now transition to the filer by touching on a data item again.
Revised the guide in the upper screen.

Known Issues with SDK 2.3.1 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.

CTR-SDK Version 2.3.1 System Updater 0.15.5

(2011/04/21)

Note 139-01: (BOSS) Fixed problem of BOSS timer having invalid value right after CTR started [System Updater]

Immediately after the CTR started the BOSS timer sometimes had an invalid value, so it took time for a task to run. That problem was fixed.

Note 139-02: (BOSS) Fixed the bug that prevented acquisition of service termination notification [System Updater]

Sometimes you could not obtain service termination notification. That problem was fixed.

Note 139-03: (FS) Corrected Result returned when save data mounted twice [System Updater]

When save data was mounted a second time, the MountSaveData function returned a value indicating success. The has been fixed so the correct Result is returned.
This was actually changed in CTR-SDK 2.1 but was accidentally omitted from the change log.

Note 139-04: (OS) Fixed the shutdown process when FATAL ERROR occurs [System Updater]

When the POWER Button was pressed quickly after a FATAL ERROR occurred, the system would not perform the normal shutdown process and instead force the power off. That problem was fixed.

Note 139-05: (UDS) Fixed problem of deadlocking when wireless turned off during Finalize [System Updater]

If the wireless button was switched off during the call to nn::uds::Finalize, in some cases depending on the timing nn::uds::Finalize would not return. That problem was fixed.

Known Issues with SDK 2.3.1 System Updater 0.15.5

In some extremely rare cases the screen will stay black after the system is closed and opened. The symptoms are improved by closing and reopening the system at a point where only rendering cannot be restored properly (i.e., sound output, button input, and other features run normally).
This same issue, however, can also occur with applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have a sequence or time when rendering does not recover after awakening from sleep.
If you reset the settings using the Config tool, start an application without going through the startup sequence on the HOME Menu, and then open and close the system, the system will stop and the top and bottom screens will turn black.

CTR-SDK Version 2.3.0 Release

(2011/04/15)

Note 138-01: (APPLET) Fixed inability to get entire parameter with `applet::ReceiveDeliverArg` function [SDK]

The parameter information obtained with the applet::ReceiveDeliverArg function at such times as application jumping was only 386 bytes, or shorter than the actual data size of 768 bytes. The problem was fixed.

Note 138-02: (APPLET) Added `nn::applet::CTR::ReceiveDeliverArg`, which allows the buffer region size to be specified [SDK | System Updater]

With the nn::applet::CTR::ReceiveDeliverArg function, the buffer region for receiving DeliverArg data was set to a fixed size by NN_APPLET_PARAMETER_BUF_SIZE and NN_APPLET_HMAC_BUF_SIZE. A function with the same name has been added that enables you to specify only the needed size.

Note 138-03: (DevEnv) Moved Download Application Development Manual to programming manuals [SDK]

Moved the Download Application Development Manual ($CTR_SDK/documents/TechnicalNotes/DownloadAppManual), deleting it from the CTR-SDK and moving it to a Programming Manual.

Note 138-04: (GR) Fixed a problem with light source disable commands using `FragmentLight::MakeDisableCommand` [SDK]

When FragmentLight::MakeDisableCommand was used to generate commands to disable light sources, the value of register 0x1c6 became "0" in error. This has been corrected to 1.

Note 138-05: (GR) Added to the text about exclusive fragment operation modes in the RenderState function reference [SDK]

Supplemented the explanation in the RenderState function reference about the mode settings for exclusive fragment operations (MODE_GL/GAS_ACC_DMP/SHADOW_DMP) and logical operations/blending.

Note 138-06: (GR) Fixed a bug in `RenderState::ShadowMap::MakeCommand` [SDK]

The command to 0x100 was not generated appropriately by RenderState::ShadowMap::MakeCommand. That problem was fixed.

Note 138-07: (GR) Changed the default value for `RenderState::StencilTest::maskOp` to "0xff" [SDK]

The default value for RenderState::StencilTest::maskO was 0. It was changed to "0xff" to match the OpenGL specification.

Note 138-08: (GR) When rendering to shadow texture is enabled, commands related to the framebuffer are now issued by `RenderState::FBAccess::MakeCommand` [SDK]

When rendering to shadow textures, commands related to the framebuffer are now created using RenderState::FBAccess::MakeCommand.

Note 138-09: (GR) Added a function for generating commands for only the texture combiner's constant color [SDK]

Added the function Combiner::Stage::MakeConstantColorCommand, which generates commands only for the constant color of the texture combiner.

Note 138-10: (GR) Fixed problem of GPU hanging when padding used for vertex attribute load array elements. [SDK]

When commands were generated using Vertex::MakeEnableAttrCommand, the GPU would hang if padding was used for vertex attribute load array elements. That problem was fixed.

Note 138-11: (HID) Added the `GetAxisRotationMatrix` function [SDK]

Added the function GetAxisRotationMatrix, which requires less overhead than the existing function, to the AccelerometerReader class and the GyroscopeReader class.

Note 138-12: (HIO) Fixed a bug with `HostFile::Read` [SDK]

When using PARTNER-CTR 2011/03/25 and later versions for debugging, the following problems occurred when nn::hio::HostFile::Read was called. The problems have been fixed.

After a read there was a shift in the seek position.
The value returned was larger than the amount read.

Note 138-13: (TOOL) Fixed problem of DevMenu freezing when SD Card inserted/removed [SDK]

DevMenu would freeze if the SD Card was vigorously inserted and removed. That problem has been fixed.

Note 138-14: (TOOL) Added FontConverter files [SDK]

Added the following FontConverter files: 3ds_bitmap_font_std.xlor and 3ds_bitmap_font_std.xllt

Note 138-15: (TOOL) Fixed a bug with `makebanner` [SDK]

The change made in Note 131-48 was insufficient, and error messages were not handled correctly when the matchmaking game ID and matchmaking game mode bit were set.
This problem was corrected.

Note 138-16: (UDS) Made change relating to unique ID used by `CreateLocalCommunicationId` function [SDK | Sample Demos]

Up until now, when the nn::uds::CreateLocalCommunicationId function generated a local communication ID for development purposes, the unique ID 0xFFFFF was used. Henceforth, please use the unique IDs for game software prototypes (0xFF000 to 0xFF3FF) instead.
When the local communication ID is generated using a game software prototype unique ID (as opposed to using the unique ID 0xFFFFF), the setting for Debug Mode in the Config tool Other Setting will not affect the behavior of the API.

Note 138-17: (UDS) Revised descriptions related to block time [SDK]

In the UDS function reference, clarified that a reference value is specified for a function that blocks for longer than 100ms.

Known Issues with SDK 2.3.0 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.

CTR-SDK Version 2.3.0 System Updater 0.15.4

(2011/04/15)

Note 137-01: (APPLET) Added `nn::applet::CTR::ReceiveDeliverArg`, which allows the buffer region size to be specified [SDK | System Updater]

Note 137-02: (CAMERA) Fixed problem of stopping when system opened/closed [System Updater]

When the system was opened or closed while the camera was in use, in rare instances the system would stop. That problem was fixed.

Note 137-03: (CEC) Fixed problem of daemon stopping [System Updater]

If the system connected to a communication partner and then immediately afterward disconnected, in rare instances the StreetPass daemon would stop. That problem was fixed.

Note 137-04: (CEC) Fixed problem of connection failure with previous versions of CTR [System Updater]

When a CTR with System Updater 0.15.2 connected to a system that had System Updater version 0.15.1 or earlier, the connection would fail around half of the time. That problem was fixed.

Note 137-05: (CEC) Fixed inability to communicate again with same peer after resetting time [System Updater]

If the system's internal clock was reset, for example, because the battery was removed, in some cases the period to refrain from communicating again with same peer would be miscalculated and the inability to communicate would persist. That problem was fixed.

Note 137-06: (FS) Added support for backup devices made by second-party vendors [System Updater]

Backup devices made by second-party vendors did not operate correctly. That problem was fixed.

Note 137-07: (HTTP) Fixed bug relating to CONNECT requests [System Updater]

When an error occurred immediately after receiving Connection Established, the CONNECT request would be invalid at the next time of communications. That problem was fixed.

Note 137-08: (OS) Fixed inability to recover from sleep when country code not set [System Updater]

In an environment where the country code has not been set, for example, because the HOME Menu has never been launched, the system could not recover from sleep. That problem was fixed.

Note 137-09: (PL) Revised so that in compatibility mode, the pedometer now stores a full seven days of steps [System Updater]

In compatibility mode, the pedometer under certain conditions would store 6 minutes less than a full 7 days of steps. That has been fixed so the pedometer now stores data for the full 7 days (7 x 24 hours).

Note 137-10: (UDS) Fixed problem of process halting inside Initialize function when country code not set [System Updater]

In an environment where the country code has not been set, for example, because the HOME Menu has never been launched, the processing would stop inside the Initialize function. That problem was fixed.

Known Issues with SDK 2.3.0 System Updater 0.15.4

In some extremely rare cases the screen will stay black after the system is closed and opened. The symptoms are improved by closing and reopening the system at a point where only rendering cannot be restored properly (i.e., sound output, button input, and other features run normally).
This same issue, however, can also occur with applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have a sequence or time when rendering does not recover after awakening from sleep.
If you reset the settings using the Config tool, start an application without going through the startup sequence on the HOME Menu, and then open and close the system, the system will stop and the top and bottom screens will turn black.
If the POWER Button is quickly pressed after a FATAL ERROR has been generated, the shutdown process just forces the power off.

CTR-SDK Version 2.3.0 SampleDemos

(2011/04/15)

Note 136-01: (UDS) Made change relating to unique ID used by `CreateLocalCommunicationId` function [SDK | Sample Demos]

Known Issues with SDK 2.3.0 SampleDemos

　 None.

CTR-SDK Version 2.2.0 System Updater 0.15.3

(2011/04/12)

Note 135-01: (HOME Menu) Support for DSiWare [System Updater]

The following features related to DSiWare have been added to the HOME Menu:

Listing the DSiWare in NAND.
Starting Nintendo DSiWare

Note 135-02: (HOME Menu) Fixed bug where application did not receive termination notification when POWER Button was held down immediately after HOME Button pressed [System Updater]

When the POWER Button was pressed and held down immediately after the HOME Button was pressed, the application was not given a termination notification.

Note 135-03: (HOME Menu) Fixed problem of not transitioning to sleep when system closed while returning to application from HOME Menu [System Updater]

When the system was closed while returning to the application from the HOME Menu, the state would not transition to sleep even if REPLY_ACCEPT was returned. That problem was fixed.

Note 135-04: (HOME Menu) Support for download applications [System Updater]

The following features related to downloadable applications have been added to the HOME Menu:

List the applications in the SD Card.
Start downloadable applications.
Hot swapping of SD Cards.

Note 135-05: (HOME Menu) Fixed problem of microphone input not working after application using microphone input is quit from the HOME Menu [System Updater]

When an application using microphone input was suspended and then quit from the HOME Menu, microphone input would be disabled until another application was launched. That problem was fixed.
When this problem happened, the banner on the HOME Menu would stop rotating in response to microphone input.

Note 135-06: (HOME Menu) Added calibration for accelerometer [System Updater]

Added a feature for correcting the offset value of the accelerometer by keeping the Y and B Buttons depressed for 3 seconds while the HOME Menu is displaying.
The corrected offset value is immediately applied to the suspended application.

Note 135-07: (HOME Menu) Changed the POWER Menu screen [System Updater]

Changed the POWER Menu screen display when the POWER Button is pressed.
The text and layout were changed, and the SLEEP Button was eliminated.
Applications do not need to do anything in response to these changes.

Note 135-08: (Mii Maker) Added a feature to move special Mii from the front-end database to the back-end database [ System Updater]

Added a feature for moving special Mii characters from the front-end database where they were registered to the back-end database.

Note 135-09: (Notifications) Added start application function to Notifications [System Updater]

By pressing the Start Application button on the Notifications details screen, you can now launch applications that have been delivered in notifications.
Information about the arguments passed to the application side will be included in the next planned release of the applet specifications.

Note 135-10: (Game Notes) Added a border to the touch-disabled range [System Updater]

Added a border to the touch-disabled range of the Game Notes screen.

Note 135-11: (Software keyboard) Fixed bug in North American/European versions where system would stop if the user pressed the HOME Button or POWER Button after pressing the button for switching dictionaries [System Updater]

The North American/European versions of the software keyboard would stop working if the user pressed the button to switch dictionaries, and then pressed the HOME Button (or the POWER Button) at the moment the dialog displayed. That problem was fixed.

Note 135-12: (Software keyboard) Fixed bug with sleep recovery that occurred in response to timing of character input [System Updater]

If the system went to sleep after characters were input but before predictive text input candidates were displayed, the system would not recover from sleep. That problem was fixed.

Note 135-13: (System Settings) Support for downloadable applications on CTR software management screen, and support for DSiWare on DSiWare management screen [System Updater]

Note 135-14: (System Settings) Fixed problem of blank in Other Settings: Region name [System Updater]

In the US/EU versions of the System Settings, the region name in the user information was saved as empty when the following procedure was carried out. That problem has been fixed.

Parental Controls were configured in the System Settings.
In the System Settings, a country that has no individual region settings was selected in Profile > Region Settings
(For example, Anguilla for the US region, or Iceland for the EU region.)

When this was done, the region name in the language that was set in the system settings was cleared.
In other words, when nn::cfg::CTR::GetSimpleAddress(pSimpleAddress) was called to obtain region information, pSimpleAddress->regionName[nn::cfg::CTR::GetLanguage()] was an empty string.
This was fixed by setting the country name as the region name.

Note 135-15: (Audio Selection Applet) Added audio selector applet [System Updater]

Added an applet that allows you to select audio recorded using Nintendo 3DS Sound.

Known Issues with SDK 2.2.0 System Updater 0.15.3

In some extremely rare cases the screen will stay black after the system is closed and opened. The symptoms are improved by closing and reopening the system at a point where only rendering cannot be restored properly (i.e., sound output, button input, and other features run normally).
This same issue, however, can also occur with applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have a sequence or time when rendering does not recover after awakening from sleep.
The system may stop with the top and bottom screens remaining black in some rare cases when closing and opening the system during camera capture.
If you reset the settings using the Config tool, start an application without going through the startup sequence on the HOME Menu, and then open and close the system, the system will stop and the top and bottom screens will turn black.

CTR-SDK Version 2.2.0 Release

(2011/04/08)

Note 134-01: (AC) Removed `AP_TYPE_FREESPOT` [SDK | System Updater]

Merged AP_TYPE_FREESPOT with AP_TYPE_HOTSPOT.

Note 134-02: (CAMERA) Added information about the CAMERA library termination procedure [SDK]

If the application exits without shutting down the camera, there will be audible noise from the HOME Menu. A recommended procedure for terminating the camera library was added to the Function Reference.

Note 134-03: (DevEnv) Added the compiler version to `version.h` [SDK]

Added the following constants, which indicate the compiler version, to version.h.

NN_VERSION_RVCT_MAJOR: RVCT major version
NN_VERSION_RVCT_MINOR: RVCT minor version
NN_VERSION_RVCT_CC_REV: RVCT compiler revision number
NN_VERSION_RVCT_LD_REV: RVCT linker revision number

Note 134-04: (DevEnv) Shared fonts are now uncompressed [SDK]

Changed the shared fonts included in CTR-SDK from compressed to uncompressed.

Note 134-05: (FRIENDS) Changed `GetFriendKeyList` to return `ResultTooLarge` [SDK]

Changed the GetFriendKeyList function so that it returns ResultTooLarge when the caller tries to retrieve a list that is larger than the number of users that can be registered in a friend list.

Note 134-06: (GX) Revised PICA macro headers [SDK]

Added the following enumerated constants to gx_MacroTexture.h to specify the format of shadow map textures and gas textures.

PICA_DATA_TEXTURE_FORMAT_SHADOW_UNSIGNED_INT = 0x0
PICA_DATA_TEXTURE_FORMAT_GAS_DMP_UNSIGNED_SHORT = 0x0

Note 134-07: (GX) Fixed memory fragmentation in `nngxInitialize` [SDK]

Memory buffers are allocated inside the nngxInitialize function. Some are kept until the nngxFinalize function is called as an administrator, and some are allocated for temporary use.
The order of buffer allocation was rearranged so that the memory freed when the nngxInitialize function terminates will not be in disparate chunks.

Note 134-08: (HID) Added a debugging mechanism to detect the SELECT button [SDK]

For debugging purposes, added the nn::hid::EnableSelectButton function to enable retrieval of SELECT Button and nn::hid::DisableSelectButton to disable it again.

Note 134-09: (HIO) Fixed a bug with `Finalize` [SDK]

Fixed a bug where work memory passed with the Initialize function was still used after the Finalize function.

Note 134-10: (HIO) Sped up file reads [SDK | System Updater]

Improved the nn::hio::HostFile::Read function speed when running a program from emulation memory in PARTNER-CTR Debugger.
Programs will not be faster when run from PARTNER-CTR UIC-MIDI.

Note 134-11: (OS) Documented stack-size restrictions specified with `nn::os::Thread::[Try]StartUsingAutoStack` [SDK]

Added documentation to the Function Reference about restrictions for the stack-size argument specified in the nn::os::Thread::[Try]StartUsingAutoStack function.

Note 134-12: (SND) Revised return values from `EncodeAdpcmData` [SDK]

The Function Reference stated that the return value from the EncodeAdpcmData function was "None," but it was actually an s32. The value was changed to void.

Note 134-13: (SND) Fixed a bug where diffused noise would emanate when the `biquad` filter was used [SDK]

Fixed a bug (since CTR-SDK 2.0) where using the biquad voice filter caused diffused noise to emanate.

Note 134-14: (SND) Fixed a bug where `nn::snd::Delay` and `nn::snd::Reverb` would be disabled when recovering from sleep or returning from the HOME Menu [SDK]

If the application went into sleep or transitioned to the HOME Menu while using nn::snd::Delay or nn::snd::Reverb, this would not be reflected in the output. This bug has been fixed.

Note 134-15: (SND) Stopped noise that continued when three buffers were used in a sound's final output stage [SDK]

Fixed a rare bug where sound cutoff would trigger continued noise when three buffers were used for the final output stage by the nn::snd::SetOutputBufferCount function.

Note 134-16: (SOCKET) Fixed a bug where `GetHostByName` stopped operation [SDK]

Fixed a bug where assigning 256 or more characters to GetHostByName would stop the operation.

Note 134-17: (TOOL) Added support for 4 GB cards [SDK]

ctr_makerom now supports 4 GB cards.
4 GB was added as one of the values that can be specified for the RFS MediaSize.

Note 134-18: (TOOL) Fixed a bug with `BossLotcheckTool` [SDK]

Fixed the BossLotcheckTool tool to prevent buffer overflow.

Note 134-19: (TOOL) Changed the language setting of the `Config` tool [SDK]

The HOME Menu could not be configured if the Config tool language was set to invalid, but this limitation has been removed and configuration is now possible.

Note 134-20: (TOOL) Display remaining volume of importable media in `DevMenu` [SDK]

Changed the DevMenu display to indicate the remaining volume of importable media.

Note 134-21: (TOOL) Changed disconnection from an access point in `FriendTestingPartner` to be handled as error [SDK]

Changed disconnection from access point in the FriendTestingPartner function to be handled as error.

Note 134-22: (TOOL) Added `SaveDataSize` to RSF files [SDK]

Added Rom/SaveDataSize to RSF. This item specifies the save data size of a download application.
For details, see the makerom documentation.

Note 134-23: (TOOL) Changed the `WMTestTool` [SDK]

Removed unneeded features from WMTestTool.

Note 134-24: (UDS) Added a function to obtain the channel [SDK | System Updater]

Added the nn::uds::GetChannel function to get the communication channel.

Note 134-25: (UDS) Changed the return values of `Send` and `Receive` [SDK]

Changed the SendTo function to return ResultMisalignedAddress if the send buffer passed to it is not 4-byte aligned.
The send data size parameter indicating the size of the send buffer must be rounded up to the nearest multiple of 4.
Changed the Receive and ReceiveFrom functions to return ResultMisalignedAddress if the receive buffer passed to them is not 4-byte aligned.
If the receive buffer size assigned to the argument is not a multiple of 4, the function returns ResultMisalignedSize.

Known Issues with SDK 2.2.0 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.
DevMenu may cause a data abort if an SD Card that is not fully inserted is pushed and pulled several times.
If the CTR Card and SD Card are inserted and removed at the same time repeatedly, DevMenu may display two CTR Card items.

CTR-SDK Version 2.2.0 System Updater

(2011/04/08)

Note 133-01: (AC) Removed `AP_TYPE_FREESPOT` [SDK | System Updater]

Merged AP_TYPE_FREESPOT with AP_TYPE_HOTSPOT.

Note 133-02: (BOSS) Added BOSS features [System Updater]

The following features were added to BOSS.

If-Modified-Since at ZoneAP level
When a task executes, the LastModifiedTime is recorded for each ZoneAP it connects to. This function thus enables it to switch the If-Modified-Since time that it notifies to the download server in accordance with the access point it is connected to.
This makes it possible to download at the connected ZoneAP level, retrieving new data and avoiding the re-acquisition of data it has already acquired.
This function is available with services that switch the distribution data at the connected access-point level.
Resume task execution after going into resume ready state while connected to a zone access point
If a task went into resume ready state while running connected to a zone access point, using this function it can later run a task connected to a non-zone access point (e.g., a task running on a home access point), and then resume when connected again to the zone access point.
This makes it possible to receive a data delivery from a particular dedicated zone access point.
Prevention of duplicated NSA data reception
The ID of download data (NSA) is recorded. Thus if an NSA that has already been downloaded is delivered, this feature will avoid retrieving the NSA twice.
The IDs of the latest NSAs that were downloaded (up to 50 max) are recorded for each task.

Note 133-03: (BOSS) Fixed a bug that prevented the play history from being recorded while in DS compatibility mode [System Updater]

The fix in Note 130-05 was insufficient. This note fixes a bug where at certain times the play history could not be recorded in DS compatibility mode, during Internet configuration.

Note 133-04: (BOSS) Fixed a bug that caused the system to take a long time to go to sleep or to end processing during policy list downloads [System Updater]

The fix in Note 130-06 was insufficient. This fix resolves the bug (if a process suddenly entered sleep or received a process termination notification while downloading a policy list, it would take a long time to complete).

Note 133-05: (FS) Prevented a drop in the write speed to expanded save data [System Updater]

There was a significant performance drop on some types of SD Cards when performing large writes (on the order of several megabytes) to files on expanded save data. This drop in performance was alleviated.

Note 133-06: (HID) Revised sampling shutdown processing of the accelerometer and gyroscope [System Updater]

There was a bug with shutting down sampling of the accelerometer and gyroscope when an application using one of them failed to free the AccelerometerReader or GyroscopeReader functions upon shutdown before calling hid::Finalize.

Note 133-07: (HIO) Sped up file reads [SDK | System Updater]

Improved the nn::hio::HostFile::Read function speed when running a program from emulation memory in PARTNER-CTR Debugger.
Programs will not be faster when run from PARTNER-CTR UIC-MIDI.

Note 133-08: (HTTP) Fixed a bug relating to reusing `KeepAlive` in communication using chunked reception [System Updater]

Fixed a bug where reusing a KeepAlive on a connection that performed chunked reception would result in a response header error.

Note 133-09: (MCU) Fixed a bug where in compatibility mode the step count record could be one hour off [System Updater]

Fixed a bug where the seven-day record of steps would be off by one hour overall while in compatibility mode; if the user used the pedometer for seven days and continued to increase the step count immediately before recording stopped.

Note 133-10: (NDM) Changed BOSS to be stopped by default [System Updater]

Changed BOSS to be stopped by default.
An application that wants to run BOSS autonomously in the background must release the stop on BOSS by using the nn::ndm::Resume function.
The stop has no effect during sleep or when the execution of nn:: boss::StartImmediate function is specified explicitly.

Note 133-11: (NET) Fixed a bug where the state may not change from `disconnected` if Wi-Fi is turned off during UDS initialization [System Updater]

Fixed a bug where if Wi-Fi was switched off while initializing UDS, the state could not change from disconnected.

Note 133-12: (NET) Added a feature to automatically recover from a fatal wireless error [System Updater]

Changed to automatically recover from fatal wireless errors.
If a fatal wireless error occurred before, the fatal error screen would appear and the system would stop. From this release, the system recovers automatically without stopping.
After automatic recovery, it will appear to the AC, CECD, NDM, and other higher layers that wireless communication mode turned on immediately after turning off.
For this reason, depending on the application's implementation, a message may appear stating that the connection was lost.

At this time, there is no auto recovery from fatal wireless communication errors occurring during background communication in sleep mode, or when using UDS communication.
(Currently, fatal errors will never happen in these cases that are not covered by auto recovery.)

Note 133-13: (NET) Added fatal error display for wireless module malfunctions [System Updater]

The system was changed to display the fatal error screen if a malfunction in the wireless module caused wireless initialization to fail.

Note 133-14: (OS) Shortened the time required for thread initialization [System Updater]

Reduced the time required for internal processing by Thread::Start and other functions that initialize threads.

Note 133-15: (OS) Fixed a bug where the timer was not properly freed [System Updater]

Fixed a bug where the nn::os::Timer function would not be properly freed if Finalize was called before Stop.

Note 133-16: (OS) Fixed a bug where importing a CIA file via SPI failed with the debugging software [System Updater]

Fixed a bug where importing a CIA file via SPI would fail with the debugging software.
Note that CIA file imports via SPI are not conducted unless an option is specified.
(It is only performed when the .spi option is specified for the NAND WRITE and L commands.)

Note 133-17: (PTM) Revised detection of changes in the system state during sleep [System Updater]

Fixed a bug where it was not possible to get correct system information when the state of the power adapter, battery level, or charge indicator changed during sleep.

Note 133-18: (SOCKET) Fixed a bug where `ENOTCONN` was returned from `Send` upon reception of RST [System Updater]

ECONNRESET is returned when RST is received while blocking on Send on a TCP socket, but there were other cases in which ENOTCONN was returned.
This bug has been fixed.

Note 133-19: (TOOL) Added a screen capture feature to the development menu [System Updater]

Added the following specifications to the development menu when the application is suspended.

Display the images of the top and bottom screens of the application while suspended
When the L Button is pressed, bitmaps of the top and bottom screens (3 screens if stereoscopic view is enabled) are saved to the SD Card

See the development menu documentation for details.

Note 133-20: (UDS) Revised the system so that a CTR-SDK internal error is not returned [System Updater]

CreateNetwork, ConnectNetwork, DestroyNetwork, and DisconnectNetwork were returning an error that is only handled internally by the CTR-SDK (nn::uds::detail::ResultFatalError). The functions were revised to no longer return the error.

Note 133-21: (UDS) Fixed a bug where the state would become `STATE_CREATING_NETWORK` after `CreateNetwork` failed [System Updater]

If the CreateNetwork function fails, the state should become STATE_DISCONNECTED, but the state sometimes became STATE_CREATING_NETWORK; this bug has been fixed.

Note 133-22: (UDS) Fixed a bug where `GetLinkLevel` would always return link level 0 [System Updater]

Fixed a bug (since CTR-SDK 2.1) where the GetLinkLevel function would always return link level 0.

Note 133-23: (UDS) Added a function to obtain the channel [SDK | System Updater]

Added the nn::uds::GetChannel function to get the communication channel.

Note 133-24: (UDS) Fixed a bug where the system stopped due to an exception during reception [System Updater]

Fixed a bug where the system would in rare cases stop with an exception when receiving a large volume of data on one port.

Note 133-25: (UDS) Revised the return values from `Scan` when the wireless switch is set to OFF [System Updater]

Fixed a bug where if the wireless switch is set to off during a call to the Scan function, it should return ResultWirelessOff but was returning ResultInvalidState.

Known Issues with System Updater in SDK Version 2.2.0

In some extremely rare cases the screen will stay black after the system is closed and opened. The symptoms are improved by closing and reopening the system at a point where only rendering cannot be restored properly (i.e., sound output, button input, and other features run normally).
This same issue, however, can also occur with applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have a sequence or time when rendering does not recover after awakening from sleep.
The system may stop with the top and bottom screens remaining black in some rare cases when closing and opening the system during camera capture.
If you reset the settings using the Config tool, start an application without going through the startup sequence on the HOME Menu, and then open and close the system, the system will stop and the top and bottom screens will turn black.

CTR-SDK Version 2.2.0 Sample Demos

(2011/04/08)

Note 132-01: (APPLET) Added `lib_applet` [Sample Demos]

In CTR-SDK 2.1, applet[.h|.cpp] added to demo1, demo2, and so forth. has been moved into the $SampleDemos/common directory in the format lib_applet.

Note 132-02: (APPLET) `applet::Enable` and others added to sample demos [Sample Demos]

The applet::Enable function was added to the sample demos. Starting from the HOME Menu is now also possible.
Some demos have also been revised to use lib_applet and now enable HOME Button and sleep transitions.

The following demos do not support HOME Menu startup.

hio
http
makebanner
news
ssl
template

Note 132-03: (GX) Sped up the `ScreenCapture` sample [Sample Demos]

Sped up saving to SD Card in the ScreenCapture sample.
There was a problem with the old implementation that caused performance to degrade.

Known Issues with SDK 2.2.0 Sample Demos

　 None.

CTR-SDK Version 2.1.0 Release

(2011/03/25)

Note 131-01: (APPLET) Revised so that `PrepareToCloseApplication` is called from `CloseApplication` [SDK]

Revised so that PrepareToCloseApplication is called from CloseApplication.

Note 131-02: (APPLET) Added wrapper functions for HOME Menu transitions and POWER Menu transitions [SDK]

Added the nn::applet::ProcessHomeButtonAndWait and nn::applet::ProcessPowerButtonAndWait wrapper functions concerning HOME Menu transition and POWER Menu transition processing.

Note 131-03: (BOSS) Changed the default setting value for the `TASK_PERMISSION` attribute [SDK]

Changed the default setting for the TASK_PERMISSION attribute of a task to TASK_PERMISSION_IN_PARENTAL_CONTROL so tasks can be run when Internet access is enabled by Parental Controls.

Note 131-04: (CAMERA) Added the `GetParallax` function [SDK]

Added the GetParallax function to calculate parallax for the specified distance from the camera using the calibration data.

Note 131-05: (CAMERA) Revised the `GetStereoCameraCalibrationMatrix` function [SDK]

The GetStereoCameraCalibrationData function returns a 3 X 4 matrix to use for two-dimensional geometric conversions.
The z-axis scale should have been 1 but was mistakenly set to 0. This has been fixed.

Note 131-06: (CAMERA) Added the `GetStereoCameraCalibrationMatrixEx` function [SDK]

Stereo camera placement errors vary widely, so the GetStereoCameraCalibrationMatrixEx function was added to return a correction matrix that would not lose the edges of the image even for systems that had placement errors near the limit.

Note 131-07: (CAMERA) Added the `SetBrightnessSynchronization` function [SDK | System Updater]

Added the SetBrightnessSynchronization function to enable a feature that links the stereo camera brightness.
By default, the above link feature is disabled.

Note 131-08: (CEC) Changed the `MessageBox` class function names [SDK]

Changed function names because some function names had abbreviations in them.

GetBoxMessNumMax → GetBoxMessageNumMax
GetBoxMessNum → GetBoxMessageNum
GetMessageMessSize → GetMessageSize
GetMessageMessTypeFlag → GetMessageTypeFlag
GetMessageMessIdPair → GetMessageIdPair
GetMessageMessId → GetMessageId
GetMessIndex → GetMessageIndex

Note 131-09: (CEC) Added debug functions to transition to StreetPass-exclusive mode [SDK]

The system can switch between various types of background communication (including Internet and StreetPass), but we also provide a feature for switching background communication to StreetPass-exclusive mode.

nn::cec::CecControl::EnterExclusiveState
nn::cec::CecControl::LeaveExclusiveState

This can be used to verify StreetPass communication and other operations.
These functions operate only when debug mode is enabled.

Note 131-10: (CRYPTO) Added a 4-byte alignment restriction for the hash acquisition pointer [SDK]

An error may occur if the output destination pointer pOut is not 4-byte aligned for Sha1Context::GetHash, or CalculateSha1, and CalculateHmacSha1. This restriction, which also applies to Sha256, is included in the function reference.

Note 131-11: (CX) Changed the `IsFinishedUncompRL` function name to `IsFinishedUncomp [SDK]`

The IsFinishedUncompRL function name was inappropriate, so it has been changed to IsFinishedUncomp.
The old function name is kept for compatibility, but it has been removed from public release.

Note 131-12: (DLP) Deleted symbols related to DUP [SDK | System Updater|SampleDemos]

Deleted the symbols related to DUP (updates through Download Play).
In conjunction with this, some of the information about the client that can be obtained from the server will change.
Specifically, the DUP client is always in the CLIENT_STATE_JOINED_SESSION (state before child device distribution).
After the DUP completes, transitions to CLIENT_STATE_DOWNLOADING and child device distribution begin.
Finally, nn::dlp::Server::GetClientStatus was removed because the download progress during DUP can be determined. It was replaced with nn::dlp::Server::GetClientState.

Note 131-13: (DLP) Added a function to determine if a device is a child [SDK | Sample Demos]

Added a function to determine if a device is a child device.
The function is nn::dlp::IsChild, which is defined in dlp_Common.h.
Use it when neither nn::dlp::Server nor nn::dlp::FakeClient can be used (i.e., when the Initialize function has not been called).

Note 131-14: (DevEnv) Support for C++ exceptions [SDK]

Made changes so that C++ exceptions can be used.
However, C++ exceptions are disabled by default with the CTR-SDK build system.
When using C++ exceptions, add the CCFLAGS += --rtti --exceptions LDFLAGS += --exceptions specification to the application's OMakefile.

Note 131-15: (DevEnv) Added how to import a TWL NAND application to CTR [SDK]

Added how to import a TWL NAND application to the development menu, ctr_makecia reference, and Download Application Development Manual.

Note 131-16: (DevEnv) Support for the CCL format [SDK]

Support added to build for the CCL format. This separates the CCI executable code and ROM-FS portions and loads them separately to the debugger.
In OMakefile, specify LIST for the CTR_APPTYPE variable to generate the CCL format.
The CCL format is not currently supported, however, so it cannot be used for debugging or other purposes.

Note 131-17: (DevEnv) Added Download Application Development Manual [SDK]

The Download Application Development Manual was added to $CTR_SDK/documents/TechnicalNotes/DownloadAppManual.

Note 131-18: (DevEnv) Added build variables for the vertex shader assembler and linker [SDK]

Added SHADER_ASFLAGS and SHADER_LDFLAGS as build variables that can be specified as options for the vertex shader assembler and linker, respectively.

Note 131-19: (FS) Added an archive that can directly write to an SD Card [SDK]

Added an archive that can directly write to an SD Card.
It cannot load files nor open directories.
It can be used by calling the nn::fs::MountSdmcWriteOnly function.

Note 131-20: (FS) Changed error-handling specifications for two archive functions [SDK]

The specification for the following two functions was changed so that internal errors do not return an error before transitioning to the error display screen.
- nn::fs::GetRomRequiredMemorySize
- nn::fs::MounrRom
These functions only return successful, so there is no longer any need for error handling by the application.

Note 131-21: (FS) Revised to deny access when application save data is invalid [SDK]

When accessing card applications or download applications, the application data cannot be accessed if the application's save data is invalid.
The return value indicates invalid save data.

In conjunction with this change, a C8804497 error occurs when launching a card application that uses save data if the inserted CTR card does not have on-board backup memory.

Note 131-22: (FS) Documented buffer access when reading or writing a file [SDK]

Explained in the FS library function reference the result of buffer access while reading or writing to a file.

Note 131-23: (FS) Deleted `ResultArchiveInvalidated` from expanded-save-data error handling [SDK]

There were cases when ResultArchiveInvalidated was returned when mounting, creating, deleting, or enumerating expanded save data archives, but a ResultMediaNotFound error is now returned instead.
As a result, error handling for ResultArchiveInvalidated is unnecessary when dealing with expanded save data archives.
However, for expanded save data directory and file operations, ResultArchiveInvalidated must be handled as it had been previously.

Note 131-24: (GR) Fixed a bug that prevented using `Vertex::DisableAttr` to disable vertex attributes that were enabled with `Vertex::EnableAttrAsArray` [SDK]

Vertex attributes enabled using the Vertex::EnableAttrAsArray function could only be disabled using Vertex::DisableAll, which was a bug. This has been revised so that attributes can be disabled using Vertex::DisableAttr.

Note 131-25: (GX) Updated the PICA macro header [SDK]

Added two enumerated constants, PICA_DATA_TEXTURE_FORMAT_SHADOW_UNSIGNED_INT and PICA_DATA_TEXTURE_FORMAT_GAS_DMP_UNSIGNED_SHORT to the PicaDataTexture0SamplerType enumerated type in order to specify shadow map texture and gas texture formats.

Note 131-26: (GX) Added the `glGetTexLevelParameter[if]v` function [SDK]

The glGetTexLevelParameter[if]v function has been added to the API to get information related to textures that are currently bound.

Note 131-27: (GX) Added the `nngxAdd3DCommandNoCacheFlush` function [SDK]

The nngxAdd3DCommandNoCacheFlush function, which does not flush the cache of the region specified by bufferaddr, has been added for cases when GL_FALSE is added to the copycmd argument of the nngxAdd3DCommand function.

Note 131-28: (GX) Expanded capability of the `nngxAddCmdlist` function [SDK]

The nngxAddCmdlist function was revised so that a command request to reference external command buffers can be added.

Note 131-29: (GX) Added the `nngxAddVramDmaCommandNoCacheFlush` function [SDK]

The nngxAddVramDmaCommandNoCacheFlush function, which does not flush the cache of the region specified by srcaddr, has been added for the nngxAddVramDmaCommand function.

Note 131-30: (GX) Revised `nngxCmdlistStorage` to reduce the number of allocator calls [SDK]

Reduced the number of times the memory allocator is called by the nngxCmdlistStorage function.

Note 131-31: (GX) Fixed bugs in `nngxCopyCmdlist` and `nngxClearFillCmdlist` [SDK]

Fixed the bugs that caused the gas density information to be incorrectly updated when command lists included the nngxCopyCmdlist or nngxClearFillCmdlist functions.

Note 131-32: (GX) Revised `nngxInitialize` to reduce the number of allocator calls [SDK]

Reduced the number of times the memory allocator is called by the nngxInitialize function.
Also, optimized the request size.

Note 131-33: (GX) Updated the shader tool [SDK]

The following changes were made to the shader tool.

The break command, which is not covered by the specification, cannot be compiled.
An error occurs when the break command is called immediately before the endloop command.
An error occurs when a jpb or jpc command is called immediately before a else, endif, endloop, or ret command
An error occurs when a jpb or jpc command jumps in an if or loop statement.
Fixed typos in error messages.
Added the -preprocess option to support shader assembler preprocessing.

Note 131-34: (GX) Updated the documentation [SDK]

The following changes were made to the GX documentation.

DMPGL20_specification.pdf

Added "Obtaining Texture Level Parameters"
Added a description of dmp_LightEnv.absLutInput{RR,...}
Added supplementary explanations for "Shadow Attenuation Term" and "Bump Mapping"

DMPGL20_programming_guide.pdf

Added a description to 13.5 "Normal Map Formats and Types"

DMPGL20_system_API_specification.pdf

Added descriptions of the nngxAddVramDmaCommandNoCacheFlush and nngxAdd3DCommandNoCacheFlush functions
Revised the Catmull-Clark subdivision shader register settings

VertexShaderReferenceManual.pdf

Added a description of the preprocessing execution option
Supplemented explanations of the jpb, jpc, and breakc commands

Note 131-35: (HID) Changed the gyro sensor zero point correction setting value [SDK]

Reviewed and changed the strength of zero-point correction when configuring GYROSCOPE_ZERODRIFT_STANDARD of hid::ZeroDriftMode.
The zero-point correction for STANDARD is now stronger.
Nothing has changed for TIGHT and LOOSE.
Revise applications in accordance with the new STANDARD settings.
The previous settings for STANDARD are now more similar to the settings for TIGHT.

Note 131-36: (HID) Announced change for assessing the accelerometer calibration value when transitioning to the HOME Menu [SDK]

Explained in the reference that the calibration value may change upon transition from the application to the HOME Menu. The implementation of this feature is planned for a future release.

Note 131-37: (HIO) Added reference to `nn::hio::CTR::SerialChannel::GetReadableSize` [SDK]

Documented the different sizes that can be received based on the attr argument.

Note 131-38: (JPEG) Added the `GetLastDateTimePointer` function [SDK]

Added the GetLastDateTimePointer function to return a pointer to the Exif date and time information.

Note 131-39: (MATH) Added functions that were previously omitted from the reference [SDK]

All of the functions in $CTR_SDK/include/nn/math/math_Utility.h were omitted from the Function Reference. This oversight has been corrected.

Note 131-40: (MIDI) Changed the `nn::midi::CTR::Open` function to determine the UIC-MIDI device [SDK]

In CTR-SDK 2.0 and later, the UIC-MIDI device is identified when the nn::midi::CTR::Open function is called.
When a UIC-MIDI device is not recognized, nn::midi::ResultUnknownDevice is returned.
The CTR system cannot correctly recognize the UIC-MIDI device when this result is returned. Verify that the UIC-MIDI is inserted in the card slot and then reload the program.

The debugger software specification prior to the PARTNER-CTR 2011/03/09 version does not allow for correct recognition of a reinserted UIC-MIDI device, therefore, by pressing the Reload button.
To correctly recognize the UIC-MIDI device, use the debugger software and either click Load or drag the file icon to the correct screen location.

Note 131-41: (TOOL) Added `BossLotcheckTool` [SDK]

Added BossLotcheckTool to verify BOSS task information or NS data information registered by the application.
For more details, see the Function Reference.

Note 131-42: (TOOL) Changed the option to generate a CXI file [SDK]

Specify -f exec in makerom to generate a CXI file. Previously, this was specified using -f nand.
The -f nand specification still works with CTR-SDK version 2.1, but this capability will be removed in the future.
For details, see the makerom reference page.

Note 131-43: (TOOL) Changed the `Config` tool [SDK | System Updater]

Made the following changes to the Config tool.

Language settings can now be configured
When the language settings are changed to invalid, some menu settings are changed instantaneously
Revised the feature to shift gyro acceleration correction values to write a fixed value to the correction value so individual differences in the shift value do not appear
To perform verification using this feature in the future, use the Config tool from CTR-SDK 2.1 and later

For more details, see the Function Reference.

Note 131-44: (TOOL) Added support for importing to SD Cards [System Updater] [SDK]

Added a feature to the development menu so that downloaded applications can be imported to SD Cards.

Note 131-45: (TOOL) Updated `SaveDataFiler` [SDK]

Made the following changes to the SaveDataFiler tool.

Added a feature to initialize shared expanded save data
Added the features Export, Import, and Destroy Individual Files for the save data of downloadable applications.
The save data of downloadable applications exported using the CTR-SDK 2.1 version of SaveDataFilercannot be imported using earlier versions of SaveDataFiler.
Other save data can be mutually imported and exported.
Changed so that pressing the B Button traverses back up the hierarchy
Changed so Result is displayed when an error occurs

For more details, see the Function Reference.

Note 131-46: (TOOL) Improved the performance of `makerom` [SDK]

Improved the performance of makerom.

Note 131-47: (TOOL) Added debug mode setting [SDK]

Added Debug mode to the Config tool settings.
When Debug mode is enabled, debugging features for the following functions are enabled.
For details, see the individual functions in the Reference Manual.

nn::ac::DebugSetApType
nn::ac::DebugSetNetworkArea
nn::ac::DebugSetNetworkSetting1

CEC

nn::cec::CecControl::StartScanning
nn::cec::CecControl::EnterExclusiveState

nn::uds::CreateNetwork
nn::uds::ConnectNetwork

Note 131-48: (TOOL) Changed banner data capacity restrictions [SDK]

Changed some of the restrictions for data capacity.
Also, made changes so that data that violates these restrictions generates an error during conversion.

Note 131-49: (TOOL) Added tool for generating friend presence load [SDK]

Added the FriendTestingPartner tool to run friend presence background processing on the CTR where a friend relationship was made (the friend presence is updated at a high frequency).

Note 131-50: (TOOL) Added the `UdsLocalIdChecker` tool to confirm the local communication ID [SDK]

Added UdsLocalIdChecker to confirm the local communication ID.

Note 131-51: (TOOL) Added a tool to generate jamming [SDK]

Added WMTestTool, which is provided with Nintendo DS systems as a wireless test tool.
For CTR, use only the feature to generate radio interference (Noise Mode).
Import the CIA file from $CTR_SDK/tools/TargetTools/CTR-TS/Release to the CTR. Then launch the tool from the development menu.
It executes in TWL-compatible mode.
For details, see the Function Reference.

Note 131-52: (TOOL) Revised tools that was not displayed on the HOME Menu outside of the Japanese Region [SDK]

When SaveDataFiler and CecLotCheckTool were imported to a system, they were not displayed on the HOME Menu (outside of the Japanese region).
They are now displayed in all regions.

Note 131-53: (TOOL) Changed to display the firmware version on the development menu [SDK | System Updater]

The firmware version is displayed on the top screen of the development menu. Prior to this change there was no way to confirm the firmware version when the launch default was set to the HOME Menu.
Also, the version displayed on the HOME Menu System Settings was not accurate and was set to 0.

Note 131-54: (UBL) Revised the Function Reference Manual [SDK]

The corrections described in Note 128-43 were not uniformly applied to the documentation, so the text has now been deleted.

Note 131-55: (Y2R) Added the `GetPackageParameter` function [SDK]

Added the GetPackageParameter function to get PackageParameter structure parameters in one operation.

Known Issues with SDK 2.1.0 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.

CTR-SDK Version 2.1.0 System Updater

(2011/03/25)

Note 130-01: (APPLET) Fixed a bug that allowed both `IsExpectedToCloseApplication` and `IsExpectedToProcessPowerButton` to be `true` at the same time [System Updater]

A bug caused both IsExpectedToCloseApplication and IsExpectedToProcessPowerButton to be true at the same time. This occurred when the POWER Button was clicked to return control to the application while a library applet, such as the software keyboard applet or photo selection applet, was running.
This was changed so that only IsExpectedToProcessPowerButton is true.

Note 130-02: (APPLET) Fixed a bug that occurred when a card was removed while waiting for a sleep query callback [System Updater]

An inconsistency occurred in the internal state if a card was removed while the application was returning LATER in response to a SLEEP QUERY. Thereafter, the system could not enter sleep. This bug was fixed.
This was actually changed in CTR-SDK 2.0 but was accidentally omitted from the change log.

Note 130-03: (APPLET) Revised so that `AwakeCallback` is called when the battery is fully discharged during sleep [System Updater]

AwakeCallback was not called if the battery was fully discharged during sleep, so the application could not perform the finalization process. This has been revised so AwakeCallback is called.

Note 130-04: (BOSS) Added BOSS features [System Updater]

The following features were added to BOSS.

Added the Execute Background Tasks Immediately feature.
This is a feature to immediately start background task execution. The function is nn::boss::Task::StartBgImmediate.
Added the Specify Maximum Number of Files for BOSS Storage feature.
This feature ensures the number of files in BOSS storage do not exceed the specified number. The function is an overridden version of nn::boss::RegisterStorage.
Changed the method of scheduling.
Unlike the scheduling method used to date, the highest priority is given to task priority at the time the order of task execution is determined.
The control over task execution order has been changed to be even more precise.
(For example, if a MEDIUM priority task and a HIGH priority task are set to execute at the same time, the HIGH priority task will always be executed first.)

Note 130-05: (BOSS) Fixed a bug that prevented the play history from being recorded while in DS compatibility mode [System Updater]

Fixed a problem associated with the bug in the BOSS finalization process of Internet settings that prevented PTM from finalizing and prevented the play history during DS compatibility mode from being recorded.

Note 130-06: (BOSS) Fixed a bug that caused the system to take a long time to go to sleep or to end processing during policy list downloads [System Updater]

Fixed a bug that occasionally caused the system to take a long time to complete entering sleep or to end processing when notification arrived during policy list downloads.

Note 130-07: (CAMERA) Added the `SetBrightnessSynchronization` function [SDK | System Updater]

Added the SetBrightnessSynchronization function to enable a feature that links the stereo camera brightness.
By default, the above link feature is disabled.

Note 130-08: (CAMERA) Revised priorities for the finalization process [System Updater]

When the HOME Menu was displayed a bug caused sound playback to be interrupted because the thread priority of the camera finalization process was high. The priority for executing the finalization process has has been lowered.
The priorities of other camera processes have not been changed.

Note 130-09: (DLP) Deleted symbols related to DUP [SDK | System Updater|SampleDemos]

Note 130-10: (DLP) Fixed a bug that prevented returning from `FakeClient::StopScan` when the wireless switch was OFF [System Updater]

Control would not return from the FakeClient::StopScan function when it was called immediately before or after switching the wireless button off. This bug was fixed.

Note 130-11: (DevEnv) Fixed a bug that prevented the system from going to sleep when the system was closed immediately after launching from the development menu [System Updater]

The system would not enter sleep when the system was closed immediately after launching an application that was loaded from the development menu using the debugger L command. This bug was fixed.

Note 130-12: (FRIENDS) Organized the `Results` returned by `Login` [System Updater]

Made changes so that the friends::Login function does not return ResultTemporarilyBusy or ResultAlreadyDone.
ResultSuccess is now returned in these situations.

Note 130-13: (FRIENDS) Changed the timing for autonomous login after resuming [System Updater]

Changed the delay time for automatic logins. If a sufficient amount of time has passed after the system was suspended, the time delay between resume and automatic login is reduced, even if the most recent automatic login failed.

Note 130-14: (FS) Revised the `nn::fs::TryDelete` and `nn::fs:TryRename` functions [System Updater]

An nn::fs::ResultBadFormat error was sometimes returned when deleting using nn::fs::TryDeleteFile or nn::fs::TryDeleteDirectory if a file with the same name as the directory was present in the same path.
In addition, an nn::fs::ResultInvalidArgument error was returned when using nn::fs::TryRenameFile or nn::fs::TryRenameDirectory if the same name was used for both a file and a directory in the same path.
These have been fixed and an nn::fs::ResultOperationDenied error is now returned.

Note 130-15: (FS) Revised the `nn::fs::TryDeleteDirectory` and `nn::fs::TryDeleteDirectoryRecursively` functions [System Updater]

When trying to delete directories with names that contained "..." using the nn::fs::TryDeleteDirectory or nn::fs::TryDeleteDirectoryRecursively functions, deletion failed and an nn::fs::ResultOperationDenied error was returned.
This bug has been fixed and the directories are now deleted.

Note 130-16: (FS) Added format determination process when mounting card save data [System Updater]

Added a process to determine if the driver layer format is correct when a card application is mounting its own save data.
If the format is invalid, an nn::fs::ResultBadFormat error is returned. You should first retry formatting.

Note 130-17: (FS) Fixed a bug that prevented processing to return when an SD Card was removed while accessing data from a download application [System Updater]

Control did not return when an SD Card was removed while accessing download application data. This bug was fixed.

Note 130-18: (FS) Fixed the bug that caused `nn::fs::TryDeleteFile` to fail for expanded save data files [System Updater]

Fixed a bug that caused an error to be returned when using nn::fs::TryDeleteFile for a file in expanded save data in an invalid state regardless of whether the actual process completes.

Note 130-19: (FS) Fixed the bug that caused loading a file to fail at some specific time [System Updater]

Fixed a bug that caused a failure in verification when loading a file. It occurred on rare occasions in certain situations.
This bug occurred only with CTR-SDK 2.0 or later.

Note 130-20: (FS) Fixed a bug that prevented an SD Card from being properly recognized when it was removed and inserted under specific conditions [System Updater]

Fixed a bug that prevented an SD Card from being properly recognized when it was removed and inserted under specific conditions.

Note 130-21: (HTTP) Fixed a bug that caused `Read` functions to timeout after canceling a `ChunkedPost` [System Updater]

Fixed a bug that sometimes caused Read functions to time out after implementing http::Connection::NotifyFinishSendPostData and Connection::Cancel at the same time during ChunkedPost processing . (Specifications call for ResultTimeout to be returned.)

Note 130-22: (HTTP) Added a function to specify whether to enable `KeepAlive` communication [System Updater]

Added the SetKeepAliveAvailability function to specify whether KeepAlive communication is used.

Note 130-23: (NET) Fixed the wireless FATAL error that occurred when specific applications were operating [System Updater]

Fixed a bug that caused wireless FATAL errors at a relatively high frequency when using background communications or local communications in specific applications.

Note 130-24: (OS) Revised `nn::os::SetDeviceMemory` to enable changing the device memory size [System Updater]

Revised the nn::os::SetDeviceMemory function. It can now change the device memory size.
However, the device memory size must be a multiple of 1,048,576 bytes (1 MB) both before and after the change.

Note 130-25: (OS) Fixed a bug that prevented errors from displaying when a card was removed [System Updater]

Fixed a problem that caused an active CTR card application to freeze without displaying the error screen under certain conditions when the card was removed.

Note 130-26: (OS) Added support for debugging download applications [System Updater]

The debugger can now load and debug downloadable applications.

Note 130-27: (OS) Fixed a bug that occasionally caused the system to freeze when it was opened and closed quickly [System Updater]

Fixed a bug that occasionally caused the system to freeze when it was opened and closed quickly.

Note 130-28: (SOCKET) Changed specification for when RST is received [System Updater]

Changed the behavior so data that has already been received can be read even when RST is received at a TCP socket.

Note 130-29: (SOCKET) Fixed a bug that caused data received at a TCP socket to be corrupted [System Updater]

Fixed a bug that caused received data to be corrupted if certain conditions overlapped when resent data was received at a TCP socket.

Note 130-30: (SOCKET) Improved connectivity [System Updater]

Fixed a bug that prevented a successful connection if enough wait time was not allowed when the receiving host's TCP socket specified a window size of 0 (using SYN-ACK).

Note 130-31: (TOOL) Changed the `Config` tool [SDK | System Updater]

Made the following changes to the Config tool.

Language settings can now be configured
When the language settings are changed to invalid, some menu settings are changed instantaneously
Revised the feature to shift gyro acceleration correction values to write a fixed value to the correction value so individual differences in the shift value do not appear
To perform verification using this feature in the future, use the Config tool from CTR-SDK 2.1 and later

For more details, see the Function Reference.

Note 130-32: (TOOL) Changed System Updater specifications [System Updater]

Made changes so whether to reboot after updating can be selected.

Note 130-33: (TOOL) Changed to display the firmware version on the development menu [SDK | System Updater]

Note 130-34: (UDS) Revised the `Result` values when `ConnectNetwork` fails [System Updater]

Fixed a bug where the Result values indicating failure of the ConnectNetwork function differed from the Function Reference.
In order to maintain compatibility, the Result values returned for applications built with CTR-SDK 1.x or earlier are based on the previous definitions.

Note 130-35: (UDS) Fixed a bug that prevented event notification when wireless disabled mode was entered immediately after Initialization [System Updater]

A bug prevented updated connection states from being signaled when wireless communication was disabled immediately after the nn::uds::Initialize function succeeded.
This bug has been fixed.

Note 130-36: (UDS) Fixed a bug that caused the system to enter an invalid state when `Finalize` was executed during communication [System Updater]

Fixed a bug that caused the system to enter an invalid state when the Finalize function was called without calling the DestroyNetwork or DisconnectNetwork function during communication.

Known Issues with System Updater in SDK Version 2.1.0

In some extremely rare cases the screen will stay black after the system is closed and opened. The symptoms are improved by closing and reopening the system at a point where only rendering cannot be restored properly (i.e., sound output, button input, and other features run normally).
This same issue, however, can also occur with applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have a sequence or time when rendering does not recover after awakening from sleep.
In very rare cases, a fatal error occurs when background communication is performed.
The following error values may be displayed at this time.

0xF9606C0F Level: -1 Summary: 11 Module: 27 Desc: 15
0xF9606C11 Level: -1 Summary: 11 Module: 27 Desc: 17

CTR-SDK Version 2.1.0 Sample Demos

(2011/03/25)

Note 129-01: (AC) Deleted calls to `fs::Finalize` in the sample demos [Sample Demos]

Calls to the fs::Finalize function are unnecessary and therefore were deleted from the AC-related sample demos.
This was actually changed in CTR-SDK 2.0 but was accidentally omitted from the change log.

Note 129-02: (APPLET) Organized the code for applet-related processes [Sample Demos]

Reorganized the code in demo1 and demo2 related to applets such as sleep, HOME Button, and POWER Menu.
Also deleted the code that terminated the application autonomously without interpreting the HOME Menu.

Note 129-03: (CAMERA) Fixed a bug in the `Stereo` demo [Sample Demos]

A bug that caused capture to restart was fixed in the camera Stereo demo. The bug occurred when Capture Disable was specified on the lower screen and the system was closed and opened.

Note 129-04: (DLP) Deleted symbols related to DUP [SDK | System Updater|SampleDemos]

Note 129-05: (DLP) Deleted `DummyUpdatePartition` [Sample Demos]

Deleted DummyUpdatePartition from the sample demos because DUP (updates via download play) is no longer necessary for server application development.

Note 129-06: (DLP) Added a function to determine if a device is a child [SDK | Sample Demos]

Note 129-07: (FS) Added sample demos [Sample Demos]

Added sample demos for the FS library.
The demos include sample code to mount ROM archives, save data, and expanded save data, and sample code for subsequent file operations.

Note 129-08: (GR) Revised `lib_grfw` so that the DMPGL display buffer functions are not used [Sample Demos]

Revised the lib_grfw library, which is the framework for GR library demos, so that the DMPGL display buffer object functions (nngxBindDisplaybuffer, nngxDisplaybufferStorage, nngxSwapBuffers, and so forth) are not used and allocation of the display buffer is explicitly performed.
Also, revised the nngxSwapBuffersByAddress function to enable setting of display buffer swap values.

Note 129-09: (OS) Deleted calls to `os::Initialize` from the sample demos [Sample Demos]

Calls to the os::Initialize function are unnecessary and therefore were deleted from the sample demos.

Note 129-10: (SND) Added Applet support for the `SimplePlayer` sample demo [Sample Demos]

The SimplePlayer sample demo was revised to support applets, so HOME Button and Sleep Mode transitions are now possible.

Known Issues with SDK 2.1.0 Sample Demos

　 None.

CTR-SDK Version 2.0.0 Release

(2011/02/24)

Note 128-01: (APPLET) Removed `nn::applet::CTR::GetSleepNotificationState`, `nn::applet::CTR::ClearSleepNotificationState` [SDK]

Until now the investigation of the application's returning a hold for sleep queries was carried out by the nn::applet::CTR::GetSleepNotificationState function, and it was necessary for it to be cleared on the application side by the nn::applet::CTR::ClearSleepNotificationState function, but with this method there were instances, based on timing, where sleep notifications could not be picked up.
The response to the hold was therefore standardized to nn::applet::CTR::IsExpectedToReplySleepQuery.
In addition, the nn::applet::CTR::GetSleepNotificationState and nn::applet::CTR::ClearSleepNotificationState functions have been removed from public release.

Note 128-02: (APPLET) End library applet when exiting application [SDK]

When an application ends, changes have been made such that if a Library Applet is in a preloaded state, it will be terminated.
This process will be performed by the applet::PrepareToCloseApplication function.

Note 128-03: (BOSS) Revised so that CA certificate is automatically set in the NADL task [SDK]

Revisions have been made such that when registering a NADL task, the necessary CA certificate is automatically set in the BOSS library.
As a result, CA certificate setting processes are no longer needed on the application side.

Note 128-04: (CRYPTO) Increased the speed of SHA-256 process functions [SDK]

Increased the speed for implementations related to SHA-256 in the crypto library.

Note 128-05: (DBG) Added macros for debugging log output [SDK]

Added macros (NN_LOGV and NN_PUT) that perform output of debugging logs.

Note 128-06: (DLP) Simplified the state and events of the server at distribution [SDK | System Updater|Sample Demos]

Simplified server states and events during data distribution to simplify application development.
As a result, when developing server applications, the developer no longer needs to be aware of system updates in DLP.
Specifically, the changes are as follows.
The server data distribution states defined for the ServerState enumerated type, shown below, have been gathered together into one state: SERVER_STATE_DISTRIBUTING.

SERVER_STATE_PREPARING_FOR_SYSTEM_DISTRIBUTION
SERVER_STATE_DISTRIBUTING_SYSTEM
SERVER_STATE_WAITING_RECONNECT
SERVER_STATE_PREPARING_FOR_TITLE_DISTRIBUTION
SERVER_STATE_DISTRIBUTING_TITLE

The events notified for server data distribution defined for the EventType enumerated type, shown below, have been gathered together into one event: EVENT_TYPE_SERVER_STATE_DISTRIBUTING.

EVENT_TYPE_SERVER_STATE_PREPARING_FOR_SYSTEM_DISTRIBUTION
EVENT_TYPE_SERVER_STATE_DISTRIBUTING_SYSTEM
EVENT_TYPE_SERVER_STATE_WAITING_RECONNECT
EVENT_TYPE_SERVER_STATE_PREPARING_FOR_TITLE_DISTRIBUTION
EVENT_TYPE_SERVER_STATE_DISTRIBUTING_TITLE

Note 128-07: (DevEnv) Added libraries that will be linked by default [SDK]

Made changes such that the following libraries will be linked by default.

boss
friends
gd
gr
news
ngc
nwm
rdt
tpl
ubl
ulcd

Note 128-08: (DevEnv) Organized the build rules [SDK]

Organized the omake rule definitions, used by builds that use omake.
With the aim of fixing bugs and improving maintenance, we plan to continue making changes in CTR-SDK 2.1.
The old build rules exist in $CTR_SDK/build/omake_deprecated, but we plan to delete them in the next release.

Note 128-09: (DevEnv) Avoided an error when deleting the header [SDK]

In previous versions of the CTR-SDK, when the header was deleted you needed to use --depend to recreate the dependency relationships, but changes have been made so that this is no longer needed.

Note 128-10: (FND) Revised the unit heap `Dump` function [SDK]

Fixed a bug where information on allocated blocks and unallocated blocks was not correctly displayed by the unit heap's Dump function.

Note 128-11: (FONT) Changed the specifications for the `ArchiveFont::InitStreamingConstruct` function [SDK]

Changed the specifications such that an error is returned when an argument is missing or incorrect in the nn::font::ArchiveFont::InitStreamingConstruct function.
Up until now there was only an assert failure check, which led to undefined behavior in release builds.

Note 128-12: (FS) Revised return values for Mount*SaveData [SDK]

The error when the archive name passed to nn::fs::Mount*SaveData was already registered or was longer than 7 characters without including a colon (":") character was nn::fs::ResultOutOfMemory.
These have been respectively revised to return the nn::fs::ResultAlreadyExists and nn::fs::ResultInvalidArgument errors.

Note 128-13: (FS) Revised the `nn::fs::ForceEnableLatencyEmulation` function [SDK]

In addition to the feature to emulate changes in access speed when a non-volatile memory device deteriorates. we also added the feature to emulate the wait for a fixed time when an FS conflict occurs with the BOSS library in the background.

Note 128-14: (FS) Added the `nn::fs::GetExtSaveDataFormatInfo` function [SDK]

Gets the format information for expanded save data. The information that can be obtained is the maximum number of files and directories specified when formatting.

Note 128-15: (FS) Added the `nn::fs::GetSaveDataFormatInfo` function [SDK]

Added the nn::fs::GetSaveDataFormatInfo function to get save data's format information.
The available information is the maximum number of files and directories specified at formatting and the flag for whether automatic redundancy is applied to the entire save data region.

Note 128-16: (FS) Support for release builds for `nn::fs::hio` and the `HOST_IO` build option [SDK]

Made changes such that nn::fs::hio and the HOST_IO build option can be used in release builds.

Note 128-17: (FS) Increased access speed to expanded save data [SDK]

Improved the access speed for expanded save data.
For more details, see the separately released document, CTR Performance Tips.

Note 128-18: (GD) Added GD library [SDK | SampleDemos]

Added the new GD library as a graphics library.
Also added a sample demo that uses the GD library.
See the Function Reference Manual for differences with the existing GL and GR libraries.

Note 128-19: (GR) Added the `RenderState::ShadowMap` class [SDK]

Added the RenderState::ShadowMap class to set the value of the 0x100 register.
The Shadow still remains, but we plan to abolish it in the future.

Note 128-20: (GR) Fixed a bug in `Shader::MakeOutAttrCommand` [SDK]

There was a bug in Shader::MakeOutAttrCommand_ which generates the output attribute commands when a reserved geometry shader (for example, point sprites) is used, including generic attributes.

Note 128-21: (GR) Added constructors for `Vertex` internal classes (`LoadArray`, `InterleaveInfo`, and `IndexStream`) [SDK]

Vertex::LoadArray, which is an internal class for Vertex, was revised from a structure to a class, and constructors were added for the following internal classes: Vertex::LoadArray, Vertex::InterleaveInfo, and Vertex::IndexStream. Changes were also made such that the minimum member variables are now initialized.

Note 128-22: (GR) Added functions to specify the vertex and geometry shaders within the shader binary used and to generate only the commands necessary when switching shaders [SDK]

Added the Shader::SetShaderIndex function to specify the vertex and geometry shader within the used shader binary, and the Shader::MakeShaderCommand function to generate only the commands necessary when switching the used shaders.

Note 128-23: (GR) Added `Vertex::LoadArray::DisableAll` and `Vertex::AttrConstArray::DisableAll` for internal use by `Vertex::DisableAll` to disable vertex attributes and initialize member variables [SDK]

Added the Vertex::LoadArray::DisableAll and Vertex::AttrConstArray::DisableAll methods to disable vertex attributes and initialize member variables, and made changes such that these methods, and not std::memset within the Vertex::DisableAll method which disabled all vertex attributes, will be used.

Note 128-24: (GX) Changed the PICA macro header [SDK]

Made the following changes to the PICA macro headers.

gxMacroTexture.h
Added PICA_DATA_TEXTURE0_SAMPLER_TYPE_FALSE to the enumerated type tag name PicaDataTexture0SamplerType
gxMacroMisc.h
Corrected errors in the Function Reference Manual for PicaDataGasColorLutInput and PicaDataDepthTest2

Note 128-25: (MATH) Added the `One` function to `Vector2`, `Vector3`, and `Vector4` [SDK]

Added the One function that returns a vector, all of which elements are 1.0f, to the following classes: Vector2, Vector3 and Vector4.

Note 128-26: (MATH) Made the constructor explicit [SDK]

To curtail implicit type conversions which go against programmers' intents, constructors with one argument defined for each class in the MATH library were made explicit.

Note 128-27: (OS) Changed `Thread::IsAlive` [SDK]

Made changes such that IsValid is also confirmed within IsAlive.

Note 128-28: (OS) Fixed a bug where the rounding mode was different outside of the main thread [SDK]

Fixed a bug where the rounding method for threads other than the main thread was not rounding to the nearest value for floating point numbers.

Note 128-29: (PTM) Revised so that functions for getting system information do not block [SDK | System Updater]

Since calling the GetAdapterState, GetBatteryLevel, and GetBatteryChargeState functions were blocked, changes were made such that they were not blocked.
As a result of these changes, once there has been an actual change in the remaining battery level, there will be at most a delay of ten seconds until the GetBatteryLevel function can get the changed value.
The values are immediately reflected after the change for the GetAdapterState and GetBatteryChargeState functions.

Note 128-30: (SND) Fixed a bug where noise would occur when using the biquad filter [SDK]

When using the biquad filter, sometimes noise would occur on large amplitude signals. This has been fixed.

Note 128-31: (SND) Added a parameter check for FxReverb [SDK]

Within nn::snd::FxReverb::SetParam, made revisions to check whether each of the variables for m_pFilterSize has a positive value.

Note 128-32: (SND) Added functions to increase the number of buffers at sound's final output stage [SDK]

Added the nn::snd::SetOutputBufferCount function to increase the number of buffers at sound's final output stage.

Note 128-33: (TOOL) Changed so that pressing the B Button in DevMenu now moves to the parent directory [SDK]

Made changes such that pressing the B Button while the SD Tab is displayed will take you to the parent directory.

Note 128-34: (TOOL) TWL system titles are not displayed in DevMenu [SDK]

Made changes such that TWL system titles are not displayed in DevMenu.

Note 128-35: (TOOL) System applications are not displayed in DevMenu [SDK]

Made it such that system applications are not displayed in DevMenu.

Note 128-36: (TOOL) Made small revisions to descriptions in DevMenu [SDK]

Made it such that the columns in the SD Tab can be sorted.
Also added a percentage indicator to the progress bar when importing.

Note 128-37: (TOOL) Fixed a bug where `DlpClient` would abort during a download [SDK]

There was a bug where DlpClient would occasionally abort if communications were interrupted during a download. This has been fixed.

Note 128-38: (TOOL) Improved the method of specifying files to exclude from ROMFS [SDK]

Added specifications to the RSF Reject parameters to allow for more flexible specification of files to exclude from ROMFS.
There is no change in operations when using the existing Reject parameters to specify files.
For details on the new specifications, see the ctr_makerom reference page.

Note 128-39: (TOOL) Added the `CardDevice` item to RSF [SDK]

Added the CardDevice field to RSF.
As a result of this change, applications that have None specified for BackupMemoryType will result in a warning when ctr_makerom is run as long as nothing appropriate is set for the CardDevice field.
For details, see the ctr_makerom reference page.

Note 128-40: (TOOL) Added `SaveDataFiler` [SDK]

Added SaveDataFiler and a reference page for it.
SaveDataFiler is a tool that includes features for viewing, importing and exporting the save data on the CTR Card, and the expanded save data on the SD card.
For more details, refer to the CTR-SDK function reference.

Note 128-41: (TOOL) Updated `makebanner` [SDK]

Made the following modifications specific to makebanner.
・Corrected mistakes in the manual regarding makebanner and makeexbanner
・BannerModelConverter now supports NW4CForBanner
In step with this change, you now need .NET Framework version 3.5 or later to execute BannerModelConverter.

Note 128-42: (TOOL) Revised `makeciaarchive` [SDK]

Fixed a bug that resulted in a larger than usual CFA file size when --romfs-root was specified.

Note 128-43: (UBL) Revised the Function Reference Manual [SDK]

Changed the phrasing of expanded save data to the system's NAND memory.
Also deleted the references to DevMenu from the Description of the Initialize function, as they were not needed.

Note 128-44: (UDS) Added functions to check whether networks found by scan are connectable [SDK]

Added API to confirm during scanning the state specified by a master using the uds::DisallowToConnect function.

Note 128-45: (UDS) Improved error checking when functions are executed in an uninitialized state [SDK]

Revised such that a check for completed initialization is performed for functions that can only be executed between the execution of the uds::Initialize function and the execution of the uds::Finalize function.

Known Issues with SDK 2.0.0 Release

In the GD LightingSample demo, you will see a phenomenon where the area the light is shining on will periodically flash.

CTR-SDK Version 2.0.0 System Updater

(2011/02/24)

Note 127-01: (AC) Changed the return value of the `Connect` function [System Updater]

The result returned when connection was completed indicated whether you could get on the Internet but this has been changed to return a simple success or failure only, and a separate API was added to confirm whether the network connection could get onto the Internet during a connection.

Note 127-02: (AC) Fixed a Wi-Fi station connection bug [System Updater]

Fixed a bug where you could not connect to Wi-Fi stations based on their SSIDs.

Note 127-03: (APPLET) Support for holding down the POWER Button during Sleep Mode [System Updater]

Until now, holding down the POWER Button during Sleep Mode didn't result in the power turning off until the cover opened and the system woke up.
Made changes such that holding down the POWER Button was a main case for the system to wake up, and that the power would turn off without a need to open the cover.

Note 127-04: (APPLET) Fixed a bug where `SleepQueryCallback` would not be called even if the system was opened while writing to media [System Updater]

There was a bug where, because SleepQueryCallback was not called even if the cover was opened while writing to media, screen and sound recovery would not occur. This has been fixed such that SleepQueryCallback is called when the cover is opened.

Note 127-05: (APPLET) Fixed a bug where screen capture information would be overwritten during a transition [System Updater]

The capture information held by the system for a System Applet would be overwritten at capture when a Library Applet was launched.
As a result, information on whether a 3D (3D screen) capture occurred becomes invalid, and in some cases different images are displayed on the right and left sides of the upper screen.
This was actually changed in CTR-SDK 0.14.22 but was accidentally omitted from the change log.

Note 127-06: (BOSS) Fixed a bug where the execution result of a task determined to be 304 would result as an error [System Updater]

Fixed a bug where an error would be obtained as the task's execution result when the BOSS proprietary If-Modified-Since check was 304 for an NSD of 200 KB or more.

Note 127-07: (BOSS) Fixed the bug that prevented BOSS storage from UnMounting [System Updater]

Fixed a bug where, if the GetNsDataHeaderInfo function was called for an invalid serial ID, any BOSS storage mounted within that would not be able to be unmounted.

Note 127-08: (BOSS) Fixed a bug where `Suspend` would take a lot of time if there were a large number of files in BOSS storage [System Updater]

Fixed a bug where Suspend would take a lot of time (it would take a lot of time to enter Sleep Mode even after closing the cover) when BOSS storage was full and there was a large number of files.

Note 127-09: (BOSS) Fixed the GetTaskInfo bug [System Updater]

Fixed a bug where you could not correctly get TaskPermission and LAST_MODIFIED_TIME via the GetTaskInfo function.

Note 127-10: (BOSS) Fixed a bug where `NsData::GetHeaderInfo` would not return [System Updater]

Fixed a bug where, if the NsData::GetHeaderInfo function was called at the same time as a data download, in rare instances you would not return from that function.

Note 127-11: (BOSS) Fixed a bug where tasks would end up running after `PauseAllTasks` was executed [System Updater]

Fixed a bug where, after the execution of the PauseAllTasks functions, tasks would end up running with a new infra-network connection as a trigger.

Note 127-12: (BOSS) Fixed a bug where a new application's tasks could not be registered if another application's database became full [System Updater]

Fixed a bug where a new application's tasks could not be registered when another application's database became full and the automatic delete operation that should have been performed on that application's information was not performed.

Note 127-13: (BOSS) Fixed a bug where data could not be downloaded after a task was determined successful when canceling a task [System Updater]

Fixed a bug where, if a task was cancelled at a specific timing, the task would end up being handled as successful, and subsequent data downloads would not work.

Note 127-14: (BOSS) Fixed a bug where data was downloaded to inappropriate BOSS storage [System Updater]

Fixed a bug where, due to an exception error in an application's information database, download data would end up being downloaded to inappropriate BOSS storage.

Note 127-15: (BOSS) Fixed a bug where the same data was downloaded [System Updater]

Fixed a bug where an error in task execution resulted in the clearing of LastModifiedTime, such that the same data would end up being downloaded again the next time.

Note 127-16: (BOSS) Revised symptoms where task execution results would result in errors in environments where the signal strength was poor [System Updater]

There were cases where executed tasks would result in an error due to poor signal strength and tasks would not re-execute until the next execution time, but this has been revised such that in these cases the result will be retry, and the task will re-execute in a shorter time.

Note 127-17: (CAMERA) Fixed a bug where internal state inconsistencies would result during Applet transitions [System Updater]

There were bugs where the camera LED would either remain lit or else not light up at all because the camera state would not correctly be returned when performing Applet transitions (transitioning to the HOME Menu when pressing the HOME Button, for example) or when rapidly opening and closing the cover.

Note 127-18: (CAMERA) Fixed an issue where the camera image was shifted up and down [System Updater]

When opening and closing the cover and when transitioning to the HOME Menu, there were cases where a buffer error that should have occurred did not occur, and as a result there was the possibility that the camera image would shift up and down. This has been fixed.

Note 127-19: (CAMERA) Fixed a bug where the `Activate` function would always return `IsSleeping` when the system was rapidly opened and closed [System Updater]

Fixed a bug where, when the cover is rapidly opened and closed, the Activate function would always continue to return IsSleeping in the interval it took to close and open the cover once.

Note 127-20: (CAMERA) Fixed a bug where the cameras would lose synchronization when the system was rapidly opened and closed [System Updater]

Fixed a bug where the cameras would not synchronize even when calling the SynchronizeVsyncTiming function as part of the application's waking up process, because the waking up process was not executed when the cover was opened and closed rapidly.

Note 127-21: (DLP) Fixed a bug that resulted in a halt if the language code was set to `INVALID_LANGUAGE` [System Updater]

Fixed a bug that resulted in a halt on the CTR if Server::Initialize was called when the market was set to either Europe or the US and the language code was set to INVALID_LANGUAGE.

Note 127-22: (DLP) Simplified the state and events of the server at distribution [SDK | System Updater|Sample Demos]

SERVER_STATE_PREPARING_FOR_SYSTEM_DISTRIBUTION
SERVER_STATE_DISTRIBUTING_SYSTEM
SERVER_STATE_WAITING_RECONNECT
SERVER_STATE_PREPARING_FOR_TITLE_DISTRIBUTION
SERVER_STATE_DISTRIBUTING_TITLE

The events notified for server data distribution defined for the EventType enumerated type, shown below, have been gathered together into one event: EVENT_TYPE_SERVER_STATE_DISTRIBUTING.

EVENT_TYPE_SERVER_STATE_PREPARING_FOR_SYSTEM_DISTRIBUTION
EVENT_TYPE_SERVER_STATE_DISTRIBUTING_SYSTEM
EVENT_TYPE_SERVER_STATE_WAITING_RECONNECT
EVENT_TYPE_SERVER_STATE_PREPARING_FOR_TITLE_DISTRIBUTION
EVENT_TYPE_SERVER_STATE_DISTRIBUTING_TITLE

Note 127-23: (DevEnv) Fixed a bug where you could not return to the HOME Menu from the card removal error screen [System Updater]

Fixed a bug where a screen is displayed to instruct you to return to the HOME Menu if a card is removed while card-based software is running, you sometimes cannot return to the HOME Menu by pressing the HOME Button at this screen (the upper and lower screens will remain black).

Note 127-24: (FRIENDS) Fixed a bug where it would take a lot of time to get automatically online after disconnecting from an access point [System Updater]

Fixed a bug where it would take a lot of time to get automatically online again when reconnecting in a short period after disconnecting from an access point.

Note 127-25: (FRIENDS) Fixed a bug where you could not automatically get online when immediately reconnecting after disconnecting from an access point [System Updater]

Fixed a bug where you could not automatically get online, no matter how long you waited, when immediately reconnecting after disconnecting from an access point you were connected to.

Note 127-26: (FRIENDS) Fixed a bug where you could not automatically get online [System Updater]

Fixed a bug where you could not automatically get online with the Friend Presence feature after waking from the Sleep Mode, based on timing.

Note 127-27: (FS) Improved ROM access speed [System Updater]

Improved the ROM access speed.
For more details, see the separately released document, CTR Performance Tips.

Note 127-28: (FS) Fixed a bug where expanded save data was not correctly mounted after hot-swapping an SD Card [System Updater]

Fixed a bug where, after hot-swapping an SD card and mounting expanded save data, even though the nn::fs::MountExtSaveData function returned nn::ResultSuccess, the process was insufficient, and attempts to access files, etc., within the archive after that would return the nn::fs::ResultArchiveInvalidated error.
This bug was registered in BOSS and elsewhere, and could occur when mounting expanded save data with the possibility of being accessed at the same time by other processes.

Note 127-29: (FS) Fixed a bug where the files were renamed with the name "." or ".." in save data or expanded save data [System Updater]

Fixed a bug where files with the name "." or ".." in save data or expanded save data would be renamed.

Note 127-30: (FS) Fixed a bug where files in save data or expanded save data would be renamed to a higher level directory [System Updater]

Fixed a bug where if you attempted to rename save data and expanded save data to a higher-level directory, everything under that directory was deleted.

Note 127-31: (FS) Improved save data access speed [System Updater]

Improved the save data access speed.
For more details on the improvements, see the separately released document, CTR Performance Tips.

Note 127-32: (FS) Guaranteed the values when creating save data files [System Updater]

When creating save data files with the nn::fs::TryCreateFile function, made changes such that we guarantee the first 512 bytes of the file (or all data of the file for smaller sized files) are filled with zeroes.

Note 127-33: (FS) Fixed a bug where a directory would become a file when interrupting the directory creation or renaming process [System Updater]

If you removed an SD memory card while creating or renaming a directory, the entry for what should have been a directory will end being one for a file, based on the timing of the removal. This has been fixed.

Note 127-34: (FS) Fixed a bug where the expanded save data root directory would be deleted or renamed [System Updater]

Fixed a bug where you could delete or rename the expanded save data's root directory.

Note 127-35: (FS) Guaranteed the values when creating expanded save data files [System Updater]

When creating expanded save data files with the nn::fs::TryCreateFile function, made changes such that we guarantee the first 512 bytes of the file (or all data of the file for smaller sized files) are filled with zeroes.

Note 127-36: (GX) Fixed a bug where `nngxIsStereoVisionAllowed` returns `true` when generating `hid::CTR::GyroscopeReader` [System Updater]

When generating hid::CTR::GyroscopeReader, nngxIsStereoVisionAllowed returned true even when the 3D depth slider was all the way down. This has been fixed.

Note 127-37: (GX) Fixed a bug where the screen would freeze black when executing `nngxFinalize` [System Updater]

Fixed a bug where the nngxFinalize call's timing would sometimes overlap that of VSync and in rare cases result in a system freeze.

Note 127-38: (HTTP) Fixed a bug resulting from `Cancel` directly after starting communication [System Updater]

Fixed a bug where, when Cancel was performed immediately after starting communication, other functions would not return a response for that communication.

Note 127-39: (MIC) Revised the `nn::mic::SetAmp` and `nn::mic::SetLowPassFilter` functions [System Updater]

There was a bug where sound processes were blocked for long periods of time when executing the nn::mic::SetAmp function (with a false argument) or when executing the nn::mic::SetLowPassFilter function (regardless of argument).
As a result, there would be losses of sound or short instances of noise heard. This has been fixed.

Note 127-40: (MIDI) Revised the UIC-MIDI driver [System Updater]

Revised the specifications such that at the same time the UIC-MIDI features are being used, a backup device can be accessed.

Note 127-41: (NDM) Fixed a bug where the autonomous operations of background communications would remain halted when in Wi-Fi disabled mode [System Updater]

Fixed a bug where background communication ceased to run autonomously if Wi-Fi was disabled at the same time as uds::Initialize, ac::Connect, ac::ConnectAsync, or dlp::Client::Initialize was called, even if Wi-Fi was subsequently enabled.

Note 127-42: (NDM) Fixed a bug where BOSS would not enter autonomous operations when the system was closed but the system was not in Sleep Mode [System Updater]

Fixed a bug where if Sleep Mode was rejected when the system is closed, BOSS ceased to run autonomously until the system either entered Sleep Mode or was opened.

Note 127-43: (OS) Fixed a bug where the debugger would hang when a forced break occurred during `event` execution [System Updater]

Fixed a bug where the debugger would hang when a forced break was applied for an application while an event was executing.

Note 127-44: (OS) Fixed a bug where the card removal error was displayed twice [System Updater]

Fixed a bug where, if the game card was removed using a specific procedure, the error screen would be displayed again after disappearing once after pressing the HOME Button when the card removal error display first appeared.

Note 127-45: (OS) Revised the display of debugger registers during hardware breaks and exceptions [System Updater]

Fixed a bug where there was an error in the displayed value of debugger registers during hardware breaks and exceptions.

Note 127-46: (OS) Fixed a bug that caused the debugger to hang up when the battery dropped to 0% [System Updater]

Fixed a bug where the debugger would hang when the battery reached 0%.

Note 127-47: (OS) Improved break point processing [System Updater]

Improved the execution time of debugger breakpoints.
To reflect this change you need to use debugger software from the 2010/12/22 version or later of PARTNER-CTR.

Note 127-48: (PL) Fixed a bug where the number of steps was not correctly recorded if recorded for more than seven consecutive days in compatibility mode [System Updater]

Fixed a bug where some or all of the steps recorded during compatibility mode would disappear when recording steps and using compatibility mode for seven or more days in a row.
Seven days worth of steps will be recorded from the start of compatibility mode.

Note 127-49: (PL) Fixed a bug in the pedometer history when repeatedly changing the time [System Updater]

Fixed a bug where the number of steps from before the time was changed would remain, for an interval in which there was no walking, when repeatedly changing the time.
With this fix, the bug where a number of steps from before the time was changed would remain, but would suddenly become zero, or some would remain, was also resolved.

Note 127-50: (PL) Fixed a bug where step count could not be saved for a maximum of one day if pedometer was left unused for more than eight days without increasing the step count [System Updater]

Fixed a bug where, regardless of whether the system had been turned on, if you left it alone for eight days without increasing the step count you would be unable to save up to one day's step count afterward.

Note 127-51: (PTM) Revised so that functions for getting system information do not block [SDK | System Updater]

Note 127-52: (SOCKET) Fixed a bug where `INFTIM` could not be used to specify a timeout for `Poll` [System Updater]

Fixed a bug where a fatal error would result when setting INFTIM for the timeout while continuing to specify the non-blocked mode's socket descriptor for Poll.

Note 127-53: (SOCKET) Fixed a bug where name resolution would always fail when setting a DNS server with a specific address [System Updater]

Fixed a bug where name resolution always failed when the DNS server address, either distributed by DHCP or set manually, was between x.x.x.224 and x.x.x.239.

Note 127-54: (TOOL) Changed System Updater specifications [System Updater]

Made the following changes to System Updater:

Changed to provide a System Updater for each region.
As part of this change, removed RegionSelector.
Made changes such that CIA files included in the HomeMenu package can be imported.
Changed menus to make Test Menu (for development) and HOME Menu selectable.
These can also be changed using the Config tool after applying System Updater.
Made changes such that the Config tool can be imported.
Made changes such that system initialization will not occur.

Note 127-55: (UDS) Fixed a bug where the `ResultInvalidNode` error would not be returned even when specifying a node ID not found by the `GetNodeInformation` function [System Updater]

Fixed a bug where the ResultInvalidNode error would not be returned even when specifying a node ID that does not exist in the GetNodeInformation function.

Note 127-56: (UDS) Fixed a bug where UDS functions would be unable to complete when you transitioned to wireless disabled mode or when you suddenly entered Sleep Mode during UDS communications [System Updater]

During UDS communication, particularly while executing a process to transition a state with the CreateNetwork function, etc., and when transitioning to wireless disabled mode or entering Sleep Mode, a deadlock would occur within the system, and any subsequently executed functions might not complete. This has been fixed.

Note 127-57: (UDS) Fixed a bug affecting the connectivity for the last device, when the number of connected devices is equal to maximum number of connections specified by the master.[System Updater]

When the same number of devices that the master has specified as the maximum number for connections has connected, the last device, which should be allowed to successfully connect, is determined to fail to connect. This has been fixed.

Note 127-58: (UDS) Fixed a bug where UDS processes would no longer work when you transitioned to wireless disabled mode at a specific time [System Updater]

Fixed a bug where the ConnectNetwork function would no longer complete when transitioning to wireless disabled mode at some point in the timing when a client was attempting to connect to the network.

Note 127-59: (UDS) Fixed a bug where Client/Spectator disconnection could not be performed correctly when signal status was poor [System Updater]

Fixed a bug where clients would not correctly handle disconnection when signal quality was extremely poor and there was a large volume of communication data.

Known Issues with System Updater in SDK Version 2.0.0

Once REPLY_LATER has been returned to a SleepQuery issued because the system was closed (or for some other reason), if a card is removed before REPLY_ACCEPT or REPLY_REJECT is returned the system will no longer be able to enter Sleep Mode.
In some extremely rare cases the screen will stay black after the system is closed and opened. Only rendering cannot be restored properly: sound output, button input, and other features run normally. Closing and opening the system again resolves this issue. This same issue can also be caused by applications, depending on how they are implemented. If this happens with your application, make sure that your application's implementation does not have any possible sequence or timing in which rendering might not recover after awakening from sleep.
The following bugs have been found with the file system.

If the MountSdmc or MountExtSaveData functions have not succeeded and the GetSdmcSize function is called, an error (NotFound) is returned.
If a file is accessed as a directory or vice versa, an unexpected Result (DESCRIPTION_FAT_BROKEN_ENTRY or DESCRIPTION_INVALID_PATH_FORMAT) is sometimes returned.
Even though you can create a directory with "..." in its name on an SDMC archive, an error (OperationDenied) is returned when you attempt to delete it.

If a card's save data is in an invalid format, you should be able to run nn::fs::FormatSaveData to put the save data into a normal state, but in some rare cases the invalid format is not cleared up even if FormatSaveData itself returns ResultSuccess.
When you format the save data of a card that has been intentionally tampered with, the data is sometimes not formatted correctly even if the return value indicates success. In this case, Mount will fail and return BadFormat or MediaAccessError immediately after Format or after several files have been created.
In very rare cases, a fatal error occurs during infrastructure or background communication. The following error values are displayed at this time.

0xF9606C0F Level: -1 Summary: 11 Module: 27 Desc: 15
0xF9606C11 Level: -1 Summary: 11 Module: 27 Desc: 17
0xF9606C04 Level: -1 Summary: 11 Module: 27 Desc: 4

On very rare occasions a fatal error occurs while carrying out local communication (UDS or DLP).

0xF9606C10 Level: -1 Summary: 11 Module: 27 Desc: 16

CTR-SDK Version 2.0.0 SampleDemos

(2011/02/24)

Note 126-01: (BOSS) Removed CA certificate setting code [Sample Demos]

Since the necessary CA certificate is now automatically set in the BOSS library when registering NADL tasks, the unnecessary CA settings code has been removed from the sample demo.

Note 126-02: (CEC) Added StreetPass sample demo. [Sample Demos]

Added the cec_demo2 sample demo that supports screen display.

Note 126-03: (DLP) Simplified the state and events of the server at distribution [SDK | System Updater|Sample Demos]

SERVER_STATE_PREPARING_FOR_SYSTEM_DISTRIBUTION
SERVER_STATE_DISTRIBUTING_SYSTEM
SERVER_STATE_WAITING_RECONNECT
SERVER_STATE_PREPARING_FOR_TITLE_DISTRIBUTION
SERVER_STATE_DISTRIBUTING_TITLE

The events notified for server data distribution defined for the EventType enumerated type, shown below, have been gathered together into one event: EVENT_TYPE_SERVER_STATE_DISTRIBUTING.

EVENT_TYPE_SERVER_STATE_PREPARING_FOR_SYSTEM_DISTRIBUTION
EVENT_TYPE_SERVER_STATE_DISTRIBUTING_SYSTEM
EVENT_TYPE_SERVER_STATE_WAITING_RECONNECT
EVENT_TYPE_SERVER_STATE_PREPARING_FOR_TITLE_DISTRIBUTION
EVENT_TYPE_SERVER_STATE_DISTRIBUTING_TITLE

Note 126-04: (GD) Added GD library [SDK | SampleDemos]

Added the new GD library as a graphics library.
Also added a sample demo that uses the GD library.
See the Function Reference Manual for differences with the existing GL and GR libraries.

Note 126-05: (GR) Added the `Silhouette` demo that performs silhouette rendering using reserved geometry shaders [Sample Demos]

Added the Silhouette demo that performs silhouette rendering using reserved geometry shaders.

Note 126-06: (GX) Revised so that the unnecessary commands are not generated when the rendering function is the `glDrawElements`in demos that directly generate 3D commands [Sample Demos]

Since the 0x253[0:0] register is initialized to 0x0 during nngxInitialize for the demos that directly generate 3D commands (TriangleSimpleCmd and FragmentLightingSimpleCmd), changes were made to not generate unnecessary commands that would write 0x0 to register 0x253[0:0] for every frame when the rendering API was glDrawElements.

Note 126-07: (GX) Deleted the definitions of unused constant registers in vertex shaders for the DMPGL sample demos [Sample Demos]

Deleted the definitions of unused constant registers in vertex shaders for the DMPGL sample demos.

Note 126-08: (GX) Added a feature in the demo that edits the parameters of a procedural texture to display a gradation bar for the alpha color [Sample Demos]

In the ProcTexEditor demo that edits that parameters of procedural textures, a change was made to display a gradation bar for the alpha color.
It displays the alpha color lookup table in RGBA shared mode and the Fa lookup table in alpha independent mode.

Known Issues with SDK 2.0.0 Sample Demos

When launching demo1 from the HOME Menu, and accessing save data using the A + X Buttons, if you then press the HOME Button there is a high probability that the demo will freeze.
In the DLP SimpleServer server, a DUP cannot be run because an update archive cannot be attached.

CTR-SDK Version 1.1.0 Release

(2011/02/15)

Note 125-01: (CAMERA) Revised the `SetReceiving` function reference [SDK]

The reference for how to use handles with SetReceiving was revised.

Note 125-02: (CFG) Added a function for verifying PIN numbers for Parental Controls [SDK]

The CheckParentalControlPinCode function was added for verifying Parental Controls PIN codes.
Plans call for removing the GetParentalControlPinCode function used to get the PIN code.
Be sure to use the CheckParentalControlPinCode function to verify PIN codes.

Note 125-03: (DLP) Changed the specifications of the `FakeClient::StartScan` function [SDK | Sample Demos]

Because old specifications of the FakeClient::StartScan function allowed developers to specify a wireless channel when they should not have been able to, a FakeClient::StartScan function that does not allow wireless channel specification has been prepared.
This function automatically scans all scannable channels.
Use this function from now on.
Also, use of the FakeClient::GetChannels functions, used to get scannable channels, is prohibited.

Although the FakeClient::GetChannels function and the FakeClient::StartScan function that allows wireless channel specification can be accessed to maintain mutual compatibility, please use the new functions so that unnecessary problems do not arise.

Note 125-04: (DLP) Fixed a bug where user names were not NULL-terminated [SDK]

A bug was fixed where node user name strings did not terminate with NULL when the string was 10 characters long.
With this change, the NodeInfo user names obtained by the following functions now always include NULL at the end (11th character).

nn::dlp::FakeClient::GetServerInfo
nn::dlp::FakeClient::GetNodeInfo

Note 125-05: (DevEnv) Addressed symptoms treated as specifications [SDK]

A document about symptoms that are handled as specifications under CTR-SDK 1.x has been added to $CTR_SDK/documents/ReleaseNotes/knownIssues.html.

Note 125-06: (FND) Added an interface for returning the number of blocks already allocated for the unit heap [SDK]

An interface for returning the number of blocks already allocated for the unit heap has been added.

Note 125-07: (FS) Revised the error return value when mounting an archive of the same name [SDK]

There was a bug where nn::fs::ResultOutOfMemory was being returned as an error when mounting a new archive using a name already registered.
This has been revised so that nn::fs::ResultAlreadyExists is returned.

Note 125-08: (GX) Revised the default settings of `dmp_FragmentLightSource[i].position` and `dmp_FragmentLightSource[i].spotDirection` [SDK]

A bug has been fixed where the default settings for the reserved uniforms, dmp_FragmentLightSource[i].position and dmp_FragmentLightSource[i].spotDirection, did not match the specification manual.

Note 125-09: (GX) Added `NN_GX_CMDLIST_GAS_UPDATE` to the `nngxSetCmdlistParameteri` function [SDK]

pname has been newly added for making settings related to updating additive blend results for rendering gas density information.

Note 125-10: (GX) Added the new `nngxSwapBuffersByAddress` function [SDK]

The nngxSwapBuffersByAddress function has been added. This function can specify the address of a buffer to be directly swapped without using a display buffer object.

Note 125-11: (NGC) Revised default settings related to the stencil test [SDK]

When using the glStencilFunc function for stencil tests, the default setting for the func argument differed in terms of the state on the driver and the value in the GPU register.
Although the state was GL_ALWAYS as per specifications, the register value was GL_NEVER. If glStencilFunc(GL_ALWAYS, 0, ~0) was specified, this would lead to a bug where operation would advance using GL_NEVER without updating the value of the register to match the actual state.
This bug has been fixed.

Note 125-12: (GX) Updated documentation [SDK]

The following graphics-related documentation was updated.

$CTR_SDK/documents/DMPGL20/DMPGL20_specification.pdf

Deleted DMP_subdivision0.obj because it was determined there was a risk it could lead to illegal operations
Added a description of additive blend D2 when rendering gas density information
Added a supplement about periodicity in random number generation for procedural textures

$CTR_SDK/documents/DMPGL20/DMPGL20_programming_guide.pdf

Changed the default value of dmp_LightEnv.lutEnabledRefl from GL_TRUE to GL_FALSE
Added a description of a problem where block-shaped noise is being rendered for certain pixels
Added a supplement about noise settings for procedural textures
Added the fact that rendering is not being performed correctly if the viewport size is larger than 1023x1016
Added the fact that the early depth test is not being performed correctly if a viewport offset is used

$CTR_SDK/documents/DMPGL20/DMPGL20_system_API_specification.pdf

Added a detailed description of the value of NN_GX_CMDLIST_HW_STATE
Added a supplement about the registers, 0x0af[11:8], 0x126[25:24], 0x1c0, and 0x229[1:0]
Deleted unnecessary register settings listed for the reserved geometry shader
Revised the description of clearing the frame buffer cache
Revised the description of color buffer address alignment
Added NN_GX_CMDLIST_GAS_UPDATE to the nngxSetCmdlistParameteri function
Added the new nngxSwapBuffersByAddress function
Deleted the RGBA8 format from the display buffer

$CTR_SDK/documents/DMPGL20/VertexShaderReferenceManual.pdf

Added a description of the performance check feature of the shader linker
Revised swizzling by the mad instruction and changed the upper limit on the number of masking patterns from 64 to 32
Fixed typos related to instructions that cannot be consecutively called
Added information about shader implementations that can lead to undefined operations
Added a supplemental description of swizzling

Note 125-13: (GX) Updated the reserved geometry shader [SDK]

The reserved geometry shader has been updated as follows.

Registers have been relocated and unnecessary constant register definitions inside each shader have been deleted
Deleted subdivision0.obj because there was a risk it would lead to undefined operations

Note 125-14: (GX) Fixed a bug with the `glShaderBinary` function that would occur under specific conditions [SDK]

A bug was fixed where an error was being illegally generated by the glShaderBinary function when a generic attribute was being specified for an attribute later than the seventh in the definition of a #pragma output_map statement in the shader assembler.

Note 125-15: (SND) Fixed a bug related to assert failures [SDK]

A bug was fixed where the Sender::Cancel function would sometimes result in an assert failure if signal reception was poor, regardless of whether the build was a Release build.
Also, code was revised so that the ASSERT macro of the RDT library is disabled for Release builds.

Note 125-16: (SND) Fixed a bug when using `AllocVoice` where NULL would return and then the sound thread would stop [SDK]

A bug was fixed that would occur when the AllocVoice function was called from a thread other than a sound thread where NULL would be returned and then the sound thread would stop.
This bug did not occur in CTR-SDK 0.14.23 or earlier.

Note 125-17: (SND) Fixed bug causing noise when using linear interpolation [SDK]

A bug found in CTR-SDK 1.0 was fixed where noise would arise in segments without any sound if INTERPOLATION_TYPE_LINEAR was specified using the nn::snd::Voice::SetInterpolationType function.
This bug did not occur in CTR-SDK 0.14.23 or earlier.

Note 125-18: (TOOL) Added a feature for selecting menus to the Config tool [SDK]

A feature has been added so that Config tool can be used to select the menu to be started when power is turned on or when performing debugger reset. Up until this version, this menu could only be selected using MenuSelector.csu.
For details, see the documentation for the Config tool.

Note 125-19: (TOOL) Added a binary for save data that generates `nn::fs::ResultVerificationFailed` [SDK]

A binary so the nn::fs::MountSaveData function returns nn::fs::ResultVerificationFailed has been added to $CTR_SDK/tools/TargetTools/CTR-TS.
Be sure to write it to a backup device using PARTNER-CTR and use it.

Note 125-20: (TOOL) Added a feature for outputting a warning when conditions leading to hardware bugs are violated when using the shader [SDK]

The shader assembler and shader linker now output a warning if an attempt is made to use a shader implementation described in Section 2.10, "Shader Implementations that Cause Invalid Operations" added to $CTR_SDK/documents/DMPGL20/VertexShaderReferenceManual.pdf under this version.

Note 125-21: (TOOL) Added a feature for measuring shader performance [SDK]

A feature has been added for detecting instructions that cause stalling and a feature that estimates the number of clocks required per vertex when executing from a shader assembler implementation specified as an option to ctr_VertexShaderLinker32.exe.
These features are disabled by default.
For details, see $CTR_SDK/documents/DMPGL20/VertexShaderReferenceManual.pdf.

Note 125-22: (UDS) Fixed a bug where user names obtained using the `NetworkDescriptionReader::GetNodeInformationList` function were not being NULL-terminated [SDK]

A bug was fixed where strings were not being NULL-terminated if the string for a user name was 10 characters long when getting a user name using the NetworkDescriptionReader::GetNodeInformationList function if scanning was performed after turning the power on and UDS communication had not yet been carried out even once, including by another application.

Known Issues with SDK 1.1.0 Release

The GetNodeInformation function in the UDS library gives a Result value indicating success even when a nonexistent node ID is specified.

CTR-SDK Version 1.1.0 SampleDemos

(2011/02/15)

Note 124-01: (CAMERA) Revised the Stereo demos [Sample Demos]

Added support for the POWER Button and HOME Menu button to the camera/Stereo demo.
Also, the following bugs associated with this demo were fixed.

Could not perform retry for the nn::camera::Activate function if the system was opened and closed repeatedly
If the system was closed while configuring the cameras, two buffers for images would be allocated upon retry

Note 124-02: (DLP) Changed the specifications of the `FakeClient::StartScan` function [SDK | Sample Demos]

Note 124-03: (DLP) Fixed a bug where the `SimpleServer` would not run except in the JP market [Sample Demos]

A bug was fixed where the SimpleServer would not operate outside the JP market.
The cause was due to the fact that the JP market had been set for the Child_0 icon. The icon was changed to support all markets.

Note 124-04: (DevEnv) Switched electronic manuals for samples [Sample Demos]

The data format used in the electronic manual included with demo1 was old and could not be displayed, so it was replaced with the most recent data.

Note 124-05: (DevEnv) Added sample demo references [Sample Demos]

A description of sample demos was added under $SampleDemos/documents.

Note 124-06: (FS) Fixed a bug with the `FragmentLightSimpleCmd` sample demo [Sample Demos]

The bug was due to using a function not of the Try type for save data in demo1 code, so this bug was fixed by determining results using a function of the Try type.

Note 124-07: (GX) Added a `ProjectionTexture` sample [Sample Demos]

The sample, gx/DMPGL/ProjectionTexture, for procedural textures was newly added.

Note 124-08: (GX) Revised how functions used with `demo1` save data are used [Sample Demos]

A bug was fixed where register 0x149 was not being set correctly in relation to the value of position w for Light 0.
This bug was addressed in the CTR-SDK 1.1 graphics driver update.

Note 124-09: (HID) Added a gyro demo [Sample Demos]

The sample demo gyroscope, for using the gyro, was added.

Note 124-10: (TPL) Fixed a bug with the `ReadTexturePackage2` demo [Sample Demos]

A bug was fixed where incorrect mipmap settings were being used by the ReadTexturePackage2 demo.

Known Issues with SDK 1.1.0 Sample Demos

　 None.

CTR-SDK Version 1.0.0 Release

(2011/01/25)

Note 123-01: (CEC) Removed version of `nn::cec::MessageBox::CreateMessageBox` function that does not specify icon data [SDK]

Removed the version of the nn::cec::MessageBox::CreateMessageBox function that does not specify icon data, since there is no need to use it.

Note 123-02: (CEC) Revised the Function Reference Manual [SDK]

Added the following to the CEC library function reference.

MessageBox Class Error Handling
Precautions when Implementing MessageBox::OpenMessageBox

Also removed descriptions of the MessageBoxInfoReader class, since this class is not supported.
Also see the Programming Manual for details on how to implement.

Note 123-03: (FS) Fixed bug causing verification failure on loading from ROM [SDK]

Fixed a bug that would rarely cause verification to fail when reading from a file or directory opened from an archive mounted using MountRom, with the function returning a Result of type nn::fs::ResultVerificationFailed.

Note 123-04: (GR) Changed `Shader::SetDrawMode` function to support `GL_TRIANGLE_STRIP` and `GL_TRIANGLE_FAN` when in triangle render mode [SDK]

Changed the gr::Shader class to support GL_TRIANGLE_STRIP and GL_TRIANGLE_FAN when in triangle render mode.

Note 123-05: (GR) Changed member function that generates commands to a `const` member function for the `gr::Viewport`, `gr::Scissor`, and `gr::Shadow` classes [SDK]

Changed the gr::Viewport::MakeCommand, gr::Scissor::MakeCommand, and gr::Shadow::MakeCommand member functions to be const member functions.

Note 123-06: (GR) Changed all `private` member variables to `protected` member variables [SDK]

Changed all private member variables in the library to protected member variables.

Note 123-07: (GR) Fixed bug in command to set register `0x85` to the physical address of a cube map's +X plane [SDK]

Fixed a bug in the Texture::Unit0::MakeCommand function when generating the command to set register 0x85 to the physical address of a cube map's +X plane.

Note 123-08: (GR) Added function and class methods to disable graphics settings [SDK]

Added the gr::MakeDisableAllCommand function and other class methods to generate 3D commands to disable graphics settings (such as shader modes, vertex attributes, fog, fragment lighting, textures, and render states).

Note 123-09: (GR) Added methods to generate fragment lighting light source color information commands and geometric information commands [SDK]

Added the FragmentLight::Source::MakeColorCommand function to generate fragment lighting light source color information commands, and the FragmentLight::Source::MakeGeometryCommand function to generate geometric information commands.

Note 123-10: (GX) Fixed a bug in fragment light shadow attenuation commands [SDK]

Fixed a bug in the FragmentLight::MakeLightEnvCommand function causing miscalculation of the value in the register corresponding to the dmp_FragmentLightSource[i].shadowed uniform.

Note 123-11: (GR) Added methods to configure lookup table commands when input values are `[0.0, 1.0]` or `[-1.0, 1.0]` [SDK]

Added the LookUpTable::SetAbsTable method to configure lookup table commands when the input value is [0.0, 1.0], and the LookUpTable::SetNotAbsTable for when the input value is [-1.0, 1.0].
The LookUpTable::SetTable function is kept for compatibility purposes, and this now calls the LookUpTable::SetAbsTable function internally by default.

Note 123-12: (GR) Added default argument to configure the last difference value of a lookup table [SDK]

Added a default argument for the last difference value of a lookup table to the LookUpTable::SetTable, Fog::SetTable, ProcedureTexture::SetNoiseLookUpTable, ProcedureTexture::SetRgbMapLookUpTable, and ProcedureTexture::SetAlphaMapLookUpTable functions.
This default value is 0.0f.

Note 123-13: (GX) Added a shader assembler performance check feature [SDK]

Added a shader assembler performance check feature to the ctr_VertexShaderLinker32.exe shader linker.
See VertexShaderReferenceManual.pdf for details.

Note 123-14: (MIC) Changed `Finalize` function to call `ResetBuffer` internally [SDK]

Revised Finalize function to avoid possible unstable operation should the application forget to call ResetBuffer before calling Finalize.

Note 123-15: (NGC) Revised the Function Reference Manual [SDK]

Added the following (previously missing) content to the Function Reference Manual.

Working memory region alignment
No need to split threads
Maximum number of threads that can be checked at once

Note 123-16: (SND) Fixed bug where the `Voice` object obtained from `AllocVoice` was sometimes not initialized [SDK]

Fixed a bug where the Voice object obtained from AllocVoice was sometimes not initialized.

Note 123-17: (SND) Fixed bug causing infinite loop when calling `applet::ProcessPowerButton` or `applet::ProcessHomeButton` when there is no sound thread [SDK]

Fixed a bug causing an infinite loop when calling the applet::ProcessPowerButton or applet::ProcessHomeButton functions after calling the nn::snd::Initialize function but before creating a sound thread.

Note 123-18: (SND) Fixed bug causing noise when using linear interpolation [SDK]

Fixed a bug causing noise when using INTERPOLATION_TYPE_LINEAR as the interpolation method of a Voice object.

Note 123-19: (TOOL) Changed `CecLotcheckTool` [SDK]

Made the following changes to CecLotcheckTool.

Added address reset feature to allow StreetPass again with the same peer
Changed CecLotcheckTool to allow it to be imported into NAND
Changed build type to Development

Note 123-20: (TOOL) Removed `FriendTool` [SDK]

Removed FriendTool for registering friends from the CTR-SDK package.
Use the friend roster included in the HomeMenuPackage for establishing friendships.

Note 123-21: (UDS) Split out the `CreateNetwork` and `Scan` functions [SDK]

In previous versions, it was possible for developers to input argument values specifying channels and other communication parameters that should not be used. To fix this issue, the automatically selectable parameters were removed, and the new CreateNetwork and Scan functions are now provided as the standard interfaces for these features.
The previous function that specifies the channels to use as the default argument value is still available for purposes of backwards compatibility, but Nintendo recommends using and supporting the new function to avoid any possible problems.

Note 123-22: (UDS) Emphasized the size check of the passphrase specified in the `CreateNetwork` and `ConnectNetwork` functions [SDK]

Previous versions contained a bug in the CreateNetwork and ConnectNetwork functions, allowing the size of the passphrase to be specified as 0. This was changed to check for passphrases of at least 8 and at most 255 characters.

Note 123-23: (UDS) Changed `SendTo` argument check to an assert [SDK]

Since any problems with data being sent will be discovered during normal debugging, there is little need for operational checks in production versions, so these checks were changed to NN_ASSERT checks.

Note 123-24: (UDS) Changed data size specifiable in the `SetApplicationDataToBeacon` function [SDK]

The SetApplicationDataToBeacon function reference stated that the argument data size had to be less than NET_DESC_APPDATA_SIZE_MAX. However, the function specification states that data can be NET_DESC_APPDATA_SIZE_MAX in size, so the reference content was changed to reflect this, and the library checks were changed similarly.

Note 123-25: (UDS) Added constants for receive buffer size specified in the `uds::Attach` function [SDK]

Added the ATTACH_BUFFER_SIZE_DEFAULT and ATTACH_BUFFER_SIZE_MIN constants for the size of the receive buffer specified in the uds::Attach function.

Note 123-26: (UDS) Changed `Result` value for the `uds::DestroyEndpoint` function [SDK]

The DestroyEndpoint function previously allowed for the specification of an invalid EndpointDescriptor, such that calling DestroyEndpoint on an Endpoint that had already been destroyed would return an error value of ResultNotInitialized. This was changed to return the more appropriate ResultNotAuthorized error instead.

Known Issues with SDK 1.0.0 Release

The GetNodeInformation function in the UDS library gives a Result value indicating success even when a nonexistent node ID is specified.

CTR-SDK Version 1.0.0 SampleDemos

(2011/01/25)

Note 122-01: (APPLET) Revised to reflect `demo1-sys` [Sample Demos]

Revised demo1 to show implementation of sample demo demo1-sys, which supports startup, quitting, and sleep processing, with the keyboard applet removed.

Note 122-02: (GR) Added the `GraphicsDrawing` demo for rendering 2D shapes [Sample Demos]

Added the GraphicsDrawing demo for rendering 2D geometric shapes using the GR library.

Note 122-03: (GR) Added the `ParticleSystem` demo for rendering the results of particle systems using the reserved geometry shader [Sample Demos]

Added the ParticleSystem demo for rendering the results of particle systems using the reserved geometry shader with the GR library.

Note 122-04: (GX) Fixed bug causing strange rotations of the model when running for extended periods [Sample Demos]

There was a bug in gx/DMPGL/TriangleSimple and demo1 where calculation precision issues would cause strange behavior in the rotation of polygons on the upper screen when running the demos for extended periods.
Revised to reset the floating-point value specified as the rotation angle at set intervals.

Known Issues with SDK 1.0.0 Sample Demos

　 None.

CONFIDENTIAL