Re: [avrdude-dev] Fwd: FTDI flashing stops at different positions

[Hannes Weisbach]

>>> 
>> Since your issues seem to be timing related, I don't think anymore your 
>> problem relates to the infinite loop I was talking about.
> 
> Hm I've heard from another avrdude user, that some days ago avrdude
> starts making some problems. He is on avrasp, but it works not
> reliable for now. He is on linux too. Maybe there are issues on
> udev/usb or whatever?!
That is certainly possible, but since you said you measured something with an 
oscilloscope I would draw the conclusion that USB is working - otherwise the 
FTDI would not do anything. That reminds me to ask which FTDI chips exactly are 
you using? Are you using a self-build programmer or did you buy one?
I saw you used the 'avrftdi'-programmer. Did you made any adjustments in 
avrdude.conf and if so which ones?
> 
> 
>>> Ah, additionally I've tried to get a log, but there is only a
>>> FTDI LOG: 80 20 fb 82 00 00
>>> FTDI LOG: 80 60 fb 82 00 00
>>> repeatedly in the file. Is this right?!
>> No. there should be more. This is only the flashing of the programming led 
>> (for the standard avrftdi configuration).
> 
> Sounds strange because I used the standard procedure to redirect the
> output to a file by using a ">" - and on the file i only have the
> lines mentioned above. On the screen there is much more output, but
> this would not be redirected tothe file - dont ask why, I've no clue!!
That is because some output is printed to stderr and some on stdout. To get 
both in one file, first route stderr to stdout ("2>&1") and then stdout to a 
file (" > file", as you already did). See [1] for details.
> 
>>> My command line looked like this:
>>> avrdude -p m8 -c avrftdi -b 1000000 -U
>>> flash:w:/home/daniel/ng/quax/17a410_i2c_r08/hex/bl-17a_p40_m1.hex:a
>>> -vvvv >avrdude_quax.log
>> As I said, -b 1000000 is too fast. The additional output on the terminal 
>> slows the program down. Try -b 10000.
> 
> But if I use 100000 or less, nothing happens - the flashing process
> stops at 0%! I will try it on another computer.
> Maybe it is important for you: my Linux is a debian sid derivative:
> siduction, kernel 3.4-4.towo-siduction-amd64 x86_64 (64 bit, gcc:
> 4.7.0)
I can't tell if your problem is Linux-related, but I don't think so.
I guess I can tell more with a complete log.
Short of that, I can only advise you to
a) use a debugger like gdb to find out what exactly is happening and/or
b) use a scope to see what is the actual data transferred between the FTDI and 
the AVR (if any).

If you have a picture or screenshot from the scope I'll take that too and 
decode the data if you do not know how.

Best regards,
Hannes

[1] http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO-3.html