Symptoms Treated as Specifications

Because a SystemUpdater update is required to fix the following known issues, they are treated as part of specifications under CTR-SDK 1.x.
  1. [AC] The AC library's Connect function sometimes returns ResultSuccess when it succeeds; this differs from the information in the Function Reference Manual.
  2. [APPLET] Once REPLY_LATER has been returned, if a card is removed before REPLY_ACCEPT or REPLY_REJECT is returned, the system is no longer be able to enter Sleep Mode.
  3. [APPLET] After the HOME Button is pressed while the card removal error is displayed, the error screen is sometimes displayed again.
  4. [APPLET] In some extremely rare cases the screen will remain black after the system is closed and opened.
  5. [BOSS] When a BOSS task is executed, the original specifications call for it to return DONE as a result when the HTTP status code is 304; instead, it sometimes returns ERROR.
  6. [CAMERA] The camera's Activate state sometimes does not return when there is an Applet transition at the same time the system is opened or closed while the cameras are being used.
  7. [CAMERA] If the system is opened and closed rapidly while the cameras are being used, Activate continues to return the IsSleeping error.
  8. [CAMERA] If you open and close the system rapidly or perform an Applet transition while the cameras are being used, the upper half of the captured image may be displayed on the lower screen and the lower half of the captured image may be displayed on the upper screen.
  9. [CAMERA] The V-Sync for the left and right cameras will on rare instances fail to match even if the camera::SynchronizeVsyncTiming function is called upon recovery from Sleep Mode.
  10. [DLP] Execution stops and the upper and lower screens turn red if the nn::dlp::Server::Initialize function is called while INVALID_LANGUAGE is set by RegionSelector and the market is USA or EUR.
  11. [FS] File system-related bugs
  12. [FS] An error results when an SD card has been mounted by an application if it is removed and re-inserted and then an attempt is made to mount it again without it having ever been unmounted by the application.
  13. [FS] If save data on the card is in an invalid format, in rare cases that invalid status will not be cleared even if FormatSaveData returns success.
  14. [FS] When you format the save data on a card that was intentionally spoofed, the data is sometimes not formatted correctly even if the return value indicates success.
  15. [FS] Sometimes extra data (expanded save data) cannot be deleted.
  16. [NWM] In very rare cases, a fatal error occurs during infrastructure or background communication.
  17. [NDM] If WiFi disabled status is duplicated due to certain functions calls, background communication ceases to run autonomously.
  18. [NDM] If Sleep Mode is rejected when the system is closed, BOSS ceases to run autonomously until the system either enters Sleep Mode or is opened.
  19. [OS] If you set the battery to 0% with the PARTNER-CTR debugger software, the debugger hangs.
  20. [OS] Sometimes after pulling out an SD card you cannot return to the home menu and the upper and lower screens remain black even if you press the HOME Button.
  21. [PTM] If the system has been in DS-compatible mode for seven days or more, the number of steps counted since entering DS-compatible mode will be lost.
  22. [PTM] If the system is closed and opened while writing to media, the screens and sound will not recover for a while.
  23. [PTM] After eight days pass without the step count increasing, at most you cannot save the step count for one day.
  24. [SND] Sometimes the sound drops out and you can hear noise when executing the SetAmp or SetLowPassFilter functions.
  25. [SOCKET] When the address of the DNS server lies between x.x.x.224 and x.x.x.239, the resolution of all names fails.
  26. [UDS] Execution hangs on rare occasions if the system enters Sleep Mode or wireless is turned off while a UDS connection is starting or communication is in progress.
  27. [UDS] On very rare occasions a fatal error occurs while carrying out local communication.

Symptom

The AC library's Connect function sometimes returns ResultSuccess when it succeeds; this differs from the information in the Function Reference Manual.

Frequency of Occurrence

This occurs infrequently when Connect succeeds.

Affects

All applications that use the AC library.

Comments

Because there is no need to use different conditional branches that distinguish between ResultLanConnected and ResultWanConnected, which should have originally been returned when Connect succeeds, handle IsSuccess instead.

Support Period

CTR-SDK 2.0


Symptom

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.

Frequency of Occurrence

This grows more frequent the longer it takes for REPLY_ACCEPT or REPLY_REJECT to be returned after REPLY_LATER.

