Re: [avrdude-dev] Fwd: avrdude.conf - ftdi-section

[Daniel Schulz]

Well Jason, a big thank you to you for your advice! It seems to be
working. I read out the fuse bytes,
But I think, to the description/manual should be added some short
sentences for bloody beginners like me.
Isn't it essential to mention that for this case the "-P" parameter
must not be set like for many other programmers and seen in tutorials?
This was confusing me.
And yes, it should be obvious, that in case of SPI the "baudrate"
isn't the baudrate of a standard sio. But unfortunately nowhere is
mentioned that you have to pay attention to it.

On the other side, the description is misleading in avrdude.conf in
the sector "ftdi":

#ISP-signals - lower ACBUS-Nibble (default)
  reset  = 4;
  sck    = 1;
  mosi   = 2;
  miso   = 3;

On the FT2232D it is not the ACBUS but the ADBUS and the pincount is
from 0-7 (pins 24 down to 16 and that could be followed on every
breakout board). I think it is better if this could be added to the
manual, because I was wasting days for finding a solution until I've
found this mailing list. And now it ends up with having 2 devices for
doing 1 and the same thing - programming an atmega (because in my
perplexity I've ordered yesterday a cheap avr isp programmer ;-)

Anyways, so keep on working - it is a big project and you did a good
job! Thank you again
Daniel

2011/11/3 Jason Hecker <address@hidden>:
> I think you are doing it wrong.  Try and copy or use an existing FTDI
> programmer definition in the config file and get AVRDUDE to access the
> FTDI part with the USB VID:PID, not via /dev/ttyUSB as SPI is not a
> serial/RS232 protocol.
>
> In the example off my page:
>
> $ ./avrdude -c um232h -p m1280 -v -b 3750000 -U
> flash:w:ATmegaBOOT_168_atmega1280.hex
>
> The "um232h" is the definition of the FTDI programmer in avrdude.conf
> and it uses the special MPSSE mode on the FTDI parts to drive the SPI
> port.  Part of this definition includes the pinout as well as what
> code in AVRDUDE to use (avrdtfi), what the VID:PID of the FTDI part
> is.  For a starters in your case try -b 1000000 to program at 1MHz.
> With the FTDI parts in MPSSE mode you aren't using traditional serial
> protocols.
>
> Jason
>
>
> On 3 November 2011 04:09, Daniel Schulz <address@hidden> wrote:
>> That was unfortunately not the only problem. As I wrote in my last
>> posting, the FTDI-module gets disconnected by the following simple
>> process:
>> avrdude -p m8 -P /dev/ttyUSB0 -c avrftdi  (or even by reading out the
>> fuses: avrdude -p m8 -P /dev/ttyUSB1 -c avrftdi -b 19200   -U
>> lfuse:r:-:i -vvv)
>> and I really don't know why?!
>> The disconnect happens between these 2 lines from avrdude: (as far as
>> I was able to observe it by tail -f)
>>
>>  Description     : FT2232D based generic programmer
>>
>>  avrdude info: Pin is zero val 0!
>>
>>
>> 2011/11/2 Joerg Wunsch <address@hidden>:
>>> As Daniel Schulz wrote:
>>>
>>>> My setup:
>>>> ADBUS0 : SCK
>>>> ADBUS1 : MOSI
>>>> ADBUS2 : MISO
>>>>
>>>> ADBUS4 : RESET
>>>>
>>>>
>>>> Is RESET correct on ADBUS4?
>>>
>>> I already replied that it must go to ADBUS[3], because /RESET is
>>> essentially the chip select signal when performing ISP programming.
>>>
>>> No idea whether this was the only problem or not.
>>>
>>> --
>>> cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL
>>>
>>> http://www.sax.de/~joerg/                        NIC: JW11-RIPE
>>> Never trust an operating system you don't have sources for. ;-)
>>>
>>> _______________________________________________
>>> avrdude-dev mailing list
>>> address@hidden
>>> https://lists.nongnu.org/mailman/listinfo/avrdude-dev
>>>
>>
>> _______________________________________________
>> avrdude-dev mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/avrdude-dev
>>
>