FTDI Bricked their clones again, Do a loopback test and see if there is any text returned. There are a few guides to unbrick the new method (Use an older driver, but update the date and version strings)
proto-pic:
FTDI Bricked their clones again, Do a loopback test and see if there is any text returned. There are a few guides to unbrick the new method (Use an older driver, but update the date and version strings)
So the origional FDTI cables have 'clone chips' in their own product and the original Arduino's have them to?
There's data coming from the boards but programming wont work.
This is the output during programming:
C:\Program Files (x86)\Arduino/hardware/tools/avr/bin/avrdude -CC:\Program Files (x86)\Arduino/hardware/tools/avr/etc/avrdude.conf -v -v -v -v -patmega328p -carduino -PCOM4 -b115200 -D -Uflash:w:C:\Users\HFA73~1.ARE\AppData\Local\Temp\build7561266059177628740.tmp/sketch_mar22a.cpp.hex:i
avrdude: Version 6.0.1, compiled on Apr 3 2014 at 23:12:16
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "C:\Program Files (x86)\Arduino/hardware/tools/avr/etc/avrdude.conf"
Using Port : COM4
Using Programmer : arduino
Overriding Baud Rate : 115200
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [04]
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x04
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [09]
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x09
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [00]
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x00
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [04]
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x04
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [09]
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x09
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [04]
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x04
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [09]
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x09
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [04]
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x04
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [01]
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x01
avrdude: Send: 0 [30] [20]
avrdude: Recv: . [11]
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x11
avrdude done. Thank you.
Which of course should have no effect on an "Uno" at all, since it doesn't use an FTDI chip.
What brand of "Uno" do you have, do you know? (Can you post a picture?)
Arduino IDE version 1.5.8.
Why that version? Did you successfully install the "drivers" as well?
There all original Italian UNO's and the one i build myself using the Atmel 328P component with Optiboot installed. They all worked before the reinstall.
After some hesitation i reprogrammed the self build UNO using the IDE and the Due placing a new bootloader inside the chip and voilĂ it worked again.
This one could be programmed again so i did the same with one UNO and that one worked again also.
I have no explanation on how this could be be-course one of the UNO's i havent used for some years.
For now the problem is solved.
The answer to the used version, at first i installed the latest one, but as in the old situation all worked with the 1.5.8. version i wnet back to the state i knew it worked.