Symptoms Treated as Specifications

Because a SystemUpdater update is required to fix the following current known issues, they are treated as part of specifications under CTR-SDK 2.x.
  1. [AC] An uninitialized result may be returned when calling the ac::Connect function.
  2. [APPLET] The IsExpectedToCloseApplication does not send a notification even when the battery is set to 0% by the SPI debugger.
  3. [APPLET] Sometimes the LCD does not turn on when recovering from Sleep mode.
  4. [APPLET] Noise occurs when exiting some applications from the HOME Menu.
  5. [APPLET] The system sometimes stops on a black screen if a FATAL error occurs at the point the system is closed.
  6. [APPLET] Sometimes the system stops on the POWER Menu screen if the HOME Button is pressed immediately after going to the POWER Menu from an application that takes time to shut down.
  7. [APPLET] On rare occasions the system stops on a black screen if the system is closed/opened immediately after exiting an application.
  8. [APPLET] The system sometimes goes to a black screen or HOME does not work when recovered if the SD Card is removed during sleep.
  9. [APPLET] A card-removed error does not occur even if card emulation is turned OFF when starting an application by dragging to SPI debugger.
  10. [BOSS] Sometimes the system accesses the X-BOSS-Closed field of the very last task executed when it shouldn't.
  11. [BOSS] Sometimes information indicating immediate background execution status for a task executed immediately in the background is not flushed from NAND memory.
  12. [CAMERA] Sometimes the next startup fails if the system is opened and closed continuously at the same time when starting the camera.
  13. [CAMERA] On rare occasions the camera LED remains lit if the system is opened and closed repeatedly after calling camera::Finalize.
  14. [CEC] The maximum number of messages that can be stored in a box has changed.
  15. [FS] Sometimes DESCRIPTION FAT NOT FOUND is returned if CreateExtSaveData is executed on an SD Card in a certain state.
  16. [FS] Sometimes a FATAL error occurs when the SD Card is removed during ROM access.
  17. [SOCKET] The Send and Recv functions return ECONNRESET if connection is denied.
  18. [SSL] Lock cannot be released if an invalid client certificate is set.

Symptom

An uninitialized Result is sometimes returned if the ac::Connect function is called at the exact instant when the connection with an access point is forcibly disconnected due to poor reception environment.

Frequency of Occurrence

Extremely rare.

Affects

All applications that use the ac::Connect function.

Support Period

CTR-SDK 3.0


Symptom

When the battery is set to 0% with an application being executed by the debugger, power goes off before shutdown notification (issued by executing the IsExpectedToCloseApplication function) can reach that application.

Frequency of Occurrence

Always.

Affects

Application being executed by the debugger.

Support Period

CTR-SDK 3.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.

  • There may be a sequence or exact timing of events involved where rendering is not restored when awaking from Sleep Mode.

Support Period

TBD


Symptom

Noise occurs when exiting some applications from the HOME Menu.

Frequency of Occurrence

Depends on the application

Affects

All applications.

Support Period

TBD


Symptom

The system sometimes stops on a black screen if a FATAL error (including card removal error) occurs at the point the system is closed.

Frequency of Occurrence

Occurs at a high frequency if the time is right.

Affects

All applications.

Support Period

TBD


Symptom

Sometimes the system stops on the POWER Menu screen if the HOME Button is pressed immediately after transitioning to the POWER Menu from an application that takes time to shutdown.

Frequency of Occurrence

The longer an application takes to shut down, the greater the frequency.

Affects

All applications.

Support Period

CTR-SDK 3.0


Symptom

On rare occasions the system stops on a black screen if the system is closed and opened immediately after exiting an application.

Frequency of Occurrence

Extremely rare.

Affects

All applications that call the AssignGpuRight function when cancelling Sleep mode.

Comments

This issue does not arise unless the AssignGpuRight function is called when cancelling Sleep mode.

Support Period

CTR-SDK 3.0


Symptom

The system sometimes goes to a black screen or HOME does not work if the SD Card is removed during sleep.

Frequency of Occurrence

Extremely rare.

Affects

All applications.

Support Period

TBD


Symptom

