mumblepins / arduino

Automatically exported from code.google.com/p/arduino
Other
0 stars 0 forks source link

Upload fails on some boards with "arduino" programmer type (but works with "stk500v1") #869

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
On some boards (maybe those with the FT232RL datecode 1138 (2011 week 38)), 
uploading seems to fail with the avrdude 5.10 in Arduino 1.0 using the 
"arduino" programmer type.  With the stk500v1 protocol (which doesn't do the 
auto reset in avrdude), the upload seems to work: 
http://arduino.cc/forum/index.php/topic,81330.15.html

I wonder if the problem is with the timing of the delay for the auto-reset in 
the arduino programmer type in the new avrdude.  Maybe this particular version 
of the FTDI hardware / drivers ignores pulses of less than a certain length of 
something similar.  

Original issue reported on code.google.com by dmel...@gmail.com on 29 Mar 2012 at 1:31

GoogleCodeExporter commented 9 years ago
I have the same problem with my ArduPilot that I use for my QuadCopter.  I can 
upload codes with 0022 without any hassles but I am not able to upload with 
0100.  I can upload new code using the Mission Planner and the serial monitor 
in Arduino works on 115200 but when the uploading starts my TX light flashes 3 
times and then goes dead...

Original comment by Kotze...@gmail.com on 30 Mar 2012 at 4:44

GoogleCodeExporter commented 9 years ago
What operating system are you using?  Does the upload work if you change 
"arduino" to "stk500v1" in the boards.txt file in Arduino 1.0?

Original comment by dmel...@gmail.com on 30 Mar 2012 at 1:43

GoogleCodeExporter commented 9 years ago
My default boards.txt file looks like the below:

mega2560.name=Arduino Mega 2560 or Mega ADK

mega2560.upload.protocol=stk500v2
mega2560.upload.maximum_size=258048
mega2560.upload.speed=115200

mega2560.bootloader.low_fuses=0xFF
mega2560.bootloader.high_fuses=0xD8
mega2560.bootloader.extended_fuses=0xFD
mega2560.bootloader.path=stk500v2
mega2560.bootloader.file=stk500boot_v2_mega2560.hex
mega2560.bootloader.unlock_bits=0x3F
mega2560.bootloader.lock_bits=0x0F

mega2560.build.mcu=atmega2560
mega2560.build.f_cpu=16000000L
mega2560.build.core=arduino
mega2560.build.variant=mega

I've tried to change "mega2560.upload.protocol=stk500v2" to 
"mega2560.upload.protocol=stk500v1" and to 
"mega2560.upload.protocol=arduino" but still the same problem.

Original comment by Kotze...@gmail.com on 30 Mar 2012 at 2:00

GoogleCodeExporter commented 9 years ago
And I am on Windows 7 32bit...

Original comment by Kotze...@gmail.com on 30 Mar 2012 at 2:02

GoogleCodeExporter commented 9 years ago
In issue #806 the idea of changing the protocal from "stk500v2" to "wiring" was 
suggested.  I tried it and it worked!!! :-)

Original comment by Kotze...@gmail.com on 31 Mar 2012 at 5:01

GoogleCodeExporter commented 9 years ago
Yeah, this issue doesn't apply to the Mega 2560 - that uses a different upload 
protocol and therefore different "programmer" options to avrdude.  

Original comment by dmel...@gmail.com on 31 Mar 2012 at 4:50