Affects

All applications that return REPLY_LATER to a SleepQuery.

Comments

Closing the corresponding application resolves this problem.

Support Period

Scheduled for support in CTR-SDK 2.0


Symptom

If the HOME Button is pressed while the card removal error is displayed, the error screen is sometimes displayed again. This symptom has been confirmed to occur with the following procedure.

  1. Use the HOME Button to suspend an application.
  2. Close the system to put it into Sleep Mode.
  3. Remove a card while the system is in Sleep Mode.
  4. Open the system; the card removal error screen is displayed.

Frequency of Occurrence

Although it is timing-dependent, this occurs with high frequency when the procedure above is followed.

Affects

All card-based software.

Comments

Even if the error screen is displayed again, if you just wait control will return to the HOME Menu without a problem.

Support Period

Scheduled for support in CTR-SDK 2.0


Symptom

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.

Frequency of Occurrence

Extremely rare.

Affects

All applications.

Comments

Because this same symptom can also be caused by an application's implementation, if you encounter this always check the following.

  • Is there a sequence or timing during which rendering is not restored by awake following Sleep Mode?

Support Period

TBD


Symptom

When a BOSS task is executed, the original specifications call for it to return DONE as a result when the HTTP status code is 304 (NOT MODIFIED); instead, it sometimes returns ERROR.

Frequency of Occurrence

Although an accurate frequency is unknown because this depends on server behavior, it has been confirmed to occur in one of eight units running over 10 hours.

Affects

All applications that handle task execution results.

Comments

To handle HTTP status code 304, access the status code instead of the task's execution results.

Support Period

CTR-SDK 2.0


Symptom

The camera's Activate state sometimes does not return when there is an Applet transition (such as a HOME Button press) at the same time as the system is opened or closed while the cameras are being used.

Frequency of Occurrence

Low, but we have yet to investigate a concrete probability.

Affects

All applications that use the cameras.

Comments

Opening and closing the system once resolves this issue.

Support Period

Scheduled for support in CTR-SDK 2.0


Symptom

If the system is opened and closed rapidly while the cameras are being used, Activate continues to return the IsSleeping error.

Frequency of Occurrence

The precise frequency at which this occurs is unknown because it is only caused by the act of opening and closing the system rapidly. Because this is by nature infrequent and is resolved when the system is opened and closed, it is probably the case that recovery often occurs without the user noticing.

Affects

All applications that use the cameras.

Comments

Opening and closing the system once resolves this issue.

Support Period

Scheduled for support in CTR-SDK 2.0


Symptom

If you open and close the system rapidly or perform an applet transition while the cameras are being used, the upper half of the captured image may be displayed on the lower screen and the lower half of the captured image may be displayed on the upper screen.

Frequency of Occurrence

The probability of reproducing this decreases as you use the cameras at higher frame rates. Just for reference, we have heard reports of this occurring in applications that run at 15 fps but not from applications that run at 30 fps. The reproducibility also increases the sooner the application calls SetReceiving after the previous transfer has completed.

Affects

All applications that use the cameras.

Comments

This problem can be resolved by closing the system again and then opening it after it has entered Sleep Mode. If you stop and restart capture operations from the callback function registered by applet::SetAwakeCallback to be invoked upon recovery from Sleep Mode (when the system is opened), no problems occur. Specifically, this is the following sequence. StopCapture → Wait for the capture operation to stop → ClearBuffer → SetReceiving → StartCapture

Support Period

CTR-SDK 2.0


Symptom

The V-Sync for the left and right cameras will on rare instances fail to match even if the camera::SynchronizeVsyncTiming function is called upon recovery from Sleep Mode.

Frequency of Occurrence

This occurs only rarely when recovering from sleep.
The problem does not occur if the function is called when the cameras are started or during a HOME Menu transition.

Affects

All applications that use the outer cameras.

Comments

The symptoms appear to be resolved by inserting a HOME Menu transition.

Support Period

CTR-SDK 2.0


Symptom

Execution stops and the upper and lower screens turn red if the nn::dlp::Server::Initialize function is called while INVALID_LANGUAGE is set by RegionSelector and the market is USA or EUR.

Frequency of Occurrence

