Trouble making FTDI drivers work (win 10 & atmega2560)

Development Tools IDE 1.x
1

Greetings!

New here on the board (no pun intended), and i'm looking for some troubleshooting advice installing the FTDI USB-com port drivers. This far i've:

  • successfully installed the CDM and ftd2xx drivers in windows
  • gone through the FTDI troubleshooting procedure, and also
  • checked the arduino troubleshooting guide.

Apologies if i've missed some crucial info somewhere.

My problem is that my device still won't be recognized by windows after connecting it to my computer. I've tried using several of the FTDI drivers from the manual install list, with no results and therefore the port menu option remains greyed out... Now i'm out of ideas for making uploading my sketches work.

My specs:
Win 10
Atmega2560 IC

Will post more specs if needed. Any advice is greatly appreciated!

2

Making your own board? I would cleanup whatever old drivers were installed and get the latest certified drivers from FTDI.

3

Thanks for your reply,

The hardware is a premanufactured ADDAC001 module, for the eurorack synth system:

http://vcc.addacsystem.com/index.php/intro/

After replying, uninstalling the drivers seem to have done the trick. Thanks for your quick feedback.

4

Aaand here we go again. Plugged in the unit and suddenly windows decided not to recognize the unit again. It worked yesterday... I am at loss for ideas.

5

Try using another USB cable.

Another thing to try is connecting through a USB hub with power adapter connected. This will ensure that 500mA is available for each USB port. Note that some PC and Notebooks have their USB ports limited to lower current levels (250mA or even 100mA), which could cause issues.

If the above fails, try another PC.

If this fails ... I would suspect a problem with your USB device.

6

In addition to dlloyd's great advice USB 3.0 has been seen to also cause issues that is often fixed by putting a POWERED USB 2.0 hub between the USB 3.0 port and the Arduino.

Try avoid using USB 3.0 cables also.

7

Thank you all for your input. It turns out that i used the USB 3.0 port, when the USB 2.0 port is the only one that works.