6.1 When ADEV Initialization Fails

Factors such as the ADEV status can cause initialization to fail.

  • Initialization fails.
  • The ADEV console you want to initialize does not appear (or it no longer appears) on the ADEV connection list in InitializeAdevWin.

If this happens, verify the following.

You are using InitializeAdev.exe (or InitializeAdevWin.exe).

We recommend directly calling InitializeAdev.exe or InitializeAdevWin.exe.

The following files also call these functions directly.

  • %NINTENDO_SDK_ROOT\InitializeAdev.bat
  • %NINTENDO_SDK_ROOT\Tools\CommandLineTools\DevKitSetup.bat
  • %NINTENDO_SDK_ROOT\Tools\CommandLineTools\DevKitSetup.ps1

Verifying the Specified Parameters

If you are using the InitializeAdev.exe command-line tool, verify that the specified parameters match. (The serial number works with or without a check digit.)

Verifying Whether the Version Has Restrictions

Firmware version 13.0.0-3.0 and later can be used for ADEV. If you try to initialize the system with an earlier version of the firmware, it fails during the process.

Repeating Initialization

Sometimes initializing the ADEV several times results in success. Try to initialize again.

Fully Charging the ADEV Console

Try to perform initialization after fully charging the ADEV console.

To charge the device you must attach the AC adapter. You cannot charge simply by connecting the device to a PC with a USB cable.

Reconnecting the USB Cable and Turning the Power On

Try initializing the ADEV console again after reconnecting the USB cable and turning the power on.

If initialization is particularly unsuccessful, reconnect the USB cable with the following procedure.

  1. Disconnect the USB cable from the ADEV system.
  2. Hold down the POWER Button on the upper left of the ADEV console for approximately 12 seconds to turn the power off.
  3. Reconnect the USB cable to the ADEV console while the power is off.
  4. The ADEV turns on automatically when it is connected. Try initialization again.

If you are using the device connected to a Relay Box-A, try connecting it directly to the PC without using the relay box.

Exiting Target Manager If It Is Running

Exit Target Manager if it is running, and then try to initialize ADEV.

Sometimes Target Manager stays in the system tray, so also check there.

Verifying the ADEV Console Is Recognized by Device Manager

Verify that the ADEV is recognized as a USB device in Device Manager.
For more information, see 6 Initializing the ADEV > ADEV Drivers.

Manually Activating Safe Mode

Sometimes initialization is successful after activating safe mode.

Info

Safe mode is a mode that runs with minimum features.

Use safe mode in the following situations.

  • The console is not operating properly and must be restored.
  • ADEV initialization fails.
  • The ADEV is not detected when it is initialized.
  • The power is on but the system menu does not appear.

Safe mode can be activated with user operations.

After safe mode is activated, you may not be able to start in normal mode until the EDEV is initialized, so we recommend using safe mode only when you must restore or initialize.

Procedures for Entering Safe Mode

There are two ways to enter safe mode.

(Method 1) With Joy-Con (R) Attached

We recommend this method.

  1. Hold down the POWER Button (for approximately 12 seconds) and turn off the ADEV console with the USB cable connected. (The system restarts after the button is held down for 20 seconds, so do not go much longer than 12 seconds.)
  2. Attach the Joy-Con (R) to the ADEV console. (Do not attach the Joy-Con (L).)
  3. Press the POWER Button while holding down the volume down button.
  4. To check whether safe mode is running, see Method for Verifying Whether the System Has Entered Safe Mode. If the system did not enter safe mode correctly, particularly when the menu screen is displayed, restart the process from step 1.

(Method 2) Without Joy-Con Attached

  1. Hold down the POWER Button (for approximately 12 seconds) and turn off the ADEV console with the USB cable connected. (The system restarts after the button is held down for 20 seconds, so do not go much longer than 12 seconds.)
  2. Press the buttons on the upper left of the console in the following order.
    1. Press the POWER Button while holding down the volume down button.
    2. While holding down the POWER Button, release the volume down button and press the volume up button.
    3. While holding down the volume up button, release the POWER Button.
    4. Release the volume up button.
  3. To check whether safe mode is running, see Method for Verifying Whether the System Has Entered Safe Mode. If the system did not enter safe mode correctly, particularly when the menu screen is displayed, restart the process from step 1.
Info

Could Not Enter Safe Mode

For cases where the system enters the standard startup sequence and displays the menu despite attempting to enter safe mode, sometimes adjusting the intervals between button operations will fix the issue. (This is because some operations may not be detected if the intervals between button operations is too fast.)

As a guide, try using an interval of 0.6 seconds. This interval is equivalent to 4 beat intervals at 100 beats per minute (BPM). We recommend searching for a video with "BPM=100" that you can use as a guide.

Verifying Whether the System Has Entered Safe Mode

Use the following procedure to verify whether the system has entered safe mode.

  1. In InitializeAdevWin.exe, click Re-Scan to display the systems that are in safe mode in the list of connected systems.
  2. NX DevKit Safe Mode is displayed for four seconds on the ADEV screen immediately after startup. (Nothing is displayed afterward that point.)

Using USB 2.0 When USB 3.0 Connection Fails

ADEV setup may fail depending on the compatibility with the USB 3.0 controller.
Try the following.

  • Update the USB 3.0 controller driver to the latest version.
  • Update the USB 3.0 controller firmware to the latest version. (Sometimes this firmware is not publicly available.)
  • Run setup by connecting the device to a USB 2.0 port.

Setup has been confirmed to fail when using a PC with the following USB 3.0 controller.

  • Renesas Electronics USB 3.0 Host Controller

Contacting Support

If initialization is unsuccessful after attempting these procedures, contact Nintendo support.

When contacting support, the process will be smoother if you include the following information.

  • Serial number of the ADEV unit
  • SDK/FW version
  • Initialization log
    • For InitializeAdevWin, copy the log that appears in the log window to a text file and send in the text file.
    • For InitializeAdev, execute a log with the --verbose option added and save it to a file.
  • All of the data under the %USERPROFILE%\AppData\LocalLow\Nintendo directory for the PC (and user) that encountered this symptom.
    • Information such as the time of initialization is stored in this folder.


 


CONFIDENTIAL