Always.

Affects

All North American and European applications that use the Download Play feature.

Comments

Although guideline item 13.1 Handling Undefined Languages requires you to confirm that your program behaves properly even with INVALID_LANGUAGE, because of this bug you don't need to be able to confirm behavior for Download Play. However, this does not mean that you do not need to handle INVALID_LANGUAGE. Have your application run Download Play properly even for INVALID_LANGUAGE. Furthermore, the system will never return a language code corresponding to INVALID_LANGUAGE at launch, so this will not occur on the final retail product.

Support Period

CTR-SDK 2.0


Symptom

The following types of bugs have been found with the current 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.
  • When a new file is created in the same physical region as a deleted file, even if you have not written anything to it you can sometimes read the content of the deleted file.
  • You can call DeleteDirectory and RenameDirectory on the root directory for expanded save data.
  • You can rename save data and expanded save data to "." or "..". You cannot open or delete files that have been renamed in this way.
  • 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 you attempt to rename save data and expanded save data to a higher-level directory, everything under that directory is deleted.

Frequency of Occurrence

Depends on the symptom.

Affects

All applications.

Support Period

Scheduled for support in CTR-SDK 2.0


Symptom

If you run the following operations in order, a file system error (such as DESCRIPTION_ARCHIVE_INVALIDATED) is returned when an SD Card is used.

  1. Mount and use an SD Card from an application. (This is how expanded save data and SpotPass are used)
  2. Remove and insert the SD Card.
  3. Mount and use the SD Card again from the application without unmounting it.

Frequency of Occurrence

Always.

Affects

All applications that use expanded save data and SpotPass.

Comments

An error stops being returned if you restart the application or unmount the SD Card after it has been removed and inserted. (In other words, the SD Card can then be used normally.)

Support Period

CTR-SDK 2.0


Symptom

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.

Frequency of Occurrence

Because this becomes less likely as you continue to use save data following a format and also as the number of bytes written increases, it does not have a large effect on normal usage. However, it can be relatively easier for this to occur in format-destroy cycles for debugging.

Affects

All card-based software.

Comments

You do not need any additional implementation other than one that handles errors for invalid formats. If the aforementioned symptom occurs, several of the functions executed after FormatSaveData will return errors associated with nn::fs::ResultBadFormat. If you execute FormatSaveData again at this time, save data returns to the normal state. (This means repeating the sequence for handling corrupted save data twice.)

Support Period

Scheduled for support in CTR-SDK 2.0


Symptom

When you format the save data in a card that was intentionally spoofed, 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.

Frequency of Occurrence

The problem only occurs when data is intentionally spoofed. In general, it will never occur if cards are just inserted and removed with the final retail product.

Affects

All card-based software.

Comments

This is restored normally if Format is run when BadFormat or MediaAccessError is returned.

Support Period

Scheduled for support in CTR-SDK 2.0


Symptom

It is sometimes impossible to delete extra data (expanded save data).

Frequency of Occurrence

This always occurs when you follow the procedure below.

  1. Create expanded save data from an application and then create BOSS storage there.
  2. Look at the banner for that application in the HOME Menu without a single downloaded contextual banner in the application's BOSS storage.
  3. Launch System Settings and attempt to delete the application's expanded save data. This will fail.

Affects

All applications that SpotPass.
Specifically, this occurs in applications that create BOSS storage in the expanded save data region.

Comments

Because SpotPass has mounted expanded save data in step 2, System Settings is unable to delete the expanded save data. If you remove and insert an SD Card after step 2, it becomes impossible to mount expanded save data. If you close and then re-open System Settings without looking at the application's banner, you can delete data properly.

Support Period

CTR-SDK 2.0


Symptom

In very rare cases, a fatal error occurs during infrastructure or background communication. The following error values are displayed at this time.

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

Frequency of Occurrence

Extremely rare.

Affects

All applications that use infrastructure or background communication
This symptom may occur when the system performs communication even if the application does not.

Comments

This bug may occur during background communication that uses infrastructure communication or during P2P communication via infrastructure communication.

Support Period

TBD


Symptom

Background communication will cease to run autonomously if Wi-Fi is turned off at the same time as uds::Initialize, ac::Connect, ac::ConnectAsync, or dlp::Client::Initialize is called.