A card removal error does not occur even if card emulation is turned OFF when starting an application by dragging it into SPI debugger.

Frequency of Occurrence

Always.

Affects

All applications.

Support Period

CTR-SDK 3.0


Symptom

When the immediately preceding task received a service shutdown in the the X-BOSS-Closed field, the current task will be erroneously identified as being in service shutdown status if it cannot establish a connection.

Frequency of Occurrence

Always.

Affects

All applications that use BOSS tasks.

Comments

If this occurs, there is a chance of unintended behavior by the application if the registered application gets the service shutdown using GetProperty and then executes a process based on the obtained value. At present, this problem does not occur in the typical user environment because we have spread the message not to use the service shutdown flag on the operations side.

Support Period

TBD


Symptom

If the power of a CTR system is turned off immediately after immediate background execution of a given task, information indicating that that task is being immediately executed in the background is not flushed from the BOSS database stored in NAND. The next time the CTR system starts, that task will be in the same status as one that executes normally in the background.

Frequency of Occurrence

Always.

Affects

All applications.

Comments

All applications that use immediate background execution of BOSS tasks.

Support Period

TBD


Symptom

If the system is opened and closed continuously at the same time the Activate function is executed on the camera, it will not be processed even though success is returned. Also, if Sleep mode is rejected, and the system is finally closed after repeatedly opening and closing it, the camera can be activated even though the system is closed.

Frequency of Occurrence

Occurs at a high frequency if the time is right. (The probability of the application rejecting Sleep mode increases depending on how many times the system is repeatedly opened and closed.)

Affects

All applications that use the camera.

Comments

Use the following workaround for this problem when using the Activate function to turn the camera ON/OFF.

  1. Turn the camera ON/OFF using the Activate function.
  2. Wait (using a timeout) for the Event object returned by the GetVsyncInterruptEvent function to be signaled. (The timeout to use depends on the frame rate of the camera. If the frame rate is 5 fps, use a timeout of 200 ms.)
  3. When turning the camera ON: Activate succeeds if Event is signaled several times repeatedly before the timeout. When turning the camera OFF: Activate succeeds if there have been several timeouts.

Support Period

TBD


Symptom

On rare occasions, the camera LED remains lit if the system is opened and closed repeatedly after calling camera::Finalize.

Frequency of Occurrence

Rare.

Affects

All applications that use the camera.

Comments

This problem can be resolved by turning off the power or starting the camera again.

Support Period

CTR-SDK 3.0


Symptom

Values for things such as the maximum number of messages that can be received sometimes change if an application is suspended by pressing the HOME Button.

Frequency of Occurrence

Extremely rare.

Affects

All application that use StreetPass.

Comments

Note: Do not allow a malfunction as there is a possibility that more data than the amount set may be received. To restore settings, the box must be deleted and recreated. This problem does not occur if the HOME Menu is not running.

Support Period

TBD


Symptom

On rare occasions, no processing from the CTR aimed at the SD Card can be made if the SD Card is removed while creating expanded save data for the first time on that SD Card. This problem may also occur when creating expanded save data for the first time on an SD Card with very little free space.

Frequency of Occurrence

Extremely rare.

Affects

All applications that use expanded save data.

Comments

Recovery is possible by deleting the directory on the PC in which the problem SD Card is located.

Support Period

CTR-SDK 3.0


Symptom

Sometimes one of the following two FATAL errors occurs when the SD Card is removed during ROM access.

RSL : 0xD9004588
      Level: -5
      Summary:  8
      Module : 17
      Desc   :392

RSL : 0xC8A0F001
      Level: -7
      Summary:  5
      Module : 60
      Desc   :  1

Frequency of Occurrence

Extremely rare.

Affects

All card-based applications.

Support Period

TBD


Symptom

The Send and Recv functions return ECONNRESET if connection is denied using CONNECT.

Frequency of Occurrence

Always.

Affects

Applications directly using the socketAPI.

Support Period

CTR-SDK 3.0


Symptom

Lock cannot be released if an invalid client certificate is set.

Frequency of Occurrence

Always.

Affects

When using an invalid client certificate.

Support Period

CTR-SDK 3.0


CONFIDENTIAL