I downloaded and installed the latest stable release of Arduino IDE 2.0 as of 22nd October 2022. The OS is Win10 LTSC version. I installed most boards and when I plug in an UNO rev3 or Mega, I see no ports available when selecting the board. In device manager the board is not recognized as having a driver.
However, during installation, several driver installation popups came up wbich I accepted.
Does anyone know why the boards arent recognized or no USB devices seem to work? Thank you.
What are you using that version of Windows 10?
Please provide a detailed description of what you mean by that. Include the full and exact text of any error or warning messages shown in the Device Manager.
By this, do you mean that you are experiencing problems with USB devices other than Arduino boards?
Please tell us which USB to serial adapter chip your Arduino board has. This is a black chip near the USB socket.
The chip will usually be identified by writing on the top. This might say something like "Atmel MEGA16U2" or "WCH CH340G" or "SILABS CP2102" or "FTDI FT232RL".
Examples:
Microchip ATmega16U2
WCH CH340
FTDI FT232R
If it isn't clear, alternatively you can provide the link to where you bought the board from and we'll see if we can determine the chip from the product listing.
@ptillisch are you familiar with Win10 LTSC, it's missing many components so that it only needs updates twice a year. It's entire possible that it's missing critical facilities.
Please read the considerations section of the following article: LTSC: What is it, and when should it be used? - Microsoft Community Hub
Perhaps not "familiar", but I know what LTSC is.
Possibly it is missing the necessary facilities, but I think it is worth seeing whether we can get @terrorhertz up and running before jumping to that conclusion. It might just as well be the usual problem that they have cheapo Chinese derivative boards with the CH340 chip not supported by the drivers the IDE installs.
1 Like
I will answer more fully when Im home. In the meantime, the reason I'm using Win10 LTSC is because I have an offline workstation that I built only for electromagnetic simulation, the new software requires Win 10 and I wanted a cutdown OS with less bloat and since the computer is never connected to the internet I can have the anti virus and other security features turned off. So after initial setup the computer never goes online.
I was using Win7 for years with no problem, but now the Arduino IDE 2.0.x requires Win10 or later so on a new install of the Win10 LTSC I also Installed the new IDE and all boards I'm likely to ever use.
I would prefer to use my Raspberry Pi 4 to run the IDE but I dont think its available last time I checked.
I can confirm that all of my other USB devices such as Western Digital external backup drives, USB sticks and my android phone all work perfectly with the Win 10 LTSC OS.
I've been using a range of Arduino boards for several years, some original/genuine UNO, Mega and Due boards, as well as the cheaply bought variations. I tried 3 different types with the same problem. The most recent have the Atmel USB chip whereas the older have the FTDI interface chip.
In device manager it appears that there are no drivers but will have to report the actual message later this evening when home.
After trying again with the Due and Mega, both genuine Arduino boards, I saw that they were recognized as an additional com port and I could select it in the IDE. They have the ATMEGA16U2.
However the UNO also has this chip by the USB port and when I plug that in, in device manager under Universal Serial Bus, it comes up as "Unknown USB device(device description request failed)".
As for any old FTDI boards like seeeduimo 2.12 with the ATMEGA168 microcontroller and FTDI FT232RL, the port was recognized only when I updated the drivers found in the drivers directory as part of the IDE install. My FTDI cable was also recognized. I did not attempt to program the Seeduino as I forgot which arduino its compatible with.
So all seems good aoart from the genuine Arduino Uno with the 16U2 not being seen as a com port.
Another observation, when changing from 16U2 boards to FTDI type, the comport was seen in the device manager but not in the IDE unless I closed and restarted the IDE. This this a bug? Thank you.
@terrorhertz Just for confirmation. You did have the PC connected to the internet when you initially ran the IDE?
Initially no, I installed it offline but then realised it wouldnt work and had to be connected for its first startup. So I did that, and while online I installed all the boards I wanted. Then it went offline when I tried to use it.
The fact the others with the ATmega16U2 worked but this one does not makes me think it is something specific to the board itself, rather than the PC configuration.
Make sure the USB cable is fully plugged into the computer and the Arduino board.
Check whether the problem still occurs when using a different USB cable.
If you have any external circuitry/wiring/modules/shields/etc. connected to the board, check whether the problem still occurs after removing them.
Make sure the board is not sitting on a conductive surface and that there is no conductive debris on the top or bottom of the board.
I didn't find anything a page for the 2.12, but I found it listed under the wiki page for the 2.2, so I would assume the general usage is the same:
Based on this information, I recommend this:
- Select Tools > Board > Arduino Duemilanove or Diecimila from the Arduino IDE menus.
- Select Tools > Processor > ATmega168 from the Arduino IDE menus.
Yes it sounds like it.
Please provide a detailed description of what you mean by "changing from 16U2 boards to FTDI type".
Where in the IDE were you looking at the ports (it is listed in several different places in Arduino IDE 2.x)?
I tried the two seeduino and Uno rev3 with the same cables in my old Win 7 laptop with IDE 1.6 13 and they were recognized and easily programmed with the Blink example. This confirm the boards are fine.
Sill having problems with them on Win 10 with IDE 2.0, no change from yesterday's effort.
Im using both the menu bar "Tools" to select board and port when its available and when its not showing I can see un device manager that its not being recognised. The same applies to the search box at the top of the IDE. If the port is availability it shows fine, but not for the Uno or old Seeduino. The seeduino are compatible with the boards you mention in the previous post. Anyway, I confirm the boards are functioning using the old IDE.
I also noticed the Adruino Micro works with the old IDE but not 2.0.
I will just have to use the old IDE if I use the Seeduino or Uno, and IDE 2.0 for whatever will work with it.
All drivers seem to be installed correctly as far as I can see when I tried to reinstall, they all had a green tick next to them.
Nice work on the investigation! This shows that the problem is something at the hardware or operating system level; not at the Arduino IDE level.
What do you mean by "works"? Do you mean the same problem of the port not showing?
When you say "old IDE", is that really what you mean, or do you mean the combination of Arduino IDE 1.6.13 and your old Win 7 laptop vs the combination of Arduino IDE 2.0.0 and Windows 10 LTSC on your offline workstation?
The Mini with FTDI cable is recognised and can be programmed with IDE 1.6 13 on Win7, but not on IDE 2.0 on Win 10.
I don't know what the issues are but at least I can use the Mega or Due which I plan to use for my next projects. For any problematic boards I can revert to the last of the "old" IDE.
Can you or anyone confirm (or deny 
)that the installation of 2.0 includes the automatic installation of drivers? I found that I had to install them with the driver files that came with the IDE 2.0 download. Only then would it recognize the Mega and Due boards.
Drivers are now installed only as part of the boards platform installation, not as part of the IDE installation.
This is actually how it has been for many years even with Arduino IDE 1.x with most platforms. The exception was for the boards that came preinstalled as part of the Arduino IDE installation ("Arduino AVR Boards" platform). The Arduino IDE 1.x installation included drivers for those boards.
From a user perspective, the Arduino IDE installation still does include the installation of those drivers. The reason is that the Arduino IDE automatically installs the "Arduino AVR Boards" platform if not already installed the first time it is ran after installation. When it installs that boards platform, the drivers are also installed. So this is mostly a difference from the perspective of the Arduino IDE developers.
Thanks for the explanations. Its much appreciated. I look forward to working with Arduino again.
You are welcome. I'm glad if I was able to be of assistance.
Regards,
Per
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.