Frequency of Occurrence

Although the timing is severe, this occurs consistently.

Affects

All applications.

Comments

Even if your application encounters this bug, SpotPass will run while infrastructure communication is connected. Power-cycling the system resolves this symptom.

Support Period

CTR-SDK 2.0


Symptom

If Sleep Mode is rejected when the system is closed, SpotPass ceases to run autonomously until the system either enters Sleep Mode or is opened.

Frequency of Occurrence

Always.

Affects

All applications.

Comments

Even if your application encounters this bug, StreetPass will run while infrastructure communication is connected.

Support Period

CTR-SDK 2.0


Symptom

If you set the battery to 0% with the PARTNER-CTR debugger software, the debugger hangs.

Frequency of Occurrence

Always.

Affects

All applications.

Comments

The only way to check shutdown processing is to actually set the battery to 0 using a CTR test unit.

Support Period

CTR-SDK 2.0


Symptom

Although 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).

Frequency of Occurrence

Approximately one in ten times.

Affects

All card-based software.

Support Period

CTR-SDK 2.0


Symptom

After the system has been in DS compatibility mode for a week or longer, the steps counted since the system entered DS compatibility mode disappear in proportion to the amount of time that steps are counted.

Frequency of Occurrence

Always.

Affects

All applications that use the pedometer.

Comments

This does not occur if the system is turned off or control returns to the HOME Menu within a week of entering DS compatibility mode.

Support Period

Scheduled for support in CTR-SDK 2.0


Symptom

If the system is closed while data is being written to a storage media and the system is then re-opened before data has finished being written, neither the screen nor sound will be restored for some time. This delay depends on factors other than data writes to storage media, so you may wait longer than the anticipated write time.

Frequency of Occurrence

Always.

Affects

All card-based software.

Comments

The cause of this problem also prevents the SleepQueryCallback from being invoked if the system is closed while data is being written to storage media. There are a number of functions that write data other than TryWrite, including FormatSaveData, CreateExtSaveData, and operations that rename files and directories.

Support Period

CTR-SDK 2.0


Symptom

Regardless of whether the system has been turned on, if you leave it alone for eight days without increasing the step count, you will be unable to save up to one day's step count afterward.

Frequency of Occurrence

Always.

Affects

All applications that use the pedometer.

Support Period

CTR-SDK 2.0


Symptom

When you run the following functions, sound is sometimes cut off with a noise that sounds like "chi."

  • nn::mic::CTR::SetAmp function (with false specified as an argument)
  • nn::mic::CTR::SetLowPassFilter Function

Frequency of Occurrence

Approximately one in ten times.

Affects

All applications that use the microphone.

Comments

The noise is caused when sound is cut off by the relevant function blocking sound processing for a long time. To work around this problem, run the functions in question when you stop sound.

Support Period

CTR-SDK 2.0


Symptom

Name resolution always fails when the DNS server address, either distributed by DHCP or set manually, is between x.x.x.224 and x.x.x.239. Even connection tests do not succeed at this time.

Frequency of Occurrence

Always.

Affects

All applications that use the network.

Comments

You can work around this problem by manually setting the DNS server address to one that does not cause the problem to occur.

Support Period

CTR-SDK 2.0


Symptom

Execution hangs on rare occasions if the system enters Sleep Mode or wireless is turned off while a UDS connection is starting or communication is in progress.

Frequency of Occurrence

This can be easily reproduced if you try.

Affects

All applications that use UDS communication.

Comments

You can prevent execution from hanging only when the system enters Sleep Mode. To do so, call DestroyNetwork and DisconnectNetwork before the system enters Sleep Mode. Consequently, the same problem occurs when the dlp::Server::OpenSessions and dlp::Server::Finalize functions are called.

Support Period

CTR-SDK 2.0


Symptom

On very rare occasions a fatal error occurs while carrying out local communication (UDS or DLP). 

RSL : 0xF9606C10
      Level  : -1
      Summary: 11
      Module : 27
      Desc   : 15

Frequency of Occurrence

Although this basically occurs only in very rare instances, it appears that the frequency of occurrence depends on how the application is implemented.

Affects

All applications that use local communication.

Support Period

TBD