I don't know what's going on with others. Just tried mine again (1.0.6 on Win7Pro), IDE had been open for a couple of days so I get a build folder disappeared error. Restarted the IDE, opened Blink and it downloaded fine again. My Sony Vaio with WinVista that I used for nearly 4 years (and still use occasionally because it has many sketches on it and sometimes I have eagle routing going on in one room while I code in another where the hardware is, but less and less as the keyboard is getting fiddly) still runs file also. I am stumped as to others have such difficulty. I let both computers do Windows updates automatically. Maybe that has something to do with it?
Same issue here. I tested 3 nanos so far on Win7 x64 and WinXP x86. Tried reinstalling FTDI drivers without success.
Even I am having the same issue on Windows7 (64-bit).Tried re-installing driver from http://www.ftdichip.com/Drivers/VCP.htm lot of times.Please suggest some way to resolve this issue.
Same problem here. :disappointed_relieved:
I got a new Nano module. Connected it, the driver auto-installed fine, uploaded the code, everything is OK.
One hour later I replug the board to USB and it is no longer recognized by Win7 64bit - no driver! I manually installed the driver, but it still doesn't work.
This Nano is a clone, it has "www.funduino.com" and "LISA 2011" written on the PCB.
I have found this so far... flip the board over.. near the usb connector there is a FTDI chip read the second line.. You will need a magnifying glass to read it. If it say 1408 It is same chip as mine that I am having trouble with as of Oct 1st. 2014 if it say 1436 It is the same chip as mine that still works, (I have 3 of these)
This info does not help fix the problem but maybe we can narrow it down to a set of H/W Then I am hopeful that some really smart person can fix up a driver.
My chip has a 1402 code.
Can you guys look at the USB device ID and tell me what it is? (right click on the device, Properties, Details, Hardware ID from the drop down list).
Mine is USB\VID_0403&PID_0000&REV_0600 and this PID is the source of the problem: the drivers only recognize PIDs 60xx, not 0000 !!
working one is FTDIBUS\COMPORT&VID_0403&PID_6001
failing one is (it has 2 lines) USB\VID_0403&PID_0000&REV_0600 USB\VID_0403&PID_0000
I confirm the same problem with FTDI 232RL since 1 October....I have problem with 90% ebay purchased FT232. I also have original Digikey chips that working perfect now. Seems like there was some global update from FTDI or Windows to block fakes....
Yep, should be PID_6001...
I have contacted FDTI support for this problem, I am waiting for their reply.
There was a recent FTDI windows driver update, although I can’t see anything that might cause devices to stop working.
FTDI - Other hardware - USB Serial Converter
Download size: 825 KB
You may need to restart your computer for this update to take effect.
Update type: Optional
FTDI Other hardware software update released in August, 2014
I believe this is FTDI version 2.12.00, release note here http://www.ftdichip.com/Drivers/CDM/CDM%202%2012%2000%20Release%20Info.rtf I guess if there was a change to nobble fakes they might not publish that info.
That update is pending in my Windows update…
Possibly due to recent news about USB hacking vulnerability they have been tightening up on USB drivers, or someone just goofed an update.
FDTI have a tool to edit the data in their devices called FT_PROG, it might be a way to recover faulty devices. It’s also a way to mess it up completely, but if it doesn’t work anyway maybe no loss. http://www.ftdichip.com/Support/Utilities.htm
As it turns out the problem is caused by counterfeit chips, I must delete the workaround procedure I have found, because altering device drivers is contrary to the FTDI license agreement.
If you have such a fake chip, please contact the seller for reimbursement.
Unfortunately FT_PROG cannot be used because the program does not see the problematic chip.
Just to be clear, the workaround I described above is to make the driver work with the defective chips, not only FT_PROG!
Vincent77 thank you very much! :) The workaround worked for me, I get my board operating again.
another question, do I need to modify all 60XX positions?
Thank you, not it clear.
Vincent get’s the glory. Thanks for finding the solution. I saw that the PID in the .inf file didn’t match that shown using USBView but I hadn’t gotten around to trying it. The remaining question in my mind is how did the PID get set to 0000. I looked at the .inf file in the Arduino-1.05r2 download that I originally used and which worked and the PID there is 6001, so at some point the PID in my Arduino Nano must have matched one of the 6000 series PIDS. Go figure.
Thanks Vincent. Your solution works great.
Mine has FTDIBUS\COMPORT&VID_0403&PID_6001
Is that programmable? I see a whole bunch of application notes http://www.ftdichip.com/Support/Documents/AppNotes.htm
And the FT_PROG Utility http://www.ftdichip.com/Support/Utilities.htm#FT_Prog
Oops - didn't see the 2nd page of comments before I posted.