Tools>Port> "Serial Ports" is greyed out. For example, on my Macbook the only option available (pre-checked) is /dev/cu.Bluetooth-Incoming-Port". In Windows, Tools> "Port" is greyed out, nothing selected or selectable at all.
I have this same result with the UNO and the MEGA2560 R3. I have had similar results in Windows 10, Mac OS 10.12, and Ubuntu, with Arduino 1.8.0 and 1.8.2.
An image in Mac and in Windows is attached.
Any help is appreciated!
Pretty sure I had installed the USB drivers, but I went ahead and uninstalled 1.8.2 from my Windows computer (the only one with USB 2.0), and reinstalled it, with the driver install selected. The IDE seems to know that I connected a Mega 2560, but I get the same grey unclickable port option. Is there another driver that I am not thinking of?
woodard:
The IDE seems to know that I connected a Mega 2560
What makes you think that?
woodard:
Is there another driver that I am not thinking of?
Many clones use the CH340 USB-serial chip. That chip is not supported by the drivers included with the Arduino IDE so you need to download it from the manufacturer's website (though last I checked their driver is not compatible with macOS Sierra and you need to use a modified driver instead). You would need to check the chip next to the USB jack on the boards to see what they have. There are other, less common, chips you may see on some clones that are also not supported by the drivers included with the IDE. My understanding is that the CH340 driver is included on Linux so the fact that it's not working for you on Ubuntu either makes me question if this is the problem but worth checking at least.
"What makes you think that?" -Faulty inductive reasoning on my part:) I switched to an UNO, restarted the IDE and it still thinks that its a Mega. I have an UNO from Creation Crate, and it does indeed have the CH340 USB chip, but installing drivers have didn't help immediately (unless there are steps that I haven't followed correctly). I can't tell which chip on the mega is the USB chip, but the board is from Elegoo, and Atmel is inscribed on other chips on the device, if that helps at all.
But, all of the sudden, after unhooking and re-hooking everything, I now see "COM3" under ports, so I can consider this case closed for the time being!
Thank you very much for your help and insight!
i fixed mine.
downloaded the CH340 USB fix, and changed the port in tools in the sketch program, in my case com 1 to com 3 and it worked.
I am so happy.
I have the same problem - genuine Arduino Uno (ATmega328 / ATmega16U2) is not seen neither under Sierra 10.12.3 on MacBook 13"/2012 Non-Retina nor under Windows 7 on the same MacBook and 2 other Windows computers. The cable is tested and works well with other USB devices. On MacBook any USB device plugged to any of 2 on-board USB ports is hooked at USB 3.0 Hub but the Bluetooth device seen in Arduino IDE is hooked at USB 2.0 Hub. Unfortunately I cannot figure out how to connect Arduino to USB 2.0 hub.
Arduino Uno has been taken from sealed electrostatic protection pack - no damages, no stresses. On plugging the board under Sierra OS a green LED works but on pressing RESET button nothing more happens. Under Windows the yellow LED blinks shortly additionally on pressing the button.
As I understood the Uno with ATmega16U2 does not require additional drivers but last two days I played with all available drivers installing and removing them and so far nothing helped...
I suspect there is something with USB 2.0/3.0 hubs and Arduino Uno but my knowledge is below that level... Any ideas?..
woodard:
Tools>Port> "Serial Ports" is greyed out. For example, on my Macbook the only option available (pre-checked) is /dev/cu.Bluetooth-Incoming-Port". In Windows, Tools> "Port" is greyed out, nothing selected or selectable at all.I have this same result with the UNO and the MEGA2560 R3. I have had similar results in Windows 10, Mac OS 10.12, and Ubuntu, with Arduino 1.8.0 and 1.8.2.
An image in Mac and in Windows is attached.
Any help is appreciated!
check System Information app on your mac to see what cables it supports. try that.
Thanks a lottt!!. My issue got resolved on installing this driver
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.
