Arduino 2.0.0 Not recognising Arduino Nano (Elegoo)

Just installed IDE 2.0.0 and have tried my existing boards, my Arduino Nano is not recognised for some reason, Any help would be much appreciated.

Sketch uses 924 bytes (3%) of program storage space. Maximum is 30720 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 2039 bytes for local variables. Maximum is 2048 bytes.
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x00

The only port available is:

/dev/cu.usbserial-2340 Serial Port (USB)

Hi @SierraGolfMike. Please try the following procedure to check whether this is the port of your Arduino board:

  1. Unplug your Arduino board from the computer.
  2. Select Tools > Port from the Arduino IDE menus.
  3. Note the ports, if any, listed in the menu.
  4. Close the Tools menu.
    The ports list is only updated when the Tools menu is re-opened, so this step is essential.
  5. Plug your Arduino board into the computer.
  6. Select Tools > Port from the Arduino IDE menus. - The new port listed in the menu is the one for your Arduino board.

If you don't see any change in the contents of the menu with the board plugged compared to when it is unplugged, we will need to investigate why it was not detected.

Possibly unrelated, but I have reported before that IDE 2.0 does not always show available serial ports in its "Select other board and port" dialogue although they show in Tools/Port from the menu

image

In passing, can you please clarify the purpose of the "Show all ports" checkbox ?

Try a different USB cable. Some are power/charge only I think.

The port was showing up, I thought it might be a CH340 board so installed the latest driver but still getting the sam error????

See my reply!

Are you saying that the /dev/cu.usbserial-2340 port was not present in the menu after you disconnected the board and was present after you connected the board?

If the board disappears from the IDE when you disconnect it, the board is recognised. In that case, try the different options under tools -> processor on the IDE.

Yes, the port only showed up when I plugged the board in.

Under tools > processor, I changed to ATmega328P (old boot loader) and it worked.

Thank you for your help it is very much appreciated.

Hi @UKHeliBob. I apologize for the slow response. It is a good question. You have probably noticed that some ports under the Tools > Port menu in the Arduino IDE are identified as a specific board:

image

This is possible because the port has some unique identifying property (e.g., the VID/PID pair of a USB CDC serial port) that is associated with the board definition in boards.txt of its platform.

In other cases, the port does not have any unique identifying properties. For example, the FTDI FT232RL chip on the Arduino Nano board uses the manufacturer-supplied VID/PID pair, which is also used by many other devices, so a port created by an FT232R can not be reliably identified as a Nano board.

The "☐ Show all ports" checkbox in the "Select Other Board and Port" dialog controls whether or not the ports which have not been identified as an Arduino board are shown in the "PORTS" list in that dialog (and only in that dialog).

If you try it out, it might seem that this feature is broken because the unidentified ports are still shown. The reason for this is because the ports of the "Serial" and "Network" protocols were exempted from the filter:

Since those are the most common types of ports discoverable by the IDE for most users, that code causes the checkbox to have no effect.

The Arduino "pluggable discovery" system allows any boards platform developer to use any arbitrary communication channel between the board and the Arduino development software. So this does mean that, even though Arduino has only created discoveries for the "Serial" and "Network" protocols, there are other protocols. At the moment, I am only aware of two other protocols:

(I think we will see more protocols emerge over time as the community starts to take advantage of the new "pluggable discovery" system)

The "Teensy" boards platform has identification properties configured for its boards, so "Teensy" protocol ports will always be shown in this dialog. However, the "Raspberry Pi Pico" boards platform does not have identification properties for the "uf2conv" protocol port (this is the RP2040 when in "USB Mass Storage Mode"). So these ports are the only ones I know of that will actually appear and disappear:

Somewhat related to this discussion is an issue tracking the need to avoid giving special treatment to arbitrary port protocols (as is done for "Serial" and "Network" in this case):

Thanks for the explanation, but is there any good reason why you would not want to see all ports ?

Because it is common for additional ports that have nothing to do with Arduino boards to be discovered. Those can be confusing to new users. If the user will be exclusively working with identifiable boards (which are becoming increasingly prevalent since most modern microcontrollers have the native USB capability that makes it easy to produce a unique VID/PID pair), showing other ports is pointless.

The most common ones historically have been the COM1 built-in serial port often found on Windows machines or the similar /dev/cu.Bluetooth-Incoming-Port port on macOS machines. But there are some additional strange things like this with the other protocols. For example, my USBasp is discovered in the IDE as a "Teensy" protocol port (unidentified, so the visibility is dependent on the state of that checkbox). I haven't experienced it personally, but I believe some consumer network devices like WiFi connected printers can also appear as "Network" protocol ports.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.