Troubleshooting

Device Detection

1. If your device is not being detected by the operating system. (You can check this by going to , type Device Manager and open it. Then expand the section (if one exists) Ports (COM & LPT). If no devices show or the section does not exist, this means the device was not detected.`
2. First make sure that you've got the correct drivers installed. See this for details on installing the correct driver.
3. Verify that your USB cable supports data transfer. If you've got a mobile phone or another device you know that works with your PC, try to connect it with the same cable. If that device is not working either, chances are that the cable you're using is either damaged or does not support data transfer.
4. If the USB cable works with other devices, try using a shorter USB cable.

Device Connection

If your device is being detected by your OS but N2D22 can't connect to it, you can try:

1. Make sure that you've got the correct drivers installed. See this for details on installing the correct driver. You might need to restart your PC for changes to take effect.
2. You can try updating Python and/or esptool.py in case there are bugfixes that resolve the problem.
3. Examine the log file produced by N2D22, if you see something like raise SerialException("could not open port {!r}: {!r}".format(self.portstr, ctypes.WinError()))serial.serialutil.SerialException: could not open port 'COM5': PermissionError(13, 'Access is denied.', None, 5) then you may need to disable your anti-virus software and try again. If that doesn't work you can try running N2D22 with the --fixdriver flag to mitigate this error or try Portable mode.
4. Start N2D22 in Portable mode (--portable).

General Troubleshooting

• N2D22 has introduced better debugging functionality to help rectify problems. You can use the functionality to resolve your own problems. When the program crashes (or terminates normally) a file called dump-xxx.log will be generated in the same directory as N2D22.exe. You can examine the file yourself to find potential error messages or warnings generated by N2D22, esptool or the .NET Framework.
• You can use the --debug flag to see live debugging messages. See additional options for details on the command-line parameters available.

Remarks

• If you are unable to resolve a problem, you can get external support by raising an issue with the log file attached.
• If you successfully resolved a problem, we recommend you raise-close and issue or submit a Wiki PR describing the details of your problem and the solution to help others.